Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1271227 > unrolled thread

Bug#950504: closed by Jeremy Bícha <jbicha@debian.org> (closing old gdm3 bugs)

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#950504: closed by Jeremy Bícha   <jbicha@debian.org> (closing old gdm3 bugs) "Md Ayq" <mdayq@lenta.ru> - 2025-11-22 21:40 +0100
    Bug#950504: closed by Jeremy Bícha <jbicha@debian.org> (closing old gdm3 bugs) Jeremy Bícha <jbicha@debian.org> - 2025-11-22 22:00 +0100
      Bug#950504: closed by Jeremy Bícha <jbicha@debian.org> (closing old gdm3 bugs) "Md Ayq" <mdayq@lenta.ru> - 2025-11-23 04:40 +0100

#1271227 — Bug#950504: closed by Jeremy Bícha <jbicha@debian.org> (closing old gdm3 bugs)

[Multipart message — attachments visible in raw view] — view raw

Thank you so much for the quick reply. 👏 Only slightly over five years. 🚀 Excellent timing! 💨
Now seriously: I don't have the laptop in question at my disposal any longer, so I can't reproduce the original bug—at least not the way it was stated back then. Even if I had the laptop, I'm unsure I'd be able to answer any questions that would have come up even if you or anyone else dealt with the bug. Often, when I submit a bug report, my time allocated to the bug is over, and I'm unable to deal with the follow-up questions but have to do production work (living with the bug in some way). Any advice concerning improving the outcome (i.e., getting the bugs fixed) within the same amount of time?

[toc] | [next] | [standalone]

#1271231 — Bug#950504: closed by Jeremy Bícha <jbicha@debian.org> (closing old gdm3 bugs)

On Sat, Nov 22, 2025 at 3:29 PM Md Ayq <mdayq@lenta.ru> wrote:
> Often, when I submit a bug report, my time allocated to the bug is over, and I'm unable to deal with the follow-up questions but have to do production work (living with the bug in some way). Any advice concerning improving the outcome (i.e., getting the bugs fixed) within the same amount of time?

The Debian GNOME team is quite small and is responsible for a large
number of packages with a large number of bugs so we're simply not
able to fix every bug that is reported.

I have helped improve things somewhat by closing bugs that are old and
don't appear to apply to current supported Debian releases with a note
that people could open a new bug if someone can still reproduce the
issue. Now that you've verified that you can't reproduce the issue, it
would only be extra clutter for the bug to remain open.

Unfortunately, some bugs like the one you reported here may be fairly
complicated to resolve since the issue may be a hardware issue (needs
fixed in the kernel or in mesa or similar) or a bug in lower-level
software. It can be difficult to find someone or a group of people to
isolate the issue, create a fix, and then get the fix into a Debian
package, especially for those using Debian Stable. I don't have
helpful advice for this kind of issue.

Thank you,
Jeremy Bícha

[toc] | [prev] | [next] | [standalone]

#1271246 — Bug#950504: closed by Jeremy Bícha <jbicha@debian.org> (closing old gdm3 bugs)

[Multipart message — attachments visible in raw view] — view raw

Jeremy, I see. Thank you for the reply in any case!
Md

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web