Your message dated Thu, 22 Oct 2026 00:15:42 -0400
with message-id <E1xJkDO-0000000BbQu-1QGz@zion>
and subject line Re: Bug#866985: Crash while viewing and scrolling through
existing bug report.
has caused the Debian Bug report #866985,
regarding Crash while viewing and scrolling through existing bug report.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
866985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866985
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: reportbug
Package: reportbug
Version: 7.1.7
Crash while viewing and scrolling through existing bug report.
Crash...
(reportbug:2841): Gdk-ERROR **: The program 'reportbug' received an X
Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 212803 error_code 11 request_code 130 (MIT-SHM)
minor_code 5)
(Note to programmers: normally, X errors are reported
asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)
Trace/breakpoint trap
Regards
Phil
--
Playing the game for the games sake.
Web: https://kathenas.org
Twitter: kathenasorg
Instagram: kathenasorg
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Hi,
the error is the X server refusing a shared memory (MIT-SHM) request for
lack of resources, raised inside GDK. As Nis wrote in 2020, it only
happened with a few specific bugs, but nobody could tell us which ones,
so there's nothing to reproduce it with. Closing.
If it happens again with a current version, please reopen and tell us
the number of the bug you were viewing.
Regards,
Sandro
--- End Message ---
