1s step failed.

2nd step, i cant find the reported issue

On Mon, 25 Aug 2025 at 10:00, Daniel van Vugt <[email protected]>
wrote:

> We can't tell what's crashing here but it seems likely to be bug
> 2121332.
>
> 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 us the ID of the newly-created bug.
>
> 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
> ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
> Do you find any links to recent problems on that page? If so then please
> send the links to us.
>
> Please take care to avoid attaching .crash files to bugs as we are
> unable to process them as file attachments. It would also be a security
> risk for yourself.
>
> ** Changed in: gnome-control-center (Ubuntu)
>        Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2121211
>
> Title:
>   gnome-control-center-print-renderer crashed with SIGSEGV
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2121211/+subscriptions
>
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2121211

Title:
  gnome-control-center-print-renderer crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2121211/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to