do not see what kind of report is being submitted - no details provided

Asked by crysman on 2019-09-24

Every (re)boot, I got this error popup window displayed. It is quite new, earlier Xubuntu versions had not been having this issue. The problem is: what is it about? There are no details whatsoever :/ I will attach a screenshot next reboot...

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: update-notifier 3.192.18
ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Sep 24 09:33:27 2019
ExecutablePath: /usr/bin/update-notifier
InstallationDate: Installed on 2018-09-03 (385 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: update-notifier
UpgradeStatus: Upgraded to disco on 2019-06-16 (99 days ago)

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu update-notifier Edit question
Assignee:
No assignee Edit question
Solved by:
Chris Guiver
Solved:
2019-09-24
Last query:
2019-09-24
Last reply:
2019-09-24
Chris Guiver (guiverc) said : #1

Thank you for taking the time to report this issue and helping to make Ubuntu better.

Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker.

We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs.

You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709

Chris Guiver (guiverc) said : #2

Thank you for taking the time to report this bug and helping to make Ubuntu better.

The message you see "System program problem detected ... Do you want to report.." indicates a crash occurs, and is asking for your permission to submit the crash report. You can find the crash file located in the directory /var/crash/

Looking in this directory, just from the file (the crash report will end in a '.crash') you get detail about what program/library had the issue (from filename), and date/time of the crash (from date/time stamp of the file). You can view this file as it's ASCII or text though particularly the end part of the file may not be very user-friendly. This is what gets uploaded.

Once a file is reported (uploaded); it's name is changed to end with '.crash.upload' so you don't see the message again, however there are occasions when this does not occur. If the file fails to upload, it'll not have it's name changed and you'll see the error message on next boot.

You can remove the file yourself (particularly if you've attempted to report it, but it failed and you don't want to annoyed by the repeated message) with the command

`sudo rm /var/crash/[filename.crash]`

where you replace [filename.crash] with the name of the file you see there, or you could use `sudo rm /var/crash/*.crash` to remove all crash files sitting in the directory. `sudo` is necessary to elevate your privilieges needed because it's not a user directory, the `rm` is the command to remove/erase a file. The `backticks` should not be typed.

crysman (crysman) said : #3

Hello, thanks for the info provided, it is useful, but does not help. What I need:

1) the dialogue box should inform about /var/crash - should be an easy fix - where can I make a feature request on this? I consider it a BUG (not providing the info about the log)

2) /var/crash is the same content before I click on "Report problem..." and after, have a look:

