[Bug 1728588] Re: session crashed with wl_registry@2: error 0: invalid global wl_o utput (36) after kernel: [drm:intel_mst_disable_dp [i915]] *ERROR* failed to upd ate payload -22
** Description changed: I turned off my screen for a few hours then turned it on again and my session was no longer there and i had to login again. The following lines from syslog at the time that i turned on the screen again look suspicious. My hypothesis is that the error from the Intel kernel driver caused the "Fatal server error" "wl_registry@2: error 0: invalid global wl_o - utput (36)" in gnome-shell. Since the screen is actually still operational, what should have happened is that gnome-shell should have gracefully dealt with whatever happened without a fatal error. - + utput (36)" in gnome-shell. Since the screen is actually still operational (after all, the computer didn't crash, only that session, and i was immediately shown the login screen and able to login again), what should have happened is that gnome-shell should have gracefully dealt with whatever happened without a fatal error. Oct 30 05:46:16 bshanks-SP4 kernel: [358036.641989] [drm:intel_mst_disable_dp [i915]] *ERROR* failed to upd ate payload -22 Oct 30 05:46:16 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563dd13c c40 Gjs_ShowAppsIcon.dash-item-container] connect method - Oct 30 05:46:16 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563dd13c - c40 Gjs_ShowAppsIcon.dash-item-container] disconnect method - Oct 30 05:46:16 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563dd13c - c40 Gjs_ShowAppsIcon.dash-item-container] emit method - Oct 30 05:46:16 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563dd33d - 540 Gjs_ShowAppsIcon.dash-item-container] connect method - Oct 30 05:46:16 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563dd33d - 540 Gjs_ShowAppsIcon.dash-item-container] disconnect method - Oct 30 05:46:16 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563dd33d - 540 Gjs_ShowAppsIcon.dash-item-container] emit method - Oct 30 05:46:17 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563dbbe0 - 280 Gjs_ShowAppsIcon.dash-item-container] connect method - Oct 30 05:46:17 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563dbbe0 - 280 Gjs_ShowAppsIcon.dash-item-container] disconnect method - Oct 30 05:46:17 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563dbbe0 - 280 Gjs_ShowAppsIcon.dash-item-container] emit method - Oct 30 05:46:17 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563d8952 - d00 Gjs_ShowAppsIcon.dash-item-container] connect method - Oct 30 05:46:17 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563d8952 - d00 Gjs_ShowAppsIcon.dash-item-container] disconnect method - Oct 30 05:46:17 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563d8952 - d00 Gjs_ShowAppsIcon.dash-item-container] emit method - Oct 30 05:46:18 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563df178 - 040 Gjs_ShowAppsIcon.dash-item-container] connect method - Oct 30 05:46:18 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563df178 - 040 Gjs_ShowAppsIcon.dash-item-container] disconnect method - Oct 30 05:46:18 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563df178 - 040 Gjs_ShowAppsIcon.dash-item-container] emit method - Oct 30 05:46:18 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563dcaa9 - 040 Gjs_ShowAppsIcon.dash-item-container] connect method - Oct 30 05:46:18 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563dcaa9 - 040 Gjs_ShowAppsIcon.dash-item-container] disconnect method - Oct 30 05:46:18 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563dcaa9 - 040 Gjs_ShowAppsIcon.dash-item-container] emit method + ... + (a bunch of similar warnings about addSignalMethods) + ... Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: (EE) Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: Fatal server error: Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: (EE) wl_registry@2: error 0: invalid global wl_o utput (36) Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: (EE) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 06:01:36 2017 DisplayManager: gdm3 InstallationDate: Installed on 2016-04-06 (572 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
[Bug 1728588] [NEW] session crashed with wl_registry@2: error 0: invalid global wl_output (36) after kernel: [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22
Public bug reported: I turned off my screen for a few hours then turned it on again and my session was no longer there and i had to login again. The following lines from syslog at the time that i turned on the screen again look suspicious. My hypothesis is that the error from the Intel kernel driver caused the "Fatal server error" "wl_registry@2: error 0: invalid global wl_output (36)" in gnome-shell. Since the screen is actually still operational (after all, the computer didn't crash, only that session, and i was immediately shown the login screen and able to login again), what should have happened is that gnome-shell should have gracefully dealt with whatever happened without a fatal error. This is the first time this has happened, and it did not used to happen before my upgrade to Artful a few days ago. Oct 30 05:46:16 bshanks-SP4 kernel: [358036.641989] [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22 Oct 30 05:46:16 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563dd13c c40 Gjs_ShowAppsIcon.dash-item-container] connect method ... (a bunch of similar warnings about addSignalMethods) ... Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: (EE) Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: Fatal server error: Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: (EE) wl_registry@2: error 0: invalid global wl_output (36) Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: (EE) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 06:01:36 2017 DisplayManager: gdm3 InstallationDate: Installed on 2016-04-06 (572 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-26 (4 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful 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/1728588 Title: session crashed with wl_registry@2: error 0: invalid global wl_output (36) after kernel: [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728588/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 850649] Re: gnome-terminal extremely slow and display buggy
*** This bug is a duplicate of bug 877438 *** https://bugs.launchpad.net/bugs/877438 There are multiple bugs being discussed in this thread, all of which fit the title and bug description at the top, but some of which are limited to various situations, and some of which are not. Not all of them are duplicates of bug #877438, and so the duplicate status should probably be removed. A request was made above for ubuntu-bug xorg, so here's one: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/919470 Note that in the case of bug 919470, there is slowness but no display corruption; bug DOES occur in Unity-2D; bug DOES occur in terminator as well as gnome-terminal; bug DOES NOT occur with xterm. -- 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/850649 Title: gnome-terminal extremely slow and display buggy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/850649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 850649] Re: gnome-terminal extremely slow and display buggy
*** This bug is a duplicate of bug 877438 *** https://bugs.launchpad.net/bugs/877438 p.s. i think importance should be greater than low for this bug; having a terminal with a lot of information being rapidly printed to it is an extremely common situation. -- 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/850649 Title: gnome-terminal extremely slow and display buggy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/850649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 726431] Re: session saving (wishlist)
thanks, no, I don't plan to work on it, I'm just interested in the feature, particularly for window placement (I'm less interested in resumption of state within the application). At the current time, I know of no way in Ubuntu 11.04 to have applications startup automatically upon login and appear at specified Compiz viewports. Devilspie apparently can only send windows to the first row of Compiz viewports ( https://bugs.launchpad.net/ubuntu/+source/devilspie/+bug/380880 ), and Compiz's Place Windows feature only works sporadically on windows created by Startup Applications ( https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/727098 ). -- 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/726431 Title: session saving (wishlist) -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
