[Bug 1764643] Re: Logout after console use freezes GUI
** Changed in: gdm3 (Ubuntu) Status: Incomplete => Fix Released -- 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/1764643 Title: Logout after console use freezes GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1764643/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764643] Re: Logout after console use freezes GUI
I'm sorry, but I no longer have the crash-report. I performed a clean install of Ubuntu (now 18.04) and the bug is gone. Next to the release difference (17.10 to 18.04), I did not install the nVidia proprietary driver. For me, this problem's solved. -- 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/1764643 Title: Logout after console use freezes GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1764643/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770731] Re: [nvidia] multimonitor display artifacts
Please also run this command and send us the output: lspci -k ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1770731 Title: [nvidia] multimonitor 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 1771161] Re: system hangs after too fast typing password
Also, after you reboot are there any files left in /var/crash ? If so then please run: ubuntu-bug /var/crash/YOURFILE.crash and let us know the result. -- 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/1771161 Title: system hangs after too fast typing password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1771161/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771161] Re: system hangs after too fast typing password
OK, thanks. I wonder if there is some VT switching going on there that fast typing is racing against. Does hitting Ctrl+Alt+F1 before typing the password help? Or Ctrl+Alt+F2? ** Tags added: unlock ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** 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 gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1771161 Title: system hangs after too fast typing password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1771161/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771161] Re: system hangs after too fast typing password
Ok, it's like You start ubuntu or want it back to work after suspend and there is an annoying a little bit moment before login window to appear...it's often like a black screen covers already that login window and something is alike still 'loading' but You can login anyway (start typing to quicken the process) as I did it in former versions of ubuntu. The thing is that when You start typing password to early like without waiting till this black screen disappears so to see the login window, the system hangs like it's impossible to login/type: cannot write anything in login password or the 'dots' mimicking password when You normally type it starts to run like automat (like You could push and hold some typing button endlessly) and You can't stop this process. The only way is to reboot ubuntu via hard reset. -- 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/1771161 Title: system hangs after too fast typing password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1771161/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770725] Re: You can not see the image of the movie
Please also tell us which movie player you are using. -- 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: You can not see the image of the movie 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 1771466] Re: Super+D wrongly leaves windows minimized if a new window appears while in "hiding" state
Please report this behavioural issue to the Gnome developers here: https://gitlab.gnome.org/GNOME/gnome-shell/issues And then let us know the URL of the new bug created there. -- 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/1771466 Title: Super+D wrongly leaves windows minimized if a new window appears while in "hiding" state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1771466/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771419] Re: System restarts after locking screen
Also, the 'hidpi-daemon' that crashed is not part of Ubuntu, it seems..? ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- 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/1771419 Title: System restarts after locking screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1771419/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745440] Re: "Apply" button is missing from Displays
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1745440 Title: "Apply" button is missing from Displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771419] Re: System restarts after locking screen
Your crash file shows:
Traceback:
Traceback (most recent call last):
File "/usr/lib/hidpi-daemon/hidpi-notification", line 45, in
notification_closed
obj = bus.get('com.system76.hidpi')
File "/usr/lib/python3/dist-packages/pydbus/proxy.py", line 47, in get
0, timeout_to_glib(timeout), None)
Please let us know if you find any other crash files in /var/crash are
report them only by running:
ubuntu-bug /var/crash/YOURFILE.crash
and do not attach crash files to bugs.
--
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/1771419
Title:
System restarts after locking screen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1771419/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771434] Re: Log Out/login does not recognize new supplementary group; Hangs after repeated Log Out/login cycles
You seem to be reporting two separate bugs. Please reword this one so as to move the other into a new bug report. ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- 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/1771434 Title: Log Out/login does not recognize new supplementary group; Hangs after repeated Log Out/login cycles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1771434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771269] Re: Password is not accepted on the first attempt. Must always authenticate twice.
*** This bug is a duplicate of bug 1765261 *** https://bugs.launchpad.net/bugs/1765261 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 1765261, 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 1765261 [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt -- 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/1771269 Title: Password is not accepted on the first attempt. Must always authenticate twice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1771269/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771161] Re: system hangs after too fast typing password
Can you please rephrase that? It's hard to understand the exact problem you are experiencing. ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- 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/1771161 Title: system hangs after too fast typing password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1771161/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771273] Re: Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your bug report is missing crash details. In order to debug a crash we will need a crash report. To create one, please follow these steps: 1. If you are not running a future development release of Ubuntu then apply the workaround from bug 994921. 2. If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport. 3. If the crash is in Xorg then uncomment this option from /etc/gdm3/custom.conf: # Additionally lets the X server dump core if it crashes #Enable=true 4. Reboot. 5. Reproduce the crash. 6. Look in /var/crash for crash files and when found, run: ubuntu-bug /var/crash/YOURFILE.crash 7. Add a comment here telling us the ID of the new bug that was created in step 6. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments, and doing so is also a security risk for yourself. ** 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/1771273 Title: Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1771273/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771308] Re: Adding the user to a new group doesn't take effect on logout and back in
As far back as I remember this has been the case... I think it's an OS feature that the currently running process does not inherit the new group list from /etc/group. It's only when the process starts that the group list is read. I'm not sure this is a bug, but it's really about the state of the process. So it's a kernel issue if at all. ** Package changed: gdm3 (Ubuntu) => linux (Ubuntu) -- 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/1771308 Title: Adding the user to a new group doesn't take effect on logout and back in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771308/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770731] Re: multimonitor display artifacts
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1770731 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: bionic multi-monitor nvidia ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags removed: multi-monitor ** Tags added: multimonitor ** Summary changed: - multimonitor display artifacts + [nvidia] multimonitor display artifacts -- 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 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 1770883] Re: Shift key does not work for first character of password
*** This bug is a duplicate of bug 1765261 *** https://bugs.launchpad.net/bugs/1765261 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 1765261, 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 1765261 [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt -- 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/1770883 Title: Shift key does not work for first character of password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1770883/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770725] Re: You can not see the image of the movie
Please run this command and send us the output: lspci -k ** No longer affects: wayland (Ubuntu) ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Incomplete ** Also affects: totem (Ubuntu) Importance: Undecided Status: New ** Changed in: totem (Ubuntu) Status: New => Incomplete -- 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: You can not see the image of the movie 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 1770238] Re: [nvidia] Logging in results in a black screen for many minutes after which the login screen reappears and I am able to login fine.
*** This bug is a duplicate of bug 1543192 *** https://bugs.launchpad.net/bugs/1543192 Thanks for the links. Note that each of those links themselves contains links to the main problem reports at the bottom of the page. So you are experiencing bug 1771485, bug 1543192, bug 1771486 and bug 1771484 at least. As we know those bugs are often about login failures and black screen problems I think it is more useful to continue with those specific bugs instead of this one. Especially bug 1543192, which other Nvidia users are reporting. P.S. Some duplicate bug links don't work because the main bug is marked as Private. Just let us know which ones and we can make the public... ** This bug has been marked a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ["no screens found"] -- 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/1770238 Title: [nvidia] Logging in results in a black screen for many minutes after which the login screen reappears and I am able to login fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770238/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770721] Re: Installed the discord snap and gnome shell crashed
I can't see anything familiar about this crash yet, so please forgive me and try the *new* standard response :) Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your bug report is missing crash details. In order to debug a crash we will need a crash report. To create one, please follow these steps: 1. If you are not running a future development release of Ubuntu then apply the workaround from bug 994921. 2. If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport. 3. If the crash is in Xorg then uncomment this option from /etc/gdm3/custom.conf: # Additionally lets the X server dump core if it crashes #Enable=true 4. Reboot. 5. Reproduce the crash. 6. Look in /var/crash for crash files and when found, run: ubuntu-bug /var/crash/YOURFILE.crash 7. Add a comment here telling us the ID of the new bug that was created in step 6. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments, and doing so is also a security risk for yourself. ** 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/1770721 Title: Installed the discord snap and gnome shell crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1770721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770509] Re: gui crashes on login
*** This bug is a duplicate of bug 1766137 *** https://bugs.launchpad.net/bugs/1766137 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 1766137, 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 1766137 [regression] Password accepted but login fails (blank purple screen and mouse pointer only) -- 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/1770509 Title: gui crashes on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770509/+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
That's OK. We can probably ignore most Xwayland crashes anyway. They are mostly just Xwayland dying because gnome-shell crashed... Do you get any other crash files in /var/crash? ** 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/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
[Bug 1771486] [NEW] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create()
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 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: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- 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/1771486 Title: systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771486/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771485] [NEW] systemd-logind crashed with SIGABRT in log_assert_failed_realm() from close_nointr() from session_device_free() from session_release_controller() from session_drop_controller()
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/c0d063b28aafc2663824a7f8f5b86fa757b0c467 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: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic -- 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/1771485 Title: systemd-logind crashed with SIGABRT in log_assert_failed_realm() from close_nointr() from session_device_free() from session_release_controller() from session_drop_controller() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769695] Re: Freeze of Surface for 2 Minutes
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/1769695 Title: Freeze of Surface for 2 Minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769695/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759836] Re: systemd-udevd consumes 100% of CPU
** Changed in: bluez (Ubuntu) Status: Incomplete => 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/1759836 Title: systemd-udevd consumes 100% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764643] Re: Logout after console use freezes GUI
> I now have a crash report of this call to killall. Should I report it, and include its number here, as I did before? Yes please. ** Tags added: artful ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Incomplete -- 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/1764643 Title: Logout after console use freezes GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1764643/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1740522] Re: GLib: g_variant_new_string: assertion 'string != NULL' failed
If this bug is a problem for you then please ask the gdm developers to prioritize it here: https://bugzilla.gnome.org/show_bug.cgi?id=792236 -- 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/1740522 Title: GLib: g_variant_new_string: assertion 'string != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1740522/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726688] Re: totem media player in the Ubuntu dock right click menu does not work, rewind does not work, nor full screen works
** Tags added: bionic cosmic ** Changed in: totem (Ubuntu) Importance: Undecided => Low -- 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/1726688 Title: totem media player in the Ubuntu dock right click menu does not work, rewind does not work, nor full screen works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1726688/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1600606] Re: Totem is missing the playlist. Please reintroduce it.
I think using a fork of anything is likely to create more problems in the long term than it solves. Note that the totem developers do not monitor this conversation. Please report the issue to the totem developers here: https://bugzilla.gnome.org/enter_bug.cgi?product=totem -- 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/1600606 Title: Totem is missing the playlist. Please reintroduce it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1600606/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715602] Re: ubiquity-dm / Install Ubuntu - Power button does nothing
** Tags added: 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/1715602 Title: ubiquity-dm / Install Ubuntu - Power button does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1715602/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1750780] Re: Race with local file systems can make open-vm-tools fail to start
This bug was fixed in the package open-vm-tools - 2:10.2.0-3~ubuntu0.17.10.1 --- open-vm-tools (2:10.2.0-3~ubuntu0.17.10.1) artful; urgency=medium * backport Bionic open-vm-tools to Artful (LP: #1741390) - d/control: B-D for dh-autoreconf and dh-systemd - d/rules: re-add autoreconf and systemd - d/control: B-D to debhelper version of xenial supporting compat 10 - d/compat: compat level 10 is latest xenial supported level - d/rules: go back from override_dh_installsystemd to override_dh_systemd_enable and override_dh_systemd_start as needed on xenials debhelper version. - d/rules: drop --no-restart-after-upgrade which only exists in debhelper 10, the version 9 behavior defaults to what we need. - debian/rules: dh_systemd_start in xenial has issues with the escaping of the run-vmblock\\x2dfuse.mount job, so drop this call - debian/open-vm-tools-desktop.postinst: add a fixed version of what dh_systemd_start would have added - d/open-vm-tools-desktop.prerm, d/open-vm-tools-desktop.postrm: add what dh_systemd_start would have added (as-is since those sections worked) - d/control: update maintainers * d/open-vm-tools.service: Add After=local-fs.target dependency ensuring filesystems are ready to fix a race on startup (LP: #1750780) open-vm-tools (2:10.2.0-3ubuntu3) bionic; urgency=medium * Disable PrivateTmp for the open-vm-tools.service as it triggers issues when triggering processes that need tmp through VMOMI API (LP: #1758428) open-vm-tools (2:10.2.0-3ubuntu2) bionic; urgency=medium * Revert change in d/open-vm-tools.service that added After=local-fs.target. It turned out that the systemd in bionic already implicitly fixes this issue (the change is still needed for backports) (LP: 1750780) open-vm-tools (2:10.2.0-3ubuntu1) bionic; urgency=medium * d/open-vm-tools.service: Add After=local-fs.target dependency ensuring filesystems are ready to fix a race on startup (LP: #1750780) open-vm-tools (2:10.2.0-3) unstable; urgency=medium * [47e50a1] Fix debhelper dep for backports * [34538a5] Make tools.conf useful. Thanks to Dariusz Gadomski (Closes: #889884) open-vm-tools (2:10.2.0-2) unstable; urgency=medium * [249d54c] Fix wayland segfault. Adding a patch from Fedora to fix a wayland/gnome related segfault. Thanks to Oliver Kurth (Closes: #887755) open-vm-tools (2:10.2.0-1) unstable; urgency=medium * [f0bf956] Add .travis.yml which was removed by gbp. * [892e2f6] Build with gtk3. * [03a655b] Check if debhelper handles \ in systemd units. Thanks to Oliver Kurth (Closes: #886191) * [5bf9301] Drop -dkms package. Thanks to Christian Ehrhardt (Closes: #884656) * [236cdba] Update upstream source from tag 'upstream/10.2.0' Update to upstream version '10.2.0' with Debian dir d5190e486b6beb65ee7ed31c0c23a789b8f60cab (Closes: #884496) * [692beff] snapshot changelog. * [45aa743] Add .travis.yml which was removed by gbp. * [aabeded] Fix dpkg --compare-versions call * [0697425] Better debhelper version parsing. * [390ec09] fix even more makefile bugs. * [6e5fa38] Refreshing patches. Dropping kernel-module related patches. * [cbfec05] Drop dh_autoreconf, not needed anymore. * [d5fef50] autotools-dev is done by dh now. * [b66ab14] use dh_installsystemd open-vm-tools (2:10.1.15-1) unstable; urgency=medium * [78a17f1] Remove fixed CXX std setting. * [f96f479] Updated version 10.1.15 from 'upstream/10.1.15' with Debian dir c44394c71e055f4cfd3a15ee578fc9895d64ebb1 * [682790b] Refreshing patches. -- Christian Ehrhardt Thu, 15 Feb 2018 09:36:20 +0100 ** Changed in: open-vm-tools (Ubuntu Artful) Status: Fix Committed => Fix Released -- 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/1750780 Title: Race with local file systems can make open-vm-tools fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750780/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1750780] Re: Race with local file systems can make open-vm-tools fail to start
This bug was fixed in the package open-vm-tools - 2:10.2.0-3~ubuntu0.16.04.1 --- open-vm-tools (2:10.2.0-3~ubuntu0.16.04.1) xenial; urgency=medium * backport Bionic open-vm-tools to Xenial (LP: #1741390) - d/control: B-D for dh-autoreconf and dh-systemd - d/rules: re-add autoreconf and systemd - d/control: B-D to debhelper version of xenial supporting compat 10 - d/compat: compat level 10 is latest xenial supported level - d/rules: go back from override_dh_installsystemd to override_dh_systemd_enable and override_dh_systemd_start as needed on xenials debhelper version. - d/rules: drop --no-restart-after-upgrade which only exists in debhelper 10, the version 9 behavior defaults to what we need. - debian/rules: dh_systemd_start in xenial has issues with the escaping of the run-vmblock\\x2dfuse.mount job, so drop this call - debian/open-vm-tools-desktop.postinst: add a fixed version of what dh_systemd_start would have added - d/open-vm-tools-desktop.prerm, d/open-vm-tools-desktop.postrm: add what dh_systemd_start would have added (as-is since those sections worked) - d/control: update maintainers * d/open-vm-tools.service: Add After=local-fs.target dependency ensuring filesystems are ready to fix a race on startup (LP: #1750780) open-vm-tools (2:10.2.0-3ubuntu3) bionic; urgency=medium * Disable PrivateTmp for the open-vm-tools.service as it triggers issues when triggering processes that need tmp through VMOMI API (LP: #1758428) open-vm-tools (2:10.2.0-3ubuntu2) bionic; urgency=medium * Revert change in d/open-vm-tools.service that added After=local-fs.target. It turned out that the systemd in bionic already implicitly fixes this issue (the change is still needed for backports) (LP: 1750780) open-vm-tools (2:10.2.0-3ubuntu1) bionic; urgency=medium * d/open-vm-tools.service: Add After=local-fs.target dependency ensuring filesystems are ready to fix a race on startup (LP: #1750780) open-vm-tools (2:10.2.0-3) unstable; urgency=medium * [47e50a1] Fix debhelper dep for backports * [34538a5] Make tools.conf useful. Thanks to Dariusz Gadomski (Closes: #889884) open-vm-tools (2:10.2.0-2) unstable; urgency=medium * [249d54c] Fix wayland segfault. Adding a patch from Fedora to fix a wayland/gnome related segfault. Thanks to Oliver Kurth (Closes: #887755) open-vm-tools (2:10.2.0-1) unstable; urgency=medium * [f0bf956] Add .travis.yml which was removed by gbp. * [892e2f6] Build with gtk3. * [03a655b] Check if debhelper handles \ in systemd units. Thanks to Oliver Kurth (Closes: #886191) * [5bf9301] Drop -dkms package. Thanks to Christian Ehrhardt (Closes: #884656) * [236cdba] Update upstream source from tag 'upstream/10.2.0' Update to upstream version '10.2.0' with Debian dir d5190e486b6beb65ee7ed31c0c23a789b8f60cab (Closes: #884496) * [692beff] snapshot changelog. * [45aa743] Add .travis.yml which was removed by gbp. * [aabeded] Fix dpkg --compare-versions call * [0697425] Better debhelper version parsing. * [390ec09] fix even more makefile bugs. * [6e5fa38] Refreshing patches. Dropping kernel-module related patches. * [cbfec05] Drop dh_autoreconf, not needed anymore. * [d5fef50] autotools-dev is done by dh now. * [b66ab14] use dh_installsystemd open-vm-tools (2:10.1.15-1) unstable; urgency=medium * [78a17f1] Remove fixed CXX std setting. * [f96f479] Updated version 10.1.15 from 'upstream/10.1.15' with Debian dir c44394c71e055f4cfd3a15ee578fc9895d64ebb1 * [682790b] Refreshing patches. open-vm-tools (2:10.1.10-3) unstable; urgency=medium * [00bc9bb] Build with CXXFLAGS=-std=c++14. Thanks to Rene Engelhard and Oliver Kurth (Closes: #876121) * [6b61376] Re-add .travis.yml. Seems it went missing with the last merge. * [bf07ae8] Work around dh_systemd escaping bugs again. Seems the unit escaping changed with a new dh version. Work around the known and reported fails again. Thanks to Christian Ehrhardt (Closes: #875657) open-vm-tools (2:10.1.10-2) unstable; urgency=medium [ Shota Aratono ] * [5ab87bd] Fix scsi timeout setting error on debian stretch * [c0847eb] Fix attempting change setting to unintentional target [ Raphaël Hertzog ] * [dc2e27f] Add patch to support resolution switching with KMS. This is needed for proper support of Wayland sessions. (Closes: #872779) open-vm-tools (2:10.1.10-1) unstable; urgency=medium * Drop the extra part of the version string. Easier to handle in the short variant. * [6be6a49] Updating watch file. Use tags from github. * [8c25235] Updated version 10.1.10 from 'upstream/10.1.10' with Debian dir 3dddea7985f21457b294b5f554d5ecdf32aabfff * [195cead] Refreshing patches. Removing cve-2015-5191.patch as it is part of the upstream release. * [e6b3fd5] Build using libssl-dev and libxmlsec1-dev. (Closes: #859416) ope
[Bug 1734887] Re: No caps lock indicator on login screen
Same thing is happening on 18.04 -- 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/1734887 Title: No caps lock indicator on login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1734887/+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)
** Changed in: gdm Status: Incomplete => In Progress -- 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 1771466] [NEW] Super+D wrongly leaves windows minimized if a new window appears while in "hiding" state
Public bug reported: Toggling Super+D hides or un-hides all windows so you can access icons on the desktop. But this breaks if a new window appears while the windows are hidden: They become PERMANENTLY hidden, i.e. Super+D does not restore them. They seem to be "minimized" -- you have to individually un-minimize each window to get your session back. This is very annoying, and is common: The only reason for using Super+D is to see something on the desktop; probably you then need to do something with it, i.e. click it. If that action opens a new window, which is almost certain, you're hosed. STEPS TO REPRODUCE: 1. Open a bunch of windows and artfully arrange them. 2. Type Super+D (they all become hidden) 3. Double-click the "Trash" desktop icon and wait for a file browser to open. RESULTS: Once the file-viewer opens, Super+D will not restore the previously-hidden windows. Instead, it seems to forget about them and instead hide the new window (and un-hide it if pressed a second time --before yet another window is opened, of course). EXPECTED RESULTS: The state should be well-defined: Either normal or windows-hidden. Once in the windows-hidden state, Super-D should un-hide the hidden windows e ven if new windows have been created in the interim. SUGGESTED FIX: 1. (preferred): On the first Super+D, hide all windows and remember their IDs. On the next Super+D, un-hide just those windows, if they still exist, and do nothing at all with any other windows which might be present (i.e. new ones). Then return to the initial state, where Super+D hides all visible windows. 2. (if the above is too hard to implement): If a new window appears while in the "hiding" state, make the new window immediately become hidden also; only on the second Super+D would the new window become visible along with the old ones. 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 15 16:40:22 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['keepaw...@jepfa.de', 'rece...@leonardo.bartoli.gmail.com', 'drive-m...@gnome-shell-extensions.gcampax.github.com', 'sound-output-device-choo...@kgshank.net', 'suspend-button@laserb', 'systemmoni...@gnome-shell-extensions.gcampax.github.com', 'workspaces-to-d...@passingthru67.gmail.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'" InstallationDate: Installed on 2018-04-05 (40 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** 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/1771466 Title: Super+D wrongly leaves windows minimized if a new window appears while in "hiding" state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1771466/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771454] [NEW] package udev 229-4ubuntu21.2 failed to install/upgrade: package udev is not ready for configuration cannot configure (current status 'half-installed')
Public bug reported: im new to this .i just keep getting a notification for this issue ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu21.2 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-lowlatency 4.13.16 Uname: Linux 4.13.0-41-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CustomUdevRuleFiles: 70-snap.vlc.rules 70-snap.core.rules Date: Mon May 7 12:39:52 2018 DuplicateSignature: package:udev:229-4ubuntu21.2 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package udev (--configure): package udev is not ready for configuration ErrorMessage: package udev is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-04-22 (23 days ago) InstallationMedia: Ubuntu-Studio 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Hewlett-Packard Presario CQ57 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-lowlatency root=UUID=a37ad82e-7984-4719-a835-1cf59ee97750 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: systemd Title: package udev 229-4ubuntu21.2 failed to install/upgrade: package udev is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.47 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3577 dmi.board.vendor: Hewlett-Packard dmi.board.version: 24.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068B12000320491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=CO S=PRE dmi.product.name: Presario CQ57 Notebook PC dmi.product.version: 068B12000320491620100 dmi.sys.vendor: Hewlett-Packard ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1771454 Title: package udev 229-4ubuntu21.2 failed to install/upgrade: package udev is not ready for configuration cannot configure (current status 'half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771454/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771434] [NEW] Log Out/login does not recognize new supplementary group; Hangs after repeated Log Out/login cycles
Public bug reported: If a supplementary group is added to a user who is currently logged in to a graphical session, then strange breakage occurs: Problem #1: If the changed user logs out and then logs in again, their processes still do not have the new group membership. It seems necessary to reboot for the group add to take effect in graphically logins. However "su - " in a terminal does get a process with tne new group. Problem #2: If the changed user repeatedly does "Log Out" and then logs in again via gdm, eventually "Log Out" stops working completely (invoking it has no discernible effect). STEPS TO REPRODUCE: 1. Log in graphically as any existing user (might not be relevant). 2. Control-Alt-F3 to get a vt login; log in as root. In the root shell: adduser testuser (enter a password) (hit ENTER to take defaults for all other prompts) 3. Alt-Ctrl-F1 to get to the grpahical login Log in as "testuser" 4. Control-Alt-F3 to return to the root shell. usermod -a -G sudo testuser # group 'sudo' is an example 5. Alt-Ctrl-F1 to get to the grpahical login Return to session of user "testuser" Upper-right-corner-menu->testuser->Log Out (returns to graphical login selector) 6. Log in as "testuser" again Start a gnome-terminal and type "id" RESULTS: "id" shows that the process does NOT have "sudo" as a supplementary group. EXPECTED RESULTS: New graphical logins should see credential changes. 7. Repeatedly do Upper-right-corner-menu->testuser->Log Out Log in again as "testuser" RESULTS: After 3 or 4 iterations, "Log Out" stops working altogether. (When finished "deluser --remove-home testuser" to clean up) 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 15 14:17:25 2018 InstallationDate: Installed on 2018-04-05 (40 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Summary changed: - Log Out/login does not recognize new supplementary group; Lot Out hangs eventually + Log Out/login does not recognize new supplementary group; Hangs after repeated Log Out/login cycles ** Description changed: If a supplementary group is added to a user who is currently logged in to a graphical session, then strange breakage occurs: Problem #1: If the changed user logs out and then logs in again, - their processes still do not have the new group membership. + their processes still do not have the new group membership. - It seems necessary to reboot for the group add to take effect in - in graphically logins. + It seems necessary to reboot for the group add to take effect in + graphically logins. However "su - " in a terminal does get a + process with tne new group. Problem #2: If the changed user repeatedly does "Log Out" and then - logs in again via gdm, eventually "Log Out" stops working - completely (invoking it has no discernible effect). + logs in again via gdm, eventually "Log Out" stops working + completely (invoking it has no discernible effect). STEPS TO REPRODUCE: 1. Log in graphically as any existing user (might not be relevant). 2. Control-Alt-F3 to get a vt login; log in as root. -In the root shell: - adduser testuser - (enter a password) - (hit ENTER to take defaults for all other prompts) + In the root shell: + adduser testuser + (enter a password) + (hit ENTER to take defaults for all other prompts) - 3. Alt-Ctrl-F1 to get to the grpahical login -Log in as "testuser" + 3. Alt-Ctrl-F1 to get to the grpahical login + Log in as "testuser" 4. Control-Alt-F3 to return to the root shell. - usermod -a -G sudo testuser # group 'sudo' is an example + usermod -a -G sudo testuser # group 'sudo' is an example 5. Alt-Ctrl-F1 to get to the grpahical login -Return to session of user "testuser" + Return to session of user "testuser" -Upper-right-corner-menu->testuser->Log Out -(returns to graphical login selector) + Upper-right-corner-menu->testuser->Log Out + (returns to graphical login selector) 6. Log in as "testuser" again -Start a gnome-terminal and type "id" + Start a gnome-terminal and type "id" RESULTS: "id" shows that the process does NOT - have "sudo" as a supplementary group. + have "sudo" as a supplementary group. EXPECTED RESULTS: New graphical logins should see credential changes. 7. Repeatedly do - Upper-right-corner-menu->testuser->Log Out - Log in again as "testuser" + Upper-right-corner-m
[Bug 1771432] [NEW] package udev 234-2ubuntu12.3 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127
Public bug reported: - ProblemType: Package DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12.3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 AptOrdering: mysql-server-5.7:amd64: Install NULL: ConfigurePending Architecture: amd64 CustomUdevRuleFiles: 80-canon_mfp2.rules 70-snap.core.rules Date: Mon May 14 14:42:53 2018 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 MachineType: Hewlett-Packard HP ProBook 430 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=94718cde-02bd-40cb-baab-db57e87057a5 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: systemd Title: package udev 234-2ubuntu12.3 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 UpgradeStatus: Upgraded to artful on 2018-03-05 (71 days ago) dmi.bios.date: 09/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M73 Ver. 01.42 dmi.board.name: 2246 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 59.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM73Ver.01.42:bd09/26/2016:svnHewlett-Packard:pnHPProBook430G2:pvrA3008CD10003:rvnHewlett-Packard:rn2246:rvrKBCVersion59.23:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 430 G2 dmi.product.version: A3008CD10003 dmi.sys.vendor: Hewlett-Packard ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- 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/1771432 Title: package udev 234-2ubuntu12.3 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771432/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764643] Re: Logout after console use freezes GUI
Seems related to https://bugs.launchpad.net/bugs/1758512 . -- 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/1764643 Title: Logout after console use freezes GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1764643/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1737053] Re: [MIR] brotli
$ change-override -S -s cosmic -c main brotli Override component to main brotli 1.0.3-1ubuntu1 in cosmic: universe/misc -> main brotli 1.0.3-1ubuntu1 in cosmic amd64: universe/python/optional/100% -> main brotli 1.0.3-1ubuntu1 in cosmic arm64: universe/python/optional/100% -> main brotli 1.0.3-1ubuntu1 in cosmic armhf: universe/python/optional/100% -> main brotli 1.0.3-1ubuntu1 in cosmic i386: universe/python/optional/100% -> main brotli 1.0.3-1ubuntu1 in cosmic ppc64el: universe/python/optional/100% -> main brotli 1.0.3-1ubuntu1 in cosmic s390x: universe/python/optional/100% -> main libbrotli-dev 1.0.3-1ubuntu1 in cosmic amd64: universe/libdevel/optional/100% -> main libbrotli-dev 1.0.3-1ubuntu1 in cosmic arm64: universe/libdevel/optional/100% -> main libbrotli-dev 1.0.3-1ubuntu1 in cosmic armhf: universe/libdevel/optional/100% -> main libbrotli-dev 1.0.3-1ubuntu1 in cosmic i386: universe/libdevel/optional/100% -> main libbrotli-dev 1.0.3-1ubuntu1 in cosmic ppc64el: universe/libdevel/optional/100% -> main libbrotli-dev 1.0.3-1ubuntu1 in cosmic s390x: universe/libdevel/optional/100% -> main libbrotli1 1.0.3-1ubuntu1 in cosmic amd64: universe/libs/optional/100% -> main libbrotli1 1.0.3-1ubuntu1 in cosmic arm64: universe/libs/optional/100% -> main libbrotli1 1.0.3-1ubuntu1 in cosmic armhf: universe/libs/optional/100% -> main libbrotli1 1.0.3-1ubuntu1 in cosmic i386: universe/libs/optional/100% -> main libbrotli1 1.0.3-1ubuntu1 in cosmic ppc64el: universe/libs/optional/100% -> main libbrotli1 1.0.3-1ubuntu1 in cosmic s390x: universe/libs/optional/100% -> main python-brotli 1.0.3-1ubuntu1 in cosmic amd64: universe/python/optional/100% -> main python-brotli 1.0.3-1ubuntu1 in cosmic arm64: universe/python/optional/100% -> main python-brotli 1.0.3-1ubuntu1 in cosmic armhf: universe/python/optional/100% -> main python-brotli 1.0.3-1ubuntu1 in cosmic i386: universe/python/optional/100% -> main python-brotli 1.0.3-1ubuntu1 in cosmic ppc64el: universe/python/optional/100% -> main python-brotli 1.0.3-1ubuntu1 in cosmic s390x: universe/python/optional/100% -> main python3-b
[Bug 1691357] Re: User switch not possible, login screen black
I see this same behaviour on 2 machines with 18.04 when I have no swap. With swap enable the problem goes away. Bug did not exist in 17.10 or I believe until quite late in the 18.04 development cycle. -- 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/1691357 Title: User switch not possible, login screen black To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1691357/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767536] Re: Accessing the WIFI section of the "Settings" window causes massive freezes
** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1767536 Title: Accessing the WIFI section of the "Settings" window causes massive freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1767536/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767536] Re: Accessing the WIFI section of the "Settings" window causes massive freezes
Confirming I can reproduce this on my Dell Latitude E7470 in a clean live-boot environment for Bionic. Attaching my backtrace. ** Attachment added: "gdb-program.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1767536/+attachment/5139933/+files/gdb-program.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1767536 Title: Accessing the WIFI section of the "Settings" window causes massive freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1767536/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771419] [NEW] System restarts after locking screen
Public bug reported: System will restart always after locking screen, there is no way to prevent this from what i've tried ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "_usr_lib_hidpi-daemon_hidpi-notification.1000.crash" https://bugs.launchpad.net/bugs/1771419/+attachment/5139925/+files/_usr_lib_hidpi-daemon_hidpi-notification.1000.crash -- 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/1771419 Title: System restarts after locking screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1771419/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus
Does it seem like this line could be the problem? https://github.com/GNOME/gnome- shell/blob/3b1330880fbaa1c1f98c912d6d41fe14af18e3eb/js/ui/status/keyboard.js#L382 >From here (https://github.com/GNOME/gnome- shell/blob/2997e4950ba31747b5e3260c306456b0de413421/js/misc/keyboardManager.js#L30) it seems like this will ungrab the keyboard under some circumstances. BTW this is still an issue in bionic as of today. I have never read the ubuntu/gnome sources before, so please forgive if I have misinterpreted something. Also, thanks to incredible-angst for pointing out the DBUS method, which is how I found these lines. -- 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/1244090 Title: Pressing any global keyboard shortcut causes temporary loss of focus To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1244090/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771273] Re: Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2
I didn't find a way to reproduce the problem. -- 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/1771273 Title: Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1771273/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1239010] Re: gnome-settings activation freezes computer
Freezes with Nouveau driver. Switched to NVIDIA metapackage 390 and I can now access settings. -- 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/1239010 Title: gnome-settings activation freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1239010/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747891] Re: gsd-color[1032]: failed to set screen _ICC_PROFILE
** Changed in: gnome-settings-daemon Status: Unknown => Confirmed ** Changed in: gnome-settings-daemon Importance: Unknown => Medium -- 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/1747891 Title: gsd-color[1032]: failed to set screen _ICC_PROFILE To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1747891/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770238] Re: [nvidia] Logging in results in a black screen for many minutes after which the login screen reappears and I am able to login fine.
I'm seeing more crashes where either my desktop locks up and the computer reboots. Or I get returned to the login screen. Why do some of the "DuplicateOf" links shown by the ubuntu bug report tool not work? https://bugs.launchpad.net/bugs/1745664 Two more error reports https://errors.ubuntu.com/oops/9a5971bc-5869-11e8-ac5b-fa163e30221b https://errors.ubuntu.com/oops/ace611be-5869-11e8-9c14-fa163ef911dc -- 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/1770238 Title: [nvidia] Logging in results in a black screen for many minutes after which the login screen reappears and I am able to login fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770238/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom
With proposed the issue is solved. Before: dpkg: error processing archive /var/cache/apt/archives/libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb (--unpack): libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances Errors were encountered while processing: /var/cache/apt/archives/libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) After: Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/universe amd64 libp11-kit-gnome-keyring amd64 3.28.0.2-1ubuntu1.18.04.1 [3.228 B] Fetched 3.228 B in 0s (23,8 kB/s) (Reading database ... 548794 files and directories currently installed.) Preparing to unpack .../libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1.18.04.1_amd64.deb ... Unpacking libp11-kit-gnome-keyring:amd64 (3.28.0.2-1ubuntu1.18.04.1) over (3.20.1-1ubuntu1) ... Setting up libp11-kit-gnome-keyring:amd64 (3.28.0.2-1ubuntu1.18.04.1) ... ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1768541 Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1768541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1728412] Re: Titlebar of firefox does not respond to touch screen
** Changed in: mutter Status: Confirmed => Fix Released -- 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/1728412 Title: Titlebar of firefox does not respond to touch screen To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1728412/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764137] Re: [bionic][beta][nvidia] gnome-shell high CPU utilization when using Nvidia driver
A bit odd that I cannot reproduce this on a fresh 18.04 installation on the same system. https://paste.ubuntu.com/p/PqYBPfvvKr/ -- 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/1764137 Title: [bionic][beta][nvidia] gnome-shell high CPU utilization when using Nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1764137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764137] Re: [bionic][beta][nvidia] gnome-shell high CPU utilization when using Nvidia driver
Also, the setup in comment #7 was tested with 4.17-rc4 and 4.17-rc5. -- 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/1764137 Title: [bionic][beta][nvidia] gnome-shell high CPU utilization when using Nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1764137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour when user logged in.
I get this bug if I uncoment WaylandEnable=false in /etc/gdm3/custom.conf . If I use gdm3 with Wayland I get #1764643 instead. -- 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/1758512 Title: No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour when user logged in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771394] Re: gvfsd-mtp hoovers up all memory
Sorry, 12 G of RAM, not 16. 16 is the system max, I only have 12 installed. -- 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/1771394 Title: gvfsd-mtp hoovers up all memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1771394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771394] [NEW] gvfsd-mtp hoovers up all memory
Public bug reported: When I run a Win7 Virtual Machine and attach my smartphone via USB (to run Samsung Smart Switch on the VM) gvfsd-mtp sucks up all of my 16G(!) of RAM and the system becomes unresponsive. This same workflow worked without issue in 14.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-backends 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: LXDE Date: Tue May 15 12:02:25 2018 InstallationDate: Installed on 2018-04-27 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (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 gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1771394 Title: gvfsd-mtp hoovers up all memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1771394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764643] Re: Logout after console use freezes GUI
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- 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/1764643 Title: Logout after console use freezes GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1764643/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720310] Re: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed
This bug was fixed in the package gnome-session - 3.28.1-0ubuntu3 --- gnome-session (3.28.1-0ubuntu3) bionic; urgency=medium * Prevent debian/unity-gnome-shell-migration.17.10.py script migration crash when no Ubuntu Dock or Dash to Dock installed after upgrade (LP: #1720310) -- Didier Roche Wed, 02 May 2018 09:40:42 +0200 ** Changed in: gnome-session (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1720310 Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1720310/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1749007] Re: Snap mounts should be hidden from System Monitor
This bug was fixed in the package libgtop2 - 2.38.0-2ubuntu0.18.04.1 --- libgtop2 (2.38.0-2ubuntu0.18.04.1) bionic; urgency=medium * debian/patches/05-mountlist-ignore-snap-squashfs.patch: Ignore squashfs mounted in /snap (LP: #1749007). -- Andrea Azzarone Thu, 19 Apr 2018 16:05:53 +0200 ** Changed in: libgtop2 (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-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1749007 Title: Snap mounts should be hidden from System Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1749007/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771376] [NEW] Categories should be a tag optionally added to applications
Public bug reported: In GNOME Shell, aside from the Sundry and Utilities app folders, apps are not sorted by categories, and the Main Menu app makes these too prominent. Main Menu should detect when the user is on GNOME Shell and not display by category but instead list all the apps in one section (and not use the sidebar at all). Main Menu should also then display the categories as editable tags in the Properties of each app. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alacarte 3.11.91-3 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: communitheme:ubuntu:GNOME Date: Tue May 15 15:12:35 2018 InstallationDate: Installed on 2017-08-03 (284 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: alacarte UpgradeStatus: Upgraded to bionic on 2018-04-22 (23 days ago) ** Affects: alacarte (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1771376 Title: Categories should be a tag optionally added to applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1771376/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768555] Re: Update gnome-calendar to 3.28.2
Fixed in cosmic: https://launchpad.net/ubuntu/+source/gnome- calendar/3.28.2-1 ** Changed in: gnome-calendar (Ubuntu) Status: Confirmed => Fix Released ** Also affects: gnome-calendar (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-calendar (Ubuntu Bionic) Status: New => Triaged ** Changed in: gnome-calendar (Ubuntu Bionic) Status: Triaged => Confirmed ** Changed in: gnome-calendar (Ubuntu Bionic) Importance: Undecided => Low ** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1768555 Title: Update gnome-calendar to 3.28.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1768555/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css_node_validate_in
** Description changed: + * Impact + gnome-control-center sometimes hits a segfault + + * Test case + - Check if the e.u.c reports stop with the new version + + or + + - Open GNOME Control Center + - Go to Devices->Display panel + - Close the window + - Open GNOME Control Center again (in overview mode) + + the settings should open without error + + * Regression potential + check the panels can be opened without error and that switching between them works as well + + -- + The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 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/. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1759468 Title: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css_node_validate_internal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1759468/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768555] Re: Update gnome-calendar to 3.28.2
** No longer affects: gnome-calendar (Ubuntu Bionic) ** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1768555 Title: Update gnome-calendar to 3.28.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1768555/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
** No longer affects: dconf (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dconf in Ubuntu. https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1735929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771353] [NEW] Server feature level is now lower than when we began our transaction. Restarting with new ID
Public bug reported: systemd 237-3ubuntu10 from bionic There is no /etc/netplan/* file. I'm getting some sort of a loop when systemd-resolved tries to resolve the hostname of my canonistack instance: ubuntu@bip:~$ systemd-resolve bip.lcy02.canonistack bip.lcy02.canonistack: resolve call failed: All attempts to contact name servers or networks failed systemd-resolved debug output loops over like this: Transaction 36341 is now 19121. Cache miss for bip.lcy02.canonistack IN A Transaction 19121 for scope dns on */*. Using feature level UDP+EDNS0 for transaction 19121. Sending query packet with id 19121. Processing incoming packet on transaction 19121. (rcode=SUCCESS) Server feature level is now lower than when we began our transaction. Restarting with new ID. Transaction 19121 is now 17157. Cache miss for bip.lcy02.canonistack IN A Transaction 17157 for scope dns on */*. Using feature level UDP+EDNS0 for transaction 17157. Sending query packet with id 17157. Processing incoming packet on transaction 17157. (rcode=SUCCESS) Server feature level is now lower than when we began our transaction. Restarting with new ID. ... Packet capture shows a loop like this: 13:38:32.293524 IP 10.55.32.54.53786 > 10.55.32.1.53: 46096+ [1au] A? bip.lcy02.canonistack. (50) 13:38:32.293753 IP 10.55.32.1.53 > 10.55.32.54.53786: 46096* 1/0/0 A 10.55.32.54 (55) 13:38:32.294026 IP 10.55.32.54.53786 > 10.55.32.1.53: 64494+ [1au] A? bip.lcy02.canonistack. (50) 13:38:32.294249 IP 10.55.32.1.53 > 10.55.32.54.53786: 64494* 1/0/0 A 10.55.32.54 (55) I'm going to attach the full debug output, and the pcap file. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "systemd-resolved.log" https://bugs.launchpad.net/bugs/1771353/+attachment/5139831/+files/systemd-resolved.log -- 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/1771353 Title: Server feature level is now lower than when we began our transaction. Restarting with new ID To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771353/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766799] Re: gnome-control-center (ERROR) ../shell/cc-panel-list.c → 926 → cc_panel_list_set_active_panel → assertion failed → (data != NULL)
** Branch linked: lp:~ubuntu-desktop/gnome-control-center/ubuntu -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1766799 Title: gnome-control-center (ERROR) ../shell/cc-panel-list.c → 926 → cc_panel_list_set_active_panel → assertion failed → (data != NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1766799/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771290] Re: Untranslated list of encodings in preferences
** Changed in: gnome-terminal (Ubuntu) Status: New => Triaged ** Changed in: gnome-terminal (Ubuntu) Importance: Undecided => Medium ** Also affects: gnome-terminal (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-terminal (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: gnome-terminal (Ubuntu Bionic) Status: New => Triaged -- 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/1771290 Title: Untranslated list of encodings in preferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1771290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css_node_validate_in
Andrea, your commits there don't apply cleanly to GNOME 3.28. Do you want to rebase for 3.28? Also, could you convert the bug description to SRU format? https://wiki.ubuntu.com/StableReleaseUpdates#Procedure -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1759468 Title: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css_node_validate_internal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1759468/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 84060] Re: [7.04] alacarte crashed with AttributeError in __getPath()
Thank you for reporting this bug to Ubuntu. Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alacarte (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/84060 Title: [7.04] alacarte crashed with AttributeError in __getPath() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/84060/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771031] Re: Please remove libgnome from Ubuntu
** No longer affects: ggcov (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgnome in Ubuntu. https://bugs.launchpad.net/bugs/1771031 Title: Please remove libgnome from Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camorama/+bug/1771031/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724926] Re: No button to launch nm-connection-editor for Advanced functionality like VLANs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1724926 Title: No button to launch nm-connection-editor for Advanced functionality like VLANs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724926/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765799] Re: Applications menu does not get populated with recently installed apps using apt
** Tags added: patch ** Changed in: gnome-menus (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-menus (Ubuntu) Assignee: (unassigned) => fossfreedom (fossfreedom) ** Changed in: gnome-menus (Ubuntu) Importance: Undecided => Low -- 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/1765799 Title: Applications menu does not get populated with recently installed apps using apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1765799/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747891] Re: gsd-color[1032]: failed to set screen _ICC_PROFILE
** Bug watch added: GNOME Bug Tracker #749338 https://bugzilla.gnome.org/show_bug.cgi?id=749338 ** Also affects: gnome-settings-daemon via https://bugzilla.gnome.org/show_bug.cgi?id=749338 Importance: Unknown Status: Unknown -- 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/1747891 Title: gsd-color[1032]: failed to set screen _ICC_PROFILE To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1747891/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756369] Re: Google Calendar is not syncing in Ubuntu 18.04
Confirmed here too. When I go to the Calendar application nothing is synced while my Google account is added to my Online Accounts in settings. When I go to Calendar -> Calendars -> Google (click to setup) and log into my Google Account, after I click Allow to allow Gnome Calendar to use my Google account, the window disappears and nothing happens. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1756369 Title: Google Calendar is not syncing in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1756369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1090723] Re: desktop icons are partly covered by launcher on multi-monitor setup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/1090723 Title: desktop icons are partly covered by launcher on multi-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1090723/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771316] [NEW] Dialog renders at the center of combined monitor space with a multi-monitor setup
Public bug reported: On Ubuntu 18.04, with the "Show Icons" and "Thrash" enabled, trying to empty the trash results in the dialog being rendered at the center of the combined desktop space. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 Uname: Linux 4.15.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue May 15 17:44:05 2018 InstallationDate: Installed on 2018-04-27 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic nautilus ** Attachment added: "Screenshot from 2018-05-15 17-42-28.png" https://bugs.launchpad.net/bugs/1771316/+attachment/5139744/+files/Screenshot%20from%202018-05-15%2017-42-28.png -- 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/1771316 Title: Dialog renders at the center of combined monitor space with a multi- monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1771316/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771308] [NEW] Adding the user to a new group doesn't take effect on logout and back in
Public bug reported: Steps to reproduce: Log in to a GNOME session Use adduser to add yourself to an existing group Log out and back in Open a terminal, run "groups" and notice that your user isn't in the new group. Reboot and log in, and you user is now in the group. ** 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/1771308 Title: Adding the user to a new group doesn't take effect on logout and back in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1771308/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
On 2018-05-13 04:47, Gunnar Hjalmarsson wrote: > Those XKB options are probably set by the > keyboard-configuration.config script in the keyboard-configuration > package. So maybe we need to figure out a proper way to make that > script keep its hands off /etc/default/keyboard when a desktop is > upgraded. The attached debdiff is an attempt at that. When the keyboard- configuration package is upgraded, the main code in the postinst script is not run. When installing, including reinstalling the package, it works as usual, and also when running "dpkg-reconfigure keyboard- configuration". I uploaded the patch to this PPA (bionic): https://launchpad.net/~gunnarhj/+archive/ubuntu/console-setup (The proposed changes to d/control and d/rules proved to be needed for the PPA upload.) ** Patch added: "console-setup_lp1762952.debdiff" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+attachment/5139733/+files/console-setup_lp1762952.debdiff ** Changed in: console-setup (Ubuntu) Status: Confirmed => In Progress ** Changed in: console-setup (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu
Well, since it's in "proposed", which I guess means waiting for feedback, and is not an urgent update at all, my feedback was maybe you should hold it off and release along with that other fix to save an update for users :-) Anyway, filed that as bug 1771290, rest is up to you. Thanks a lot! :-) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1747171 Title: "New Tab" disappeared from the GNOME Terminal menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1747171/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715602] Re: ubiquity-dm / Install Ubuntu - Power button does nothing
Also affected 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/1715602 Title: ubiquity-dm / Install Ubuntu - Power button does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1715602/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715602] Re: ubiquity-dm / Install Ubuntu - Power button does nothing
** Also affects: oem-priority Importance: Undecided Status: New -- 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/1715602 Title: ubiquity-dm / Install Ubuntu - Power button does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1715602/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771290] [NEW] Untranslated list of encodings in preferences
Public bug reported: The list of encodings in Preferences → Compatibility is in English. The list in the Terminal → Set Character Encoding menu is properly translated, though. Upstream bugreport: https://bugzilla.gnome.org/show_bug.cgi?id=795358 Upstream trivial fix: https://git.gnome.org/browse/gnome- terminal/commit/?h=gnome-3-28&id=1828cb6d5 Could you please backport this tiny fix to Bionic LTS? (We're planning to release gnome-terminal 3.28.2 containing this plus at least one other tiny fix in about a week.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.1-1ubuntu1 [modified: usr/bin/gnome-terminal usr/lib/gnome-terminal/gnome-terminal-server usr/share/applications/org.gnome.Terminal.desktop usr/share/glib-2.0/schemas/org.gnome.Terminal.gschema.xml usr/share/metainfo/org.gnome.Terminal.appdata.xml] 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: Unity:Unity7:ubuntu Date: Tue May 15 09:46:24 2018 InstallationDate: Installed on 2016-11-09 (551 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to bionic on 2018-03-14 (61 days ago) ** Affects: gnome-terminal (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-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1771290 Title: Untranslated list of encodings in preferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1771290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726688] Re: totem media player in the Ubuntu dock right click menu does not work, rewind does not work, nor full screen works
still on Ubuntu 18.10 Cosmic: corrado@corrado-p6-cc-0509:~$ apt policy totem totem: Installed: 3.26.0-0ubuntu6 Candidate: 3.26.0-0ubuntu6 Version table: *** 3.26.0-0ubuntu6 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p6-cc-0509:~$ -- 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/1726688 Title: totem media player in the Ubuntu dock right click menu does not work, rewind does not work, nor full screen works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1726688/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771282] [NEW] After running the application from the terminal, on exit it issues an error message.
Public bug reported: After running the application from the terminal e.g. gedit myfile +12, on exit it issues the following error message: (gedit:12035): Gtk-WARNING **: 09:47:06.893: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.28.1-1ubuntu1 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 15 09:55:53 2018 InstallationDate: Installed on 2018-03-05 (70 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gedit UpgradeStatus: Upgraded to bionic on 2018-04-26 (18 days ago) ** Affects: gedit (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 gedit in Ubuntu. https://bugs.launchpad.net/bugs/1771282 Title: After running the application from the terminal, on exit it issues an error message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1771282/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771278] [NEW] search in gnome is not working
Public bug reported: 1) Description:Ubuntu 18.04 LTS Release:18.04 2) gnome-shell: Installed: 3.28.1-0ubuntu2 Candidate: 3.28.1-0ubuntu2 Version table: *** 3.28.1-0ubuntu2 500 500 http://lu.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) When I press Super key and start typing to search, the results of the search should appear. 4) Instead nothing happens. I see this errors in syslog. May 15 08:44:24 Acer18 gnome-shell[2385]: JS ERROR: TypeError: provider.display is undefined#012_clearDisplay/<@resource:///org/gnome/shell/ui/search.js:605:13#012_clearDisplay@resource:///org/gnome/shell/ui/search.js:604:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_reset@resource:///org/gnome/shell/ui/search.js:495:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012setTerms@resource:///org/gnome/shell/ui/search.js:555:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_onTextChanged@resource:///org/gnome/shell/ui/viewSelector.js:532:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012reset@resource:///org/gnome/shell/ui/viewSelector.js:464:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/viewSelector.js:284:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_animateVisible@resource:///org/gnome/shell/ui/overview.js:554:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/overview.js:540:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012toggle@resource:///org/gnome/shell/ui/overview.js:670:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_initializeUI/<@resource:///org/gnome/shell/ui/main.js:197:13 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 15 08:49:24 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['vscode-search-provi...@jomik.org']" b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-05-02 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** 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/1771278 Title: search in gnome is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1771278/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
