I don't think the [Test Plan] is enough to verify the fix, however. The screenshot functionality would still be working even if the fix wasn't applied.
You need to verify that /tmp is no longer being used, and that $XDG_RUNTIME_DIR or $HOME are used instead.
Here are some suggestions:
- if the screenshot file stays around for a while, you can verify that it's not in /tmp but find it in $XDG_RUNTIME_DIR or $HOME
- if the temporary file is quickly deleted, maybe you can use opensnoop.bt (from bpftrace) or an inotify mechanism to catch it being created and thus prove where it is being created from now on. A notify script I used a while ago to watch a directory:
#!/bin/bash
monitor_path="$1"
inotifywait -m "$monitor_path" -e create -e moved_to |
while read path action file; do
echo "The file '$file' appeared in directory '$path' via '$action'"
ls -la "$path/$file"
done
Hi,
thanks for this fix.
I don't think the [Test Plan] is enough to verify the fix, however. The screenshot functionality would still be working even if the fix wasn't applied.
You need to verify that /tmp is no longer being used, and that $XDG_RUNTIME_DIR or $HOME are used instead.
Here are some suggestions:
- if the screenshot file stays around for a while, you can verify that it's not in /tmp but find it in $XDG_RUNTIME_DIR or $HOME
- if the temporary file is quickly deleted, maybe you can use opensnoop.bt (from bpftrace) or an inotify mechanism to catch it being created and thus prove where it is being created from now on. A notify script I used a while ago to watch a directory:
#!/bin/bash
monitor_path="$1"
inotifywait -m "$monitor_path" -e create -e moved_to |
while read path action file; do
echo "The file '$file' appeared in directory '$path' via '$action'"
ls -la "$path/$file"
done