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 92504] New: [NVA5] Corruption in Plasma 5 on resume after changing screen configuration
Date: Fri, 16 Oct 2015 19:19:50 +0000	[thread overview]
Message-ID: <bug-92504-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 92504
           Summary: [NVA5] Corruption in Plasma 5 on resume after changing
                    screen configuration
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: alexander-fd-Bd8g6ntRJIRxuZdfhUSrJg@public.gmane.org
        QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org

Created attachment 118931
  --> https://bugs.freedesktop.org/attachment.cgi?id=118931&action=edit
dmesg output (since boot)

Steps to reproduce:
 * Use laptop with "NVIDIA Corporation GT216M [GeForce GT 330M]" or similar
 * Install KDE Plasma 5
 * Reboot
 * Log in to Plasma 5 desktop

 * Open the main menu and do *Quit* -> *Suspend*
 * Wait for the system to suspend
 * Resume the system and unlock the screen
 * Disconnect or connect external monitor (use *Menu* -> *Computer* -> *System
settings* -> *Screen* to force screen detection if it doesn't happen
automatically)

 * Open the main menu and do *Quit* -> *Suspend*
 * Wait for the system to suspend
 * Resume the system and unlock the screen
 * Open the main menu, network indicator or any other menu from the panel
(`plasmashell`)


*What should happen?*

Nothing - it should "just work"

*What happens instead?*

Massive corruption the first time you open any menu

Also, after reproducing this error a few times without rebooting, the
corruption becomes worse on every suspend until the system hangs. I'm not sure
if this is related through…

*Where was this error produced?*

Tanglu Linux 4.0 ALPHA (Debian based) using:
 * Latest 4.2.0-trunk linux-image
 * MESA git snapshot or MESA 11.0.2
 * LibDRM 2.4.64
 * X11 1.17.2
 * xorg-video-nouveau 1.0.11

-- 
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: 3648 bytes --]

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

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

             reply	other threads:[~2015-10-16 19:19 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 19:19 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-92504-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-10-16 19:20   ` [Bug 92504] [NVA5] Corruption in Plasma 5 on resume after changing screen configuration bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-16 19:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-16 19:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-16 19:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-16 19:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-16 19:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-16 20:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-16 20:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-17 14:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-17 14:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-17 14:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-17 14:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-17 17:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-17 18:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-17 18:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-17 18:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-18 14:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-19  1:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-19 15:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-19 15:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-19 15:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-19 15:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-19 17:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-19 17:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-20  5:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-20 18:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-20 18:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-20 18:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-20 18:38   ` [Bug 92504] [NVA5] Corruption in Plasma 5 on resume -- set_domain failures bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22  1:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22  2:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22  3:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22  9:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-25 18:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-27 21:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-29 15:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-29 18:42   ` 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-92504-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.