https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #24 from retrooper...@gmail.com ---
Ok. Thank you.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #23 from Nate Graham ---
You don't have to leave Garuda Linux if you're otherwise happy with it; I'm
just saying you should ask them about this, because evidently they have an
extensively customized Latte Dock config which appears to be
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #22 from retrooper...@gmail.com ---
Migrating is gonna take a while XD.
I'm just a bit sad, because it took like 3 days to fully migrate to this
distro. Now I'm probably gonna be switching back.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #21 from Nate Graham ---
Nonetheless, my point remains. :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #20 from retrooper...@gmail.com ---
I didn't uninstall it, I just killed its process. It just hid many features,
you know the app launcher menu operating systems like Windows have? Basically I
had something like that and it dissapeared
https://bugs.kde.org/show_bug.cgi?id=44
Nate Graham changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #18 from retrooper...@gmail.com ---
Huge update: I managed to confirm that its a steam fullscreen issue with
latte-dock. As soon as I enabled the fullscreen setting in Terraria, it crashed
the game!
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #17 from retrooper...@gmail.com ---
Update: It doesn't seem to crash for every steam game, Terraria which launched
NOT In fullscreen seems to work? I'm not sure if its a fullscreen or not
fullscreen issue. But what is odd is games like
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #16 from retrooper...@gmail.com ---
I don't think the steam game successfully launched, because usually that
specific steam game would launch in fullscreen right away. And after I saw the
game displayed as Currently running in Steam, I tried
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #15 from retrooper...@gmail.com ---
Seems like my distribution relies heavily on Latte-dock. I killed the
latte-dock process and even tried configuring it to not automatically enable on
system login. Lots of features aren't working anymore,
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #14 from Nate Graham ---
Well that's weird. Does the problem go away if you temporarily uninstall Latte
Dock?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #13 from Alex ---
Thanks for the log.
Maybe this line is it:
Aug 22 11:29:01 NewLaptopDevice dbus-daemon[2877]: [session uid=1000 pid=2877]
Activating service name='org.kde.LogoutPrompt' requested by ':1.32' (uid=1000
pid=3257
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #12 from retrooper...@gmail.com ---
Created attachment 140939
--> https://bugs.kde.org/attachment.cgi?id=140939=edit
Journal log
Here is the log file
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #11 from retrooper...@gmail.com ---
I'm not sure what you mean by 'boot it happened in' or the 'last boot'? I will
try launching a steam game, then run that command and then I will send you the
output.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=44
Alex changed:
What|Removed |Added
CC||alex...@protonmail.com
--- Comment #10 from Alex ---
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #9 from Nate Graham ---
Thanks! Unfortunately it is all gibberish to me. Is there anyone around who can
help interpret it?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #8 from retrooper...@gmail.com ---
'sudo dmesg' gave me this output (Its quite long so I put it in pastebin)
https://pastebin.com/9REiKH8r
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #7 from Christophe Giboudeaux ---
`sudo dmesg` then
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #6 from retrooper...@gmail.com ---
My GPU is Intel HD Graphics 4000, I'm using the latest Mesa drivers (through
AUR package manager) and "dmesg" in the console gives this output:
dmesg: read kernel buffer failed: Operation not permitted
--
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #5 from Nate Graham ---
Yeah.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #4 from retrooper...@gmail.com ---
Should I check the output of 'dmesg' after my X server crashes? Basically I log
back in (put in my pass) then run the cmd?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #3 from Nate Graham ---
In that case, something is crashing the X server, so I highly doubt any KDE
code is at fault here. What graphics hardware and drivers are you using? can
you find anything in the `dmesg` log when the session crashes?
https://bugs.kde.org/show_bug.cgi?id=44
--- Comment #2 from retrooper...@gmail.com ---
I'm running x11
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=44
Nate Graham changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
CC|
24 matches
Mail list logo
