Hello,
from the beginning upgrading to ubuntu 26.10 I wasn’t able to report bugs. There were crashes in my system, yet no crash report could be uploaded to launchpad. I had to manually report them. Are you facing such an issue?
Regards!
1 Like
@Claus7 try checking whether Apport is enabled, please (enabled=1):
cat /etc/default/apport
https://ubuntu.com/project/docs/contributors/qa-and-testing/report-a-bug/
FYI: I just amended the title to say alpha/beta instead of beta, as we’re still in beta freeze prior to release of the actual beta which is scheduled for Thursday 1 October 2026.
3 Likes
Hello,
thank you for your responses. The output is:
#set this to 0 to disable apport, or to 1 to enable it
#you can temporarily override this with
#sudo service apport start force_start=1
enabled=1
edit: in the meantime I did the following:
I removed octave package that refuses to get installed.
I issued the command: sudo rm /var/crash/*
and:
sudo apt update && sudo apt install --reinstall apport apport-gtk
I tried to reinstall octave, I saw the error crushes, I press continue and nothing happens…
Regards!
1 Like
Do you have a crash file?
ls -lah /var/crash/
Since you deleted all the previous reports, knowing whether a new one is generated after the next crash will be useful IMHO.
ls -lah /var/crash/
1 Like
Hello,
I can see the octave package, which I mentioned earlier. I have other crushes as well, which are not placed there though.
Regards!
1 Like
@Claus7 have you tried this, please?
ubuntu-bug /var/crash/<YOUR FILE>.crash
I think it could help submit the bug to Launchpad.
Hello,
I tried the command using sudo in front (without it, it didn’t work). The result is the same. I cannot upload the bug to ubuntu launchpad. The behavior is the same as described before.
edit: I faced the same using virtualbox while having my main OS as 26.04. Back then, one of the common errors were when I was trying to install octave and I was facing the same issue: octave was not installable. I do not think that this is due to the upgrade I have conducted…
Regards!
@Claus7, as @guiverc mentioned in this thread the release of the beta is tomorrow, I would wait for it and test again. Others might have better ideas, like @steelf who is doing miracles on the community since a couple of weeks now.
2 Likes
@dmxplx Dim, just coincidences, I make mistakes just as often 
@Claus7 Never run ubuntu-bug with sudo. It needs your desktop session and browser to authenticate with Launchpad, which fails silently under root.
The crash file in /var/crash is owned by root, which is why running it without sudo failed. Take ownership of the file first:
sudo chown $USER:$USER /var/crash/*.crash
Then run it using apport-cli to see the actual terminal output:
apport-cli /var/crash/<filename>.crash
If Apport refuses to report it, apport-cli will print the exact reason right instead of failing silently.
3 Likes
Hello,
thank you for your responses. I keep trying to see if I can send bug reports without using the terminal.
My answers to your suggestions are the following:
-
Not all crushes that I have noticed are reported inside /var/crash
-
The ones that reported some are owned by me as a user some by root
-
I tried the command you mentioned to one of the crashes that were owned by me as a user.
The result was:
apport-cli _usr_bin_osmo.1000.crash
*** Send problem report to the developers?
After the problem report has been sent, please fill out the form in the
automatically opened web browser.What would you like to do? Your options are:
S: Send report (11.2 MB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
Please choose (S/V/K/I/C): S*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
…REDACTED config part /etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg, insufficient permissions
After that I kept seeing my terminal filled with “…” without any change.
In the old times I had faced a similar issue and that was due to an apport bug that was fixed. Searching a little bit more I guess that it might be wayland related.
If anyone of you has 26.10 alpha/beta, can you send bug reports without issuing any commands when a crash takes place?
edit: the first output pointed me here: https://discourse.ubuntu.com/t/insufficient-permissions-from-ubuntu-bug/73521 , yet there is no answer there.
Regards!
The dots are the upload progress indicator. Unpacking and uploading an 11 MB crash dump takes a few minutes, so let it run until it outputs the Launchpad link.
The REDACTED lines are harmless warnings because Apport cannot read root-only cloud-init configs as a normal user.
1 Like
Hello,
thank you for your response. I left it there for a long time and the only thing observed were the dots increasing in numbers.
I will leave it as is and report a bug with the terminal way.
Regards!
1 Like
Hello,
you can do it, I can’t. Thank you for the info.
Regards!
Hello,
I tried to issue the following command:
apport-cli ./octave.0.crash while inside /var/crash and the crash report was sent.
If by any chance you use octave and face installation issues you could add yourselves as affected here:
Regards!
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.