[Desktop-packages] [Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])

2022-04-22 Thread Daniel van Vugt
Bug 1964037 mentions a similar stack trace so maybe that was the problem
all along.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1964120

Title:
  gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access
  memory at address [in stack])

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Desktop has some issues but it was not showable

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu1
  Uname: Linux 5.16.12-051612-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  7 12:12:08 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-03-04 (4 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f0d7aec5a7c in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffce8d834a0
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to jammy on 2022-03-04 (4 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])

2022-04-20 Thread Daniel van Vugt
Looks like I hit this today in a Xorg session when testing Nvidia.

The log provides no details of what caused the crash other than the
system was shutting down/logging out at the time.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1964120

Title:
  gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access
  memory at address [in stack])

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Desktop has some issues but it was not showable

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu1
  Uname: Linux 5.16.12-051612-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  7 12:12:08 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-03-04 (4 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f0d7aec5a7c in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffce8d834a0
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to jammy on 2022-03-04 (4 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])

2022-04-13 Thread Rafal
Got directed here from bug (private due to coredump attachement) that
Daniel marked a duplicate of this one.

I can reliably reproduce my original issue following:

1. Fresh boot
2. Connect external monitors
3. Put laptop to sleep
4. Wake laptop from sleep (one of two external monitors is still black)
5. Go to Settings -> Display (Gnome thinks both monitors are enabled)
6. Disable the black monitor and enable it again.
7. Gnome enables the problematic monitor for a split second and then disables 
it instantly. 

Attaching prevboot.txt for the above.

I have so far two workarounds for my issue

Workaround 1:
- go to TTY3 with Ctrl+Alt+F3 (no need to log in, just wait for all monitors to 
work)
- go to TTY1 with Ctrl+Alt+F1 (lands on GDM log in page, I log in)
- all monitors now work and applications are preserved (sometimes need to 
enable it in settings)

Workaround 2:
- power cycle the black monitor (but without messing with Settings -> Display 
first)


Happy to provide more information or test solutions. It was driving me crazy to 
at least figure out reproducibility pattern and possible workarounds (stayed 
until 3am one night experimenting...). 

Not sure if useful but I also learned:
- happens also on kernel 5.17 from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.17.2/amd64/
- happens also on live usb session from Ubuntu 22.04 so not likely my local 
changes
- does not happen on live usb of fedora 36 beta (tested as it also has gnome 42)

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+attachment/5580363/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1964120

Title:
  gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access
  memory at address [in stack])

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Desktop has some issues but it was not showable

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu1
  Uname: Linux 5.16.12-051612-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  7 12:12:08 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-03-04 (4 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f0d7aec5a7c in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffce8d834a0
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to jammy on 2022-03-04 (4 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])

2022-04-04 Thread Daniel van Vugt
If anyone can reproduce this crash then please:

1. Reproduce the crash.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.


** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1964120

Title:
  gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access
  memory at address [in stack])

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Desktop has some issues but it was not showable

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu1
  Uname: Linux 5.16.12-051612-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  7 12:12:08 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-03-04 (4 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f0d7aec5a7c in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffce8d834a0
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to jammy on 2022-03-04 (4 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])

2022-04-03 Thread Daniel van Vugt
It appears the address of a stack variable has overwritten the return
address for the offending function call. So we have no stack trace.

I wonder if there's a way to catch stack corruption without going so far
as Valgrind...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1964120

Title:
  gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access
  memory at address [in stack])

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Desktop has some issues but it was not showable

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu1
  Uname: Linux 5.16.12-051612-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  7 12:12:08 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-03-04 (4 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f0d7aec5a7c in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffce8d834a0
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to jammy on 2022-03-04 (4 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])

2022-04-01 Thread Daniel van Vugt
I think the final address ending in a7c is probably raise() so that may
not be useful information.

This is starting to smell like stack corruption.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1964120

Title:
  gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access
  memory at address [in stack])

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Desktop has some issues but it was not showable

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu1
  Uname: Linux 5.16.12-051612-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  7 12:12:08 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-03-04 (4 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f0d7aec5a7c in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffce8d834a0
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to jammy on 2022-03-04 (4 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from [Cannot access memory at address]

2022-04-01 Thread Daniel van Vugt
All the duplicates seem to get stuck at addresses in [stack] according
to ProcMaps.txt. The crash reports all say "Backtrace stopped: Cannot
access memory at address", but ProcMaps.txt seems to indicate it's a
valid stack address (read-write memory, but not executable).

** Summary changed:

- gnome-shell crashed with SIGSEGV at ?+a7c called from [heap address]
+ gnome-shell crashed with SIGSEGV at ?+a7c called from [Cannot access memory 
at address]

** Summary changed:

- gnome-shell crashed with SIGSEGV at ?+a7c called from [Cannot access memory 
at address]
+ gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory 
at address [in stack])

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1964120

Title:
  gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access
  memory at address [in stack])

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Desktop has some issues but it was not showable

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu1
  Uname: Linux 5.16.12-051612-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  7 12:12:08 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-03-04 (4 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f0d7aec5a7c in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffce8d834a0
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to jammy on 2022-03-04 (4 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp