https://bugs.kde.org/show_bug.cgi?id=408634
Zamundaaa changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://bugs.kde.org/show_bug.cgi?id=408634
Argy M changed:
What|Removed |Added
CC||argy...@gmail.com
--- Comment #38 from Argy M ---
https://bugs.kde.org/show_bug.cgi?id=408634
Ilya Bizyaev changed:
What|Removed |Added
CC||bizy...@zoho.com
--
You are receiving this
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:
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
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
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
https://bugs.kde.org/show_bug.cgi?id=408634
Nate Graham changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
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.
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
>
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
https://bugs.kde.org/show_bug.cgi?id=408634
Andreas Hartmann changed:
What|Removed |Added
CC||andihartm...@freenet.de
--- Comment #30
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
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
https://bugs.kde.org/show_bug.cgi?id=408634
Vlad Zahorodnii changed:
What|Removed |Added
CC||mutasik170...@gmail.com
--- Comment #27 from
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
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:
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:
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.
https://bugs.kde.org/show_bug.cgi?id=408634
Vlad Zahorodnii changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
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 ---
https://bugs.kde.org/show_bug.cgi?id=408634
Oliver Jõgar changed:
What|Removed |Added
CC||difite...@gmail.com
--- Comment #21 from Oliver
https://bugs.kde.org/show_bug.cgi?id=408634
Dave changed:
What|Removed |Added
CC||sixteenal...@pm.me
Ever confirmed|0
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.
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
https://bugs.kde.org/show_bug.cgi?id=408634
Weng Xuetian changed:
What|Removed |Added
CC||wen...@gmail.com
--- Comment #17 from Weng
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.
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
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
https://bugs.kde.org/show_bug.cgi?id=408634
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
--- Comment #13
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.
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
https://bugs.kde.org/show_bug.cgi?id=408634
scott changed:
What|Removed |Added
CC||scott.ashf...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=408634
Milton Hagler changed:
What|Removed |Added
CC||milton...@gmail.com
--
You are receiving this
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
https://bugs.kde.org/show_bug.cgi?id=408634
David Pyke changed:
What|Removed |Added
CC||kdeb...@loftwyr.ca
--
You are receiving this
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
https://bugs.kde.org/show_bug.cgi?id=408634
marco martinez changed:
What|Removed |Added
CC||mak...@gmail.com
--- Comment #8 from marco
https://bugs.kde.org/show_bug.cgi?id=408634
Nate Graham changed:
What|Removed |Added
CC||prote...@hotmail.it
--- Comment #7 from Nate
https://bugs.kde.org/show_bug.cgi?id=408634
Nate Graham changed:
What|Removed |Added
CC||tiagomari...@gmail.com
--- Comment #6 from Nate
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
https://bugs.kde.org/show_bug.cgi?id=408634
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--- Comment #4 from Nate Graham
https://bugs.kde.org/show_bug.cgi?id=408634
Vlad Zagorodniy changed:
What|Removed |Added
Flags||NVIDIA+
--
You are receiving this mail
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
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
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
46 matches
Mail list logo
