I need help Interpreting Ubuntu 16.04 crash logs

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

I need help Interpreting Ubuntu 16.04 crash logs

Frank Geitzler
I recently installed Ubuntu 16.04 LTS from a 2-year-old DVD onto a
Lenovo desktop system I acquired some time ago.  The system seems to
have a software problem, and I don't know how to interpret the crash
logs.  Over the past three days, the first time I boot the system each
day, I receive a pop-up message (twice) stating that the system has
encountered an error, and offering to create an incident report.  Some
time later, I attempt to download (apt-get install) some software, and
another crash occurs.

I created a folder 'Crash_Logs', and in it a file, crashlist.txt.  To
that file, I redirected the output of the command 'ls -l /var/crash',
and used the resulting filename to create the command required to move
the crash log from /var/crash to 'Crash_Logs'.  I realized while writing
this that I should have used 'ls -l -h' to show the file sizes, and went
back to the Lenovo system to re-issue the command.  The crashlist.txt is
681 bytes in size, the next three files
(_usr-bin_appstreamcil.0.crash...)  are each 8.6M in size, and the
remaining three files (_usr_bin_gnome-software.1000.crash...) are each
18M in size.  I don't know why the user-group shows as 'whoopsie' on
each of these files.

I didn't want to put large logs on the nslug, and I don't know whether
they would expose any security information (root password) for example,
but if you could suggest how I could search for the source of the
problem, I would appreciate it.

Thanks,

Frank Geitzler

# The following commands were used to move crash logs from /var/crash to
Documents/Crash_Logs

mv /var/crash/_usr_bin_gnome-software.1000.crash
Documents/Crash_Logs/_usr_bin_gnome-software.1000.crash_July02_2018

mv /var/crash/_usr_bin_gnome-software.1000.crash
Documents/Crash_Logs/_usr_bin_gnome-software.1000.crash_July03_2018

mv /var/crash/_usr_bin_gnome-software.1000.crash
Documents/Crash_Logs/_usr_bin_gnome-software.1000.crash_July04_2018

mv /var/crash/_usr_bin_appstreamcli.0.crash
Documents/Crash_Logs/_usr_bin_appstreamcli.0.crash_July02_2018

mv /var/crash/_usr_bin_appstreamcli.0.crash
Documents/Crash_Logs/_usr_bin_appstreamcli.0.crash_July03_2018

mv /var/crash/_usr_bin_appstreamcli.0.crash
Documents/Crash_Logs/_usr_bin_appstreamcli.0.crash_July04_2018

# The following is a 'ls -l list of the six crash logs presently in that
folder.
# I copied the file 'crashlist.txt' to a 'Temp' folder on a USB drive,
edited that file
# on the USB drive, and copied the output from my terminal window to the
end of the file.

frank@Lenovo1:~$ cd Documents/Crash_Logs
frank@Lenovo1:~/Documents/Crash_Logs$ ls -l
total 81224
-rw-rw-r-- 1 frank frank         681 Jul  4 14:51 crashlist.txt
-rw-r----- 1 root  whoopsie  8983557 Jul  2 17:35
_usr_bin_appstreamcli.0.crash_July02_2018
-rw-r----- 1 root  whoopsie  8954277 Jul  3 13:39
_usr_bin_appstreamcli.0.crash_July03_2018
-rw-r----- 1 root  whoopsie  8939088 Jul  4 11:20
_usr_bin_appstreamcli.0.crash_July04_2018
-rw-r----- 1 frank whoopsie 18803923 Jul  2 12:57
_usr_bin_gnome-software.1000.crash_July02_2018
-rw-r----- 1 frank whoopsie 18791173 Jul  3 17:08
_usr_bin_gnome-software.1000.crash_July03_2018
-rw-r----- 1 frank whoopsie 18683907 Jul  4 13:58
_usr_bin_gnome-software.1000.crash_July04_2018
frank@Lenovo1:~/Documents/Crash_Logs$



_______________________________________________
nSLUG mailing list
[hidden email]
http://nslug.ns.ca/mailman/listinfo/nslug
Reply | Threaded
Open this post in threaded view
|

Re: I need help Interpreting Ubuntu 16.04 crash logs

