[Bug 2075350] [NEW] gnome-shell seems to hang on monitor disconnect, killing gnome-shell process helps to bring system to life
Public bug reported: As title says: sometimes when I disconnect my laptop from DisplayPort- over-USBC monitor desktop goes to black screen (sometimes with cursor available, but only the cursor!), and over the time I've found out that opening a tty session and executing a `killall gnome-shell` brings system back to life! It looks very glitchy but it helps. The only relevant part I've found out is this part of the log. It's an extremely long thread of similar but mixed messages like: ``` июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 0x641018d41170 == июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was window-entered-monitor on MetaDisplay 0x641018e6a160. июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was window-entered-monitor on MetaDisplay 0x641018e6a160. июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was window-entered-monitor on MetaDisplay 0x641018e6a160. июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was window-entered-monitor on MetaDisplay 0x641018e6a160. июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was window-entered-monitor on MetaDis
[Bug 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
wastrel, you're my saviour! I wouldn't discover that there is an option in ages! I think this should be the default, actually, because as I've stated if sssd is not configured in the system we should use passwords, and if system administrator configures proper smartcard authentication only then should there be an option to forbid passwords. Actually, it looks even more strange that current option is sssd- exclusive when you can just unplug the key and get a password prompt anyway. -- 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/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
So... GDM actually just launches special session instance that is actually a login screen? Now it's even more weird that gnome-shell doesn't ask for PIN on lock screen. -- 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/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1933027] [NEW] Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
Public bug reported: I use my Ubuntu PC with Yubikey almost always plugged in. It provides several security token interfaces, such as U2F, GPG smartcard, proprieritary Yubico interfaces (of which I mostly use TOTP codes), and also PIV smartcard. However, I haven't configured a PIV smartcard on it. Whenever I login into the system having Yubikey plugged in, I'm prompted for login name, and then for PIN for some smartcard while also being asked to plug in one. This is very misleading on several layers: 1. I have the device providing smartcard plugged id, 2. But it's not the smartcard GDM would think it is as it's not configured properly, 3. There are no local smartcard-authenticating users right now in the system, 3. There are no remote authentication systems configured on the system (so no ActiveDirectory-smartcard logins or such). If I unplug the token UX goes back on old good track. Given the circumstances above, I'd consider that GDM (and, on my bet, any PAM configuration it uses) shouldn't offer to login using smartcard if there is no way to actually do so. I feel something is off here, so I'm reporting a bug. It could be an upstream problem though; it also could be an upstream SSSD problem, or all combined. I believe there is a more clear user experience: 1. GDM should display users that can login into the system, as it always does (if configured). It may also provide entering other login name (also if configured). This is GDM usually does without smartcards altogether. 2. When user is chosen (from the list or manually typed in), check can this user even authenticate with smartcards (i.e. if any of available smartcards is actually recognised for this user). If so, then ask for PIN. Else, don't show anything about smartcards at all (this includes when SSSD is not configured for any AD or related and this user has no local smartcard configuration). This can switch there & back based on device events. I've seen other OS doing this. Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock screen, so I guess it doesn't support it at all or correctly finds out it can't be used. Even more, I couldn't find a way to actually add my smartcard as a local login method. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 14:02:02 2021 InstallationDate: Installed on 2017-03-05 (1567 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (37 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1814169] Re: Mutter upsteam bug: cannot overwrite workspaces layout
Huh. So, when will the fixed version land? For now, I rebuild published version with the patch above. -- 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/1814169 Title: Mutter upsteam bug: cannot overwrite workspaces layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1814169/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1814169] Re: Mutter upsteam bug: cannot overwrite workspaces layout
Patch as a file ** Patch added: "0001-Allow-workspace-layout-to-be-overridden.patch" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1814169/+attachment/5234887/+files/0001-Allow-workspace-layout-to-be-overridden.patch -- 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/1814169 Title: Mutter upsteam bug: cannot overwrite workspaces layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1814169/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1814169] [NEW] Mutter upsteam bug: cannot overwrite workspaces layout
Public bug reported:
Running up-to-date Ubuntu Cosmic. Since I am running a version with
manually applied patched from below, I couldn't use the ubuntu-bug
helper.
Bug: When using GNOME extension “Workspace grid” that arranges
workspaces in a grid, one can find that horizontal switch animation is
replaced with a vertical one. This is caused by a bug in mutter itself,
it's acknowledged and fixed in upsteam. Applying the patch for the
current version in Ubuntu solves the issue as well.
GIFs of the issue could be found here: https://medium.com/@hkdb/patch-
gnome-3-30-for-workspace-grid-1ee8b1dd92f9.
Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/270.
Upsteam fix:
https://gitlab.gnome.org/rmyorston/mutter/commit/97a3a9b24b3655003467d5fac6bb1ec1c60e
(merged into master 3 months ago).
The patch to fix is, literally, adding 1 meaningful line:
>From 86a719cc78149b7db189ff7e5d1f16418d257e9e Mon Sep 17 00:00:00 2001
From: Ron Yorston
Date: Tue, 2 Oct 2018 12:47:05 +0100
Subject: [PATCH] Allow workspace layout to be overridden
meta_workspace_manager_override_workspace_layout is implemented by
calling meta_workspace_manager_update_workspace_layout which
respects the workspace_layout_overridden flag. After the first call
to meta_workspace_manager_override_workspace_layout all subsequent
calls fail silently.
Reset workspace_layout_overridden to FALSE before calling
meta_workspace_manager_update_workspace_layout.
Signed-off-by: Ron Yorston
---
src/core/meta-workspace-manager.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/core/meta-workspace-manager.c
b/src/core/meta-workspace-manager.c
index 2670f4938..abc819db0 100644
--- a/src/core/meta-workspace-manager.c
+++ b/src/core/meta-workspace-manager.c
@@ -496,6 +496,8 @@ meta_workspace_manager_override_workspace_layout
(MetaWorkspaceManager *workspac
int n_rows,
int
n_columns)
{
+ workspace_manager->workspace_layout_overridden = FALSE;
+
meta_workspace_manager_update_workspace_layout (workspace_manager,
starting_corner,
vertical_layout,
--
2.17.1
Hopefully this one is fast to test and apply ;)
** Affects: mutter (Ubuntu)
Importance: Undecided
Status: 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/1814169
Title:
Mutter upsteam bug: cannot overwrite workspaces layout
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1814169/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767669] [NEW] Systemd-resolved cannot forget local DNS Domain name after leaving the network
Public bug reported: At my university, WiFi network setup sets a local DNS Domain name (in a form of .). That's alright; but when I come home with my laptop and resume it, the local DNS Domain name is still set (checked via systemd-resovle --status), and because of that I cannot open my university website: it's domain cannot be resoved on a local DNS (of course it cannot be resolved, it's not in local network anymore). Resolving manually on any other DNS server (via dig @) works perfectly fine. Resolving any non-local name works fine too. DNS resolver IP's are right. Restarting systemd-resolved or-and NetworkManager does not fix the issue, only the full reboot can help. That's pretty annoying. I am running Ubuntu 17.10 (soon to be upgraded to 18.04). Have this issue since installing 17.10, but wasn't able to find a clue until today. What should be happening: Well, after I leave the network, resolver should forget local settings from that network, right? What is happeing: it does not. Well, at least the resolver ip's are right. P.S. It might be a NetworkManager issue but the only thing that I find that remembers local DNS is the systemd-resolved, feel free to change package. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.3 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 18:26:01 2018 InstallationDate: Installed on 2016-04-23 (734 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK Computer Inc. U40Sd ProcEnviron: LANG=ru_RU.UTF-8 TERM=tmux-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=ea1ac96c-71bd-4b8e-81ad-24abb9a24ce0 ro nogpumanager quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/docker.service → /etc/systemd/system/docker.service.d/docker.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U40Sd.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U40Sd dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU40Sd.202:bd06/16/2011:svnASUSTeKComputerInc.:pnU40Sd:pvr1.0:rvnASUSTeKComputerInc.:rnU40Sd:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: U dmi.product.name: U40Sd dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. mtime.conffile..etc.systemd.resolved.conf: 2018-04-19T19:34:54.154657 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages -- 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/1767669 Title: Systemd-resolved cannot forget local DNS Domain name after leaving the network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1767669/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1757960] Re: Gnome Shell crashes with SIGSEGV when I turn off the monitor
While I can reproduce the bug for 100%, only one file is present in /var/crash, and it was an old night crash. I still reported it: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757978 -- 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/1757960 Title: Gnome Shell crashes with SIGSEGV when I turn off the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1757960] Re: Gnome Shell crashes with SIGSEGV when I turn off the monitor
apport information ** Tags added: apport-collected artful ** Description changed: For quite some time, I have seen my gnome-shell session randomly dying on me when I am away from the desktop for quite some time. Only now have I found the reproducable cause: when my monitor is turned off (by power preserving or by pressing the power button), Shell SISSEGVs out of existance. I guess it is highly related to my destop configuration: I use proprietary NVIDIA drivers and my display is connected via DisplayPort, if this gives you ideas. Maybe in the end the bug is in the driver? - Here are some system logs around the time of a crash, maybe it can give - you ideas what to check or whom to blame. If you need any other - information, don't hesitate asking me for it, I will try my best. + Here are some system logs around the time of a crash, maybe it can give you ideas what to check or whom to blame. If you need any other information, don't hesitate asking me for it, I will try my best. + --- + ApportVersion: 2.20.7-0ubuntu3.7 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 17.10 + GsettingsChanges: + org.gnome.shell enabled-extensions ['alternate-...@gnome-shell-extensions.gcampax.github.com', 'workspace-g...@mathematical.coffee.gmail.com', 'panel-...@berend.de.schouwer.gmail.com', 'Per_Window_Keyboard_Layout@nullie-laptop', 'ubuntu-appindicat...@ubuntu.com', 'system-moni...@paradoxxx.zero.gmail.com', 'disconnect-w...@kgshank.net', 'logoutbut...@kyle.aims.ac.za', 'native-window-placem...@gnome-shell-extensions.gcampax.github.com', 'drive-m...@gnome-shell-extensions.gcampax.github.com', 'remove-dropdown-arr...@mpdeimos.com'] + org.gnome.shell command-history ['', 'r'] + org.gnome.shell favorite-apps ['org.gnome.Terminal.desktop', 'org.gnome.Nautilus.desktop', 'google-chrome.desktop'] + org.gnome.desktop.interface gtk-im-module 'ibus' + org.gnome.desktop.interface clock-show-date true + InstallationDate: Installed on 2017-03-05 (381 days ago) + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: gnome-shell 3.26.2-0ubuntu0.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=tmux-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=ru_RU.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 + Tags: artful + Uname: Linux 4.13.0-37-generic x86_64 + UpgradeStatus: Upgraded to artful on 2018-01-11 (69 days ago) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo video wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1757960/+attachment/5086659/+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/1757960 Title: Gnome Shell crashes with SIGSEGV when I turn off the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1757960] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1757960/+attachment/5086660/+files/JournalErrors.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/1757960 Title: Gnome Shell crashes with SIGSEGV when I turn off the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1757960] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1757960/+attachment/5086661/+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/1757960 Title: Gnome Shell crashes with SIGSEGV when I turn off the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1757960] Re: Gnome Shell crashes with SIGSEGV when I turn off the monirot
** Description changed: For quite some time, I have seen my gnome-shell session randomly dying on me when I am away from the desktop for quite some time. Only now have - I found the reproducable cause: when my moni + I found the reproducable cause: when my monitor is turned off (by power + preserving or by pressing the power button), Shell SISSEGVs out of + existance. I guess it is highly related to my destop configuration: I + use proprietary NVIDIA drivers and my display is connected via + DisplayPort, if this gives you ideas. Maybe in the end the bug is in the + driver? + + Here are some system logs around the time of a crash, maybe it can give + you ideas what to check or whom to blame. If you need any other + information, don't hesitate asking me for it, I will try my best. ** Summary changed: - Gnome Shell crashes with SIGSEGV when I turn off the monirot + Gnome Shell crashes with SIGSEGV when I turn off the monitor ** Attachment added: "System journal segment around one of the latest crashes" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757960/+attachment/5086652/+files/gnome-session-related.log -- 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/1757960 Title: Gnome Shell crashes with SIGSEGV when I turn off the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1757960] [NEW] Gnome Shell crashes with SIGSEGV when I turn off the monitor
Public bug reported: For quite some time, I have seen my gnome-shell session randomly dying on me when I am away from the desktop for quite some time. Only now have I found the reproducable cause: when my monitor is turned off (by power preserving or by pressing the power button), Shell SISSEGVs out of existance. I guess it is highly related to my destop configuration: I use proprietary NVIDIA drivers and my display is connected via DisplayPort, if this gives you ideas. Maybe in the end the bug is in the driver? Here are some system logs around the time of a crash, maybe it can give you ideas what to check or whom to blame. If you need any other information, don't hesitate asking me for it, I will try my best. ** Affects: gnome-shell (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 in Ubuntu. https://bugs.launchpad.net/bugs/1757960 Title: Gnome Shell crashes with SIGSEGV when I turn off the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1757961] [NEW] Gnome Shell crashes with SIGSEGV when I turn off the monirot
Public bug reported: For quite some time, I have seen my gnome-shell session randomly dying on me when I am away from the desktop for quite some time. Only now have I found the reproducable cause: when my moni ** Affects: gnome-shell (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 in Ubuntu. https://bugs.launchpad.net/bugs/1757961 Title: Gnome Shell crashes with SIGSEGV when I turn off the monirot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757961/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1360005] Re: Cyrillic symbols looks strange when using autocompletion
Tried on trusty, works fine: touch Файл\ с\ кучей\ пробелов echo ./Фа[TAB pressed]йл\ с\ кучей\ пробелов All symbols look perfectly fine. -- 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/1360005 Title: Cyrillic symbols looks strange when using autocompletion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1360005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
