[Bug 1848741] Re: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u
** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848741/+attachment/5299096/+files/lspcik.txt -- 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/1848741 Title: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848741] Re: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848741/+attachment/5299095/+files/dmesg.txt -- 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/1848741 Title: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849254] [NEW] Noto Sans Mono Bold not available from /etc/fonts/local.conf
Public bug reported: I tried to change my monospace font to "Noto Sans Mono Bold" in /etc/fonts/local.conf but that didn't have an effect so I did a little digging. First I ran $ sudo fc-cache -f -v && sudo dpkg-reconfigure fontconfig fontconfig-config Which succeeded, then: $ fc-list :style=bold | grep -i notosansmono >/usr/share/fonts/truetype/noto/NotoSansMono-Bold.ttf: Noto Sans Mono:style=Bold So then: $fc-query /usr/share/fonts/truetype/noto/NotoSansMono-Bold.ttf | less which seemed to return a normal looking result similar to: $fc-query /usr/share/fonts/truetype/noto/NotoSansMono-Regular.ttf | less Then I ran: $ fc-match -s "monospace" | grep -i bold >DejaVuSansMono-Bold.ttf: "DejaVu Sans Mono" "Bold" >MathJax_Fraktur-Bold.otf: "MathJax_Fraktur" "Bold" >padmaa-Bold.1.1.ttf: "padmaa-Bold.1.1" "Bold.1.1" >DejaVuSans-BoldOblique.ttf: "DejaVu Sans" "Bold Oblique" Which obviously isn't right since it isn't in that list. Also: $fc-match -s "NotoSansMono" | grep -i notosansmono >NotoSansMono-Regular.ttf: "Noto Sans Mono" "Regular" My system is up to date and here is my version: $lsb_release -a lsb_release: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic $uname -a >Linux 9343 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 >x86_64 x86_64 x86_64 GNU/Linux ** Affects: fonts-noto (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-noto in Ubuntu. https://bugs.launchpad.net/bugs/1849254 Title: Noto Sans Mono Bold not available from /etc/fonts/local.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1849254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841024] Re: sreen captured
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1841024 Title: sreen captured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841024/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
Dropped the bionic task until such time as this becomes a reproducible and testable bug there. ** No longer affects: mutter (Ubuntu Bionic) -- 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/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849251] Re: /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:set_workspace_state
*** This bug is a duplicate of bug 1849249 *** https://bugs.launchpad.net/bugs/1849249 ** This bug has been marked a duplicate of bug 1849249 gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) -- 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/1849251 Title: /usr/bin/gnome- shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:set_workspace_state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849251] [NEW] /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:set_workspace_state
*** This bug is a duplicate of bug 1849249 *** https://bugs.launchpad.net/bugs/1849249 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bionic eoan -- 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/1849251 Title: /usr/bin/gnome- shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:set_workspace_state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
Thanks for the bug report. Tracking in: https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b ** Summary changed: - gnome-shell crashed with SIGABRT + gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) ** Information type changed from Private to Public ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Description changed: + https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b + gnome-shell crashes with this bug every time that: * I am editing a file in geany * I open the Find window (CTRL-F) - * I move the find window to another monitor, + * I move the find window to another monitor, * I type in some text in the find window and press ENTER (or click the Next button) Note especially that the find window must be on the other monitor - if it's on the same monitor as geany, gnome-shell doesn't crash. If the find window opens on the second monitor (so I don't need to move it), gnome-shell still crashes. gnome-shell restarts, but the crash causes data loss, as most of the running applications don't reappear when it restarts. In case it's relevant, I have a laptop screen set at 2048x1152 and an external monitor configured to be above it at 2560x1440. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 Uname: Linux 5.4.0-050400rc4-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 10:37:36 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1570619894 InstallationDate: Installed on 2019-07-01 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/rocko ProcEnviron: - LANG=en_AU.UTF-8 - LANGUAGE=en_AU:en - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=en_AU.UTF-8 + LANGUAGE=en_AU:en + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: - () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /lib/x86_64-linux-gnu/libmutter-5.so.0 - () at /lib/x86_64-linux-gnu/libmutter-5.so.0 - () at /lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo separator: -- 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/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849249/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849135] Re: Activities button does not respond to clicks on a specific pixel
Thanks for the bug report and screenshot. That does confirm it is https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649 ** Tags added: eoan ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Summary changed: - Activities button does not respond to clicks on a specific pixel + Clicking Activities in the corner doesn't work in Xorg sessions ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Clicking Activities in the corner doesn't work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849157] Re: Default sound output device is never the expected one
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 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 1847570, 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 1847570 PulseAudio automatically switches to HDMI sound output on login -- 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/1849157 Title: Default sound output device is never the expected one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849183] Re: Bluetooth devices doesn't get listed while turn off and then on
** Package changed: alsa-driver (Ubuntu) => gnome-control-center (Ubuntu) ** Also affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1849183 Title: Bluetooth devices doesn't get listed while turn off and then on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1849183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849135] Re: Clicking Activities in the corner doesn't work in Xorg sessions
I will need to debug this more in detail. If we find it is Xorg giving us the negative pointer coordinates then it should be fixed there. But it might just be a mutter bug... ** Tags added: rls-ee-incoming ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1849135 Title: Clicking Activities in the corner doesn't work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849183] [NEW] Bluetooth devices doesn't get listed while turn off and then on
You have been subscribed to a public bug: When System Starts, first time Bluetooth devices(Say headphones) get connected smoothly. But after a point when headphones get disconnected, If I tried to reconnect Bluetooth settings don't list the devices. I turned it on/off multiple times but doesn't work. The only way that'd work after a system restart. Please can you check into this ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raghuvar 1999 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 21 23:39:04 2019 InstallationDate: Installed on 2019-06-30 (113 days ago) InstallationMedia: PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN43WW:bd12/22/2018:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 80XL dmi.product.sku: LENOVO_MT_80XL_BU_idea_FM_ideapad 320-15IKB dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- Bluetooth devices doesn't get listed while turn off and then on https://bugs.launchpad.net/bugs/1849183 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849050] Re: 19.10 fails to allow login from desktop if enable automatically login
*** This bug is a duplicate of bug 1845801 *** https://bugs.launchpad.net/bugs/1845801 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 1845801, 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 1845801 [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. -- 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/1849050 Title: 19.10 fails to allow login from desktop if enable automatically login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1849050/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848741] Re: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u
Thanks but that didn't attach as much info as I had hoped. Please run: lspci -k > lspcik.txt dmesg > dmesg.txt and then attach the files 'lspcik.txt' and 'dmesg.txt'. -- 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/1848741 Title: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849050] Re: 19.10 fails to allow login from desktop if enable automatically login
** Tags added: eoan ** Package changed: ubuntu => gdm (Ubuntu) ** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1849050 Title: 19.10 fails to allow login from desktop if enable automatically login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1849050/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849157] Re: Default sound output device is never the expected one
I think this is a duplicate of bug 1847570. If you agree, will you mark it as a duplicate? -- 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/1849157 Title: Default sound output device is never the expected one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782425] Re: Unable to change Power off timeout from 60 seconds ("The system will power off automatically in 60 seconds") to custom value
You are absolutely right. See bug 701186 :) -- 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/1782425 Title: Unable to change Power off timeout from 60 seconds ("The system will power off automatically in 60 seconds") to custom value To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1782425/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849050] [NEW] 19.10 fails to allow login from desktop if enable automatically login
You have been subscribed to a public bug: BUG - based on clean install 19.10 desktop x86-64 If user selects "Log me in Automatically" on install, then they can never login from the desktop login prompt. The system appears to login the use, but not actually show the session. Dropping to a different TTY, can manually login on the terminal. The issue is repeatable. The default user is 100% logged in the background, and any attempts to shutdown from the GUI warns of other users logged in. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment eoan -- 19.10 fails to allow login from desktop if enable automatically login https://bugs.launchpad.net/bugs/1849050 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849135] Re: Activities button does not respond to clicks on a specific pixel
It was already reported. Here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649 And here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1601 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1649 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1601 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1601 -- 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/1849135 Title: Activities button does not respond to clicks on a specific pixel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles
It has been fixed in Fedora and Arch, where is the fix for Ubuntu? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1847551 Title: Mutter 3.34.1 broke Night Light, screen color profiles To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1847551/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849135] Re: Activities button does not respond to clicks on a specific pixel
Thanks for testing a GNOME session, it would be nice to report it upstream as well since it doesn't seem to be due to some extension or Ubuntu specific components https://gitlab.gnome.org/GNOME/gnome-shell/issues ** 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/1849135 Title: Activities button does not respond to clicks on a specific pixel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo
What's the output of `gcc --version`? -- 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/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842865/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848309] Re: "Automatic Date & Time" is broken
On 2019-10-21 19:27, Sebastien Bacher wrote: > The sync is failing due to 'ConditionFileIsExecutable=!/usr/sbin/ntpd' That file would be provided by the universe package ntp. Are there reasons to move it back to main? -- 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/1848309 Title: "Automatic Date & Time" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848309/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848309] Re: "Automatic Date & Time" is broken
The sync is failing due to 'ConditionFileIsExecutable=!/usr/sbin/ntpd' -- 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/1848309 Title: "Automatic Date & Time" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848309/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849157] [NEW] Default sound output device is never the expected one
Public bug reported: According to this page: https://wiki.ubuntu.com/Sound#Primary_sound_output, "if you manually choose an output device in the “Sound” settings panel or a similar utility, that choice should be followed". Well, despite me having explicitly selected the headset as the output device, on every reboot it falls back to the HDMI device. The headset is always plugged in. I believe this is a regression. On Ubuntu 19.04 and previous versions, it respected my preferences about the sound device. It is reproducible on both Xorg and Wayland sessions. Specs: OS: Ubuntu 19.10 Eoan (GNOME, Ubuntu sessions) Motherboard: Gigabyte B360M GAMING HD CPU: Intel Core i3-8100 Graphics: AMD RX 560 (AMDGPU, open source) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 21 12:49:52 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-21 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1849157 Title: Default sound output device is never the expected one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848309] Re: "Automatic Date & Time" is broken
sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d └─disable-with-time-daemon.conf Active: inactive (dead) Condition: start condition failed at Mon 2019-10-21 12:34:47 CEST; 4h 5min ago Docs: man:systemd-timesyncd.service(8) Oct 21 12:34:29 sun systemd[1]: Condition check resulted in Network Time Synchronization being skipped. Oct 21 12:34:47 sun systemd[1]: Condition check resulted in Network Time Synchronization being skipped. # $ timedatectl set-ntp true $ systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d └─disable-with-time-daemon.conf Active: inactive (dead) Condition: start condition failed at Mon 2019-10-21 17:19:40 CEST; 1s ago └─ ConditionFileIsExecutable=!/usr/sbin/ntpd was not met Docs: man:systemd-timesyncd.service(8) Oct 21 12:34:29 sun systemd[1]: Condition check resulted in Network Time Synchronization being skipped. Oct 21 12:34:47 sun systemd[1]: Condition check resulted in Network Time Synchronization being skipped. Oct 21 16:41:31 sun systemd[1]: Condition check resulted in Network Time Synchronization being skipped. Oct 21 17:19:31 sun systemd[1]: Condition check resulted in Network Time Synchronization being skipped. Oct 21 17:19:32 sun systemd[1]: Condition check resulted in Network Time Synchronization being skipped. Oct 21 17:19:33 sun systemd[1]: Condition check resulted in Network Time Synchronization being skipped. Oct 21 17:19:34 sun systemd[1]: Condition check resulted in Network Time Synchronization being skipped. Oct 21 17:19:40 sun systemd[1]: Condition check resulted in Network Time Synchronization being skipped. ...still the slider cannot be activated. -- 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/1848309 Title: "Automatic Date & Time" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848309/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849135] Re: Activities button does not respond to clicks on a specific pixel
No extensions were installed. Also, I'm using the native AMDGPU drivers, not the proprietary ones. I've tested the vanilla GNOME session as you suggested, and the bug is there too. Due to the hover highlighting of the panel items, I had a visual cue to test with. The highlighting does not happen at the unclickable spot. Move one pixel away from it, and the panel item lits up again. That was on Xorg, of course. On Wayland, the problem is gone, at least initially. As I said on the initial report, after using the Wayland session for a while, I started having the problem again. No idea what caused it. -- 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/1849135 Title: Activities button does not respond to clicks on a specific pixel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849106] Re: After upgrading to 19.10, files crashes when I try to move some items to trash.
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/1849106 Title: After upgrading to 19.10, files crashes when I try to move some items to trash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1849106/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849135] Re: Activities button does not respond to clicks on a specific pixel
Thank you for your bug report? Do you have any extension installed? Could you test if that's also happening in a GNOME session (you need to install 'gnome-session:' to have the session listed on the login screen)? ** 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/1849135 Title: Activities button does not respond to clicks on a specific pixel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1848852 Title: Counter-Strike Global Offensive freezes in gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848852/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849106] Re: After upgrading to 19.10, files crashes when I try to move some items to trash.
the sudo error is known, nautilus isn't meant to be used as superuser -- 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/1849106 Title: After upgrading to 19.10, files crashes when I try to move some items to trash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1849106/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849135] Re: Activities button does not respond to clicks on a specific pixel
** Description changed: Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. - Important: This is only reproducible on Xorg, not on Wayland. + Edit: At first it seemed to be reproducible only on Xorg sessions, but + after using it for a while on Wayland, I am having the issue again. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan -- 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/1849135 Title: Activities button does not respond to clicks on a specific pixel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849142] [NEW] Discord and appindicator extension slows down ui
Public bug reported: Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: Discord and appindicator extension slows down ui To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849135] Re: Activities button does not respond to clicks on a specific pixel
** Description changed: Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. + Important: This is only reproducible on Xorg, not on Wayland. + Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan -- 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/1849135 Title: Activities button does not respond to clicks on a specific pixel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817073] Re: GNOME Shell crash when an asset is not found (due to too many logs spawn by appindicator extension)
Too quick on that one, was not fixed just by reinstalling gnome-shell-extension-appindicator. Now i also noticed that this isn't just in the game, the whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. Didn't notice before since gnome performance wasn't that good by itself up until now. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 ** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues #171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 ** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues #157 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1817073 Title: GNOME Shell crash when an asset is not found (due to too many logs spawn by appindicator extension) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1817073/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849135] [NEW] Activities button does not respond to clicks on a specific pixel
Public bug reported: Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot of the Activities button with the mouse placed on the unclickable spot" https://bugs.launchpad.net/bugs/1849135/+attachment/5298946/+files/Captura%20de%20tela%20de%202019-10-21%2011-22-54.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Activities button does not respond to clicks on a specific pixel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell
Tried it again and it didn't give me a crash report, then i tried it and it launched but the game frooze, was able to open gnome activities and close the game but then the main screen in the game was still on half of the screen frozen. However if i click to launch the game, then directly open the gnome activities and have it opened until the game has fully launched, i can play the game without a 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/1848852 Title: Counter-Strike Global Offensive freezes in gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848852/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849135] Re: Activities button does not respond to clicks on a specific pixel
** Attachment added: "Journalctl logs" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+attachment/5298947/+files/journalctl.txt ** Description changed: Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - - Ubuntu 19.10 Eoan (fresh install, all updates) + - Ubuntu 19.10 Eoan -- 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/1849135 Title: Activities button does not respond to clicks on a specific pixel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848309] Re: "Automatic Date & Time" is broken
So that's consistent with the switch status. Can you change the status in the setting and do $ systemctl status systemd-timesyncd.service and copy the log here? What happens if you try then to enable sync with that command instead of the settings? $ timedatectl set-ntp true -- 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/1848309 Title: "Automatic Date & Time" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848309/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848309] Re: "Automatic Date & Time" is broken
$ timedatectl status Local time: Mon 2019-10-21 15:46:41 CEST Universal time: Mon 2019-10-21 13:46:41 UTC RTC time: Mon 2019-10-21 13:46:37 Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: no NTP service: inactive RTC in local TZ: no -- 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/1848309 Title: "Automatic Date & Time" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848309/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848309] Re: "Automatic Date & Time" is broken
what's the output of 'timedatectl status'? -- 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/1848309 Title: "Automatic Date & Time" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848309/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846944] Re: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1846944 Title: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1846944/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782425] Re: Unable to change Power off timeout from 60 seconds ("The system will power off automatically in 60 seconds") to custom value
Sorry if I'm being naughty, but on this case the proper status should not be "Won't fix"? -- 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/1782425 Title: Unable to change Power off timeout from 60 seconds ("The system will power off automatically in 60 seconds") to custom value To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1782425/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849106] [NEW] After upgrading to 19.10, files crashes when I try to move some items to trash.
Public bug reported: After upgrading to 19.10, files crashes when I try to move some items to trash. Then I opened nautilus with 'sudo nautilus' in the terminal and there I was able to delete items, but when I go to the trash folder, it says 'This location could not be displayed. Sorry, could not display all the contents of "trash:///": Operation not supported.' ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 21 17:37:20 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1837, 726)' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-08-26 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Trying to access trash folder from 'sudo nautilus'" https://bugs.launchpad.net/bugs/1849106/+attachment/5298896/+files/Screenshot%20from%202019-10-21%2017-47-41.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/1849106 Title: After upgrading to 19.10, files crashes when I try to move some items to trash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1849106/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848309] Re: "Automatic Date & Time" is broken
As I wrote, I was using the very latest Eoan packages for the past months as this bug occurred and persisted. Therefore I could not provide any specific Ubuntu version as the version number was just "latest development". ## related jounrnalctl messages Oct 21 12:37:19 sun dbus-daemon[1577]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.284' (uid=1000 pid=21820 comm="gnome-control-center datetime " label="unconfined") Oct 21 12:37:19 sun systemd[1]: systemd-timedated.service: Succeeded. Oct 21 12:37:19 sun systemd[1]: Starting Time & Date Service... Oct 21 12:37:19 sun dbus-daemon[1577]: [system] Successfully activated service 'org.freedesktop.timedate1' Oct 21 12:37:19 sun systemd[1]: Started Time & Date Service. Oct 21 12:37:49 sun dbus-daemon[1577]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.284' (uid=1000 pid=21820 comm="gnome-control-center datetime " label="unconfined") Oct 21 12:37:49 sun systemd[1]: systemd-timedated.service: Succeeded. Oct 21 12:37:49 sun systemd[1]: Starting Time & Date Service... Oct 21 12:37:49 sun dbus-daemon[1577]: [system] Successfully activated service 'org.freedesktop.timedate1' Oct 21 12:37:49 sun systemd[1]: Started Time & Date Service. Oct 21 12:37:58 sun xdg-desktop-por[4719]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed Oct 21 12:38:19 sun dbus-daemon[1577]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.284' (uid=1000 pid=21820 comm="gnome-control-center datetime " label="unconfined") Oct 21 12:38:19 sun systemd[1]: systemd-timedated.service: Succeeded. Oct 21 12:38:19 sun systemd[1]: Starting Time & Date Service... Oct 21 12:38:20 sun dbus-daemon[1577]: [system] Successfully activated service 'org.freedesktop.timedate1' Oct 21 12:38:20 sun systemd[1]: Started Time & Date Service. ## ubuntu-bug asks me to provide a PID and I have really other priorities to deal with than to figure out which PID it is supposed to be... alex@sun:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan I hope this helps. -- 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/1848309 Title: "Automatic Date & Time" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848309/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849090] Re: Autocompletion does not work correctly with special signs
The bug only happens if a file with an equal prefix exists, e.g. after `vim 'A123$B123#asdasd'`. I am using bash, but the problem also happens in zsh if I enter `A123\$B123\#`, hit tab, enter `<` and than hit tab again. It does not happen in zsh if I hit tab again and again and it switches between all files in the folder. -- 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/1849090 Title: Autocompletion does not work correctly with special signs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1849090/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849090] Re: Autocompletion does not work correctly with special signs
Autocompletion is done by the shell and its configs, not by the terminal. ** Also affects: bash-completion (Ubuntu) Importance: Undecided Status: New -- 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/1849090 Title: Autocompletion does not work correctly with special signs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1849090/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849090] [NEW] Autocompletion does not work correctly with special signs
Public bug reported: The autocompletion of the terminal does not work correct for some special signs, e.g. if I edit a file by vim "A123\$B123#_asd" it is not possible to get it for autocompletion afterwards. If I enter cat `A123\$B123#` and then hit tab two times, the file is display correctly, but if I then enter `<` and hit tab, it is completed to cat `A123\$B123#_asd` which does not exist (so the full file is appended after `<`, not only the additional part. I am using Ubuntu 18.04 with newest updates, including gnome-terminal 3.28.2. ** Affects: bash-completion (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- 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/1849090 Title: Autocompletion does not work correctly with special signs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1849090/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848741] Re: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u
apport information ** Tags added: apport-collected ** Description changed: - I have graphics artefacts: screan tearing, pieces of the previous window - appear in the newly opened window. + I have graphics artefacts: screan tearing, pieces of the previous window appear in the newly opened window. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-09-08 (42 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + Package: gnome-shell 3.34.1-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 + RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 + Tags: eoan + Uname: Linux 5.3.0-18-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago) + UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1848741/+attachment/5298850/+files/Dependencies.txt -- 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/1848741 Title: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848741] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1848741/+attachment/5298854/+files/ShellJournal.txt -- 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/1848741 Title: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848741] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1848741/+attachment/5298851/+files/GsettingsChanges.txt -- 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/1848741 Title: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848741] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1848741/+attachment/5298853/+files/ProcEnviron.txt -- 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/1848741 Title: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1849055] Re: gnome-extensions fails to load after boot
Some of those I enabled at one point but am no longer using. On 10/20/19 11:39 PM, Daniel van Vugt wrote: > Thanks. It seems you have a number of extensions. Do they all have the > problem or just some? > > 'ubuntu-d...@ubuntu.com' > 'activities-button-text@nls1729' > 'dynamictop...@gnomeshell.feildel.fr' > 'gradienttop...@peclu.net' > 'openweather-extens...@jenslody.de' > 'transparent-gnome-pa...@ttomovcik.com' > 'suspend@terrasea_at_gmail.com' > 'add-username-toppa...@brendaw.com' > 'suspend-button@laserb' > 'drive-m...@gnome-shell-extensions.gcampax.github.com' > 'simple-n...@rmariano.github.com' > 'transparenttop...@peclu.net' > 'apps-m...@gnome-shell-extensions.gcampax.github.com' > -- 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/1849055 Title: gnome-extensions fails to load after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849055/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848741] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1848741/+attachment/5298852/+files/ProcCpuinfoMinimal.txt -- 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/1848741 Title: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782425] Re: Unable to change Power off timeout from 60 seconds ("The system will power off automatically in 60 seconds") to custom value
We know. That's just a Launchpad bug where it doesn't know the difference. -- 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/1782425 Title: Unable to change Power off timeout from 60 seconds ("The system will power off automatically in 60 seconds") to custom value To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1782425/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782425] Re: Unable to change Power off timeout from 60 seconds ("The system will power off automatically in 60 seconds") to custom value
@vanvugt: Not sure if I'm missing something, but the bug was not fixed in Gnome, just closed. -- 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/1782425 Title: Unable to change Power off timeout from 60 seconds ("The system will power off automatically in 60 seconds") to custom value To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1782425/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco
*** This bug is a duplicate of bug 1817128 *** https://bugs.launchpad.net/bugs/1817128 I've summarized my investigation so far in this new bug report: It seems a combination of ZSH, Oh-My-Zsh and possibly Powerlevel10k break the login screen somehow. https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1849081 https://github.com/robbyrussell/oh-my-zsh/issues/8296 https://github.com/romkatv/powerlevel10k/issues/280 ** Bug watch added: github.com/robbyrussell/oh-my-zsh/issues #8296 https://github.com/robbyrussell/oh-my-zsh/issues/8296 ** Bug watch added: github.com/romkatv/powerlevel10k/issues #280 https://github.com/romkatv/powerlevel10k/issues/280 -- 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/1818616 Title: gnome-keyring is not unlocked upon gdm login in disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1818616/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800043] Re: nautilus cannot write on nfs file share base dir
** Changed in: nautilus Status: Unknown => New -- 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/1800043 Title: nautilus cannot write on nfs file share base dir To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1800043/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817128] Re: gnome-keyring not automatically unlocked on login
Thanks, I've raised several issues to try to fix this problem: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1849081 https://github.com/robbyrussell/oh-my-zsh/issues/8296 https://github.com/romkatv/powerlevel10k/issues/280 ** Bug watch added: github.com/robbyrussell/oh-my-zsh/issues #8296 https://github.com/robbyrussell/oh-my-zsh/issues/8296 ** Bug watch added: github.com/romkatv/powerlevel10k/issues #280 https://github.com/romkatv/powerlevel10k/issues/280 -- 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/1817128 Title: gnome-keyring not automatically unlocked on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849081] Re: ZSH shells break Login screen
I've cross-posted this issue in the related tools since it's unclear which one causes it, but it's severe enough to make it worth triaging it. https://github.com/robbyrussell/oh-my-zsh/issues/8296 https://github.com/romkatv/powerlevel10k/issues/280 ** Bug watch added: github.com/robbyrussell/oh-my-zsh/issues #8296 https://github.com/robbyrussell/oh-my-zsh/issues/8296 ** Bug watch added: github.com/romkatv/powerlevel10k/issues #280 https://github.com/romkatv/powerlevel10k/issues/280 -- 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/1849081 Title: ZSH shells break Login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1849081/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849081] [NEW] ZSH shells break Login screen
Public bug reported: There's a bug that affects gnome-keyring, and i'll describe the steps i've done to reproduce it twice, although i don't have full details as to what exactly is causing it. Issue can be summarized as follows: On Ubuntu 19.10, but not at least 18.04 (another computer i have using the older release), there's an issue that prevents the user to login to a gnome session The issue shows up when checking the session manager: ``` service gdm3 status Process: ExecStartPre: /usr/share/gdm/generate-config (code=exited,status=0/SUCCESS) Process: ExecStartPre: /usr/lib/gdm3/gdm-wait-for-drm (code=exited,status=0/SUCCESS) ... gdm-password: gkr-pam: unable to local control file ``` Relevant components: * gdm3 3.34.1-1 * gnome-shell 3.34.1-1 * gnome-keyring 3.34.0-1 * zsh 5.77.1-ubuntu2 This does not occur on a fresh installation of Ubuntu. It only happens once some of these tools are installed: * zsh (ubuntu package https://packages.ubuntu.com/eoan/zsh , manually change shell for user) - https://askubuntu.com/questions/131823/how-to-make-zsh-the-default-shell * oh-my-zsh (brings in lots of plugins, although only git was sourced) - https://github.com/robbyrussell/oh-my-zsh/wiki/Installing-ZSH * powerlevel10k (shell theme ) - https://github.com/romkatv/powerlevel10k The tools would appear to work fine, until you reboot the machine, and are asked to login, at which point gkr-pam complains that it can't locate control file. Unfortunately i don't have better details because eventually i broke so much my login that i decided to reinstall the system from scratch. Upon installation, i started from fresh, with no zsh, and everything worked. Once zsh was installed, it will no longer work. A fix for this was to revert to bash shell. The key change was to no include this line at the top of .bashrc ``` #exec zsh ``` So i can confirm the issue is there, but that's as far as i got after several hours of investigations. I appreciate that this bug may not be a gnome-keyring specific bug, but seems that its the one been affected anyways. https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28 https://gitlab.gnome.org/GNOME/gnome-keyring/issues/26 https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L676 https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L847 https://github.com/GNOME/gnome-keyring/commit/443a821cba105e8f277828a67b3d019b67f1324a https://github.com/GNOME/gnome-keyring/commit/b22d058a055ec3e0f31ae16417f16b42baadb42f https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128 https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1818616 ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: eoan -- 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/1849081 Title: ZSH shells break Login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1849081/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844775] Re: HDR support for Ubuntu 20.04
You mean doing upstream work to add support for it? No, I don't think so. ** Summary changed: - HDR support for Ubuntu 20.04 + HDR support for Ubuntu -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1844775 Title: HDR support for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1849055] Re: gnome-extensions fails to load after boot
It?? could be the open-weather extension which is causing the error. On 10/21/19 1:29 AM, Daniel van Vugt wrote: > Yes, gnome-shell kicks them out if they have errors. And definitely some > have errors (see the log in comment #7). > > It sounds like maybe it's kicking out multiple extensions based on them > being loaded together?... > -- 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/1849055 Title: gnome-extensions fails to load after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849055/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849055] Re: gnome-extensions fails to load after boot
Yes, gnome-shell kicks them out if they have errors. And definitely some have errors (see the log in comment #7). It sounds like maybe it's kicking out multiple extensions based on them being loaded together?... -- 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/1849055 Title: gnome-extensions fails to load after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849055/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1505070] Re: gnome-session-quit --power-off produces immediate shutdown
*** This bug is a duplicate of bug 1847974 *** https://bugs.launchpad.net/bugs/1847974 ** This bug is no longer a duplicate of bug 1426851 Power button shuts down computer if a Qt application is running ** This bug has been marked a duplicate of bug 1847974 Qt apps terminate on Power-Off dialog -- 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/1505070 Title: gnome-session-quit --power-off produces immediate shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1505070/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848563] Re: Activities overview unwanted scrolling when clicking popup menu on page 4 onward
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Changed in: gnome-shell (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1848563 Title: Activities overview unwanted scrolling when clicking popup menu on page 4 onward To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848563/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847974] Re: Qt apps terminate on Power-Off dialog
** Summary changed: - Some apps terminates on Power-Off dialog + Qt apps terminate on Power-Off dialog ** Package changed: gnome-shell (Ubuntu) => qtbase-opensource-src (Ubuntu) ** Changed in: qtbase-opensource-src (Ubuntu) Status: Opinion => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1847974 Title: Qt apps terminate on Power-Off dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1847974/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1849055] Re: gnome-extensions fails to load after boot
The extensions do load when I enable them.?? The problem is that after a reboot they are not enabled and I need to do it by hand. This does not happen after every reboot but occurs often enough when I start up the computer that it's annoying. On 10/21/19 12:59 AM, Daniel van Vugt wrote: > The log in comment #7 shows a number of your extensions are failing to > load because they are not yet compatible with Gnome 3.34 or at least > Ubuntu's Gnome 3.34. > > Please try them one-by-one to see which ones work and which don't. If > it's only a subset of them then we should use bug 1835706 instead, to > track them individually. > > For those extensions that can't be tracked in Launchpad (because they > did not come from Ubuntu) you will need to contact the extension authors > separately. > -- 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/1849055 Title: gnome-extensions fails to load after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849055/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848836] Re: Unmounted drive shortcut is on the dock
** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/1031 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1848836 Title: Unmounted drive shortcut is on the dock To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1848836/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730765] Re: Mounted external devices do not appear in dock
The issue was resolved in Ubuntu 19.10, the dock lists devices now. If you have problems with the implementation best to open a new report describing the details ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1730765 Title: Mounted external devices do not appear in dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1730765/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844650] Re: No authentication window pops up if thunderbolt device be plugged before booting
** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844650 Title: No authentication window pops up if thunderbolt device be plugged before booting To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1844650/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849055] Re: gnome-extensions fails to load after boot
The log in comment #7 shows a number of your extensions are failing to load because they are not yet compatible with Gnome 3.34 or at least Ubuntu's Gnome 3.34. Please try them one-by-one to see which ones work and which don't. If it's only a subset of them then we should use bug 1835706 instead, to track them individually. For those extensions that can't be tracked in Launchpad (because they did not come from Ubuntu) you will need to contact the extension authors separately. -- 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/1849055 Title: gnome-extensions fails to load after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849055/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34
** Also affects: gnome-shell-extension-weather (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1835706 Title: Extensions don't load in gnome-shell 3.33/3.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1835706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844650] Re: No authentication window pops up if thunderbolt device be plugged before booting
@Rex The link is on also-affect project list. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1794 -- 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/1844650 Title: No authentication window pops up if thunderbolt device be plugged before booting To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1844650/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844650] Re: No authentication window pops up if thunderbolt device be plugged before booting
@cktenn please kindly provide the link of the issue on gnome-shell project. Thanks -- 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/1844650 Title: No authentication window pops up if thunderbolt device be plugged before booting To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1844650/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848940] Re: gnome-control-center does not respect symbolic links
** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Invalid -- 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/1848940 Title: gnome-control-center does not respect symbolic links To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848940/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800043] Re: nautilus cannot write on nfs file share base dir
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #884 https://gitlab.gnome.org/GNOME/nautilus/issues/884 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/884 Importance: Unknown Status: Unknown -- 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/1800043 Title: nautilus cannot write on nfs file share base dir To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1800043/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848747] Re: Gnome Control Center don't work
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1848747 Title: Gnome Control Center don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848309] Re: "Automatic Date & Time" is broken
The report lack basic informations, please submit using ubuntu-bug. Like the Ubuntu version used isn't even specified. Could you also add your 'journalctl -b 0' log? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/1848309 Title: "Automatic Date & Time" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848309/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846398] Re: Fractional scaling has significant visible refreshes on a 4k display
** Changed in: xorg-server Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1846398 Title: Fractional scaling has significant visible refreshes on a 4k display To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1846398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs