[Bug 1774094] Re: [Patch Included] 3.26.3-0ubuntu4 .desktop extension is duplicated when renaming a .desktop file
The attachment ".desktop rename patch for Nautilus" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1774094 Title: [Patch Included] 3.26.3-0ubuntu4 .desktop extension is duplicated when renaming a .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774094/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759758] Re: gsd-locate-pointer crashed with signal 5 in _XEventsQueued()
[Expired for gnome-settings-daemon (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1759758 Title: gsd-locate-pointer crashed with signal 5 in _XEventsQueued() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759758/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727421] Re: Desktop focus border radius not matching overview panel border radius
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1727421 Title: Desktop focus border radius not matching overview panel border radius To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774081] Re: /etc/gdm3/Init/Default not evaluated
** Changed in: gdm Status: Unknown => Expired ** Changed in: gdm Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1774081 Title: /etc/gdm3/Init/Default not evaluated To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1774081/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774053] Re: Missing characters in gnome-shell after lock screen
** Changed in: gnome-shell Status: Unknown => Confirmed ** Changed in: gnome-shell Importance: Unknown => Medium -- 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/1774053 Title: Missing characters in gnome-shell after lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1774053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774094] [NEW] [Patch Included] 3.26.3-0ubuntu4 .desktop extension is duplicated when renaming a .desktop file
Public bug reported: When attempting to rename a .desktop file in Ubuntu 18.04, .desktop is automatically appended. This causes the .desktop extension to get duplicated, where renaming `app.desktop` to `app2.desktop` will actually rename it to `app2.desktop.desktop`. The included patch fixes the issue. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Patch added: ".desktop rename patch for Nautilus" https://bugs.launchpad.net/bugs/1774094/+attachment/5146234/+files/desktop-rename.patch -- 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/1774094 Title: [Patch Included] 3.26.3-0ubuntu4 .desktop extension is duplicated when renaming a .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774094/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774081] Re: /etc/gdm3/Init/Default not evaluated
Sounds like it should work. The docs say: "When managing a display, gdm3 attempts to execute /etc/gdm3/Init/display, or /etc/gdm3/Init/Default if that does not exist." ** Changed in: gdm3 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1774081 Title: /etc/gdm3/Init/Default not evaluated To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1774081/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774081] Re: /etc/gdm3/Init/Default not evaluated
The problem has already been reported here: https://gitlab.gnome.org/GNOME/gdm/issues/317 Please comment on that bug if you have more information. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed ** Description changed: + https://gitlab.gnome.org/GNOME/gdm/issues/317 + + --- + /etc/gdm3/Init/Default is not evaluated on my fresh install of Ubuntu 18.04 (minimal). I replaced this file by one with the following content to test it: #!/bin/sh touch /tmp/a touch /mnt/a After a reboot, these files are not available. When I use the same file for /etc/gdm3/PostLogin/Default, it works. ** Bug watch added: GNOME Bug Tracker #783497 https://bugzilla.gnome.org/show_bug.cgi?id=783497 ** Also affects: gdm via https://bugzilla.gnome.org/show_bug.cgi?id=783497 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1774081 Title: /etc/gdm3/Init/Default not evaluated To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1774081/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774053] Re: Missing characters in gnome-shell after lock screen
Also tracking in https://bugzilla.gnome.org/show_bug.cgi?id=728158 ** Summary changed: - Missing characters in and after lock screen + Missing characters in gnome-shell after lock screen ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Bug watch added: GNOME Bug Tracker #728158 https://bugzilla.gnome.org/show_bug.cgi?id=728158 ** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=728158 Importance: Unknown Status: Unknown ** Tags added: nvidia -- 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/1774053 Title: Missing characters in gnome-shell after lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1774053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774047] Re: gnome (or something) uses a lot of memory
*** This bug is a duplicate of bug 1672297 *** https://bugs.launchpad.net/bugs/1672297 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 1672297, 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 1672297 gnome-shell uses lots of memory, and grows over time -- 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/1774047 Title: gnome (or something) uses a lot of memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774047/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772365] Re: gnome-shell + chrome doing nothing consumes high CPU all the time
All, Can you please test to see if moving the Chrome window away from the launcher (on the left) reduces the CPU usage of gnome-shell? I know that having windows changing near the launcher is a problem. And I will get back to fixing that soon (bug 1743976). ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => 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/1772365 Title: gnome-shell + chrome doing nothing consumes high CPU all the time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772365] Re: gnome-shell + chrome doing nothing consumes high CPU all the time
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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1772365 Title: gnome-shell + chrome doing nothing consumes high CPU all the time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773528] Re: High CPU usage by gnome-shell when using Google Chrome
*** This bug is a duplicate of bug 1772365 *** https://bugs.launchpad.net/bugs/1772365 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 1772365, 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 1772365 gnome-shell + chrome doing nothing consumes high CPU all the time -- 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/1773528 Title: High CPU usage by gnome-shell when using Google Chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773959] Re: High CPU usage by gnome-shell even when idle
I agree the CPU usage is too high. Please: 1. Avoid using extensions if you can, or at least verify a bug exists when no extensions are loaded. 2. After unloading all extensions, let us know exactly which apps are running to trigger the problem. ** Tags added: performance -- 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/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773959] Re: High CPU usage by gnome-shell even when idle
What screen resolution are you using? You can just run 'xrandr' and send us the output. -- 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/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772365] Re: gnome-shell + chrome doing nothing consumes high CPU all the time
** Summary changed: - gnome-shell + chrome doing nothing consumes 60%+ CPU all the time + gnome-shell + chrome doing nothing consumes high CPU all the time -- 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/1772365 Title: gnome-shell + chrome doing nothing consumes high CPU all the time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773959] Re: High CPU usage by gnome-shell even when idle
Also, is the terminal window touching the launcher to the left? Is it maximized? Or does the problem persist when the terminal is a small window in the middle of the screen? ** Summary changed: - High CPU usage by gnome-shell even when idle + High CPU usage by gnome-shell when only running gnome-terminal ** 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/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770731] Re: [nvidia] multimonitor ghostly flickering display artifacts
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Description changed: + https://gitlab.gnome.org/GNOME/mutter/issues/175 + + --- + On Ubuntu 18.04, running nvidia-390 driver (on a GTX 1080), and gnome shell 3.28.1. I have a 3 monitor setup. When I open a terminal in the middle window and some other window, like nautilus on the left, and quickly drag the nautilus window to the right, covering the terminal, and back without releasing the mouse, a flickering ghost of the window remains on the terminal for about a minute or so. - --- + --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 GsettingsChanges: - b'org.gnome.shell' b'favorite-apps' redacted by apport - b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" - b'org.gnome.desktop.interface' b'clock-format' b"'12h'" + b'org.gnome.shell' b'favorite-apps' redacted by apport + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + b'org.gnome.desktop.interface' b'clock-format' b"'12h'" InstallationDate: Installed on 2018-05-10 (15 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter PackageArchitecture: amd64 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- 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/1770731 Title: [nvidia] multimonitor ghostly flickering display artifacts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1770731/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773955] Re: GDM very slow after resume from suspend
** Tags added: performance ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags added: resume -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1773955 Title: GDM very slow after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1773955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714459] Re: Shell font is blurry under Wayland (panels, menus and login screen too)
Actually it was fix released. Someone should tell Red Hat :) -- 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/1714459 Title: Shell font is blurry under Wayland (panels, menus and login screen too) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714459/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
** Changed in: gnome-menus (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 137527] Re: Unhelpful response when inserting encrypted DVD in default installation
Stop On Thu, May 24, 2018, 9:45 PM Bug Watch Updater <137...@bugs.launchpad.net> wrote: > ** Changed in: totem >Status: In Progress => Expired > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (219062). > https://bugs.launchpad.net/bugs/137527 > > Title: > Unhelpful response when inserting encrypted DVD in default > installation > > Status in Totem: > Expired > Status in totem package in Ubuntu: > Triaged > > Bug description: > Ubuntu 4.10, 5.04, 5.10, 6.06, 7.04, 7.10, 8.04, 8.10, 9.04, 9.10, > 10.04, 10.10, 11.04, 11.10, 12.04, 14.04 > > 1. Install Ubuntu. > 2. Insert a standard movie DVD. > > What happens: > * In Ubuntu 10.10 and earlier, "An error occurred" - "Could not read > from resource." > * In Ubuntu 11.10, "An error occurred" - "Could not read DVD. This may > be because the DVD is encrypted and a DVD decryption library is not > installed." > > Without libdvdcss2, Totem, VLC, and others are unable to play my > original DVD-s. I know it's illegal to ship Ubuntu with libdvdcss2, > but it could be in multiverse repos, and totem's plugin installer > could install it, OR add the medibuntu repo to the list (but leave > unchecked), then Totem's plugin installer should give a hint, to use > that repo's libdvdcss2 to play your DVDs. Newbies wont find out how to > solve this problem by theirself, go back to win, and then it will be > harder to solve the bug #1 :) > > Not to be confused with: > * bug 502426, where DVDs don't play when libdvdcss is installed > * bug 745515, "An error occured location not found" while trying to play > a DVD > * bug 747433, "Totem cannot play this type of media DVD because it does > not have the appropriate plugins to be able to read from this disc" > > To manage notifications about this bug go to: > https://bugs.launchpad.net/totem/+bug/137527/+subscriptions > -- 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/137527 Title: Unhelpful response when inserting encrypted DVD in default installation To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/137527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770971] Re: Update gnome-system-monitor to 3.28.2
This bug was fixed in the package gnome-system-monitor - 3.28.2-0ubuntu1 --- gnome-system-monitor (3.28.2-0ubuntu1) bionic; urgency=medium * New upstream release (LP: #1770971) -- Jeremy Bicha Sun, 13 May 2018 11:20:50 -0400 ** Changed in: gnome-system-monitor (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1770971 Title: Update gnome-system-monitor to 3.28.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1770971/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770971] Update Released
The verification of the Stable Release Update for gnome-system-monitor has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1770971 Title: Update gnome-system-monitor to 3.28.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1770971/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774081] [NEW] /etc/gdm3/Init/Default not evaluated
Public bug reported: /etc/gdm3/Init/Default is not evaluated on my fresh install of Ubuntu 18.04 (minimal). I replaced this file by one with the following content to test it: #!/bin/sh touch /tmp/a touch /mnt/a After a reboot, these files are not available. When I use the same file for /etc/gdm3/PostLogin/Default, it works. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1774081 Title: /etc/gdm3/Init/Default not evaluated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774081/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Hi I tested gdm3 - 3.28.2-0ubuntu1.1 on Ubuntu 18.04 LTS. I ran the following tests: a) Boot Ubuntu 18.04 LTS, attempt login with correct password - pass. b) Log out and then log back in with correct password - pass. c) Log out and then enter the wrong password a few times then enter the correct password press enter to login - pass. d) Reboot Ubuntu 18.04 LTS, enter the wrong password a few times then enter the correct password, press enter to login - pass. e) Login then allow the screen to blank, attempt unlock with correct password - pass. f) Login then allow the screen to blank, attempt unlock with wrong password then enter correct password and press enter - pass. g) Click on the lock button, attempt unlock with incorrect password a few times then enter correct password and press enter - pass. h) Click on the lock button, attempt unlock with correct password - pass. Fix therefore works now and appears to have no issues so far. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773597] Re: USB flash drive won't mount
Booted a tower machine (it had been powered off) running Ubuntu 17.10 (Artful). Ran SW updates. Rebooted. Inserted encrypted USB flash drive. Was asked several times for the password. Gave it - multiple times. Finally I was able to open drive. That lasted about 10 minutes when all the files in the window disappeared (folder is empty message). Pulled the flash drive and reinserted it. This time it worked. Request for password showed up in its black window. I entered the password (twice - I might have screwed it up). Was able to access files with no problems. -- 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/1773597 Title: USB flash drive won't mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1773597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Ah, thanks for saying that since I was testing in my other machine and wasn't unable to reproduce this anymore... My second user has no password set, but there's no much difference in terms of the issue. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769981] Re: Temporary screen freeze when coming back from screen standby
I just had a series of freezes, and managed to ssh and watch logs in the meantime, the only messages that I that might be relevant are the following (repeated many times): May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/1769981 Title: Temporary screen freeze when coming back from screen standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769981/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Sorry I commented too quickly below after first tryout. After couple of boots and tryouts it did finally succeed after longer wait time and now after testing some 5 times I have managed to log with different user after loging out. it is slow, but it will get there. So certainly I see good progress, looks better now. ti 29. toukok. 2018 klo 22.47 Heikki Moisander (moisan...@gmail.com) kirjoitti: > heikki@ThinkPad-X301:~$ apt-cache policy gdm3 > gdm3: > Asennettu: 3.28.2-0ubuntu1.1 > Ehdokas: 3.28.2-0ubuntu1.1 > Versiotaulukko: > *** 3.28.2-0ubuntu1.1 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main > amd64 Packages > 100 /var/lib/dpkg/status > 3.28.0-0ubuntu1 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages > > I seem to have fixed version now. It does not work for me any different > from the previous version. Nothing happens while trying to change user or > log in with different user account. After trying I can get back to login > screen but then only way to login is boot. > > ti 29. toukok. 2018 klo 17.31 Łukasz Zemczak (1766...@bugs.launchpad.net) > kirjoitti: > >> Hello Chris, or anyone else affected, >> >> Accepted gdm3 into bionic-proposed. The package will build now and be >> available at https://launchpad.net/ubuntu/+source/gdm3/3.28.2-0ubuntu1.1 >> in a few hours, and then in the -proposed repository. >> >> Please help us by testing this new package. See >> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how >> to enable and use -proposed.Your feedback will aid us getting this >> update out to other Ubuntu users. >> >> If this package fixes the bug for you, please add a comment to this bug, >> mentioning the version of the package you tested and change the tag from >> verification-needed-bionic to verification-done-bionic. If it does not >> fix the bug for you, please add a comment stating that, and change the >> tag to verification-failed-bionic. In either case, without details of >> your testing we will not be able to proceed. >> >> Further information regarding the verification process can be found at >> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in >> advance! >> >> ** Changed in: gdm3 (Ubuntu Bionic) >>Status: In Progress => Fix Committed >> >> ** Tags removed: verification-failed-bionic >> ** Tags added: verification-needed-bionic >> >> -- >> You received this bug notification because you are subscribed to a >> duplicate bug report (1768619). >> https://bugs.launchpad.net/bugs/1766137 >> >> Title: >> [regression] Password accepted but login fails (blank purple screen >> and mouse pointer only) >> >> Status in gdm: >> Fix Released >> Status in Release Notes for Ubuntu: >> Fix Released >> Status in gdm3 package in Ubuntu: >> In Progress >> Status in gnome-shell package in Ubuntu: >> Invalid >> Status in gdm3 source package in Bionic: >> Fix Committed >> Status in gnome-shell source package in Bionic: >> Invalid >> >> Bug description: >> [ Description ] >> >> Due to a refcounting bug, a GDBusConnection was getting disposed when >> it was still required. The symptom of this was that you couldn't log >> in on the second attempt if you'd got your password wrong on the first >> attempt. All you'd see is a blank purple screen and mouse pointer >> only. >> >> [ Test case ] >> >> 1. Boot to GDM >> 2. Click your username >> 3. Type the wrong password a couple of times, pressing enter after each >> time >> 4. Type the right password >> >> If the bug is happening, after 4. the system hangs at a blank screen >> with the mouse cursor. If you then switch to a VT or otherwise connect >> to the machine, you can examine the journal and you'll see a >> G_IS_DBUS_CONNECTION failure. >> >> [ Fix ] >> >> Marco and I worked upstream on this fix. We found out that there was a >> problem like this- >> >> The GdmClient has a shared GDBusConnection for its operations. The >> first time someone calls for it, it is created and stored in the >> object's private structure. Subsequent calls return *a new reference* >> to this same object. It turned out that the asynchronous method to get >> the connection was accidentally unreferencing its object before giving >> it to the caller if it was returning an already-existing connection. >> >> For this to work properly, we need to nullify the pointer we stored >> when the connection goes away, so we know when to make a new one. >> There were some cases where we didn't add the weak references required >> to do that. Those are also fixed. >> >> [ Regression potential ] >> >> Now we share connections more than we did before. We also more >> carefully track when to clear our object. If we got this wrong, we >> might end up leaking the connection or dropping it in even more cases. >> >> [ Original report ] >> >> WORKAROUND: After typing an incorrect password, click
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
heikki@ThinkPad-X301:~$ apt-cache policy gdm3 gdm3: Asennettu: 3.28.2-0ubuntu1.1 Ehdokas: 3.28.2-0ubuntu1.1 Versiotaulukko: *** 3.28.2-0ubuntu1.1 500 500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages I seem to have fixed version now. It does not work for me any different from the previous version. Nothing happens while trying to change user or log in with different user account. After trying I can get back to login screen but then only way to login is boot. ti 29. toukok. 2018 klo 17.31 Łukasz Zemczak (1766...@bugs.launchpad.net) kirjoitti: > Hello Chris, or anyone else affected, > > Accepted gdm3 into bionic-proposed. The package will build now and be > available at https://launchpad.net/ubuntu/+source/gdm3/3.28.2-0ubuntu1.1 > in a few hours, and then in the -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how > to enable and use -proposed.Your feedback will aid us getting this > update out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested and change the tag from > verification-needed-bionic to verification-done-bionic. If it does not > fix the bug for you, please add a comment stating that, and change the > tag to verification-failed-bionic. In either case, without details of > your testing we will not be able to proceed. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance! > > ** Changed in: gdm3 (Ubuntu Bionic) >Status: In Progress => Fix Committed > > ** Tags removed: verification-failed-bionic > ** Tags added: verification-needed-bionic > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1768619). > https://bugs.launchpad.net/bugs/1766137 > > Title: > [regression] Password accepted but login fails (blank purple screen > and mouse pointer only) > > Status in gdm: > Fix Released > Status in Release Notes for Ubuntu: > Fix Released > Status in gdm3 package in Ubuntu: > In Progress > Status in gnome-shell package in Ubuntu: > Invalid > Status in gdm3 source package in Bionic: > Fix Committed > Status in gnome-shell source package in Bionic: > Invalid > > Bug description: > [ Description ] > > Due to a refcounting bug, a GDBusConnection was getting disposed when > it was still required. The symptom of this was that you couldn't log > in on the second attempt if you'd got your password wrong on the first > attempt. All you'd see is a blank purple screen and mouse pointer > only. > > [ Test case ] > > 1. Boot to GDM > 2. Click your username > 3. Type the wrong password a couple of times, pressing enter after each > time > 4. Type the right password > > If the bug is happening, after 4. the system hangs at a blank screen > with the mouse cursor. If you then switch to a VT or otherwise connect > to the machine, you can examine the journal and you'll see a > G_IS_DBUS_CONNECTION failure. > > [ Fix ] > > Marco and I worked upstream on this fix. We found out that there was a > problem like this- > > The GdmClient has a shared GDBusConnection for its operations. The > first time someone calls for it, it is created and stored in the > object's private structure. Subsequent calls return *a new reference* > to this same object. It turned out that the asynchronous method to get > the connection was accidentally unreferencing its object before giving > it to the caller if it was returning an already-existing connection. > > For this to work properly, we need to nullify the pointer we stored > when the connection goes away, so we know when to make a new one. > There were some cases where we didn't add the weak references required > to do that. Those are also fixed. > > [ Regression potential ] > > Now we share connections more than we did before. We also more > carefully track when to clear our object. If we got this wrong, we > might end up leaking the connection or dropping it in even more cases. > > [ Original report ] > > WORKAROUND: After typing an incorrect password, click Cancel, then > click your name, then enter your password again. > > --- > > Trying to log into my session (Gnome, Xorg), if I enter the wrong > password before entering it correctly, the session doesn't load and I > get a purple screen, a mouse cursor, and an invisible but clickable > menu in the top right. If I enter it correctly the first time, there > is no problem. > > I've replicated this from a fresh boot, after logging out and after > 'sudo service gdm restart' from the Ctrl-Alt-F4 console. > > This is a
[Bug 1774053] [NEW] Missing characters in and after lock screen
Public bug reported: I locked my screen, came back from lunch, and found that about half the characters in the lock screen were missing. After I logged back in, half the characters in the desktop were missing (https://drive.google.com/file/d/1mIDF4_jY0PIFOT53FoOOVoTY1BWeaNfy/view?usp=sharing). Chrome and Nautilus are not missing any characters, just the system UI. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 12:25:58 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']" b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2018-04-10 (48 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot of the start menu" https://bugs.launchpad.net/bugs/1774053/+attachment/5146135/+files/Screenshot%20from%202018-05-29%2012-20-44.png -- 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/1774053 Title: Missing characters in and after lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774047] [NEW] gnome (or something) uses a lot of memory
Public bug reported: After I log in (ubuntu session) the systen(?), shell(?) uses a lot of memory. When the computer has 2GB RAM, 1.2GB is used. When the computer has 4GB RAM, 1.7GB is used. When the computer has 8GB RAM, 2.2GB is used. I tried it out in virtualbox with a newly installed system. I changed the memory size and started ubuntu. I think a new, clean system should use the same amount of memory independently of the RAM size. Not to mention that the system is unusable, because RAM quickly fills up (memory leak?) and become laggy. Unity in 16.04 uses approx. 800kB memory. Why does gnome-shell need so much memory? I think it should be fixed, because 18.04 is an LTS release! I would like to work with it.Description:Ubuntu 18.04 LTS Release:18.04 gnome-shell: Telepítve: 3.28.1-0ubuntu2 Jelölt:3.28.1-0ubuntu2 Verziótáblázat: *** 3.28.1-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 20:21:39 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-20 (221 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-15 (44 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1774047 Title: gnome (or something) uses a lot of memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774047/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714459] Re: Shell font is blurry under Wayland (panels, menus and login screen too)
** Changed in: mutter (Fedora) Status: Confirmed => Won't Fix -- 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/1714459 Title: Shell font is blurry under Wayland (panels, menus and login screen too) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714459/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()
Launchpad has imported 7 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1239129. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2015-07-03T16:05:10+00:00 Ian wrote: 1. Install xterm 2. Write a file at /etc/X11/xorg.conf.d/20-bit16.conf containing: Section "Screen" Identifier "Screen0" DefaultDepth 16 EndSection 3. Log in with GNOME desktop 4. Go to Activities, type 'xt' and see the xterm icon appear 5. Click on the xterm icon 6. Boom This was originally encountered by installing tigervnc-server-module which comes with a config file specifying DefaultDepth 16 but clearly the vnc server itself is not required. gnome-shell outputs the following message before crashing: mutter:ERROR:x11/iconcache.c:301:standard_pict_format_for_depth: code should not be reached Analysis of this function shows that it doesn't believe that 16-bit pixmaps exist. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1766938/comments/0 On 2016-07-19T15:11:16+00:00 Fedora wrote: Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1766938/comments/1 On 2016-07-19T16:16:09+00:00 Ian wrote: Still crashes on Fedora 24 with the same error message and traceback. $ rpm -q mutter mutter-3.20.3-1.fc24.x86_64 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1766938/comments/2 On 2017-07-25T18:58:48+00:00 Fedora wrote: This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1766938/comments/3 On 2017-08-03T17:28:59+00:00 Ian wrote: Still crashes mutter-3.24.4-1.fc26.x86_64 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1766938/comments/4 On 2018-05-03T08:49:05+00:00 Fedora wrote: This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible
[Bug 1714459]
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- 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/1714459 Title: Shell font is blurry under Wayland (panels, menus and login screen too) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714459/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714459]
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- 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/1714459 Title: Shell font is blurry under Wayland (panels, menus and login screen too) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714459/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774039] [NEW] package gdm3 3.28.2-0ubuntu1.1 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10
Public bug reported: Could not install. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Tue May 29 23:33:46 2018 ErrorMessage: installed gdm3 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-05-05 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gdm3 Title: package gdm3 3.28.2-0ubuntu1.1 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-from-proposed third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1774039 Title: package gdm3 3.28.2-0ubuntu1.1 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774039/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774007] [NEW] /usr/bin/gnome-software:11:magazine_chain_pop_head:magazine_chain_prepare_fields:magazine_cache_push_magazine:private_thread_memory_cleanup:__nptl_deallocate_tsd
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.28.1-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/80db1ab810dc5348d8a286fdf246c5c7c0dc79dd 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-software (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic xenial yakkety zesty -- 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/1774007 Title: /usr/bin/gnome- software:11:magazine_chain_pop_head:magazine_chain_prepare_fields:magazine_cache_push_magazine:private_thread_memory_cleanup:__nptl_deallocate_tsd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1774007/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773597] Re: USB flash drive won't mount
** Tags added: bionic -- 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/1773597 Title: USB flash drive won't mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1773597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1700649] Re: MTP device fails to mount
usbfs: process (mtp.so) did not claim interface 0 before use I get this error message on ubuntu 18.4. I believe there are two different problems. First problem could be that InternalSD is readonly to the MTP process on the phone (see last line in log), why? Read-only requests worked. The other problem are the failed read attempts with varying errno, see below. Log from phone is: 05-28 15:32:02.505 D/MtpService(3263): Adding MTP storage 0x10001 at /storage/emulated/0 05-28 15:32:02.505 D/MtpService(3263): Adding MTP storage 0xa5bf0001 at /storage/7743-14FD 05-28 15:32:02.505 D/MtpService(3263): starting MTP server in MTP mode with storage /storage/emulated/0 disabled 05-28 15:32:13.094 E/MtpServer(3263): request read returned -1, errno: 5 05-28 15:32:13.551 D/MtpService(3263): starting MTP server in MTP mode with storage /storage/emulated/0 05-28 15:32:13.558 D/MtpService(3263): Adding MTP storage 0xa5bf0001 at /storage/7743-14FD 05-28 15:32:13.558 D/MtpService(3263): Adding MTP storage 0x10001 at /storage/emulated/0 05-28 15:32:26.711 E/MtpServer(3263): request read returned -1, errno: 5 [ above repeated several times. ] 05-28 15:35:30.269 D/MtpService(3263): Adding MTP storage 0xa5bf0001 at /storage/7743-14FD 05-28 15:35:30.270 D/MtpService(3263): Adding MTP storage 0x10001 at /storage/emulated/0 05-28 15:35:53.914 E/MtpServer(3263): deletePath stat failed for /storage/emulated/0/DCIM/Camera/IMG_20180519_202734.jpg: No such file or directory [repeated for each file] -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1700649 Title: MTP device fails to mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1700649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1700649] Re: MTP device fails to mount
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1700649 Title: MTP device fails to mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1700649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770725] Re: [i915 SNB] Totem window is all black in Wayland sessions
** Package changed: gstreamer1.0 (Ubuntu) => gstreamer-vaapi (Ubuntu) -- 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/1770725 Title: [i915 SNB] Totem window is all black in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Hello Chris, or anyone else affected, Accepted gdm3 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdm3/3.28.2-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gdm3 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-failed-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773968] Re: [SRU] 3.28.2
Hello Iain, or anyone else affected, Accepted gdm3 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdm3/3.28.2-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gdm3 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1773968 Title: [SRU] 3.28.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1773968/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered
rls-bb-notfixing means that this doesn't need to be tracked as a team release-critical bug; anyone else should feel free to work on the remaining items ** Tags added: rls-bb-notfixing -- 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/1761554 Title: [bionic] Extended characters in GNOME screen keyboard don't get entered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - gnome-screensaver & gnome-shell fail to start?
** Tags removed: rls-bb-incoming ** Tags added: rls-bb-notfixing -- 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/1765724 Title: Xenial -> Bionic - System fails to boot after upgrade - gnome- screensaver & gnome-shell fail to start? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1765724/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773561] Re: Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017: 17784-17789).
** Summary changed:
- Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017-*).
+ Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017:
17784-17789).
** Description changed:
Hello.
GIMP package ('Universe/Security' section), available in "Xenial"/16.04
LTS Release, contains unfixed security issues and is vulnerable to, for
example, heap-buffer over-read, out of bounds read and stack-based
- buffer over-read etc. The whole this is pretty strange, because Ubuntu
+ buffer over-read etc. The whole thing is pretty strange, because Ubuntu
Releases released before and after "Xenial", contains updated GIMP
- version!
+ package!
Anyway, it looks this way: in "Trusty" the available version is:
'2.8.10-0ubuntu1.2' (please see [1]). "Bionic" has '2.8.20-1.1' version
(please see [2]). Both Releases contains fixes for mentioned security
issues: CVE-2017-* etc. However, GIMP version in "Xenial" is
'2.8.16-1ubuntu1.1' and does not contain any security updates from 2017.
(The last one is from Thu, 30 Jun 2016.; please see [3]).
Security updates with fixes for mentioned CVE's (please compare changes
in 1. and 2. with 3.) were released on Thu., 18 Jan 2018 - for "Trusty"
and Tue., 26 Dec 2017 - for "Bionic". In "Xenial", the last security
update is from Thu., 30 Jun 2016 (fix for CVE-2016-4994) and there is no
further updates!
- Here is a CVE list, which are not fixed in "Xenial", but in "Trusty" and
- "Bionic" only:
+ Here is a CVE list of security issues not fixed in "Xenial", but in
+ "Trusty" and "Bionic" etc.:
- 1/ CVE-2017-17786: Out of bounds read
- 2/ CVE-2017-17789: Heap-based buffer overflow in read_channel_data
- 3/ CVE-2017-17784: Heap-buffer over-read in load_image file-gbr.c
+ 1/ CVE-2017-17784: Heap-buffer over-read in load_image file-gbr.c
+ 2/ CVE-2017-17785: Heap-based buffer overflow in fli_read_brun function
+ 3/ CVE-2017-17786: Out of bounds read
4/ CVE-2017-17787: Heap-based buffer over-read in read_creator_block
- 5/ CVE-2017-17785: Heap-based buffer overflow in fli_read_brun function
- 6/ CVE-2017-17788: Stack-based buffer over-read in xcf_load_stream
+ 5/ CVE-2017-17788: Stack-based buffer over-read in xcf_load_stream
+ 6/ CVE-2017-17789: Heap-based buffer overflow in read_channel_data
- I wanted to send an email an email to Mr Marc Deslauriers, because he
- made the last security update for GIMP in "Xenial" (fix for
- CVE-2016-4994). But I decided to report a bug on Launchpad. I hope that
- it's an acceptable way. If not, I'm sorry.
+ And the most important thing: if User had installed GIMP package in
+ "Xenial" Release, he is affected - since one year, at least - because of
+ a vulnerable version. Security issues, mentioned above, are from 2017.
+ So, maybe it's a good opportunity to update GIMP to v2.10.2 version,
+ released on 20., May 2018? (Version 2.8.X is very outdated).
- ✗✗✗ And the most important thing: if an User had installed GIMP package
- in "Xenial" Release, he is affected because he is using a vulnerable
- version since one year! Security issues, mentioned above, are from 2017.
- So, maybe it's a good opportunity to update GIMP to v2.10.2 version,
- released on 20., May 2018? At least in non-LTS Releases. Of course I'm
- not talking about "Cosmic" here. (Version 2.8.X is very outdated).
+ I wanted to send an email to Mr Marc Deslauriers, because he made the
+ last security update for GIMP in "Xenial" (fix for CVE-2016-4994). But I
+ decided to report a bug on Launchpad. I hope that it's an acceptable
+ way. If not, I'm sorry.
By the way: similar problems with unfixed security issues, can be found
e.g. in Audacious and Parole packages. But that's a different story,
completely different story...
Thanks, best regards.
__
1.
http://changelogs.ubuntu.com/changelogs/pool/main/g/gimp/gimp_2.8.10-0ubuntu1.2/changelog
2.
http://changelogs.ubuntu.com/changelogs/pool/universe/g/gimp/gimp_2.8.20-2/changelog
3.
http://changelogs.ubuntu.com/changelogs/pool/universe/g/gimp/gimp_2.8.16-1ubuntu1.1/changelog
--
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/1773561
Title:
Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017:
17784-17789).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1773561/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770725] Re: [i915 SNB] Totem window is all black in Wayland sessions
Hello Daniel van Vugt, If I remove "gstreamer1.0-vaapi" you can see the video in Wayland with Totem. Regards, -- Cristian Aravena Romero (caravena) -- 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/1770725 Title: [i915 SNB] Totem window is all black in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773984] Re: package fonts-smc 1:7.0 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-smc in Ubuntu. https://bugs.launchpad.net/bugs/1773984 Title: package fonts-smc 1:7.0 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-smc/+bug/1773984/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773984] [NEW] package fonts-smc 1:7.0 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: It happened when I was trying to execute the update for some apps. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fonts-smc 1:7.0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Tue May 29 08:37:28 2018 DuplicateSignature: package:fonts-smc:1:7.0 Unpacking linux-firmware (1.173.1) over (1.173) ... dpkg: error processing package fonts-smc (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-01-26 (123 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: fonts-smc Title: package fonts-smc 1:7.0 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fonts-smc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-smc in Ubuntu. https://bugs.launchpad.net/bugs/1773984 Title: package fonts-smc 1:7.0 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-smc/+bug/1773984/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770731] Re: [nvidia] multimonitor ghostly flickering display artifacts
Gnome bug link: https://gitlab.gnome.org/GNOME/mutter/issues/175 -- 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/1770731 Title: [nvidia] multimonitor ghostly flickering display artifacts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1770731/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767229] Re: Gnome Shell Freezes after Login
*** This bug is a duplicate of bug 1766137 *** https://bugs.launchpad.net/bugs/1766137 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1767229 Title: Gnome Shell Freezes after Login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767229/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773968] [NEW] [SRU] 3.28.2
Public bug reported: [ Description ] The second stable release in the 3.28 series. [ QA ] Log in, log out, log in again. Get your password wrong. Try different sessions. Lock the screen, try to swtich to a different user. We have a GNOME SRU exception allowing us to assume that upstream's fixes are good, and they don't require explicit QA. Please test gdm as per the above smoke testing. (https://wiki.ubuntu.com/StableReleaseUpdates/GNOME) (In this case there's bug #1766137 which will get explicitly tested.) [ Regression potential ] A bad GDM update will, at worst, mean that people can't log in graphically. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: gdm3 (Ubuntu Bionic) Importance: Undecided Assignee: Iain Lane (laney) Status: In Progress ** Also affects: gdm3 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Status: New => Fix Released ** Changed in: gdm3 (Ubuntu Bionic) Status: New => In Progress ** Changed in: gdm3 (Ubuntu Bionic) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1773968 Title: [SRU] 3.28.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1773968/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773959] [NEW] High CPU usage by gnome-shell even when idle
Public bug reported: Even when doing nothing but displaying a terminal screen with top running gnome-shell uses 10% of a CPU. That seems excessive. I disabled all extensions to try and make the test fair. Enabling the system monitor extension increases the load to 13-14%. It seems that the gnome- shell screen painting is highly CPU consuming even if screen updates are infrequent (1 a second for all these cases). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:38:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1773959 Title: High CPU usage by gnome-shell even when idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771880] Re: Seahorse unable to import certificates in Ubuntu 18.04
I also see the greyed out Import button using Seahorse 3.20.0-5 on Ubuntu MATE 18.04 LTS. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import certificates in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1771880/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773955] [NEW] GDM very slow after resume from suspend
Public bug reported: When resuming from suspend GDM is very unresponsive. It takes several seconds to show the login screen after starting to type the password and it's common to need to press enter several times before it will recognize and unlock. This is a big regression on this machine compared to 16.04 where the login interface was much more usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:17:56 2018 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1773955 Title: GDM very slow after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1773955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703479] Re: Ubuntu 17.04 & Kubuntu 17.04 LiveCD writes to bios/hardware clock; thereby messing up my installed Windows 10 Pro laptop time
On those live CDs there should be no NTP daemon running anyway. And even if so we switched which defaults to non-utc for the following reason: rtconutc chronyd assumes by default that the RTC keeps local time (including any daylight saving changes). This is convenient on PCs running Linux which are dual-booted with Windows. If you keep the RTC on local time and your computer is off when daylight saving (summer time) starts or ends, the computer’s system time will be one hour in error when you next boot and start chronyd. An alternative is for the RTC to keep Universal Coordinated Time (UTC). This does not suffer from the 1 hour problem when daylight saving starts or ends. If the rtconutc directive appears, it means the RTC is required to keep UTC. The directive takes no arguments. It is equivalent to specifying the -u switch to the Linux hwclock program. Note that this setting is overridden when the hwclockfile directive is specified. If one wants to change that he can set rtconutc in /etc/chrony/chrony.conf. But as I said this should only apply once you install it, which by default I thought is not the case. Instead you likely just have systemd-timesyncd running. Which I think defaults to systemctl status hwclock ● hwclock.service Loaded: masked (/dev/null; bad) Active: inactive (dead) And Local time: Di 2018-05-29 09:43:08 CEST Universal time: Di 2018-05-29 07:43:08 UTC RTC time: Di 2018-05-29 07:43:08 Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes systemd-timesyncd.service active: yes RTC in local TZ: no So as I read it this already does UTC, here from the man page: set-local-rtc [BOOL] Takes a boolean argument. If "0", the system is configured to maintain the RTC in universal time. If "1", it will maintain the RTC in local time instead. Note that maintaining the RTC in the local timezone is not fully supported and will create various problems with time zone changes and daylight saving adjustments. If at all possible, keep the RTC in UTC mode. Note that invoking this will also synchronize the RTC from the system clock, unless --adjust-system-clock is passed (see above). This command will change the 3rd line of /etc/adjtime, as documented in hwclock(8). I'll re-target this bug at systemd (for systemd-timesyncd) but set it to incomplete until we find out which part of the service exactly sets non-UTC time as I'd think this would be the default. You might start by looking at timedatectl on the live system. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: ntp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1703479 Title: Ubuntu 17.04 & Kubuntu 17.04 LiveCD writes to bios/hardware clock; thereby messing up my installed Windows 10 Pro laptop time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1703479/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719105] Re: Ctrl+Alt+T does not open a terminal anymore
*** This bug is a duplicate of bug 1705348 *** https://bugs.launchpad.net/bugs/1705348 ** This bug is no longer a duplicate of bug 1707828 Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later ** This bug has been marked a duplicate of bug 1705348 Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1719105 Title: Ctrl+Alt+T does not open a terminal anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1719105/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705348] Re: Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later
** Summary changed: - Takes long time to open the terminal with Ctrl + Alt + T + Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later -- 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/1705348 Title: Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1705348/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705348] Re: Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- 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/1705348 Title: Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1705348/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705348] Re: Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later
See bug 1707828 for more info. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- 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/1705348 Title: Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1705348/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1707828] Re: Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later
*** This bug is a duplicate of bug 1705348 *** https://bugs.launchpad.net/bugs/1705348 ** This bug has been marked a duplicate of bug 1705348 Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1707828 Title: Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1707828/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
