mate-desktop / mate-terminal

The MATE Terminal Emulator
http://www.mate-desktop.org
GNU General Public License v3.0
134 stars 73 forks source link

mate-terminal-1.22.1 fails to open with LTS kernels 4.4.190 and 4.9.190 other kernels OK. #303

Open texstar opened 5 years ago

texstar commented 5 years ago

Expected behaviour

Expect mate-terminal to open

Actual behaviour

A quick flash to the screen and nothing. Also no output when trying to start it from another terminal.

Steps to reproduce the behaviour

Click on the mate-icon in the menu

MATE general version

The most recent 1.22 versions.

Package version

mate-terminal-1.22.1-2pclos2019

Linux Distribution

PCLinuxOS 2019 Mate Editition

Link to downstream report of your Distribution

none

Ravensnavel commented 5 years ago

+1

Ravensnavel commented 5 years ago

Mate terminal (1.22.1 2pclos2019) works, currently, only when I boot with kernel-5.2.13. Does NOT work with kernels 4.4.190 and 4.9.190 - flashes but does not open ...!!!

kalwisti commented 5 years ago

Can confirm that the package mate-terminal (mate-terminal-1.22.1-2pclos2019) does not work with kernel 4.9.76. Clicking on the MATE Terminal icon in the bottom panel produces a momentary flash on the screen, then the window disappears immediately.

Also, trying to launch mate-terminal from within xterm (in hopes of getting some sort of output / error message) fails, with the same behavior as above: a brief flash on the screen, then the mate-terminal window disappears. No output is visible in xterm.

mate-terminal behaves normally / as expected with kernel 5.2.14.

< Note: My observations are all from bare metal on a running system (rather than from a virtual environment). >

It would be nice to have a clue as to what is causing this odd behavior, since I am sure that is affecting other users running LTS kernels.

Thank you for looking into this issue.

lukefromdc commented 5 years ago

Could that be a VTE issue? I can't test this as I have locally compiled kernels (for security with the cipher code) and a rather complex installation system and all my testing is bare metal on a running system.

rstecca commented 5 years ago

Having the same issue with mate-terminal 1.22.1-1. Current kernel is 4.9.0-4 x86_64 and MATE 1.22.1 Nvidia 1080 driver 390.129 (installed through Nvidia run script)

Not sure if this is related but after doing an apt-get upgrade the desktop system was a mess. Windows were not resizable and sticking to top left corner. Power Management and few other applications would not run, some packages were uninstalled, I had to specify to install mate-core for example. Perhaps the default green-to-blue gradient desktop background is a clue of what problem that was? On the top of all that I had this thread's issue which started at the same time. I partially mostly solved the messed desktop environment by manually marking for install a few mate-* packages (why were they removed by the upgrade in the first place???) but this problem hasn't gone away.

lukefromdc commented 5 years ago

A bad upgrade can cause almost anything to have trouble, so much so that restoring from a known good backup partition is often the fastest way back. Otherwise searching through what might be hundreds of packages for the offender can be a nightmare. Often that requires a rollback anyway, then incremental reupdating (known good packages, then one or a few at a time) until the offender is found. Been there, done that.

sc0w commented 5 years ago

I can't find deb packages of the kernel version affected to test

I think the people who reproduce this issue can just git bisect and find the culprit commit, and we can investigate it