After update of L14 terminal window no longer opens

Hardware Librem 14
1

I updated my L14 this morning and rebooted it. After updating it, terminal windows no longer open. What is strange is that I cannot even ssh in from another linux machine. I can run single line commands through ssh. Any suggestions on how I should proceed to debug this?

Everything else seems to work; firefox, chromium, etc. only terminal windows (I have also tried xtermals, etc) don’t work.

Thanks!

1 Like
2

Specify the operating system.

3

Sorry:

Linux 5.10.0-33-amd64 #1 SMP Debian 5.10.226-1 (2024-10-03) x86_64 GNU/Linux

1 Like
4

Okay, try restarting your Librem 14 and see if the issue persists.

5

I have tried that but it did not work. I managed to look at the user.log in /var/log and noticed this error:

gnome-shell[6277]: Couldn’t find child [0x55e584743c70 Gjs_ui_windowPreview_WindowPreview (“Terminal”)] in window slots

1 Like
6

Are you using any additional external monitors?

7

Yes, but I have been using it since I got the L14 in 2021.

1 Like
8

Just set the machine to one screen, logged out and logged on again. Terminal still crashes.

1 Like
9

Here is a similar issue:

Are resources for Terminal still being allocated after it crashes in System Monitor?

1 Like
10

Just booted off of a flash drive and terminals work correctly. So it looks like I should reinstall the pureos

1 Like
11

Sure, remember to backup any important data using external media first.

1 Like
12

Fortunately I did a back up yesterday.

1 Like
13

One question: the drive is encrypted. Is there anything special that I should do?

1 Like
14

Interesting the live installation instructions were deleted 8 days ago.

1 Like
15

You do not need to do anything special with the encrypted drive before reinstallation. The instructions have not been updated in over five years since @mladen worked on them, so I am not too surprised @JCS wants to rewrite it for the upcoming Crimson release.

1 Like
16

:confused: I found the problem. It is in the bashrc file. I simply renamed the file and the terminal started work. Strange thing is that if I then source the bashrc file once the terminal is open, it works.

2 Likes
17

I updated the machine this morning and it created an infinite loop between .bashrc and .bash_profile. I suspect it might have been:
bsdutils:amd64 1:2.36.1-8
util-linux:amd64 2.36.1-8
bsdextrautils:amd64 2.36.1-8

But I am not sure which one.

1 Like
18

I migrated it to official documentation as a work-in-progress objective to converge numerous/scattered information sources.

2 Likes
19

I guess that depends on how heavily customised those two files are.

1 Like
20

Indeed. In fact, I clearly put something in my .bashrc that should be in the .bash_profile. I was looking for the baseline copies of both so I could compare them with mine.

2 Likes