George N. White III
On Wed, 4 Jul 2018 at 17:23, Frank Geitzler <[hidden email]> wrote:
I recently installed Ubuntu 16.04 LTS from a 2-year-old DVD onto a
Lenovo desktop system I acquired some time ago.  The system seems to
have a software problem, and I don't know how to interpret the crash
logs. 
Over the past three days, the first time I boot the system each
day, I receive a pop-up message (twice) stating that the system has
encountered an error, and offering to create an incident report.  Some
time later, I attempt to download (apt-get install) some software, and
another crash occurs.

Have you created an incident report?  I've done that many times.
There is 

but it is sufficietly messy that you would only use it when the crash was 
in some non-Ubuntu component.

In my case, there have always been other reports where the same 
bug was encountered (Ubuntu is used in everytime zone, so there 
is always somebody running it). There are often suggestions for 
workarounds, and most problems get passed to upstream and fixes 
arrive with updates.  It is important to have your system completely 
updated before sending an incident report so you don't waste time 
reporting a problem that has already been fixed.  

If your hardware is relatively new (e.g,. more recent than late 2013)
compared to the Ubuntu release, you may need HWE:


I created a folder 'Crash_Logs', and in it a file, crashlist.txt.  To
that file, I redirected the output of the command 'ls -l /var/crash',
and used the resulting filename to create the command required to move
the crash log from /var/crash to 'Crash_Logs'.  I realized while writing
this that I should have used 'ls -l -h' to show the file sizes, and went
back to the Lenovo system to re-issue the command.  The crashlist.txt is
681 bytes in size, the next three files
(_usr-bin_appstreamcil.0.crash...)  are each 8.6M in size, and the
remaining three files (_usr_bin_gnome-software.1000.crash...) are each
18M in size.  I don't know why the user-group shows as 'whoopsie' on
each of these files.

I didn't want to put large logs on the nslug, and I don't know whether
they would expose any security information (root password) for example,
but if you could suggest how I could search for the source of the
problem, I would appreciate it.

Thanks,

Frank Geitzler

# The following commands were used to move crash logs from /var/crash to
Documents/Crash_Logs

mv /var/crash/_usr_bin_gnome-software.1000.crash
Documents/Crash_Logs/_usr_bin_gnome-software.1000.crash_July02_2018

mv /var/crash/_usr_bin_gnome-software.1000.crash
Documents/Crash_Logs/_usr_bin_gnome-software.1000.crash_July03_2018

mv /var/crash/_usr_bin_gnome-software.1000.crash
Documents/Crash_Logs/_usr_bin_gnome-software.1000.crash_July04_2018

mv /var/crash/_usr_bin_appstreamcli.0.crash
Documents/Crash_Logs/_usr_bin_appstreamcli.0.crash_July02_2018

mv /var/crash/_usr_bin_appstreamcli.0.crash
Documents/Crash_Logs/_usr_bin_appstreamcli.0.crash_July03_2018

mv /var/crash/_usr_bin_appstreamcli.0.crash
Documents/Crash_Logs/_usr_bin_appstreamcli.0.crash_July04_2018

# The following is a 'ls -l list of the six crash logs presently in that
folder.
# I copied the file 'crashlist.txt' to a 'Temp' folder on a USB drive,
edited that file
# on the USB drive, and copied the output from my terminal window to the
end of the file.

frank@Lenovo1:~$ cd Documents/Crash_Logs
frank@Lenovo1:~/Documents/Crash_Logs$ ls -l
total 81224
-rw-rw-r-- 1 frank frank         681 Jul  4 14:51 crashlist.txt
-rw-r----- 1 root  whoopsie  8983557 Jul  2 17:35
_usr_bin_appstreamcli.0.crash_July02_2018
-rw-r----- 1 root  whoopsie  8954277 Jul  3 13:39
_usr_bin_appstreamcli.0.crash_July03_2018
-rw-r----- 1 root  whoopsie  8939088 Jul  4 11:20
_usr_bin_appstreamcli.0.crash_July04_2018
-rw-r----- 1 frank whoopsie 18803923 Jul  2 12:57
_usr_bin_gnome-software.1000.crash_July02_2018
-rw-r----- 1 frank whoopsie 18791173 Jul  3 17:08
_usr_bin_gnome-software.1000.crash_July03_2018
-rw-r----- 1 frank whoopsie 18683907 Jul  4 13:58
_usr_bin_gnome-software.1000.crash_July04_2018
frank@Lenovo1:~/Documents/Crash_Logs$



_______________________________________________
nSLUG mailing list
[hidden email]
http://nslug.ns.ca/mailman/listinfo/nslug


