[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2023-01-17 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=408634

Zamundaaa  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||xaver.h...@gmail.com
 Status|CONFIRMED   |RESOLVED

--- Comment #39 from Zamundaaa  ---
We're no longer using EGLStreams to support NVidia. If there's still issues
with NVidia, please open new bug reports for those

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2021-01-27 Thread Argy M
https://bugs.kde.org/show_bug.cgi?id=408634

Argy M  changed:

   What|Removed |Added

 CC||argy...@gmail.com

--- Comment #38 from Argy M  ---
Having the same (I think) issue here, on an Optimus laptop, configured
correctly with NVIDIA for the X11 session. Without KWIN_DRM_USE_EGL_STREAMS,
the Wayland session uses the Intel card. With it, I get a black screen with an
immovable cursor, and I can't even get a tty (with Ctrl+Alt+F2-12) until I
force shutdown.

Operating System: Fedora 33
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.9-201.fc33.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4910MQ CPU @ 2.90GHz
Memory: 15.2 GiB of RAM
Graphics Processor: Quadro K2100M/PCIe/SSE2

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-11-21 Thread Ilya Bizyaev
https://bugs.kde.org/show_bug.cgi?id=408634

Ilya Bizyaev  changed:

   What|Removed |Added

 CC||bizy...@zoho.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-11-16 Thread MaxProPlus
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #37 from MaxProPlus  ---
I have the same problem with the nvidia GTX 1050 Ti. This error is not related
to intel optimus.
KDE neon 5.20 User Edition
Plasma: 5.20.3
KDE Framework: 5.75.0
Qt: 5.15.1
Kernel: 5.4.0-53-generic
Driver: nvidia-driver-455
cat /sys/module/nvidia_drm/parameters/modeset
Y
echo $KWIN_DRM_USE_EGL_STREAMS
1

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-11-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #36 from ss...@pm.me ---
Oh and on optimus if kde streams is removed it defaults to Intel gpu. Oh and
optimus manager is unsure why it failed to load nvidia. Oh and trying to force
nvidia to run by making prime can’t use Sddm and still gets stuck on black
screen with Unmovable mouse if I set auto log to log into plasma wayland
wayland by default I have yet to see it boot into wayland successfully on the
nvidia.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-11-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #35 from ss...@pm.me ---
Expect for people with optimus laptops. I have kde streams enabled and still
get black screen with unmovable mouse as long as Im using nvidia gpu. If I use
intel with kde streams disabled it loads wayland just fine and have had no
issues with waylands performace. I have a secondary laptop that only has an
intel gpu and it has been using wayland for last three months straight with no
issue

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-11-03 Thread Andreas Hartmann
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #34 from Andreas Hartmann  ---
Good point regarding KWIN_DRM_USE_EGL_STREAMS:

If KWIN_DRM_USE_EGL_STREAMS is set, the following crash disappeared:
"The complete session crashes (plasmashell?) if there are e.g. two konsole
programs running and you're pointing to the preview of each window in the
taskbar."

=> so this seems to be a software renderer problem.

The problem with black screens doesn't disappear using
KWIN_DRM_USE_EGL_STREAMS.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-11-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=408634

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=428088

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-11-03 Thread Vlad Zahorodnii
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #33 from Vlad Zahorodnii  ---
If you don't set it*

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-11-03 Thread Vlad Zahorodnii
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #32 from Vlad Zahorodnii  ---
(In reply to Andreas Hartmann from comment #31)
> The versions I'm using at the moment:
> Framework 5.20.2
> QT: 5.15.1
> Nvidia: 450.80
> SDDM: 0.18.1
> It's even not necessary to use the environment variable
> KWIN_DRM_USE_EGL_STREAMS.
If you don't set in KDE Plasma < 5.20.3, kwin will use the software renderer.

> But:
> It's massively unstable:
> Starting another session or switching to a console (CTRL-ALT-Fx) breaks the
> previous session - when coming back, the screen is black again. I have to
> kill it completely with killall -u user.
Sounds like bug https://bugs.kde.org/show_bug.cgi?id=428088

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-11-02 Thread Andreas Hartmann
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #31 from Andreas Hartmann  ---
Meanwhile I was able to start a wayland plasmashell via sddm (weston doesn't
work yet). 
I did another update of the KDE packages - after this update, the wayland
plasmashell is now "working":

The versions I'm using at the moment:
Framework 5.20.2
QT: 5.15.1
Nvidia: 450.80
SDDM: 0.18.1
It's even not necessary to use the environment variable
KWIN_DRM_USE_EGL_STREAMS.

But:
It's massively unstable:
Starting another session or switching to a console (CTRL-ALT-Fx) breaks the
previous session - when coming back, the screen is black again. I have to kill
it completely with killall -u user.
Next problem: krunner is broken - crashes massively.
More problems:
The complete session crashes (plasmashell?) if there are e.g. two konsole
programs are running and you're pointing to the preview of each window in the
taskbar.
If the theme is changed, the plasmashell crashes, too.
=> All in all: pretty unusable.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-11-02 Thread Andreas Hartmann
https://bugs.kde.org/show_bug.cgi?id=408634

Andreas Hartmann  changed:

   What|Removed |Added

 CC||andihartm...@freenet.de

--- Comment #30 from Andreas Hartmann  ---
I've got black screen and a frozen mouse cursor in the middle of the screen,
two, with plasma 5.20.2 / qt 5.15.1. No Optimus system. It's just an easy
discrete card (GeForce GT 1030).
I tried using weston (it's much more easy) - but the same problem. Screen stays
black. Using kwin_wayland or weston in a running X11 KDE session works just
fine.
Yes, I used the description here:
http://blog.davidedmundson.co.uk/blog/running-kwin-wayland-on-nvidia/

On an Ryzen 7 AMD internal VGA device, kwin_wayland is running (but it's not
really usable).

I couldn't find any usable way of debugging the problem. Maybe here is a person
which is interested to find the problem by providing ways to debug the problem?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-10-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #29 from ss...@pm.me ---
There are people who have the correct versions of everything still get the
black desktop with stuck cursor. I think it is an issue with kde detection of
optimus.

(In reply to Wyatt Childers from comment #28)
> (In reply to Wyatt Childers from comment #12)
> > Actually I did miss something, the Qt version note. I'm on 5.14.2. This
> > seems to be the latest build available on neon?
> 
> An update on this from me, I switched to Fedora, and as of Fedora 33 (KDE
> 5.19.5, Qt 5.15.1, Kernel 5.8.16, Nvidia 455.28), following the steps
> outlined here does result in a correctly rendered desktop:
> http://blog.davidedmundson.co.uk/blog/running-kwin-wayland-on-nvidia/
> 
> I do now however, experience symptoms that appear to be similar to those of
> bug 428195 while running a wayland session -- eating 16 out of 32 threads of
> a 3950X.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-10-28 Thread Wyatt Childers
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #28 from Wyatt Childers  ---
(In reply to Wyatt Childers from comment #12)
> Actually I did miss something, the Qt version note. I'm on 5.14.2. This
> seems to be the latest build available on neon?

An update on this from me, I switched to Fedora, and as of Fedora 33 (KDE
5.19.5, Qt 5.15.1, Kernel 5.8.16, Nvidia 455.28), following the steps outlined
here does result in a correctly rendered desktop:
http://blog.davidedmundson.co.uk/blog/running-kwin-wayland-on-nvidia/

I do now however, experience symptoms that appear to be similar to those of bug
428195 while running a wayland session -- eating 16 out of 32 threads of a
3950X.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-10-26 Thread Vlad Zahorodnii
https://bugs.kde.org/show_bug.cgi?id=408634

Vlad Zahorodnii  changed:

   What|Removed |Added

 CC||mutasik170...@gmail.com

--- Comment #27 from Vlad Zahorodnii  ---
*** Bug 427948 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-10-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #26 from ss...@pm.me ---
Created attachment 132349
  --> https://bugs.kde.org/attachment.cgi?id=132349=edit
wayland session log

kde 20.08-1, plasma 5.20, qt 5.15.1-3, libnvidia-egl-wayland1 1.1.5-1, arch
linux

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-09-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #25 from ss...@pm.me ---
No backend specified through command line argument, trying auto resolution
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
glamor: 'wl_drm' not supported
Missing Wayland requirements for glamor GBM backend
glamor: 'wl_eglstream_display' not supported
Missing Wayland requirements for glamor EGLStream backend
Failed to initialize glamor, falling back to sw
kdeinit5: preparing to launch '/usr/lib/kf5/klauncher'

i think this might be w/e is wrong but i dont exactly understand what it means

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-09-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #24 from ss...@pm.me ---
No backend specified through command line argument, trying auto resolution
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
glamor: 'wl_drm' not supported
Missing Wayland requirements for glamor GBM backend
glamor: 'wl_eglstream_display' not supported
Missing Wayland requirements for glamor EGLStream backend
Failed to initialize glamor, falling back to sw
kdeinit5: preparing to launch '/usr/lib/kf5/klauncher'

i think this might be w/e is wrong but i dont exactly understand what it means

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-09-29 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #23 from Nate Graham  ---
*** Bug 426944 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-09-28 Thread Vlad Zahorodnii
https://bugs.kde.org/show_bug.cgi?id=408634

Vlad Zahorodnii  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=426944

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-09-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=408634

ss...@pm.me changed:

   What|Removed |Added

 CC||ss...@pm.me

--- Comment #22 from ss...@pm.me ---
If you look at ur system settings running without gel stream it uses the intel
(In reply to Weng Xuetian from comment #17)
> I'm running archlinux with a intel+nvidia system and with
> KWIN_DRM_USE_EGL_STREAMS=1 I will also get a cursor in the middle of black
> screen.
> 
> Without KWIN_DRM_USE_EGL_STREAMS being set, I can log into the wayland
> session without any problem (not so sure what's using). gdb attach to kwin
> doesn't seems to have a deadlock or sth.
> 
> My Qt was already 5.15.0 and Plasma just updated to 5.19.0.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-08-01 Thread Oliver Jõgar
https://bugs.kde.org/show_bug.cgi?id=408634

Oliver Jõgar  changed:

   What|Removed |Added

 CC||difite...@gmail.com

--- Comment #21 from Oliver Jõgar  ---
For me, when nvidia-drm.modeset=1 and KWIN_DRM_USE_EGL_STREAMS=1 are used, the
Wayland session freezes on my BIOS boot logo and there is no cursor. When I
switch to a tty and back, I get a moving cursor and black screen.

When I don't use KWIN_DRM_USE_EGL_STREAMS, I can log in and get a desktop, but
it runs at a completely unusable framerate.

The screen is black and you can't see anything, but programs launch fine and
input devices work, as I can hear Discord launch after login.

My computer is using the "video-nvidia-440xx" proprietary driver, more
specifically 440.100, no hybrid or Optimus used, meaning this isn't limited to
hybrid graphics solutions.

CPU: Intel i5-9600K
GPU: NVIDIA GeForce GTX 1660

Manjaro 20.0.3 Stable
KDE Plasma 5.19.3
KDE Frameworks 5.72.0
Qt 5.15.0
Kernel: 5.7.9-1-MANJARO

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-08-01 Thread Dave
https://bugs.kde.org/show_bug.cgi?id=408634

Dave  changed:

   What|Removed |Added

 CC||sixteenal...@pm.me
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #20 from Dave  ---
(In reply to Weng Xuetian from comment #17)
> I'm running archlinux with a intel+nvidia system and with
> KWIN_DRM_USE_EGL_STREAMS=1 I will also get a cursor in the middle of black
> screen.
> 
> Without KWIN_DRM_USE_EGL_STREAMS being set, I can log into the wayland
> session without any problem (not so sure what's using). gdb attach to kwin
> doesn't seems to have a deadlock or sth.
> 
> My Qt was already 5.15.0 and Plasma just updated to 5.19.0.

Hardware:
- CPU: Intel i7-6700HQ
- GPU: NVIDIA GeForce GTX 950M

Software:
- KDE Plasma Version: 5.19.4
- KDE Frameworks Version: 5.72.0
- Qt Version: 5.15.0
- Kernel Version: 5.8.0-1-MANJARO

GPU Driver: video-hybrid-intel-nvidia-440xx-prime

I can confirm this. 

My laptop is currently using the Intel-NVIDIA GPU hybrid hardware
configuration. Even after following the guide on KDE's community wiki, it would
work until the login screen (SDDM). After logging in, everything froze; the
screen went black and the mouse cursor went unresponsive. 

Upon checking the "Info Center" application, and in the "Graphics" section; the
driver used was the Mesa driver (for Intel). Optimus did not work with Wayland,
but I ran it anyway in the terminal; it gave the error "the active card is
Intel, but it should be NVIDIA".

Could this issue be isolated with only the Intel-NVIDIA GPU hybrid
configuration?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-07-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #19 from prote...@hotmail.it ---
Any news about this issue?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-06-09 Thread Weng Xuetian
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #18 from Weng Xuetian  ---
Created attachment 129164
  --> https://bugs.kde.org/attachment.cgi?id=129164=edit
KWin support info when running egl stream

And actually only the graphics freezes. Things like keyboard input doesn't seem
to have a problem. I tried to blindly use krunner to start kwrite via keyboard
and kwrite does start.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-06-09 Thread Weng Xuetian
https://bugs.kde.org/show_bug.cgi?id=408634

Weng Xuetian  changed:

   What|Removed |Added

 CC||wen...@gmail.com

--- Comment #17 from Weng Xuetian  ---
I'm running archlinux with a intel+nvidia system and with
KWIN_DRM_USE_EGL_STREAMS=1 I will also get a cursor in the middle of black
screen.

Without KWIN_DRM_USE_EGL_STREAMS being set, I can log into the wayland session
without any problem (not so sure what's using). gdb attach to kwin doesn't
seems to have a deadlock or sth.

My Qt was already 5.15.0 and Plasma just updated to 5.19.0.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-06-08 Thread scott
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #16 from scott  ---
KWIN_COMPOSE=Q does not appear to have an effect. I still get the black screen
+ frozen cursor.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-06-08 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #15 from David Edmundson  ---
Optimus potentially makes things interesting.


You can try with exporting KWIN_COMPOSE=Q 

Things will be super slow, but it will be good data point to see what happens.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-06-08 Thread scott
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #14 from scott  ---
I am still experiencing a black screen and frozen cursor. This is with meeting
all prerequisites mapped out in David's blog post. Granted I am using an
optimus laptop. If any specific log files would be helpful please let me know.
Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-06-08 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=408634

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk

--- Comment #13 from David Edmundson  ---
The Qt version thing is very important. The bug fixed there matches the
symptoms you're seeing. 

I don't know when Neon will upgrade. Potentially I could patch Neon.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-06-08 Thread Wyatt Childers
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #12 from Wyatt Childers  ---
Actually I did miss something, the Qt version note. I'm on 5.14.2. This seems
to be the latest build available on neon?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-06-08 Thread Wyatt Childers
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #11 from Wyatt Childers  ---
Confirming I have followed the setup on the wiki per:

https://www.reddit.com/r/kde/comments/gz40tv/david_edmundson_busts_some_myths_of_nvidia_plasma/ftemb2f/

Also worth noting the wiki instructions are not compatible with fish shell -- I
swapped back to bash to test, as the /etc/profile.d/kwin.sh script isn't
executed with fish as your user shell.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-02-12 Thread scott
https://bugs.kde.org/show_bug.cgi?id=408634

scott  changed:

   What|Removed |Added

 CC||scott.ashf...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2020-01-01 Thread Milton Hagler
https://bugs.kde.org/show_bug.cgi?id=408634

Milton Hagler  changed:

   What|Removed |Added

 CC||milton...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2019-11-30 Thread Wyatt Childers
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #10 from Wyatt Childers  ---
Full system reinstall later, and a new processor, this still remains an issue.
This would suggest it's either the specific GPU, or some more intricate
hardware interaction provided this is working for other users on KDE Neon.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2019-10-19 Thread David Pyke
https://bugs.kde.org/show_bug.cgi?id=408634

David Pyke  changed:

   What|Removed |Added

 CC||kdeb...@loftwyr.ca

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2019-09-30 Thread marco martinez
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #9 from marco martinez  ---
I think I'm facing the same issue. I'm running plasma 5.17 beta and have set
the env variable and nvidia modeset. Running on an optimus laptop

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2019-09-30 Thread marco martinez
https://bugs.kde.org/show_bug.cgi?id=408634

marco martinez  changed:

   What|Removed |Added

 CC||mak...@gmail.com

--- Comment #8 from marco martinez  ---
Created attachment 122957
  --> https://bugs.kde.org/attachment.cgi?id=122957=edit
wayland-session.log

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2019-06-30 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=408634

Nate Graham  changed:

   What|Removed |Added

 CC||prote...@hotmail.it

--- Comment #7 from Nate Graham  ---
*** Bug 409329 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2019-06-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=408634

Nate Graham  changed:

   What|Removed |Added

 CC||tiagomari...@gmail.com

--- Comment #6 from Nate Graham  ---
*** Bug 409194 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2019-06-13 Thread Wyatt Childers
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #5 from Wyatt Childers  ---
(In reply to Nate Graham from comment #4)
> Does anything here help?
> 
> https://www.reddit.com/r/kde/comments/bzs8xn/
> kde_plasma_516_wayland_on_nvidia/

Sadly, no.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2019-06-13 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=408634

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

--- Comment #4 from Nate Graham  ---
Does anything here help?

https://www.reddit.com/r/kde/comments/bzs8xn/kde_plasma_516_wayland_on_nvidia/

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2019-06-13 Thread Vlad Zagorodniy
https://bugs.kde.org/show_bug.cgi?id=408634

Vlad Zagorodniy  changed:

   What|Removed |Added

  Flags||NVIDIA+

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2019-06-12 Thread Wyatt Childers
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #3 from Wyatt Childers  ---
Also just to rule it out, tried creating a completely new user, and seeing if I
could reproduce using that user. The behavior was effectively the same with
login through SDDM, and presumably though kwin_wayland --xwayland -- I did not
wait for it to become responsive, but the initial error set shown in attachment
120835 was the same.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2019-06-12 Thread Wyatt Childers
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #2 from Wyatt Childers  ---
Created attachment 120836
  --> https://bugs.kde.org/attachment.cgi?id=120836=edit
output after initial screen

This is the output including both the initial output, and the output presented
whenever the screen unfreezes, and renders something meaningful. It always
begins with "lock called" and ends with "Grab Released".

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408634] [Wayland] Nvidia Black Screen

2019-06-12 Thread Wyatt Childers
https://bugs.kde.org/show_bug.cgi?id=408634

--- Comment #1 from Wyatt Childers  ---
Created attachment 120835
  --> https://bugs.kde.org/attachment.cgi?id=120835=edit
text log of text before initial screen rendering

This is the output when running kwin_wayland --xwayland before it renders an
initial screen.

-- 
You are receiving this mail because:
You are watching all bug changes.