I confirm that the crash did not occur with the latest daily-legacy
image, thanks!
ubuntu@ubuntu:~$ cat /media/cdrom/.disk/info
Ubuntu Legacy 23.10 "Mantic Minotaur" - Daily amd64 (20231004)ubuntu@ubuntu:~$
ubuntu@ubuntu:~$ apt-cache policy gnome-shell
gnome-shell:
Installed: 45.0-1ubuntu2
Hopefully this solves it:
https://launchpad.net/ubuntu/+source/gnome-shell/45.0-1ubuntu2
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: gnome-shell (Ubuntu)
Milestone: None => ubuntu-23.10
--
You received this bug notification because you are a
Bug confirmed but it does unfortunately result in bug 2015857, and no
assertion mentioned in the system log.
I think the circumstances are consistent with bug 2036889 though
(asserting on X11 session shutdown), so we should focus on fixing that
first.
** No longer affects: ubiquity (Ubuntu)
**
Oh sorry, I missed the "legacy" part. I'll try and reproduce it this
week.
--
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/2036440
Title:
Choosing "Try Ubuntu" on daily-legacy
Could the gnome-shell crash be a consequence of how we are booting the
Legacy image and starting the desktop environment? I noticed the
following in the crash report "gnome-shell --sm-disable
--mode=ubiquity".
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Changed in: apport (Ubuntu)
Status: New => Invalid
--
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/2036440
Title:
Choosing "Try Ubuntu" on daily-legacy image produced
We could create an /etc/apport/report-ignore/ file with the contents
'/usr/bin/gnome-shell' so then at least the crash report dialog would
not appear. However, after choosing try Ubuntu you presented with a
black screen and some console output so its still not a great
experience.
** Also affects:
Unfortunately that log doesn't contain a gnome-shell crash.
--
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/2036440
Title:
Choosing "Try Ubuntu" on daily-legacy image produced
The gnome-shell crash is easily reproducible by choosing Try Ubuntu when
using a mantic desktop legacy image.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2036440/+attachment/5703615/+files/journal.txt
--
You received this bug notification
I have more questions than answers now...
* It looks like source_gnome-shell.py already attaches journalctl
output, so why didn't it here?
* data/general-hooks/generic.py also attaches journal errors, so why
didn't it here?
* Do we really want all Ubuntu bug reports to have journal data that
Oh, in that case you'll want to look at /usr/share/apport/general-
hooks/ubuntu.py which is provided by the apport package.
--
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/2036440
I meant all bug reports, not just gnome-shell. But gnome-shell is the
best place to start.
--
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/2036440
Title:
Choosing "Try Ubuntu"
gnome-shell already ships an apport package hook which is installed in
/usr/share/apport/package-hooks/source_gnome-shell.py and that seems to
be debian/source_gnome-shell.py from the source package. It should be
relatively straight forward to modify that and an update to it is
something the SRU
Indeed I've been meaning to learn about apport because I would like ALL
bug reports to automatically come with:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Couldn't we modify the apport hook for gnome-shell to gather the
relevant log file when ever there is a 'Signal: 6' in the crash report?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Signal 6 is SIGABRT which usually means an assertion failed, which means
the system log will contain an explanation. Next time it happens please
run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Changed in: gnome-shell (Ubuntu)
Status: Invalid => Incomplete
Since this crash is about gnome-shell, maybe this is just another case
of bug #2015857?
--
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/2036440
Title:
Choosing "Try Ubuntu" on
I'm manually able to retrace the crash file from comment #4, although
that fails, with the apport. Perhaps there is a period of time where the
core dump is not attached to the crash file?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
This bears some investigation into whether or not the core dump is
actually a part of the crash file and if not why it isn't. We want to be
able to provide crash reports from the live environment.
** Tags added: rls-mm-incoming
--
You received this bug notification because you are a member of
I'm attaching the crash file which does have a CoreDump section.
** Attachment added: "_usr_bin_gnome-shell.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2036440/+attachment/5701823/+files/_usr_bin_gnome-shell.1000.crash
** Also affects: apport (Ubuntu)
20 matches
Mail list logo
