From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 90567] New: Display freeze when starting League of Legends (Wine)
Date: Thu, 21 May 2015 15:13:47 +0000 [thread overview]
Message-ID: <bug-90567-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1629 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90567
Bug ID: 90567
Summary: Display freeze when starting League of Legends (Wine)
Product: xorg
Version: 7.6 (2010.12)
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: detlev.casanova-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 115953
--> https://bugs.freedesktop.org/attachment.cgi?id=115953&action=edit
Nouveau error log - 1
Up until recently, I was able to play League of Legends on Linux with Wine,
using the open source driver nouveau. And that was with great performances.
Since an upgrade of the game (I cannot go back to the old version though),
everytime the game starts, The display freezes (sometimes after up to 5 seconds
but it always does).
The cursor is still moving but typing commands blindly doesn't seem to work.
The network and SSH deamon being still running, I was able to collect some
Kernel logs. I attach them.
I also tried to go back to an older version of the Kernel in case the problem
was in there but that did not help (So I can't bissect the kernel to find the
possible bug)
I am not sure if the game is doing something nasty or if there is a bug in the
opensource driver.
Logs show all kind of error messages I could find.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2983 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2015-05-21 15:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 15:13 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-90567-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-05-21 15:14 ` [Bug 90567] Display freeze when starting League of Legends (Wine) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-21 15:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-21 16:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-25 8:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-25 8:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-25 9:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-25 19:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-25 19:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-25 19:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-25 19:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-25 20:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-25 20:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-25 20:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-26 16:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-26 18:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-26 18:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-26 18:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-26 20:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-26 20:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-27 5:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-27 15:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-27 16:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-27 19:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-27 20:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-21 23:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:59 ` 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-90567-8800@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.