All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 102349] nv4x crashing with plasmashell - gdb log included
Date: Wed, 04 Dec 2019 09:30:34 +0000	[thread overview]
Message-ID: <bug-102349-8800-wKSsSyDomQ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102349-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 872 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=102349

Martin Peres <martin.peres-GANU6spQydw@public.gmane.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |MOVED

--- Comment #19 from Martin Peres <martin.peres-GANU6spQydw@public.gmane.org> ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/364.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2425 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

      parent reply	other threads:[~2019-12-04  9:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21 22:11 [Bug 102349] New: nv4x crashing with plasmashell - gdb log included bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-102349-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-08-21 22:12   ` [Bug 102349] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-23  5:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-23 21:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-23 21:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-24  3:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-24  3:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-24 16:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-03 16:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-23 22:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-29 13:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-27 21:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-08-12 22:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-02 10:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-27  3:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-27  4:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-31  5:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-02 22:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-02 22:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-03 17:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-102349-8800-wKSsSyDomQ@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.