Thanks.
Our next option is to try attaching a few more .crash files to this bug.
Maybe one or two will be more human-readable. So I will make this bug
private from now on so you can do that with some security...
** Information type changed from Public to Private
** Changed in: gnome-shell
I deleted all entries in /var/crash and /var/lib/whoopsie.
I recreated the problem
ls -l /var/crash
total 92136
-rw-r- 1 fbacher whoopsie 40426131 Sep 14 14:52
_usr_bin_gnome-shell.1000.crash
-rw-r- 1 fbacher whoopsie 6167683 Sep 14 14:53 _usr_bin_Xwayland.1000.crash
-rw-r- 1
Also, if the tools aren't working for you then please tell their
maintainers by logging an additional bug here:
https://bugs.launchpad.net/ubuntu/+source/apport/+filebug
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell
Frank,
Sorry to hear things aren't working for you. I have read through your
files and:
_usr_bin_Xwayland.1000.crash: Stack trace mostly unreadable (missing symbols)
_usr_bin_gnome-shell.1000.crash: Stack trace is missing
Please confirm that you have tried both:
(a) Running this in a
** Attachment added: "Other means of delivering failed"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789962/+attachment/5188578/+files/_usr_bin_gnome-shell.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Attachment added: "Other means of delivering failed"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789962/+attachment/5188579/+files/_usr_bin_Xwayland.1000.crash
** Changed in: gnome-shell (Ubuntu)
Status: Invalid => New
--
You received this bug notification because
You can upload the .crash file to this bug report with help of the "Add
attachment or patch" button at the end of the bug page which opens this link:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789962/+addcomment
--
You received this bug notification because you are a member of
There appears to be no way to report a Wayland / gnome-shell crash. I
can create the .crash files, but they are never uploaded. I have spent
over 8 hours trying to do this but none of the suggestions have worked.
I think the bug reporting tools are broken for Wayland, but I am tired
of fighting
I give up. I have spent over 8 hours trying to report bug 1789962.
Nothing suggested works. I can create the .crash files, see a traceback,
etc. but it is never uploaded. I think that the bug reporting tools
don't take wayland into account and silently barf. If Ubuntu ever
decides to fix these
Frank,
Please also check your:
https://errors.ubuntu.com/user/
again, where is the content of:
/var/lib/whoopsie/whoopsie-id
When opening that page, please leave it open for at least 10 seconds as
it usually takes some time to populate. If that page shows any recent
links then please
Thanks Frank. Unfortunately the -p option is not helpful here.
Please run something like:
apport-cli /path/to/your/FILE.crash
and if it tells you again:
https://bugs.launchpad.net/ubuntu/+source/xorg/+filebug/...
then please click on or copy that link and then complete the process of
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
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/1789962
Title:
gnome-shell segfaults in Wayland when
I'm not sure if it worked or not, but here is what I did to try to
upload .crash
apport-cli -f
It asked what type of problem, I selected "1: Display (X.org)", which isn't
quite right since this is for Wayland, but there was not a better answer.
When asked what kind of display problem I had, I
Thanks for your efforts.
It sounds like the GUI version of apport is broken or at least not able
to give us the information we want.
Please try using 'apport-cli' in a terminal instead, which should then
print the URL of the bug report.
** Changed in: gnome-shell (Ubuntu)
Status: New =>
I have crash files, but need help uploading them. Please see last
several comments.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I have tried multiple other ways to get the crash data uploaded. Would
it help if I copied it up to my dropbox so that you could get it?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Running ubuntu-bug under Xorg gnome-shell exits very quickly. But still no
evidence that crash data was uploaded. Do I have to delete the .upload file and
rerun?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
After much grief, I realized that apport was disabled (I probably did
this in 12.04 days when it would constantly bug me to report something).
I had to do a complete uninstall and reinstall of it. Anyway, it works
now.
ubuntu-bug, however, does not appear to be doing it's thing. I'm running
it
There was NO crash file. I followed the steps above. They pointed to
documents that said that I needed to install debug symbols.
Anyway, it appears that there is no core file because my core ulimit is
0. This seems to be a side-effect of installing 18.04 on top of 16.04,
but I can't go back to
You don't need the debug symbols on your machine. After a crash file is
sent and a new bug automatically created, it gets retraced "in"
launchpad. Sometimes though, only an "error" report is created. That's
similar but the crash information goes to errors.ubuntu.com instead of
launchpad.
So
Had to manually get debug symbols for gnome-shell and libmutter. Not
sure where the crash or core file for gnome-shell goes. If all else
fails I could use strace or watch what files are created...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
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
22 matches
Mail list logo
