From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 33999] New: 2.6.37 - NV11 crashes X if glxgears maximised
Date: Mon, 7 Feb 2011 12:08:57 -0800 (PST) [thread overview]
Message-ID: <bug-33999-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=33999
Summary: 2.6.37 - NV11 crashes X if glxgears maximised
Product: xorg
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: alex.buell-XLQCo7u1tb3e9xe1eoZjHA@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
With Gnome, start glxgears, then click on maximise, X will crash. With
LIBGL_ALWAYS_SOFTWARE=1, crashes do not occur.
Starting KDE 4.6.x always result in a X crash.
Logs attached. I am always happy to assist if necessary to fix this problem.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-02-07 20:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 20:08 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-33999-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-02-07 20:13 ` [Bug 33999] 2.6.37 - NV11 crashes X if glxgears maximised bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 20:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 20:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 22:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 22:39 ` [Bug 33999] 2.6.37 - NV11 crashes X if glxgears started bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-08 0:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-08 2:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-01 2:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-01 11:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-05 14:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-05 15:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-05 21:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-07 1:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-07 16:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-14 0:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19 14:20 ` 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-33999-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.