[Bug 1482961] Re: Messed up icon sizes for .desktop files
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1482961 Title: Messed up icon sizes for .desktop files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1482961/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1518740] Re: Filesystem type not shown (NTFS or FAT32)
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1518740 Title: Filesystem type not shown (NTFS or FAT32) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1518740/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1776125] Re: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1770563 *** https://bugs.launchpad.net/bugs/1770563 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1770563, so 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. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1770563 package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned -- 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/1776125 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1776125/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1776125] [NEW] package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1770563 *** https://bugs.launchpad.net/bugs/1770563 Public bug reported: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Jun 10 19:45:46 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-06-13 (362 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 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: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-06-11 (0 days ago) ** Affects: gnome-menus (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 gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1776125 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1776125/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 508618] Re: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp
** Tags added: cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to emacs25 in Ubuntu. https://bugs.launchpad.net/bugs/508618 Title: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/508618/+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
This bug was fixed in the package im-config - 0.34-1ubuntu3 --- im-config (0.34-1ubuntu3) cosmic; urgency=medium * debian/patches/dont-set-GTK_IM_MODULE-on-wayland.patch: - Dropped. The 0.34-1ubuntu2 changes reversed due to regression, e.g. LibreOffice crash when using IBus (LP: #1761554). -- Gunnar Hjalmarsson Sun, 10 Jun 2018 21:55:00 +0200 ** Changed in: im-config (Ubuntu) Status: Fix Committed => Fix Released -- 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 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered
** Changed in: im-config (Ubuntu) Status: In Progress => Fix Committed -- 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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Release package is already unstable and isn't able to it's job. I don't see any reasons not to deploy this excepting bureaucracy. -- 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 1773561] Re: Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017: 17784-17789).
** Information type changed from Public to Public Security -- 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
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
3.28.2-0ubuntu1.1 did work fine for login logout to another user (critical in our environment). It has been few days since it was supposed to be coming and I figured that it is safe now to start installing 18.04, but fresh install 18.04 and I am still getting 3.28.0-Oubuntu1 - will not work. su 10. kesäk. 2018 klo 17.25 OliFre (1766...@bugs.launchpad.net) kirjoitti: > @Ads2 Thanks for the link. Sadly, gdm3 is neither in the > autopkgtest-list, nor update-excuses, nor update-list, so it seems > things are stuck at an earlier stage and the documentation does not > clarify where to find out at which point help could be needed. > > My intention was not to spam this report, but to find out where things are > stuck (it's not obvious) and how to give support. > It's also not about my personal (im)patience, but we have >200 desktops > and >2000 Ubuntu containers and have had to stop the migration after the > first 10 desktops due to this bug (and three(!) other ones which all have > been known *before* release and should either have been release blockers or > been mentioned as "Known Issues" with the new LTS to prevent people from > hopping onto the new supposedly-stable). For the other critical issues, QA > apparently was even worse, since Debian and in one case also RHEL have > already released fixes months or even a year ago, and there has been no > reaction on Launchpad whatsoever yet. Since we are also still affected by > critical bugs in 16.04 which have been open since 16.04's release and could > only be solved by PPA (broken OpenAFS), this makes me wonder whether Ubuntu > still is a valid choice for institutional use, but this discussion > certainly goes off topic here. > > Just let us know if there is something people could help with (testing > etc.). As it stands, the status is completely unclear apart from the > statement _to be patient_ - without indicating what the actual point is > where things are stuck. > > -- > 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: > Fix Released > 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 fresh
[Bug 1710858] Re: totem crashed with SIGSEGV in in __GI_____strtoul_l_internal() from __GI___strtoul_l() from g_ascii_strtoull() from _cogl_gpu_info_parse_version_string() from check_mesa_driver_packa
** Changed in: totem (Debian) Status: Confirmed => Fix Released -- 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/1710858 Title: totem crashed with SIGSEGV in in __GI_strtoul_l_internal() from __GI___strtoul_l() from g_ascii_strtoull() from _cogl_gpu_info_parse_version_string() from check_mesa_driver_package() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1710858/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1616148] Re: package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 101
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pygobject (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1616148 Title: package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 101 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1616148/+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)
@Ads2 Thanks for the link. Sadly, gdm3 is neither in the autopkgtest-list, nor update-excuses, nor update-list, so it seems things are stuck at an earlier stage and the documentation does not clarify where to find out at which point help could be needed. My intention was not to spam this report, but to find out where things are stuck (it's not obvious) and how to give support. It's also not about my personal (im)patience, but we have >200 desktops and >2000 Ubuntu containers and have had to stop the migration after the first 10 desktops due to this bug (and three(!) other ones which all have been known *before* release and should either have been release blockers or been mentioned as "Known Issues" with the new LTS to prevent people from hopping onto the new supposedly-stable). For the other critical issues, QA apparently was even worse, since Debian and in one case also RHEL have already released fixes months or even a year ago, and there has been no reaction on Launchpad whatsoever yet. Since we are also still affected by critical bugs in 16.04 which have been open since 16.04's release and could only be solved by PPA (broken OpenAFS), this makes me wonder whether Ubuntu still is a valid choice for institutional use, but this discussion certainly goes off topic here. Just let us know if there is something people could help with (testing etc.). As it stands, the status is completely unclear apart from the statement _to be patient_ - without indicating what the actual point is where things are stuck. -- 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 748027] Hi dear!
*** This bug is a duplicate of bug 477565 *** https://bugs.launchpad.net/bugs/477565 spank me northwoodscatholicradio.org/wp/wp-content/plugins/slider-carousel/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-utils in Ubuntu. https://bugs.launchpad.net/bugs/748027 Title: gnome-system-log: cannot read when scrolled-back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-utils/+bug/748027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1776078] [NEW] Wrong display of calendar entries with different timezone for start and stop date
Public bug reported: Timezone of stop date is ignored for ics files and caldac calendars. The attached example has a during of 7 hours. It gets imported correctly with evolution. However, it looks like an event with a duration of one hour in the calendar. Thunderbird displays the event correctly (as my iPhone). Import creates error message if stop time in local timezone is 'before' start time in specified timezone (see second example). Event is not displayed in the regular calender view but can be seen in the list view. When I open the entry, I can only choose a timezone for the entire event, i.e., not for start and stop date separately. Expected behavior: - correct display of length of event in the calendar view - separate entry fields for timezones for start and stop date (cf. Thunderbird - Lightning) Example 1: BEGIN:VCALENDAR PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN VERSION:2.0 BEGIN:VEVENT CREATED:20180610T131500Z LAST-MODIFIED:20180610T131418Z DTSTAMP:20180610T131418Z UID:20180610_JK_Test1 SUMMARY:New Test Appointment DTSTART;TZID=Europe/Berlin:20180610T13 DTEND;TZID=America/New_York:20180610T14 END:VEVENT END:VCALENDAR Example 2: BEGIN:VCALENDAR PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN VERSION:2.0 BEGIN:VEVENT CREATED:20180610T131500Z LAST-MODIFIED:20180610T131418Z DTSTAMP:20180610T131418Z UID:20180610_JK_Test2 SUMMARY:Short Test Appointment DTSTART;TZID=Europe/Berlin:20180610T13 DTEND;TZID=America/New_York:20180610T11 END:VEVENT END:VCALENDAR ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution 3.28.1-2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 15:41:39 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-04-05 (65 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Test Appointment.ics" https://bugs.launchpad.net/bugs/1776078/+attachment/5150903/+files/Test%20Appointment.ics -- 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/1776078 Title: Wrong display of calendar entries with different timezone for start and stop date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1776078/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1776013] Re: systemd-networkd: DHCP lease lost (Ubuntu 18.04)
Yes, the critical connection is the option to use in this case. You may also check the leases themselves in /run/systemd/netif/leases and check if the T1/T2/Lifetime are sensible, with each subsequent one higher than the prior. And if not, contact your ISP support to correct those. ** Changed in: systemd (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/1776013 Title: systemd-networkd: DHCP lease lost (Ubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1776013/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1776069] [NEW] "Don't know how to handle 'file:///home//Downloads/.flatpakref'"
Public bug reported: After installing Flatpak and the plugin for GNOME Software, Flatpaks downloaded from the Flatpak website (flathub.org/apps) are not able to be opened in the GNOME Software Center, with the program giving me the following error: "Don't know how to handle 'file:///home//Downloads/.flatpakref'." ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4 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.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 07:44:30 2018 InstallationDate: Installed on 2018-06-09 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) - >>> IDENTICAL BUG IN GNOME'S GITLAB: >>> https://gitlab.gnome.org/GNOME/gnome-software/issues/400/ <<< ** Affects: gnome-software Importance: Undecided Status: Confirmed ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug apps bionic ext extension flathub flatpak ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed ** Summary changed: - "Don't know how to handle 'file:///home//Downloads/.flatpakref' + "Don't know how to handle 'file:///home//Downloads/.flatpakref'" ** Description changed: After installing Flatpak and the plugin for GNOME Software, Flatpaks downloaded from the Flatpak website (flathub.org/apps) are not able to be opened in the GNOME Software Center, with the program giving me the following error: - "Don't know how to handle 'file:///home//Downloads/.flatpakref' + "Don't know how to handle 'file:///home//Downloads/.flatpakref'." ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4 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.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 07:44:30 2018 InstallationDate: Installed on 2018-06-09 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InstalledPlugins: - gnome-software-plugin-flatpak 3.28.1-0ubuntu4 - gnome-software-plugin-limba N/A - gnome-software-plugin-snap3.28.1-0ubuntu4 + gnome-software-plugin-flatpak 3.28.1-0ubuntu4 + gnome-software-plugin-limba N/A + gnome-software-plugin-snap3.28.1-0ubuntu4 ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: + IDENTICAL BUG IN GNOME'S GITLAB: https://gitlab.gnome.org/GNOME/gnome- + software/issues/400 + After installing Flatpak and the plugin for GNOME Software, Flatpaks downloaded from the Flatpak website (flathub.org/apps) are not able to be opened in the GNOME Software Center, with the program giving me the following error: "Don't know how to handle 'file:///home//Downloads/.flatpakref'." ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4 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.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 07:44:30 2018 InstallationDate: Installed on 2018-06-09 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - IDENTICAL BUG IN GNOME'S GITLAB: https://gitlab.gnome.org/GNOME/gnome- - software/issues/400 - After installing Flatpak and the plugin for GNOME Software, Flatpaks downloaded from the Flatpak website (flathub.org/apps) are not able to be opened in the GNOME Software Center, with the program giving me the following error: "Don't know how to handle 'file:///home//Downloads/.flatpakref'." ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4 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.2 Architecture: amd64 CurrentD
[Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt (if starting with Shift key). Usually works on the second attempt
I am experiencing the same issue as Vadim Peretokin above. I would agree that it appears to be a separate issue from the one discussed here -- it seems to have nothing to do with miscapitalization of the password (as revealed by "Show Text"). I have rarely experienced the issue at the first login screen but quite often at the lock screen. The only solution I have found is to reboot the machine (sometimes multiple times). I would prefer not to clutter up this discussion with an unrelated bug and can post a separate report but wanted see first if there was consensus that Vadim's and my issue sounds unrelated to the bug in this report. -- 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/1765261 Title: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt (if starting with Shift key). Usually works on the second attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765261/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt (if starting with Shift key). Usually works on the second attempt
I should have said that I am running Ubuntu 18.04 on a Dell XPS-13 9350, in case that is helpful. -- 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/1765261 Title: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt (if starting with Shift key). Usually works on the second attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765261/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1437502] Re: nautilus lacking 'new document' in context menu on GNOME
*** This bug is a duplicate of bug 1632027 *** https://bugs.launchpad.net/bugs/1632027 The workaround as suggested by Anders Hall is not very satisfactory because the first thing that you want to do after creating a new document is change the name. Previously, after creating the document you were immediately in a text field changing the name. Using the workaround, you have to select the document and select that you are changing the name before entering the name. It is pointless extra work. -- 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/1437502 Title: nautilus lacking 'new document' in context menu on GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1437502/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1632027] Re: New Document feature missing from Nautilus 3.20+
The workaround as suggested by Steve G and others is not very satisfactory because the first thing that you want to do after creating a new document is change the name. Previously, after creating the document you were immediately in a text field so that you could change the name. Using the workaround, you have to select the document and select that you are changing the name before entering the name. It is pointless extra work. -- 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/1632027 Title: New Document feature missing from Nautilus 3.20+ To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1632027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1776058] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1776058/+attachment/5150810/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1776058/+attachment/5150812/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1776058/+attachment/5150816/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1776058/+attachment/5150817/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1776058/+attachment/5150818/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1776058/+attachment/5150819/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1776058/+attachment/5150820/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1776058 Title: gnome-shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1776058/+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)
The conditions for the package to move to release are here: https://wiki.ubuntu.com/ProposedMigration#Migrating_packages_from_- proposed_to_release It's possible that the update breaks something in release, though I'm not sure what. It's also possible that we _just need to be more patient_, it's only been a few days since it was put in proposed. I don't see how spamming this bug is going to help the situation. -- 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
