| 2021-07-25 21:35:58 |
jimav |
bug |
|
|
added bug |
| 2021-07-25 21:35:58 |
jimav |
attachment added |
|
typescript-processed https://bugs.launchpad.net/bugs/1937958/+attachment/5513572/+files/typescript-processed |
|
| 2021-07-25 21:41:57 |
jimav |
description |
I wanted to report a gnome-shell bug with a backtrace, so tried to use the instructions in
https://wiki.gnome.org/Projects/GnomeShell/Debugging
which say to do the following in a separate VT:
gnome_session=$(pgrep -u $USER gnome-session)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DISPLAY)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep XAUTHORITY)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DBUS_SESSION_BUS_ADDRESS)
gdb
...etc...
However three problems came up, two minor (wrong instructions), the other major:
(1) There is more than one gnome-session process, and so the shell variable $gnome_session gets set to a list of several PIDs, which in turn causes syntax errors when using the expression "/proc/$gnome_session/environ".
In Ubuntu 21.04 I have three gnome-session processes immediately after rebooting and logging in (I have auto-login enabled, so the login happens by itself, in case that matters):
$ ps -F $(pgrep -u $USER gnome-session|perl -p -e 's/(\d+)/-p $1/')
UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
jima 9743 9725 0 55216 16084 2 13:41 tty3 00:00:00 /usr/libexec/gnome-session-binary --systemd --session=ubuntu
jima 9828 8066 0 24031 6148 8 13:41 ? 00:00:00 /usr/libexec/gnome-session-ctl --monitor
jima 9838 8066 0 129272 18176 7 13:41 ? 00:00:00 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu
gnome_session=$(pgrep -u $USER gnome-session|head -1)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DISPLAY)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep XAUTHORI
TY)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DBUS_SES
SION_BUS_ADDRESS)
(2) The instructions specify this gdb command:
call gjs_dumpstack ()
However that results in an error and the call is not made: 'gjs_dumpstack' has unknown return type; cast the call to its declared return type
(3) Most importantly, a crash: After after starting gdb in an independent VT to replace the running gnome-session process (or possibly at the moment I switched VTs back to where I could observe the gnome session), the session had immediately gotten a white screen with "Oh No... something went wrong..." forcing me log out.
I swtiched back to the independent VT, typed Control-C to get control in gdb, and produced the backtraces (see attached typescript file).
The attached typescript file shows what I did to circumvent the buggy instructions at https://wiki.gnome.org/Projects/GnomeShell/Debugging
P.S. The original crash I wanted to report was that opening any .jpg in gimp and selecting part of the image and then doing Select->Invert instantly freezes the system. The only recovery is to use a separate VT to kill the gimp process, after which gnome-shell restarts. A system error dialog appears saying gnome-session got a segfault somewhere; thus the desire to get a backtrace. But this bug report is _not_ about that bug, at least not explicitly; it is about how using the debug instructions in the wiki seem to cause a crash on their own.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Sun Jul 25 13:41:54 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-07-20 (5 days ago)
InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 (20210421)
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install) |
I wanted to report a gnome-shell bug with a backtrace, so tried to use the instructions in
https://wiki.gnome.org/Projects/GnomeShell/Debugging
which say to do the following in a separate VT:
gnome_session=$(pgrep -u $USER gnome-session)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DISPLAY)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep XAUTHORITY)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DBUS_SESSION_BUS_ADDRESS)
gdb
...etc...
However three problems came up, two minor (wrong instructions), the other major:
(1) There is more than one gnome-session process, and so the shell variable $gnome_session gets set to a list of several PIDs, which in turn causes syntax errors when using the expression "/proc/$gnome_session/environ".
In Ubuntu 21.04 I have three gnome-session processes immediately after rebooting and logging in (I have auto-login enabled, so the login happens by itself, in case that matters):
$ ps -F $(pgrep -u $USER gnome-session|perl -p -e 's/(\d+)/-p $1/')
UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
jima 9743 9725 0 55216 16084 2 13:41 tty3 00:00:00 /usr/libexec/gnome-session-binary --systemd --session=ubuntu
jima 9828 8066 0 24031 6148 8 13:41 ? 00:00:00 /usr/libexec/gnome-session-ctl --monitor
jima 9838 8066 0 129272 18176 7 13:41 ? 00:00:00 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu
(2) The instructions specify this gdb command:
call gjs_dumpstack ()
However that results in an error and the call is not made: 'gjs_dumpstack' has unknown return type; cast the call to its declared return type
(3) Most importantly, a crash: After after starting gdb in an independent VT to replace the running gnome-session process (or possibly at the moment I switched VTs back to where I could observe the gnome session), the session had immediately gotten a white screen with "Oh No... something went wrong..." forcing me log out.
I swtiched back to the independent VT, typed Control-C to get control in gdb, and produced the backtraces (see attached typescript file).
The attached typescript file shows what I did to circumvent the buggy instructions at https://wiki.gnome.org/Projects/GnomeShell/Debugging
P.S. The original crash I wanted to report was that opening any .jpg in gimp and selecting part of the image and then doing Select->Invert instantly freezes the system. The only recovery is to use a separate VT to kill the gimp process, after which gnome-shell restarts. A system error dialog appears saying gnome-session got a segfault somewhere; thus the desire to get a backtrace. But this bug report is _not_ about that bug, at least not explicitly; it is about how using the debug instructions in the wiki seem to cause a crash on their own.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Sun Jul 25 13:41:54 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-07-20 (5 days ago)
InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 (20210421)
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2021-07-25 21:44:16 |
jimav |
description |
I wanted to report a gnome-shell bug with a backtrace, so tried to use the instructions in
https://wiki.gnome.org/Projects/GnomeShell/Debugging
which say to do the following in a separate VT:
gnome_session=$(pgrep -u $USER gnome-session)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DISPLAY)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep XAUTHORITY)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DBUS_SESSION_BUS_ADDRESS)
gdb
...etc...
However three problems came up, two minor (wrong instructions), the other major:
(1) There is more than one gnome-session process, and so the shell variable $gnome_session gets set to a list of several PIDs, which in turn causes syntax errors when using the expression "/proc/$gnome_session/environ".
In Ubuntu 21.04 I have three gnome-session processes immediately after rebooting and logging in (I have auto-login enabled, so the login happens by itself, in case that matters):
$ ps -F $(pgrep -u $USER gnome-session|perl -p -e 's/(\d+)/-p $1/')
UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
jima 9743 9725 0 55216 16084 2 13:41 tty3 00:00:00 /usr/libexec/gnome-session-binary --systemd --session=ubuntu
jima 9828 8066 0 24031 6148 8 13:41 ? 00:00:00 /usr/libexec/gnome-session-ctl --monitor
jima 9838 8066 0 129272 18176 7 13:41 ? 00:00:00 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu
(2) The instructions specify this gdb command:
call gjs_dumpstack ()
However that results in an error and the call is not made: 'gjs_dumpstack' has unknown return type; cast the call to its declared return type
(3) Most importantly, a crash: After after starting gdb in an independent VT to replace the running gnome-session process (or possibly at the moment I switched VTs back to where I could observe the gnome session), the session had immediately gotten a white screen with "Oh No... something went wrong..." forcing me log out.
I swtiched back to the independent VT, typed Control-C to get control in gdb, and produced the backtraces (see attached typescript file).
The attached typescript file shows what I did to circumvent the buggy instructions at https://wiki.gnome.org/Projects/GnomeShell/Debugging
P.S. The original crash I wanted to report was that opening any .jpg in gimp and selecting part of the image and then doing Select->Invert instantly freezes the system. The only recovery is to use a separate VT to kill the gimp process, after which gnome-shell restarts. A system error dialog appears saying gnome-session got a segfault somewhere; thus the desire to get a backtrace. But this bug report is _not_ about that bug, at least not explicitly; it is about how using the debug instructions in the wiki seem to cause a crash on their own.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Sun Jul 25 13:41:54 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-07-20 (5 days ago)
InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 (20210421)
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install) |
I wanted to report a gnome-shell bug with a backtrace, so tried to use the instructions in
https://wiki.gnome.org/Projects/GnomeShell/Debugging
which say to do the following in a separate VT:
gnome_session=$(pgrep -u $USER gnome-session)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DISPLAY)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep XAUTHORITY)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DBUS_SESSION_BUS_ADDRESS)
gdb
...etc...
However three problems came up, two minor (wrong instructions), the other major:
(1) There is more than one gnome-session process, and so the shell variable $gnome_session gets set to a list of several PIDs, which in turn causes syntax errors when using the expression "/proc/$gnome_session/environ".
In Ubuntu 21.04 I have three gnome-session processes immediately after rebooting and logging in (I have auto-login enabled, so the login happens by itself, in case that matters):
$ ps -F $(pgrep -u $USER gnome-session|perl -p -e 's/(\d+)/-p $1/')
UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
jima 9743 9725 0 55216 16084 2 13:41 tty3 00:00:00 /usr/libexec/gnome-session-binary --systemd --session=ubuntu
jima 9828 8066 0 24031 6148 8 13:41 ? 00:00:00 /usr/libexec/gnome-session-ctl --monitor
jima 9838 8066 0 129272 18176 7 13:41 ? 00:00:00 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu
(2) The instructions specify this gdb command:
call gjs_dumpstack ()
However that results in an error and the call is not made: 'gjs_dumpstack' has unknown return type; cast the call to its declared return type
(3) Most importantly, a crash: After after starting gdb in an independent VT to replace the running gnome-session process (or possibly at the moment I switched VTs back to where I could observe the gnome session), the session had immediately gotten a white screen with "Oh No... something went wrong..." forcing me log out.
I swtiched back to the independent VT, typed Control-C to get control in gdb, and produced the backtraces (see attached typescript file).
The attached typescript file shows what I did to circumvent the buggy instructions at https://wiki.gnome.org/Projects/GnomeShell/Debugging
P.S. The original crash I wanted to report was that opening any .jpg in gimp and selecting part of the image and then doing Select->Invert instantly freezes the system. The only recovery is to use a separate VT to kill the gimp process, after which gnome-shell restarts. A system error dialog appears saying gnome-session [correction: gnome-shell] got a segfault somewhere; thus the desire to get a backtrace. But this bug report is _not_ about that bug, at least not explicitly; it is about how using the debug instructions in the wiki seem to cause a crash on their own.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Sun Jul 25 13:41:54 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-07-20 (5 days ago)
InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 (20210421)
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2021-07-26 02:49:13 |
jimav |
description |
I wanted to report a gnome-shell bug with a backtrace, so tried to use the instructions in
https://wiki.gnome.org/Projects/GnomeShell/Debugging
which say to do the following in a separate VT:
gnome_session=$(pgrep -u $USER gnome-session)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DISPLAY)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep XAUTHORITY)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DBUS_SESSION_BUS_ADDRESS)
gdb
...etc...
However three problems came up, two minor (wrong instructions), the other major:
(1) There is more than one gnome-session process, and so the shell variable $gnome_session gets set to a list of several PIDs, which in turn causes syntax errors when using the expression "/proc/$gnome_session/environ".
In Ubuntu 21.04 I have three gnome-session processes immediately after rebooting and logging in (I have auto-login enabled, so the login happens by itself, in case that matters):
$ ps -F $(pgrep -u $USER gnome-session|perl -p -e 's/(\d+)/-p $1/')
UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
jima 9743 9725 0 55216 16084 2 13:41 tty3 00:00:00 /usr/libexec/gnome-session-binary --systemd --session=ubuntu
jima 9828 8066 0 24031 6148 8 13:41 ? 00:00:00 /usr/libexec/gnome-session-ctl --monitor
jima 9838 8066 0 129272 18176 7 13:41 ? 00:00:00 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu
(2) The instructions specify this gdb command:
call gjs_dumpstack ()
However that results in an error and the call is not made: 'gjs_dumpstack' has unknown return type; cast the call to its declared return type
(3) Most importantly, a crash: After after starting gdb in an independent VT to replace the running gnome-session process (or possibly at the moment I switched VTs back to where I could observe the gnome session), the session had immediately gotten a white screen with "Oh No... something went wrong..." forcing me log out.
I swtiched back to the independent VT, typed Control-C to get control in gdb, and produced the backtraces (see attached typescript file).
The attached typescript file shows what I did to circumvent the buggy instructions at https://wiki.gnome.org/Projects/GnomeShell/Debugging
P.S. The original crash I wanted to report was that opening any .jpg in gimp and selecting part of the image and then doing Select->Invert instantly freezes the system. The only recovery is to use a separate VT to kill the gimp process, after which gnome-shell restarts. A system error dialog appears saying gnome-session [correction: gnome-shell] got a segfault somewhere; thus the desire to get a backtrace. But this bug report is _not_ about that bug, at least not explicitly; it is about how using the debug instructions in the wiki seem to cause a crash on their own.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Sun Jul 25 13:41:54 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-07-20 (5 days ago)
InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 (20210421)
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install) |
I wanted to report a gnome-shell bug with a backtrace, so tried to use the instructions in
https://wiki.gnome.org/Projects/GnomeShell/Debugging
which say to do the following in an ssh login or separate VT:
gnome_session=$(pgrep -u $USER gnome-session)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DISPLAY)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep XAUTHORITY)
eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DBUS_SESSION_BUS_ADDRESS)
gdb
...etc...
However three problems came up, two minor (wrong instructions), the other major:
(1) There is more than one gnome-session process, and so the shell variable $gnome_session gets set to a list of several PIDs, which in turn causes syntax errors when using the expression "/proc/$gnome_session/environ".
In Ubuntu 21.04 I have three gnome-session processes immediately after rebooting and logging in (I have auto-login enabled, so the login happens by itself, in case that matters):
$ ps -F $(pgrep -u $USER gnome-session|perl -p -e 's/(\d+)/-p $1/')
UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
jima 9743 9725 0 55216 16084 2 13:41 tty3 00:00:00 /usr/libexec/gnome-session-binary --systemd --session=ubuntu
jima 9828 8066 0 24031 6148 8 13:41 ? 00:00:00 /usr/libexec/gnome-session-ctl --monitor
jima 9838 8066 0 129272 18176 7 13:41 ? 00:00:00 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu
(2) The instructions specify this gdb command:
call gjs_dumpstack ()
However that results in an error and the call is not made: 'gjs_dumpstack' has unknown return type; cast the call to its declared return type
(3) Most importantly, a crash: Immediately upon starting the new gnome-shell process (with option --replace) a white screen appears with "Oh No... something went wrong..." forcing me log out.
The crash happens whether using an independent VT or an ssh login.
Afterwards I typed Control-C to get control in gdb, and produced the attached backtraces but they don't seem useful (see attached typescript file).
/var/syslog might be useful. I will attach the portion beginning just before starting the new gnome-shell
The attached typescript file shows what I did to circumvent the buggy instructions at https://wiki.gnome.org/Projects/GnomeShell/Debugging
P.S. The original crash I wanted to report was that opening any .jpg in gimp and selecting part of the image and then doing Select->Invert instantly freezes the system. The only recovery is to use a separate VT to kill the gimp process, after which gnome-shell restarts. A system error dialog appears saying gnome-session [correction: gnome-shell] got a segfault somewhere; thus the desire to get a backtrace. But this bug report is _not_ about that bug, but is about how using the debug instructions in the wiki are incorrect and when fixed seem to cause a crash on their own.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Sun Jul 25 13:41:54 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-07-20 (5 days ago)
InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 (20210421)
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2021-07-26 05:11:22 |
jimav |
attachment added |
|
Extrqact from /var/log/syslog https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937958/+attachment/5513619/+files/ex_syslog.txt |
|
| 2021-07-26 05:11:42 |
jimav |
attachment removed |
typescript-processed https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937958/+attachment/5513572/+files/typescript-processed |
|
|
| 2021-07-26 05:12:41 |
jimav |
attachment added |
|
typescript-processed_v2 https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937958/+attachment/5513620/+files/typescript-processed_v2 |
|
| 2021-07-26 06:32:00 |
Daniel van Vugt |
gnome-shell (Ubuntu): status |
New |
Incomplete |
|
| 2021-07-26 06:32:04 |
Daniel van Vugt |
bug |
|
|
added subscriber Daniel van Vugt |
| 2021-07-27 17:06:59 |
jimav |
attachment added |
|
typescript.3-processed https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937958/+attachment/5514109/+files/typescript.3-processed |
|
| 2021-09-04 23:56:43 |
jimav |
bug watch added |
|
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4597 |
|
| 2021-09-06 02:24:25 |
Daniel van Vugt |
bug task added |
|
gnome-shell |
|
| 2021-09-06 02:24:54 |
Daniel van Vugt |
gnome-shell (Ubuntu): status |
Incomplete |
New |
|
| 2022-01-21 03:20:34 |
Daniel van Vugt |
gnome-shell (Ubuntu): status |
New |
Won't Fix |
|
| 2022-10-29 11:21:41 |
Bug Watch Updater |
gnome-shell: status |
Unknown |
Fix Released |
|
