[Bug 1988315] Re: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter-actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_children < prev_n_childr
vanvugt, Thanks! That resolved the issue. -- 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/1988315 Title: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter- actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_children < prev_n_children)] in indicatorStatusIcon.js:317 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1988315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1988315] Re: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter-actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_children < prev_n_childr
I'm seeing this as well. I have a Wayland session, from which I ssh to another host and run geany (forwarded over ssh). Gnome-shell immediately crashes. Interestingly, forwarding xterm from the remote host does not cause a crash. -- 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/1988315 Title: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter- actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_children < prev_n_children)] in indicatorStatusIcon.js:317 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1988315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1988785] Re: ssh tunneling geany crashes session, forcing logout
Here is some info from the crash file. More is available upon request.
(I opened a separate bug for the failure to upload the crash file at
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1988870 )
Title: gnome-shell crashed with SIGABRT in
__pthread_kill_implementation()
SourcePackage: gnome-shell
Stacktrace:
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=) at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {94469445361920}}
ret =
pd =
old_mask =
ret =
tid =
ret =
resultvar =
resultvar =
__arg3 =
__arg2 =
__arg1 =
_a3 =
_a2 =
_a1 =
__futex =
resultvar =
__arg3 =
__arg2 =
__arg1 =
_a3 =
_a2 =
_a1 =
__futex =
__private =
__oldval =
result =
#1 __pthread_kill_internal (signo=6, threadid=) at
./nptl/pthread_kill.c:78
No locals.
#2 __GI___pthread_kill (threadid=, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
No locals.
#3 0x7fb038c0ec86 in __GI_raise (sig=6) at ../sysdeps/posix/raise.c:26
ret =
#4 0x55eb60f2875a in ?? ()
No symbol table info available.
#5
No locals.
#6 __pthread_kill_implementation (no_tid=0, signo=6, threadid=) at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {140394860070080}}
ret =
pd =
old_mask =
ret =
tid =
ret =
resultvar =
resultvar =
__arg3 =
__arg2 =
__arg1 =
_a3 =
_a2 =
_a1 =
__futex =
resultvar =
__arg3 =
__arg2 =
__arg1 =
_a3 =
_a2 =
_a1 =
__futex =
__private =
__oldval =
result =
#7 __pthread_kill_internal (signo=6, threadid=) at
./nptl/pthread_kill.c:78
No locals.
#8 __GI___pthread_kill (threadid=, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
No locals.
#9 0x7fb038c0ec86 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
ret =
#10 0x7fb038bf57fc in __GI_abort () at ./stdlib/abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20},
sa_mask = {__val = {94469495400448, 140722215299608, 140394859298631,
94469470593536, 31073787738849280, 94469463025520, 0, 140722215299600,
9419948534719163136, 94469438431424, 18446744073709551488, 0, 140394860072416,
140394848174200, 140722215299712, 140394860171744}}, sa_flags = 952580291,
sa_restorer = 0x7fb0390d8015}
#11 0x7fb039b1bd03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#12 0x7fb039b75e9e in g_assertion_message_expr () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#13 0x7fb03905cdb2 in clutter_actor_destroy_all_children () from
/usr/lib/x86_64-linux-gnu/mutter-11/libmutter-clutter-11.so.0
No symbol table info available.
#14 0x7fb039c4ae95 in g_closure_invoke () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#15 0x7fb039c78de4 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#16 0x7fb039c6911a in g_signal_emit_valist () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#17 0x7fb039c693a3 in g_signal_emit () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#18 0x7fb039057780 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-11/libmutter-clutter-11.so.0
No symbol table info available.
#19 0x7fb038b88055 in ?? () from /usr/lib/gnome-shell/libst-1.0.so
No symbol table info available.
#20 0x7fb039c595f0 in g_object_run_dispose () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#21 0x7fb03905b23b in clutter_actor_destroy () from
/usr/lib/x86_64-linux-gnu/mutter-11/libmutter-clutter-11.so.0
No symbol table info available.
#22 0x7fb03905cd80 in clutter_actor_destroy_all_children () from
/usr/lib/x86_64-linux-gnu/mutter-11/libmutter-clutter-11.so.0
No symbol table info available.
#23 0x7fb039c4af60 in g_closure_invoke () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#24 0x7fb039c78de4 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#25 0x7fb039c6911a in g_signal_emit_valist () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#26 0x7fb039c693a3 in g_signal_emit () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#27 0x7fb039057780 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-11/libmutter-clutt
[Bug 1988785] [NEW] ssh tunneling geany crashes session, forcing logout
Public bug reported: ssh to a host forwarding X, and open geany on remote host. The entire session crashes, and I get logged out. I'm assuming this is a mutter issue? I have always been able to forward geany over ssh before. Both machines are running ubuntu 20.10/dev/kinetic, with kernel 6.0-rc4. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mutter 43~beta-3ubuntu2 Uname: Linux 6.0.0-rc4 x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 5 18:32:22 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1988785 Title: ssh tunneling geany crashes session, forcing logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1988785/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
Also seeing this issue on a Raspberry Pi 4B, so it isn't just limited to x86_64 arch... -- 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/1969243 Title: gdm 42.0-1ubuntu4 no longer shows Wayland option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1944397] Re: HDMI does not display anything with Impish RPi desktop image
@jawn-smith, I'm using this display: https://www.waveshare.com/5.5inch-hdmi-amoled-with-case.htm with this cmdline.txt: console=tty1 root=LABEL=writable rootfstype=ext4 rootwait quiet splash video=HDMI-A-1:1080x1920M@60,rotate=90,panel_orientation=right_side_up drm.edid_firmware=edid/Waveshare5.5Amoled4.bin fbcon=rotate:1 fsck.mode=force fsck.repair=yes and that edid file is attached. ** Attachment added: "Waveshare5.5Amoled4.bin" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1944397/+attachment/5531697/+files/Waveshare5.5Amoled4.bin -- 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/1944397 Title: HDMI does not display anything with Impish RPi desktop image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1944397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1944397] Re: HDMI does not display anything with Impish RPi desktop image
I'm also seeing this same issue with a 5.15-rc4 kernel built from https://github.com/raspberrypi/linux/tree/rpi-5.15.y [ 408.326395] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:77:crtc-3] flip_done timed out [ 408.326477] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 408.326711] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:77:crtc-3] commit wait timed out -- 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/1944397 Title: HDMI does not display anything with Impish RPi desktop image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1944397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1944397] Re: HDMI does not display anything with Impish RPi desktop image
@vanvugt would you be willing to open an issue about this at https://github.com/raspberrypi/linux/issues since this does look like a kernel issue? -- 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/1944397 Title: HDMI does not display anything with Impish RPi desktop image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1944397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1895721] Re: Wayland not allowing Fractional Scaling to be set
*** This bug is a duplicate of bug 1894593 *** https://bugs.launchpad.net/bugs/1894593 ** This bug has been marked a duplicate of bug 1894593 Fractional scaling switch doesn't work -- 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/1895721 Title: Wayland not allowing Fractional Scaling to be set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1895721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1895721] Re: Wayland not allowing Fractional Scaling to be set
Dmesg: https://paste.ubuntu.com/p/jNCR2qTKWQ/ Also maybe seeing this error: Sep 15 13:37:15 nocturne gnome-control-c[2021]: file ../panels/display/cc-display-config.c: line 452 (get_fractional_scaling_key): should not be reached ** Also affects: gnome-control-center (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/1895721 Title: Wayland not allowing Fractional Scaling to be set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1895721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1895721] [NEW] Wayland not allowing Fractional Scaling to be set
Public bug reported: Setting Fractional Scaling in the X11 Gnome Session is working fine. I can set the 3000x2000 screen to 150%. In the Gnome-Wayland Session, the Fractional Scaling Toggle doesn't stick, and I don't see any fractional scaling percentage options show up. (Running a slightly customized 5.9-rc5 kernel to get backlight working, but otherwise everything is pretty ordinary for some values of ordinary.) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: mutter 3.37.91-1ubuntu1 Uname: Linux 5.9.0-rc5-dpcdon x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 15 13:40:08 2020 InstallationDate: Installed on 2020-08-24 (21 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200728) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy wayland-session -- 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/1895721 Title: Wayland not allowing Fractional Scaling to be set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1895721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)
@vorlon it is in the graphic which shows up in the GUI surrounding the checkbox to enable -proposed here: https://wiki.ubuntu.com/Testing/EnableProposed?action=AttachFile&do=get&target=devoptions_1604.png Thank you @knox for the clarification. This was largely my fault for doing a 's/focal/groovy/g' in my sources.list. I can't speak to whether the GUI source selection interface allows one to add -proposed to the primary sources.list when the devel series is running though. Is there a way to tell apt that packages which have a dependency upon libffi7 should absolutely not be mixed with packages which depend upon libffi8 because there is a breaking change? (I imagine there is no automated way to notice that hey data structures have changed between library versions.) And for the benefit of users in the future who accidentally hit this sort of issue, can anyone recommend a best practices way to downgrade all packages which are for instance built against libffi8ubuntu1? -- 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/1892915 Title: gnome-shell crashing (libffi8ubuntu1 upgrade issue) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892915/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)
Fully aware that proposed is not supported, and that this may cause instability. Just trying to be helpful as per https://wiki.ubuntu.com/Testing/EnableProposed "Proposed updates are only for testing updates and providing development feedback. Enabling this may introduce instability." This bug report was intended to help provide development feedback. -- 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/1892915 Title: gnome-shell crashing (libffi8ubuntu1 upgrade issue) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892915/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892915] Re: gnome-shell crashing with Wayland
This problem went away once I stopped using groovy-proposed and (painfully) removed libffi8ubuntu1 and all dependencies which used it. ** Also affects: libffi (Ubuntu) Importance: Undecided Status: New ** Summary changed: - gnome-shell crashing with Wayland + gnome-shell crashing (libffi8 upgrade issue) ** Summary changed: - gnome-shell crashing (libffi8 upgrade issue) + gnome-shell crashing (libffi8ubuntu1 upgrade issue) -- 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/1892915 Title: gnome-shell crashing (libffi8ubuntu1 upgrade issue) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892915/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892915] [NEW] gnome-shell crashing with Wayland
Public bug reported: Seeing this on groovy installs after an update. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.4-1ubuntu2~build1 Uname: Linux 5.8.3-050803-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 25 15:49:17 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-19 (311 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2 ShellJournal: -- Logs begin at Tue 2020-06-16 11:50:01 EDT, end at Tue 2020-08-25 15:49:37 EDT. -- -- No entries -- SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-08-10T16:14:34.416087 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages -- 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/1892915 Title: gnome-shell crashing with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892915/+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
I'm still seeing this issue on resume from sleep today on my updated 19.10 setup with gnome-shell 3.34.0-1ubuntu1. For what it is worth I also see this in my dmesg at boot: [ 19.404177] gnome-shell[3485]: segfault at 18 ip 7f82407d4924 sp 7ffeb4e50f08 error 4 in libmutter-5.so.0.0.0[7f82406e7000+f2000] [ 19.404192] Code: c3 0f 1f 44 00 00 f3 0f 1e fa 8b 47 30 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 8b 47 34 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <48> 8b 47 18 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 41 54 53 48 89 fb -- 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 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
I fixed the workaround script mentioned above here:
https://gist.github.com/satmandu/2f2da70a7a6bbbacdba01ef8fb8c18f4
This "works" on my system.
(dbus-send doesn't get the right info to work unless you give it the
info of the logged in user, which "machinectl shell" can do.)
Hopefully the fix gets merged soon and I can stop using this ugly hack.
:)
#!/bin/bash
# Place file in /lib/systemd/system-sleep/
# Run chmod +x on the file.
# This works around the wallpaper corruption on resume from suspend with Nvidia
GPUs
# reported at https://gitlab.gnome.org/GNOME/gnome-shell/issues/1084
# and due to this feature of the Nvidia driver:
#
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt
# Adapted from Paul Knopf
(https://gitlab.gnome.org/GNOME/gnome-shell/issues/1084)
# and via
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407/comments/22
# Note that this does show the user's screen when coming out of sleep briefly.
# machinectl can be found in the systemd-container package on Ubuntu.
PROGNAME=$(/usr/bin/basename "$0")
state=$1
action=$2
function log {
/usr/bin/logger -i -t "$PROGNAME" "$*"
}
log "Running $action $state"
if [[ $state == post ]]; then
log "WAKE UP"
pid_Gnome=($(/usr/bin/pgrep gnome-session))
pid_Gnome=("${pid_Gnome[@]%%:*}")
command="/usr/bin/dbus-send --type=method_call --dest=org.gnome.Shell
/org/gnome/Shell org.gnome.Shell.Eval "string:global.reexec_self\(\)""
for i in "${pid_Gnome[@]}"
do
user=$(/bin/ps -o user= -p $i)
log $i $user
if [ "$user" != "gdm" ]; then
log "machinectl shell $user@.host $command"
/bin/machinectl shell $user@.host $command
fi
done
fi
exit 0
--
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