--
George N. White III


_______________________________________________
nSLUG mailing list
[hidden email]
http://nslug.ns.ca/mailman/listinfo/nslug
Reply | Threaded
Open this post in threaded view
|

Re: I need help Interpreting Ubuntu 16.04 crash logs

Oliver Doepner
In reply to this post by Frank Geitzler


On Wed, Jul 4, 2018 at 5:22 PM, Frank Geitzler <[hidden email]> wrote:
I recently installed Ubuntu 16.04 LTS from a 2-year-old DVD onto a Lenovo desktop system I acquired some time ago.  The system seems to have a software problem, and I don't know how to interpret the crash logs.  Over the past three days, the first time I boot the system each day, I receive a pop-up message (twice) stating that the system has encountered an error, and offering to create an incident report.  Some time later, I attempt to download (apt-get install) some software, and another crash occurs.

I created a folder 'Crash_Logs', and in it a file, crashlist.txt.  To that file, I redirected the output of the command 'ls -l /var/crash', and used the resulting filename to create the command required to move the crash log from /var/crash to 'Crash_Logs'.  I realized while writing this that I should have used 'ls -l -h' to show the file sizes, and went back to the Lenovo system to re-issue the command.  The crashlist.txt is 681 bytes in size, the next three files (_usr-bin_appstreamcil.0.crash...)  are each 8.6M in size, and the remaining three files (_usr_bin_gnome-software.1000.crash...) are each 18M in size.  I don't know why the user-group shows as 'whoopsie' on each of these files.

I didn't want to put large logs on the nslug, and I don't know whether they would expose any security information (root password) for example, but if you could suggest how I could search for the source of the problem, I would appreciate it.

Thanks,

Frank Geitzler

# The following commands were used to move crash logs from /var/crash to Documents/Crash_Logs

mv /var/crash/_usr_bin_gnome-software.1000.crash Documents/Crash_Logs/_usr_bin_gnome-software.1000.crash_July02_2018

mv /var/crash/_usr_bin_gnome-software.1000.crash Documents/Crash_Logs/_usr_bin_gnome-software.1000.crash_July03_2018

mv /var/crash/_usr_bin_gnome-software.1000.crash Documents/Crash_Logs/_usr_bin_gnome-software.1000.crash_July04_2018

mv /var/crash/_usr_bin_appstreamcli.0.crash Documents/Crash_Logs/_usr_bin_appstreamcli.0.crash_July02_2018

mv /var/crash/_usr_bin_appstreamcli.0.crash Documents/Crash_Logs/_usr_bin_appstreamcli.0.crash_July03_2018

mv /var/crash/_usr_bin_appstreamcli.0.crash Documents/Crash_Logs/_usr_bin_appstreamcli.0.crash_July04_2018

# The following is a 'ls -l list of the six crash logs presently in that folder.
# I copied the file 'crashlist.txt' to a 'Temp' folder on a USB drive, edited that file
# on the USB drive, and copied the output from my terminal window to the end of the file.

frank@Lenovo1:~$ cd Documents/Crash_Logs
frank@Lenovo1:~/Documents/Crash_Logs$ ls -l
total 81224
-rw-rw-r-- 1 frank frank         681 Jul  4 14:51 crashlist.txt
-rw-r----- 1 root  whoopsie  8983557 Jul  2 17:35 _usr_bin_appstreamcli.0.crash_July02_2018
-rw-r----- 1 root  whoopsie  8954277 Jul  3 13:39 _usr_bin_appstreamcli.0.crash_July03_2018
-rw-r----- 1 root  whoopsie  8939088 Jul  4 11:20 _usr_bin_appstreamcli.0.crash_July04_2018
-rw-r----- 1 frank whoopsie 18803923 Jul  2 12:57 _usr_bin_gnome-software.1000.crash_July02_2018
-rw-r----- 1 frank whoopsie 18791173 Jul  3 17:08 _usr_bin_gnome-software.1000.crash_July03_2018
-rw-r----- 1 frank whoopsie 18683907 Jul  4 13:58 _usr_bin_gnome-software.1000.crash_July04_2018
frank@Lenovo1:~/Documents/Crash_Logs$



_______________________________________________
nSLUG mailing list
[hidden email]
http://nslug.ns.ca/mailman/listinfo/nslug


_______________________________________________
nSLUG mailing list
[hidden email]
http://nslug.ns.ca/mailman/listinfo/nslug