<code>
myuser@mypc ~ 11:42:46
❱ ll --sort=time --reverse /var/crash/
total 22392
-rwxrwxrwx 1 root whoopsie 0 zář 3 2018 .lock*
drwxr-xr-x 13 root root 4096 lis 3 2018 ../
-rw-rw-r-- 1 myuser whoopsie 0 čen 17 14:01 _usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-2.0.1000.upload
-rw------- 1 whoopsie whoopsie 37 čen 17 14:01 _usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-2.0.1000.uploaded
-rw-r----- 1 myuser whoopsie 1503128 čen 18 19:18 _usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-2.0.1000.crash
-rw-r----- 1 myuser whoopsie 576896 čen 30 08:43 _usr_lib_chromium-browser_chromium-browser.1000.crash
-rw-rw-r-- 1 myuser whoopsie 0 čec 10 22:36 _opt_brave.com_brave_brave.1000.upload
-rw------- 1 whoopsie whoopsie 37 čec 11 11:54 _opt_brave.com_brave_brave.1000.uploaded
-rw-r----- 1 root whoopsie 1593704 čec 11 12:22 _usr_lib_xorg_Xorg.0.crash
-rw-r----- 1 myuser whoopsie 4708161 čec 14 00:10 _opt_brave.com_brave_brave.1000.crash
-rw-r----- 1 myuser whoopsie 655330 srp 23 17:28 _usr_bin_fim.1000.crash
-rw-r----- 1 myuser whoopsie 9032067 srp 25 18:02 _usr_bin_ristretto.1000.crash
-rw-r----- 1 myuser whoopsie 2987190 srp 27 16:35 _usr_bin_thunar.1000.crash
drwxrwsrwt 2 root whoopsie 4096 zář 11 09:27 ./
-rw-r----- 1 myuser whoopsie 1835557 zář 11 09:27 _usr_bin_xfce4-display-settings.1000.crash
myuser@mypc ~ 11:42:52
❱ echo "problem REPORTED, waiting 2 minutes..." && sleep 120 && echo "OK"
problem REPORTED, waiting 2 minutes...
OK
myuser@mypc ~ 11:45:56
❱ ll --sort=time --reverse /var/crash/
total 22392
-rwxrwxrwx 1 root whoopsie 0 zář 3 2018 .lock*
drwxr-xr-x 13 root root 4096 lis 3 2018 ../
-rw-rw-r-- 1 myuser whoopsie 0 čen 17 14:01 _usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-2.0.1000.upload
-rw------- 1 whoopsie whoopsie 37 čen 17 14:01 _usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-2.0.1000.uploaded
-rw-r----- 1 myuser whoopsie 1503128 čen 18 19:18 _usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-2.0.1000.crash
-rw-r----- 1 myuser whoopsie 576896 čen 30 08:43 _usr_lib_chromium-browser_chromium-browser.1000.crash
-rw-rw-r-- 1 myuser whoopsie 0 čec 10 22:36 _opt_brave.com_brave_brave.1000.upload
-rw------- 1 whoopsie whoopsie 37 čec 11 11:54 _opt_brave.com_brave_brave.1000.uploaded
-rw-r----- 1 root whoopsie 1593704 čec 11 12:22 _usr_lib_xorg_Xorg.0.crash
-rw-r----- 1 myuser whoopsie 4708161 čec 14 00:10 _opt_brave.com_brave_brave.1000.crash
-rw-r----- 1 myuser whoopsie 655330 srp 23 17:28 _usr_bin_fim.1000.crash
-rw-r----- 1 myuser whoopsie 9032067 srp 25 18:02 _usr_bin_ristretto.1000.crash
-rw-r----- 1 myuser whoopsie 2987190 srp 27 16:35 _usr_bin_thunar.1000.crash
drwxrwsrwt 2 root whoopsie 4096 zář 11 09:27 ./
-rw-r----- 1 myuser whoopsie 1835557 zář 11 09:27 _usr_bin_xfce4-display-settings.1000.crash
</code>

So... I got no information at all :/

crysman (crysman) said : #4

OK, I've removed all from /var/crash - and now I am OK - no dialogue being opened any more. So thank you!

BUT...

I still want to make a feature request in order to: let the users know where the crashes are located - where to do it?

Thanks!

Best Chris Guiver (guiverc) said : #5

A bug report is the correct method to request a 'feature request', but it should be very clear it's a feature request, and why the current situation is unclear, such that readers don't mis-read your intention as I did.

Yes I wondered if it was a 'feature request', however the wording "The problem is: what is it about? There are no details whatsoever" made it feel like a support request more than feature request. It felt like you didn't fully appreciate how it worked and were more after support than suggesting change. I apologize for that, and not noticing your history clear enough. I did start writing my first response here (#2 on this question) as a reply in your bug report, and asking if support would be a better place (which I wish I'd now done, my error sorry), but what I was typing was more 'support' and not 'bug response' so I converted.

The bug can be converted back to bug report (needs a 'bug supervisor' I believe) which I'll support, or you could start a new bug linking this one, and make it clear it's a 'feature request' or suggesting user-prompts be changed (maybe had your #2 comment ended with a - "user-unfriendly, and should be changed." I'd have acted differently).

crysman (crysman) said : #6

commented there again and marked as "incomplete" and converted to bug again: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1845154

crysman (crysman) said : #7

Thanks Chris Guiver, that solved my question.