No terminal after update

vecst

I ran an update on my computer yesterday and now my terminal (default gnome-terminal) wont open.
I can switch to a tty and run commands, but it's really annoying having to switch back and forth.
Has anyone ran into this issue or know a fix? Thanks

vecst

Just to clarify, the program exists, it just doesn't do anything when I try to launch it

davidjharder

Can you run other terminals?
Try switching to TTY, installing kitty (picking one that is not associated with a specific desktop), and then run gnome-terminal from kitty and see what it says

vecst

davidjharder
okay I'm getting
# Error creating terminal: Remote peer disconnected

I tried -vvv and --verbose to see if I could get more and that's all it gave me.

journalctl -e shows

May 14 18:46:42 tundra systemd[12624]: gnome-terminal-server.service: Main process exited, code=dumped, status=11/SEGV May 14 18:46:42 tundra systemd[12624]: gnome-terminal-server.service: Failed with result 'core-dump'.

vecst

I can try that when I get home. The first thing I did was check for broken packages and reinstall. After a reboot I checked again and the same packages were broken. My mind wasn't working yet so I just ignored it, but I'm also going to delete cache then check and reinstall broken packages.

alfisya

If there are any "broken" packages now, detected by eopkg check, it is not actually broken. Your terminal not launching is a seperate problem tho.

Note: As a result of the fixes, eopkg check will fail on a bunch of packages. This is because of the symbolic links for /bin, /sbin, and /lib, and does not actually indicate a problem. This will be addressed at a later time.

Taken from https://discuss.getsol.us/d/10599-temporary-blocking-of-updates-now-unblocked/36

EbonJaeger

I have a hunch this is due to the recent glib CVE fix; I've noticed an uptick in DBus-related failures since that update went out. What I haven't seen, though, is any report on the gedit repository; I'm not sure how many distros have updated it to 47.0 like we have.

vecst

I just got a stack trace and it does indeed mention glib

EbonJaeger

vecst If you would be willing to open an issue on their issue tracker, that would be great. You may want to install the debuginfo packages for glib2, GTK, and gnome-terminal (sudo eopkg install glib2-dbginfo libgtk-3-dbginfo gnome-terminal-dbginfo), and grab a new stacktrace. That will have more symbol details, making it easier to see exactly where it's happening. Then, they can either track down the problem, and/or point us in the right direction.

vecst

Alright I opened an issue.
I noticed the first link you posted was to gedit and that also crashed so I just reported it to there.

EbonJaeger

vecst I just noticed something in that trace. Are you using vala-panel-appmenu, by any chance?

vecst

you nailed it. Dang I really like a global menu

EbonJaeger

vecst best to report the issue to them, and close the one for gedit if you haven't already.

vecst

I planned on doing that in the morning. I already closed the other and commented what the issue was just in case someone runs across it

Thanks for your help

MattA

I've just run into this issue too, also running vala-panel-appmenu.

If I disable global menu and logout/in terminal and gedit work again.
Can anyone shed any light on what the actual conflict is?

Thanks

EbonJaeger

MattA A couple of weeks back, GLib released a security fix for a DBus issue. That fix exposed further bugs with DBus handling. I believe GLib has fixed the bug that vala-panel-appmenu is hitting, though I don't think there's a release for it yet.

GLib issue: https://gitlab.gnome.org/GNOME/glib/-/issues/3366

MattA

Thanks for the info, I'll keep an eye out to see when that fix is avialable

Incidentally I also found it was causing shotwell to segfault as well eg:

$ shotwell
** Message: 16:24:57.489: main.vala:445: Starting session with system profile
Segmentation fault (core dumped)

I've fully removed the vala-panel-appmenu package for now and all apps working again but since removing it I've noticed that gedit/terminal/shotwell etc now say show this warning when starting:

$ shotwell
Gtk-Message: 16:27:25.724: Failed to load module "appmenu-gtk-module"
Gtk-Message: 16:27:25.724: Failed to load module "appmenu-gtk-module"
Gtk-Message: 16:27:25.724: Failed to load module "appmenu-gtk-module"
** Message: 16:27:25.769: main.vala:445: Starting session with system profile

$ gedit
Gtk-Message: 16:28:18.618: Failed to load module "appmenu-gtk-module"
Gtk-Message: 16:28:18.618: Failed to load module "appmenu-gtk-module"
Gtk-Message: 16:28:18.618: Failed to load module "appmenu-gtk-module"

but they DO start, I'm assuming there is config somewhere that's still referring to appmenu that's causing this but I can't for the life of me find it, can anyone point me in the right direction?

Thanks

MattA

Just for anyone else who was/is suffering with this, an updated for glib2 (release 107) appeared yesterday and installation has resolved the issues I was having and allowed me to re-install and enable appmenu :-)