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 109341] Plasma Wayland locks up immediately on sign in
Date: Tue, 15 Jan 2019 01:02:39 +0000	[thread overview]
Message-ID: <bug-109341-8800-vYfDXGKg7A@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109341-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #5 from etna-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org ---
Do you mean to say that this issue 'should' not appear on newer releases of
Mesa?

Reason being on my current setup Gnome Wayland and Weston are working fine
under Mesa 18.0.5. It's just Plasma Wayland causing the lockups.

I also tested running a nested Wayland session in Weston and then starting a
Plasma Wayland session in that nested session. No dice; locks up the system as
well. :(

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

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

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

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

  parent reply	other threads:[~2019-01-15  1:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14  3:00 [Bug 109341] New: Plasma Wayland locks up immediately on sign in bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-109341-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-01-14  3:02   ` [Bug 109341] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-14  3:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-14  3:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-14  3:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-14  3:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-15  1:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-01-15  1:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-15  7:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-109341-8800-vYfDXGKg7A@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.