Ptyxis crashes
Hi. I removed two Flatpaks (Chrome and Edge) and now my system appears unstable. For exampl, when I try to launch Ptyxis, it crashes on startup and says this (see screenshot). Any ideas?
86 Replies
same issue
maybe running it in Konsole may give a better indication of the issue
run
ptyxis in Konsole to see what it outputsI dont have konsole for my part
try
gnome-terminal if you're on gnome thennop on kde
i dont have other tty emulator
that's weird, because I have it in
/usr/bin
I go check
yep i have in the bin folder
ptyxis: symbol lookup error: ptyxis: undefined symbol: vte_terminal_get_current_container_runtime
this was the return
i'm performing a ujust update and reboot see if it fix
yeah worth a shot
seem to no doing anything but i go back after reboot
I can't find any other users with the same error
same but 3 here in less of a day and never berfore thats weird
not changing
i go back soon need eat š
what branch are you on?
I'm on
bazzite:testing and haven't had this issuebazite nvidia stable
Hi, on bazzite-deck:stable and just encountered this error
if someone is willing, try out
:testing to see if it helps
if not, go back to :stabledo you have MOTD?
no
I know it exists, but I never seemed to get it
yeah so that's a separate issues, but i can also confirm ptyxis works
I do have mine set up to launch neofetch on opening, so maybe I do something to skip MOTD
seems skips the MOTD regardless
where can we disable the motd
it was a
ujust command
i cant seem to find it now
if you rebase to :testing it's gone anyways š
that is not an intended change thoughujust toggle-user-motdim experiencing this to
is there a fix?
not work
i find the console in usr/bin/konsole and that started the terminal. But trying via ptyxis it crashes
weirdly not work
same issue
ptyxis crashes?
yup
this seam to not be related to a specific branch
i guess im due for this next time i update...
kyle is working on a fix rn
so this will be fixed eventually
This should be fixed here shortly, sorry this snuck through
I'll have a writeup on what happened
and we'll probably have a unit test for this
for the meantime you can rebase to an old build, and anyone affected by this, please note
1: Auto updates still work
2: Updates from gamemode still work
3: You can enter a TTY with control+alt+f4 and update from there with
rpm-ostree update
I will message in this thread when said update is availablewhat can be causing that issue it's really weird and not appen to everybody ?
Only affects people on the absolute latest build
It's an issue in the latest Ptyxis build, related to a dependency
ok u.U
yeah if i updated and rebooted right now, i would have this issue
a temp fix is rebooting and rolling back, but kyle will have the fix shortly
so you might as well wait and update
and all rpm-ostree make to go to the latest build?
yup
okay yeah i got the same issue, looking forward to a fix !
built as of now
update downloading oof 3gb
it always does this
every update downloads 3GB
this has to be fixed upstream
that may happen this year
but it's beyond our control
interesting why?
OCI limitation at this time, Red Hat is working to deliver diffed updates later this year
okok
which will cut that down tremendously
yeah so you have to redownload the image every update until that happens
issue still present for me (on stable)
i check tomorrow if more š
KDE or GNOME?
kde
did you restart after the update?
yup
question
did boxbuddy ever get installed?
nothing to do with this terminal
but that output states you're on the jan 16th image
yep
oh ok
maybe i dont even understand reading rpm-ostree status lol
boxbuddy work since my three day on bazzite
was it preinstalled?
yup
oh ok
why does it say
Version: 39.20240116.0idk
what it's expected?
today's date
that's january 16th, 2024
yup i know
yeah thats weird... thats an older build
but it cant be?!
because you had the terminal issue today
im going to ignore what that says
extremely strange though
if you want tomorrow i can gave some time if you want some infos i need to go to sleep now xD it's 4am
ok yeah send logs here tomorrow
you should also try
ujust update
tomorrowi've done this for updating
oh
yeah send logs tomorrow
where are my log i'm smoking i've 5 more mins
open ptyxis
it doesnt open
then enter:
sudo dmesg | fpaste
and send the link it outputs
yeah was looking up the commandsudo dmesg | fpaste
oups xD
https://paste.centos.org/view/8f552a81
wait better yet!
copy and paste the output when you enter:
ptyxis in Konsoleptyxis: symbol lookup error: /lib64/libvte-2.91-gtk4.so.0: undefined symbol: gtk_im_context_activate_osk
found KDE's issue, fixed and going up now
try again tomorrow š
GNOME is also good for anyone on those, no change needed there
i love the two DE but my eart go to the dyno
idk if you slept, but someone else on a
-nvidia image also has this funny bug
but both of you are actually up to date
it only says you're using the jan 16 buildš
great to cause confusion while debugging
different error, so progress?
I'd like to request (if possible) having Konsole automatically enabled via
ujust restore-original-terminal in the interim, if it isn't already
Won't be breaking like this again, and now people other than me can fix it as well since it's in a shared ublue copr
also got us F40 builds ready to go, including aarch64
and this is being implemented in F41, so we double won't need to deal w/ this again
I can confirm that it's fixed, updated this morning. nice š