Great. But just a warning; 17.04 reaches end of life this month:
https://wiki.ubuntu.com/Releases
So you will need to upgrade again soon. If you're using gnome-shell then
we recommend 17.10 right now. And before May 2018 we will have 18.04
ready too.
** Changed in: gnome-shell (Ubuntu)
Sta
since upgrading to Ubuntu 17.04, I'm unable to reproduce the crash any
longer FYI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739525
Title:
gnome-shell segfault at e8 in libgdk-3.so.0
To manage
Other readers may want to see also: bug 1741511
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739525
Title:
gnome-shell segfault at e8 in libgdk-3.so.0
To manage notifications about this bug go to
Bah; after sleep + resume, my GDM login had the dreaded "constantly
trying to press enter" problem on it ... (had this in Fedora long time
ago ... can't remember how I fixed it) - anyway - had to
CTRL+ALT+BACKSPACE to kill the gnome-shell and login again ... re-
initiating gdb run
--
You received
Just installed libwxgtk3.0-0v5-dbg. re-running gnome-shell in gdb again
... will see ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739525
Title:
gnome-shell segfault at e8 in libgdk-3.so.0
To
now i'm getting something
{{{
$ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
}}}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
When I run it, it opens the "report" thing, (sorry, Ubuntu 170.4 has
experienced an internal error);
same as before, I click "Continue" and it just disappears (nothing output on
the terminal either)
In analyzing the thread manually, this most recent one appears to be
irrelevant to this report a
Crash files need to have a new bug report created in order for them to
be auto-analysed correctly, and kept private from the public during that
time.
So I think using '-u' is incorrect. Just run:
ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash
It will either open a browser window or print
PS: Don't see the stacktrace auto-uploaded .. hmmm. (in the GUI, I saw
it; but couldn't copy it ;/)
PPS:
https://errors.ubuntu.com/user/1e1145eaed4889fbf4b9b34afdec32bef59b5445c5b86e87b5a55d713b285c7f490cd65ed98cd622a50b4e395de9a91482820e11dada93321d414a30066cc930
(do not yet see my most recent
PS: the annoyance of initially running ubuntu-bug didn't tell me how to
go "-u" ...
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1740967
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739525
On the weekend I upgraded to Ubuntu 17.10;
Amazingly, it crashed again :)
This time, apport is working, AND I get goodies in /var/crash.
{{{
fermulator@fermmy:~$ ll /var/crash
total 120364
drwxrwsrwt 2 root whoopsie 4096 Jan 2 19:45 ./
drwxr-xr-x 17 root root 4096 Dec 29
Also, if you install some debug symbols and then try gdb again then you
should get some more useful output than last time. The relevant debug
packages to start with are:
http://launchpadlibrarian.net/314610069/libgtk-3-0-dbg_3.18.9-1ubuntu3.3_amd64.deb
http://launchpadlibrarian.net/314610070/libgt
OK, can you check this one again? Anything recent?
xdg-open "https://errors.ubuntu.com/user/"`sudo cat /var/lib/whoopsie
/whoopsie-id`
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739525
Title:
g
Not sure what to do, apport is running for sure, but still no gnome-
shell crash files are being generated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739525
Title:
gnome-shell segfault at e8 in
$ ll /var/crash
total 8
drwxrwsrwt 2 root whoopsie 4096 Sep 4 12:12 ./
drwxr-xr-x 18 root root 4096 Feb 11 2017 ../
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
RE 1)
Yes I have PPAs in use: (hopefully it's not a crime ;o) - but, please do let me
know how to isolate one as providing "bad" or perhaps an "old" library?
{{{
/etc/apt/sources.list.d$ find . | egrep "list$"
./wire-desktop.list
./google-earth.list
./webupd8team-ubuntu-atom-xenial.list
./steam.l
(1) This is mildly suspicious. Do you have any PPAs in use?
libcogl20 1.22.0-2 [modified: usr/lib/x86_64-linux-gnu/libcogl.so.20.4.1]
(2) Please check /var/crash for fresh crash files and if found upload
them using the 'ubuntu-bug' command only, and tell us the new bug ID.
And avoid attaching cr
apport information
** Description changed:
As requested by vanvugt in #1580605, submitting a crash unique to my
user.
This isn't fun, several times per day a crash:
{{{
$ dmesg -T | grep seg
[Thu Nov 9 09:58:27 2017] gnome-shell[17846]: segfault at e8 ip
7fd954f6d6a2 sp 7f
dmesg full output from most recent crash
** Attachment added: "dmesg_full.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739525/+attachment/5025857/+files/dmesg_full.txt
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notificat
here's the full "journalctl -xe" output from a most recent crash
** Attachment added: "journalctl_full.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739525/+attachment/5025856/+files/journalctl_full.txt
--
You received this bug notification because you are a member of Ubun
(I think I may have disabled auto-apport reports long ago because of the
constant annoyance) - no reports since `2015-12-15 18:12`
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739525
Title:
gnome-
Hmm, there don't seem to be any instances of the original problem in
those logs.
Can you please try (after reproducing the problem again) attaching full
output from 'journalctl', and also from dmesg? Full logs are fine, but
you may wish to also increase the privacy of the bug report again.
Second
(retracted that categorization as it significantly reduces potential
participants - i self-audited the content and nothing drastic is
revealed; although I filed apport bugs to address it in the future
#1739531 and #1739532)
** Information type changed from Private Security to Public
--
You recei
apport information
** Tags added: apport-collected third-party-packages xenial
** Description changed:
As requested by vanvugt in #1580605, submitting a crash unique to my
user.
This isn't fun, several times per day a crash:
{{{
$ dmesg -T | grep seg
[Thu Nov 9 09:58:27 2017] gnom
PS: the latest logs/reports will indicate that I"m running an `nvidia`
GPU w/ nouveau (previously however I was running Radeon R9 290X w/ open
source Radeon drivers) - so it's not graphics hardware related.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this
Thanks. Please run this command on the affected machine to give us more
information:
apport-collect 1739525
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
26 matches
Mail list logo
