Displaying 4 results from an estimated 4 matches for "biergaizi".
2014 Jun 13
6
[Bug 79988] New: Suspend to ram stoped to work
https://bugs.freedesktop.org/show_bug.cgi?id=79988
Priority: medium
Bug ID: 79988
Assignee: nouveau at lists.freedesktop.org
Summary: Suspend to ram stoped to work
QA Contact: xorg-team at lists.x.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: marccollin7379 at gmail.com
2014 Jun 20
5
[Bug 80300] New: [NVE7] Fails to suspend on 3.15
https://bugs.freedesktop.org/show_bug.cgi?id=80300
Priority: medium
Bug ID: 80300
Assignee: nouveau at lists.freedesktop.org
Summary: [NVE7] Fails to suspend on 3.15
QA Contact: xorg-team at lists.x.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: e.swanson+xorgbugs at
2023 Jan 04
1
[networkupstools/nut] Project Release Cycle Plan Needed (Issue #1769)
...ir distro is a year behind our latest release (and
ship one 6-7 years old instead) and lacks stuff fixed after 2.7.4 or even
2.8.0, it usually "just works" so the model is viable. Sometimes new corner
cases are uncovered and new bugs to fix are recognized.
Jim
On Wed, Jan 4, 2023, 19:05 biergaizi <notifications at github.com> wrote:
> First, apologize for the non-technical nature of this issue report. But I
> believe resolving this issue is crucial to downstream users given its
> importance. It's also worth reposting this issue to the mailing list for
> discussion.
&g...
2023 Jan 04
1
[networkupstools/nut] Project Release Cycle Plan Needed (Issue #1769)
...ir distro is a year behind our latest release (and
ship one 6-7 years old instead) and lacks stuff fixed after 2.7.4 or even
2.8.0, it usually "just works" so the model is viable. Sometimes new corner
cases are uncovered and new bugs to fix are recognized.
Jim
On Wed, Jan 4, 2023, 19:05 biergaizi <notifications at github.com> wrote:
> First, apologize for the non-technical nature of this issue report. But I
> believe resolving this issue is crucial to downstream users given its
> importance. It's also worth reposting this issue to the mailing list for
> discussion.
&g...