[Bug 974660] New: [G84][G98/GT218] exiting startx session with nouveau requires power button to recover
http://bugzilla.opensuse.org/show_bug.cgi?id=974660 Bug ID: 974660 Summary: [G84][G98/GT218] exiting startx session with nouveau requires power button to recover Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: mrmazda@earthlink.net QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- Created attachment 672207 --> http://bugzilla.opensuse.org/attachment.cgi?id=672207&action=edit hwinfo --gfxcard and Xorg.0.log Mailing list thread that generated no responses: https://lists.rosenauer.org/pipermail/evergreen/2016-April/001745.html This seems like bug 866445 except for older release and only just regressed lately. To reproduce: 1-login on any of tty[1-6] on fully up'd 13.1 using G84 (8600GT) or G98/GT218 (8400 GS) 2-start a plasma or icewm session using startx 3-exit normally Actual result: 1-black screen 2-no keyboard response 3-power button required to recover Expected result: 1-visible shell prompt 2-keyboard working normally I suppose enabling X11:XOrg and latest stable kernel so modeset instead of nouveau might be a workaround, but I haven't tried. Same installation instead using AMD Cedar and xf86-video-ati or onboard Intel GMA X4500 with xf86-video-intel works as expected. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=974660
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=974660
http://bugzilla.opensuse.org/show_bug.cgi?id=974660#c1
Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=974660
http://bugzilla.opensuse.org/show_bug.cgi?id=974660#c2
--- Comment #2 from Felix Miata
http://bugzilla.opensuse.org/show_bug.cgi?id=974660
http://bugzilla.opensuse.org/show_bug.cgi?id=974660#c3
Egbert Eich
13.1 is Evergreen. Where else is anyone supposed to report an Evergreen bug when an Evergreen mailing list report generates no response, especially when the regression arose subsequent to end of official support?
I don't know myself. Maybe Ludwig can help here. When you retort this to evergreen, you should which packages got updated after you saw it working last. /var/log/zypp/history will provide valuable information hopefully you remember when you saw it working last or when you did the update which broke it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=974660
http://bugzilla.opensuse.org/show_bug.cgi?id=974660#c4
Felix Miata
http://bugzilla.opensuse.org/show_bug.cgi?id=974660
http://bugzilla.opensuse.org/show_bug.cgi?id=974660#c5
--- Comment #5 from Felix Miata
http://bugzilla.opensuse.org/show_bug.cgi?id=974660
http://bugzilla.opensuse.org/show_bug.cgi?id=974660#c6
--- Comment #6 from Felix Miata
http://bugzilla.opensuse.org/show_bug.cgi?id=974660
http://bugzilla.opensuse.org/show_bug.cgi?id=974660#c7
--- Comment #7 from Felix Miata
http://bugzilla.opensuse.org/show_bug.cgi?id=974660
http://bugzilla.opensuse.org/show_bug.cgi?id=974660#c8
--- Comment #8 from Felix Miata
http://bugzilla.opensuse.org/show_bug.cgi?id=974660
Felix Miata
http://bugzilla.opensuse.org/show_bug.cgi?id=974660
http://bugzilla.opensuse.org/show_bug.cgi?id=974660#c9
--- Comment #9 from Felix Miata
participants (1)
-
bugzilla_noreply@novell.com