Re: [Trisquel-users] wacom driver
The English name of his working directory is "Download". Here is a trick to avoid the "localized" directory names. When installing the system, choose "English". When you log on the system for the first time, change its localization. The system would ask you whether to change existing directory names to your local language, choose "no". And you can have localized user interface whereas the directory names such as "Download" or "Music" are still in English. However, if the freshness of kernel is important, then I advise him to give Debian testing/unstable a try. (Don't add contrib or non-free repository and the system should be free/libre.) I've been using kernel 5.7 for quite some days.
Re: [Trisquel-users] wacom driver
I think your error is because of the special characters in the name of your working directory: "ダウンロード". Change that directory name from /home/fuckoff/ダウンロード/ to /home/fuckoff/SurferDudeApps/ or something like that. Don't name it with Japanese characters, and don't give it any name that would have a space in it. For example, don't name it /home/fuckoff/Surfer Dude's Apps/ If that doesn't work, the error might mean that you have to run "make && make install" as "sudo make && make install". Lastly, you are using an older kernel that's from early 2018. If I was running a modern digital tablet, I'd be seriously thinking about using a kernel that's not over 2 years old. Lots of new kernels available at jxself's web page: https://jxself.org/linux-libre/
[Trisquel-users] Re : Can't boot after update
If so, any method on https://help.ubuntu.com/community/Grub2/Installing#Fixing_a_Broken_System (I would use "via ChRoot") should work. Nevertheless, wouldn't GRUB report an error? @goodlookingsoftware: the 15 lines you get when hitting 'e' may actually be useful to understand the problem.
Re: [Trisquel-users] wacom driver
the log of my struggle: fuckoff@fuckoff-ThinkPad-X200:~/ダウンロード/input-wacom-0.46.0$ ./autogen.sh bash: ./autogen.sh: そのようなファイルやディレクトリはありません fuckoff@fuckoff-ThinkPad-X200:~/ダウンロード/input-wacom-0.46.0$ ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking whether make supports the include directive... yes (GNU style) checking dependency style of gcc... none checking if build path '/home/fuckoff/ダウンロード/input-wacom-0.46.0' has spaces... no checking for kernel type... Linux checking for linux-based kernel... yes checking for kernel source/headers... /lib/modules/4.15.0-108-generic/build checking kernel version... 4.15.0-108-generic checking RHEL6 minor release... 0 checking RHEL7 minor release... 0 checking power supply version... v4.1+ checking abs accessor version... v2.6.36+ checking CONFIG_MODULE_SIG... y checking CONFIG_MODULE_SIG_FORCE... checking CONFIG_LOCK_DOWN_KERNEL... y checking CONFIG_LOCK_DOWN_IN_EFI_SECURE_BOOT... checking secure boot state... off checking if modules must be signed... recommended checking CONFIG_MODULE_SIG_HASH... sha512 checking for module signing hash algorithm... sha512 checking for kernel autogenerated key at /lib/modules/4.15.0-108-generic/build/certs/signing_key.pem... no checking for kernel autogenerated cert at /lib/modules/4.15.0-108-generic/build/certs/signing_key.x509... no checking for shim MOK key at /var/lib/shim-signed/mok/MOK.priv... no checking for shim MOK cert at /var/lib/shim-signed/mok/MOK.der... no checking for rEFInd MOK key at /etc/refind.d/keys/refind_local.key... no checking for rEFInd MOK cert at /etc/refind.d/keys/refind_local.cer... no checking for module signing key... checking for module signing certificate... configure: WARNING: Kernel module signing is recommended but we are unable to find signing keys. Consider re-running configure with the options '--with-signing-key=' and '--with-signing-cert=' set. checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating 2.6.32/Makefile config.status: creating 2.6.38/Makefile config.status: creating 3.7/Makefile config.status: creating 3.17/Makefile config.status: creating 4.5/Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands configure: BUILD ENVIRONMENT: linux kernel - yes 4.5 kernel source - yes /lib/modules/4.15.0-108-generic/build NOTE: The kernel drivers included in this package are only tested with the X Wacom driver built from xf86-input-wacom. If you are running an X server version older than 1.7, please use the drivers provided by the linuxwacom package. Please run 'make && make install'. fuckoff@fuckoff-ThinkPad-X200:~/ダウンロード/input-wacom-0.46.0$ make && make install make all-recursive make[1]: ディレクトリ '/home/fuckoff/ダウンロード/input-wacom-0.46.0' に入ります Making all in 4.5 make[2]: ディレクトリ '/home/fuckoff/ダウンロード/input-wacom-0.46.0/4.5' に入ります Building input-wacom drivers for 4.5 kernel. make -C /lib/modules/4.15.0-108-generic/build M=/home/fuckoff/ダウンロード/input-wacom-0.46.0/4.5 make[3]: ディレクトリ '/usr/src/linux-headers-4.15.0-108-generic' に入ります CC [M] /home/fuckoff/ダウンロード/input-wacom-0.46.0/4.5/wacom_wac.o CC [M] /home/fuckoff/ダウンロード/input-wacom-0.46.0/4.5/wacom_sys.o LD [M] /home/fuckoff/ダウンロード/input-wacom-0.46.0/4.5/wacom.o CC [M] /home/fuckoff/ダウンロード/input-wacom-0.46.0/4.5/wacom_w8001.o Building modules, stage 2. MODPOST 2 modules CC /home/fuckoff/ダウンロード/input-wacom-0.46.0/4.5/wacom.mod.o LD [M] /home/fuckoff/ダウンロード/input-wacom-0.46.0/4.5/wacom.ko CC /home/fuckoff/ダウンロード/input-wacom-0.46.0/4.5/wacom_w8001.mod.o LD [M] /home/fuckoff/ダウンロード/input-wacom-0.46.0/4.5/wacom_w8001.ko make[3]: ディレクトリ '/usr/src/linux-headers-4.15.0-108-generic' から出ます make[2]: ディレクトリ '/home/fuckoff/ダウンロード/input-wacom-0.46.0/4.5' から出ます make[2]: ディレクトリ '/home/fuckoff/ダウンロード/input-wacom-0.46.0' に入ります make[2]: ディレクトリ '/home/fuckoff/ダウンロード/input-wacom-0.46.0' から出ます make[1]: ディレクトリ '/home/fuckoff/ダウンロード/input-wacom-0.46.0' から出ます Making install in 4.5
[Trisquel-users] wacom driver
It seems that each time linux-libre kernel was updated, I have to do something to make wacom driver work again. I would appreciate it if you could get rid of the trouble. My stomach hurts. It still seems that xserver-xorg-input-wacom etc in a repository is broken.
[Trisquel-users] cannot update Mullvad app
Somehow I succeeded in downloading the update package. On Trisquel 9. After clicking the "install this package" (パッケージをインストール）button, the window disappears and nothing happens. Please let me install it.
Re: [Trisquel-users] Can't boot after update
Looks like grub is unable to find the kernel.
Re: [Trisquel-users] Can't boot after update
If it is an option, I would suggest a fresh install of Trisquel 8 (if this is what you have been using). It is almost impossible to diagnose your problem if you cannot easily access the files on the computer, through a live system for example. One could only make bling guesses.
Re: [Trisquel-users] Can't boot after update
Thanks. The screen goes dark.
Re: [Trisquel-users] Can't boot after update
If you do not hit any key, what happens?
Re: [Trisquel-users] Can't boot after update
Things I've tried: When I hit enter with the first or second line selected, the screen goes dark and stays dark. When I hit 'e' I see a screen with a similar box with 15 lines of what looks like config or code. If I hit f10 from that screen, the screen goes dark and stays dark. When I hit 'c' a command line, I get a "grub>" command line following some instructions starting "Minimal BASH-like line editing is supported..."
Re: [Trisquel-users] Can't boot after update
> The highlighted entry will be executed automatically in 21s. What happens after the 21s are gone or 'Enter' is pressed?
Re: [Trisquel-users] Can't boot after update
When the computer turns on, it shows a screen with the following text. At the top it says: GNU GRUB version 2.02 ...then in the box it says: * Trisquel GNU/Linux Advanced options for Triquel GNU/Linux ...then at the bottom it says: Use the and keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting of 'c' to a command-line. The highlighted entry will be executed automatically in 21s.
[Trisquel-users] Can't boot after update
I ran a Trisquel update and now my computer, a MacBook A134, won't boot. Can someone recommend steps to debug it? I'm not physically at the computer, but my 72-year-old father can be guided through not-too-tortuous tasks. The only context I can think to add is that the computer previously ran fine but would never start up on its own after a reboot. A reboot would always just shut it down.
Re: [Trisquel-users] Remove BOM from UTF8 files
Thanks, everyone! This code did the job: #!/bin/bash for filename in $HOME/Documents/bom/*.log; do sed -i $'1s/^\uFEFF//' "$filename" done
[Trisquel-users] Re : Remove BOM from UTF8 files
That should work. Of course, the sed command loldier gave must replace the one that deletes every line with "#". Also, writing "$filename" instead of $filename allows the file name to contain characters such as spaces, which have a "special" meaning for the shell.
Re: [Trisquel-users] Remove BOM from UTF8 files
No doubt a for loop would do the trick. https://en.wikipedia.org/wiki/For_loop
Re: [Trisquel-users] Remove BOM from UTF8 files
There's a utility 'bomstrip' (tool to strip Byte-Order Marks from UTF-8 text files). sudo apt install bomstrip https://www.ueber.net/who/mjl/projects/bomstrip/ http://muzso.hu/2011/11/08/using-awk-sed-to-detect-remove-the-byte-order-mark-bom
Re: [Trisquel-users] Remove BOM from UTF8 files
Can't we just use looping for that? For example, I use this command to process multiple files. It removes lines with hashtag sign in every TXT file of all TXT files in current directory. What do you think? for filename in file*.txt; do sed -i '/#/d' $filename; done
Re: [Trisquel-users] Remove BOM from UTF8 files
That line seems to work as intended. Now, we need Magic Banana tell us how to process the remaining 699 log files automatically.
Re: [Trisquel-users] Remove BOM from UTF8 files
https://stackoverflow.com/questions/45240387/how-can-i-remove-the-bom-from-a-utf-8-file sed -i $'1s/^\uFEFF//' file.txt
