Hello,
Thank you very much! My apologies for attaching the crash file - I hadn't
realized this might be problematic.
I followed what you indicated (particularly #2) and found the following
links:
https://errors.ubuntu.com/oops/2f0e2248-3008-11eb-8c9b-fa163e983629
https://errors.ubuntu.com/oops/21ec9802-3008-11eb-b997-fa163e102db1
https://errors.ubuntu.com/oops/5fdb36f4-2f3c-11eb-8677-fa163ee63de6

I think I may have erroneously send multiple of the same crash reports - my
apologies if this was the case.
Please let me know if there is anything else I might provide.

Thanks,

Daniel

On Thu, Nov 26, 2020 at 9:15 PM Daniel van Vugt <[email protected]>
wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. It sounds like some part of the system has crashed. To
> help us find the cause of the crash please follow these steps:
>
> 1. Look in /var/crash for crash files and if found run:
>     ubuntu-bug YOURFILE.crash
> Then tell us the ID of the newly-created bug.
>
> 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
> ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
> Do you find any links to recent problems on that page? If so then please
> send the links to us.
>
> 3. If step 2 also failed then apply the workaround from bug 994921,
> reboot, reproduce the crash, and retry step 1.
>
> Please take care to avoid attaching .crash files to bugs as we are
> unable to process them as file attachments. It would also be a security
> risk for yourself.
>
>
> ** Tags added: groovy
>
> ** Changed in: gnome-shell (Ubuntu)
>        Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1905759
>
> Title:
>   gnome-shell crashed with SIGABRT in GI_raise()
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Description:  Ubuntu 20.10
>   Release:      20.10
>
>   In the middle of work screen will randomly glitch green then revert to
>   the login screen - behaviour with both Wayland and not Wayland.
>   Apport.log shows:
>
>   ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: called for pid 2318,
> signal 6, core limit 0, dump mode 1
>   ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: executable:
> /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
>   ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: debug: session gdbus
> call: (true,)
>
>   ERROR: apport (pid 11042) Thu Nov 26 11:51:51 2020: wrote report
>   /var/crash/_usr_bin_gnome-shell.1000.crash
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905759/+subscriptions
>


-- 
Candidate for Bachelors of Science
University of Waterloo

-- 
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/1905759

Title:
  gnome-shell crashed with SIGABRT in GI_raise()

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 20.10
  Release:      20.10

  In the middle of work screen will randomly glitch green then revert to
  the login screen - behaviour with both Wayland and not Wayland.
  Apport.log shows:

  ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: called for pid 2318, 
signal 6, core limit 0, dump mode 1
  ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
  ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: debug: session gdbus 
call: (true,)

  ERROR: apport (pid 11042) Thu Nov 26 11:51:51 2020: wrote report
  /var/crash/_usr_bin_gnome-shell.1000.crash

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to