Dear Daniel,
this bug was created from an *.crash file. I only added some additional
information. The part of the system that crashed is the x server.
I have an according .crash, .upload, and .uploaded file on my machine,
but this report is not listed on my whoopsie reports page.
Is it secure to
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
apt-cache policy "gimp*"
gimp-refocus:
Installed: (none)
Candidate: (none)
Version table:
gimp-help-common:
Installed: 2.8.2-2ubuntu1
Candidate: 2.8.2-2ubuntu1
Version table:
*** 2.8.2-2ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
5
This is the journalctl output just before starting gimp until I was
logged in again and able to create this log file.
** Attachment added: "gimp-crash.log.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895816/+attachment/5411311/+files/gimp-crash.log.txt
--
You received this bug n
It seems to be a problem with gimp and images because I can reproduce
the problem when opening gimp with any image file.
** Attachment added: "1"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895816/+attachment/5411309/+files/1
--
You received this bug notification because you are a m
I started gimp on the command line with:
gimp -c --verbose image.png
The attached file is the result.
** Attachment added: "gimp.log.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895816/+attachment/5411310/+files/gimp.log.txt
--
You received this bug notification because you ar
