Maybe so, but the affected laptop only has one (built-in) screen and the config file has no effect unless I use Device1.

Thank you, HoaS. I found this thread and your excellent instructions while investigating Xorg crashes on an old Sony Vaio after upgrading from Chimaera to Daedalus.

For completion's sake, these are the steps I needed to follow after your instructions:
0. The debuild -us -uc step generates six new .deb packages.
1. Install the six new packages with sudo apt install *.deb. These new packages do not conflict with any of the currently-installed graphics packages, so there is no need to uninstall anything.
2. Add this line to /etc/environment: MESA_LOADER_DRIVER_OVERRIDE=i965
3. Reboot

After rebooting, inxi -G shows that mesa-amber is being used (i.e., you'll see that dri = i965 and mesa version = 21).

P.S. In my specific case, it seems mesa version 22 has nothing to do with the Xorg crashes, so mesa-amber unfortunately did not fix the problem. I'll describe my problem and its solution in a separate thread.

Rant: Did you actually read this?

This illustrates exactly what I dislike about Xorg. Everything is overly complicated. This is not a human-friendly description. The header says the DontZap option is boolean, so expected default values would be "true" or "false", not "off" (what exactly is off?).

But all's well that ends well. Thanks to lightdm and sxhkd I don't have to deal with this

I figured it out. I just needed to add a line to /etc/lightdm/lightdm.conf. Now instead of just this in the relevant section:

[SeatDefaults]
autologin-user=bruno
autologin-user-timeout=0

I have this:

[SeatDefaults]
autologin-user=bruno
autologin-user-timeout=0
session-cleanup-script=service lightdm restart

With that added line, now all I need to restart Xorg is sudo pkill Xorg. Thanks for pointing me in the right direction, HoaS!

I do have autologin enabled for my user, with this in /etc/lightdm/lightdm.conf:

[SeatDefaults]
autologin-user=bruno
autologin-user-timeout=0

I'd rather not ditch lightdm, since I would have to reconfigure multiple machines.

There's no actual problem. A few years ago, Xorg disabled Control+Alt+Backspace as the keyboard shortcut for restarting X (supposedly for security reasons). I liked having that shortcut because it was useful for the rare instances when X would freeze. If X acts up, I'd rather simply restart it than doing a full reboot. So the goal is to bring back that functionality by creating a script that works as intended, then binding it to Control+Alt+Backspace.

Wanting to get this script to work is mostly an exercise in getting my computer to do what I want it to do.

Thank you, HoaS. Yes, that's helpful. I'll give patching caja a shot sometime.

Meanwhile, I'll let the MATE developers know about the issue and patch so that they can consider adopting it. It would be nice to have this without having to recompile anything.

Hi, viverna. Anything sold on thinkpenguin.com (their prices are high but the customer service is excellent) will have universal GNU/Linux compatibility because they only sell free software-friendly devices. Here's something they sell:
https://www.thinkpenguin.com/gnu-linux/ … 1394bapcie

Also, the FSF maintains the helpful h-node.org database. To see the firewire adapters in their database, go to duckduckgo.com and enter this search query: firewire site:h-node.org. If the "does it work with free software?" line says "yes" then the device will have universal GNU/Linux compatibility.

Hi, Devuman. Sorry for leading you on a wild goose chase trying to ssh into R2. It seems ralph.ronnquist was right and your router does not offer ssh access into it.

I'm glad you were able to achieve what you needed by setting up a "virtual server" on R2.

P.S. In the future, if you ever have to choose between ralph.ronnquist's advice and someone else's, save yourself some trouble and just go with ralph.ronnquist's

Here's how to kill openvpn in one line in terminal:

sudo pkill -f openvpn

Depending on how you run openvpn, you may not need the -f.

That's not surprising because they're both on the same network (LAN2).

That's because LT2 and PC1 are on different networks, so it's not trivial to establish a connection. We have to go through R2. Let's see if we can SSH from LT2 to PC1 (if you can do SSH, then you can do SFTP).

At the risk of stating the obvious, remember that a router by definition stands between two networks, so it should have at least two IP addresses. R2 in your example has an IP address on LAN1 and a different IP address on LAN2.

Try this:

1. Make sure R2 and PC1 are both running SSHD (I'm assuming those two devices are not running a firewall, or at least have the SSH port open)

2. Run this command on LT2:

ssh -t <R2user>@<R2address-on-LAN1> "ssh <PC1user>@<PC1address-on-LAN2>"

Here is an example with made-up passwords and ip addresses:

ssh -t devuman@192.168.1.150 "ssh devuman@192.168.2.135"

You will be prompted for a password twice (first your password on R2, then your password on PC1).

P.S. Nice diagram!

EDIT: If you can establish an SSH connection from LT2 to PC1 using this long method, then we can be optimistic that with the right port forwarding rules we can achieve an SFTP connection without too much fuss. See my subsequent post below.

3 x Tiny Core Linux (my daily driver laptop plus my two wireless routers)
2 x Devuan ASCII (wife's laptops)
1 x Arch Linux ("media player" laptop connected to television--has not been updated since 2015)

Hi, Tatwi. Thanks for sharing! The AppImage loads quickly and everything looks good. However, I can't open any files.

When I select File -> Open, no files show up in the file selection window unless I choose "All files". Then, whatever image file I select (even a common format such as jpeg) I get an error window saying "Unknown file type".

Alas, I don't know enough about how GIMP/GTK file selection works to fix this.