Monday, October 4, 2021

How to pixelate text in the Gimp

There are times when I want to post a screenshot, but need to obscure personal information, as in the screenshot above from my previous post. Pixelating the text is a good solution because it can make the text unreadable whilst still leaving an impression of the text. I did this some time before for a previous post, and needed to do it again today for another post, but had forgotten how to do it. This time I am going to write a quick tutorial to remind me how to do it next time, and to help anybody who might want to do the same thing.

First, open the image in the Gimp:

Then select the text you want to pixelate with the Rectangle Select Tool:

Next, cut the selection:

And paste as a new layer:

Go to Filters > Blur > Pixelise and reduce the size of your pixel blocks until the text is unreadable but still gives the impression of text. Be careful that it is not possible to still read the text if you squint - in this image I need to go one step further:

When you are happy that the text is unreadable, go to Image  > Flatten image:

And here is the final result:








Filter emails in Evolution

Here is a quick tutorial on how to filter emails in Evolution. It took me a while to work out how to do it, so I thought I'd make a note of what I did to remind myself when I inevitably forget later on, and to help anybody who wants to do the same thing.

First, right click on the folder where you want to create a new folder to put your filtered emails in. Click on (you guessed it) New Folder. I put mine in Google Mail > All Mail.

To filter emails by sender, right click on an email you want to create a filter for and select Create > Create a Filter Rule for Sender.

In the dialogue that appears, select the folder you created in the first step.

Click on Add Condition if the sender uses more than one address to send emails from. (My daughter's school has used four different domains to send emails, so I had to add four conditions.)

To apply the filter, click on Message > Apply Filter.

To filter all existing emails, select you inbox and click on Edit > Select All then  Message > Apply Filters.




Saturday, October 2, 2021

Boot message - Failed to start

Update: solved (see below).

Booting up my installation of Debian Testing (Bookworm) I noticed this message:

 
 
[FAILED] Failed to start: Raise network interfaces.

See 'systemctl status networking.service' for detials.

Was this something bad? I hadn't noticed anything like it before. The word 'FAILED' in capital letters and red made me worried.

Systemd does not apparently keep a log of these boot messages. To find a failed command, issue the following command:

# systemctl --failed

  UNIT               LOAD   ACTIVE SUB    DESCRIPTION
● networking.service loaded failed failed Raise network interfaces

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.

To see networking.service messages, issue this command:

# journalctl -u networking.service --no-pager
-- Boot e29338dc96c041638d5b465983e41817 --
Oct 02 18:35:32 Toshiba-laptop ifup[618]: Cannot find device "eth0"
Oct 02 18:35:32 Toshiba-laptop ifup[552]: ifup: failed to bring up eth0
Oct 02 18:35:27 Toshiba-laptop systemd[1]: Starting Raise network interfaces...
Oct 02 18:35:29 Toshiba-laptop systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Oct 02 18:35:29 Toshiba-laptop systemd[1]: networking.service: Failed with result 'exit-code'.
Oct 02 18:35:29 Toshiba-laptop systemd[1]: Failed to start Raise network interfaces.


Well, that clears that up: there's no Ethernet cable plugged into this computer. 

 

Update: I found the source of this issue (Debian User Forums). It is not the system looking for an Ethernet connection that happens to be unplugged, but the system looking for an Ethernet connection that does not exist, due to some unexplained entries in a configuration file, namely:

/etc/network/interfaces.d/setup

The entries below were causing the system to try to bring up network interfaces at boot time. Commenting them out got rid of the "Failed" message.

auto lo 

iface lo inet loopback 

auto eth0 

iface eth0 inet dhcp/

The  only mystery now is what added those lines when they shouldn't be there? Suspicion at the moment falls on the Debian Live Non-Free installation media, which I used to install Debian Bullseye.

Monday, September 27, 2021

Installing Brother HL-1212 W-Fi Mono Laser Printer in Debian Bookworm/Bullseye (Gnome)

[Update 2: The latest version of printer-driver-brlaser works without issue now in Bookworm post release and Trixie (Testing), which both at version 6.3 at the time of writing. Bullseye still has 6.1, so the issue may remain.]

[Update: Unfortunately printer-driver-brlaser is affected by a bug that means documents with images sometimes fail to print with no error message at all. Gnome says the document has printed successfully, CUPS says the document has printed successfully, but nothing appears from the printer, not even blank pages, and the printer records no error.

Back to the driver from the Brother web site then.

See Google Groups, and Github. The driver is patched on Github but it seems there is no Debian maintainer for the package, so no hope for the moment that the Debian package affected (6.2) will be fixed any time soon.]


The Brother HL-1212 WiFi printer does not do driverless printing. See previous post. "Modern" printers don't need drivers, but budget printers like this one (still on sale at the time of writing) seem to date back a decade or two and need drivers.

Previously, I downloaded a driver installation tool from Brother (which worked very well). I am now using Debian Bookworm (Testing), and found today that Debian has included a driver for this printer it its repositories in Bullseye, namely in:

printer-driver-brlaser

Adding the printer was a very easy process. In the printer dialogue click "Add". The printer dialogue found the printer without adding the network address, although there is an option to search by IP address. Three options came up - the printer name, the printer name with some sort of address I didn't recognise appended to it, and a CUPS reference. I chose the first one and the printer entry that came up printed a test page straight away. (Gnome Software said it needed to look for additional things to install, went away and did so, and came back to say it couldn't find anything, but the printer worked anyway.) 

The printer entry contained fields for driver and address, so I selected/entered those, even though the printer seemed to work OK already.

The HL-1212W is available in the UK from Argos with four additional toner cartridges for £159.99, which is quite a good deal if you do a lot of printing.



Tuesday, June 15, 2021

Things that are broken in Debian Bullseye - Thunderbird

An update of Thunderbird (1:78.10.0-1) to 1:78.11.0-1 yesterday seems to have broken it. It says:

Authentication failure while connecting to server imap.gmail.com

I though maybe that Google's strict security didn't recognise the new version so I tried resetting third party app access, but that just got me an error message:

NS-ERROR-NET-INADEQUATE-SECURITY

Thunderbird seems to have had this issue before and a previous fix worked for me.

There are bug reports already here and here and here. The same fix has been noted here.

I am not sure if the fix:

network.http.spdy.enabled.http2 = false

introduces any security risk.

Saturday, May 15, 2021

Blogger deleting posts in error

I woke up this morning to find five emails from Google Blogger telling me that posts had been deleted because they violated Google's terms on Viruses and Malware. What? A weather script for Conky? A post describing how I added memory to my laptop? Either somebody is injecting malicious code into Blogger posts, or this is an error, I thought. My best guess is it's a false positive detection of malicious content by Google. A quick Google found several people who had experienced the same issue on Blogger Help.

I got an email this morning that one of my blog posts was deleted for going against community guidelines.

I literally post about nail polish and using all my own images so there is no way it breaks any rules, so I’m confused and a little annoyed that it’s been totally deleted not just turned to draft so I can’t recover any of what I had written. Is there anything I can do about this or stop it happening again?!
 
And
 
I had written a blog yesterday about my son's battle with cancer and somehow received a phishing warning on my blog site. 

I'm not even entirely sure what happened or how this happened, but my Thursday, May 13th post was deleted by blogger saying I had violated their malware and viruses policy. 

I'm so confused by all of this and not sure if it was a link to a resource or what exactly was the cause of this - I link many medical terms regarding his diagnosis so people can learn more about them. But since this was completely deleted I don't have a way of recovering this blog (which is basically a journal of my son's cancer battle). 

Is there a way I can obtain this basic text from blogger or even from cached files on my local computer? I seem to be at my wit's end.
 
All seem to be getting the same stock answer:
 
Hi:  your posts may have been removed in error. 
Blogger is aware of the issue and working on a fix.
Looks like Google Blogger is going to owe a lot of people a serious apology. It seems no actual human being looked at the posts before they were deleted to see if they actually contained anything malicious. Deleting posts without human supervision, explanation or opportunity for appeal or review? Pretty bad look if it turns out to be an error.

UPDATE: I received emails to say that my posts have been reinstated (without explanation or apology), but the posts seem to have been reinstated as drafts. I hit the Publish button for all of them, so hopefully they are up again.

Monday, April 12, 2021

An update on Debian updates

I recently wrote several posts on updates in Debian, on XFCE and Gnome, Bullseye and Buster.

The default, I wrote, was no notifications of updates by default on XFCE in Bullseye, and no automatic updates, and notification of updates and automatic installation of security updates in Gnome on Buster.

However, after applying the same default to XFCE, I noticed that I was actually getting automatic updates to all packages.

Sure enough, Gnome on Buster was also getting more than security updates.

It turns out that unattended-upgrades (the package which installs automatic updates in Debian,  actually updates all packages by default in Debian Buster and later. (The default in previous version of Debian was security updates only.)

I discovered this in a post on the Debian User Forum, which linked to the Debian Buster release information page. I found the NEWS.Debian file thanks to Debian documentation. 

It reads: 

Unattended-upgrades in previous versions defaulted to install security updates only on Debian by using the label=Debian-Security origin pattern. Now it is changed to allow updates with label=Debian, which allows applying stable updates in stable releases and following all package updates in testing and unstable. 

In stable releases this unlocks installation of security updates depending on package versions present only in stable updates. 

Note that testing and unstable can often contain packages for which installation or upgrade performed by unattended-upgrades fails and requires the administrator to fix the system later.

My fault then for not reading the release information when I upgraded from Stretch.

The Debian Wiki page says:

The purpose of unattended-upgrades is to keep the computer current with the latest security (and other) updates automatically.

Which to me implies that other updates are optional, but obviously not.

I have updated the post on automatic updates in XFCE.  As I am currently using XFCE on Debian Testing, I have disabled updates to all packages by commenting out the line:

//      "origin=Debian,codename=${distro_codename},label=Debian";

I have checked my Gnome installation on Debian Buster, and it also contains the line above, which means that "stable updates" are applied automatically. I've also updated my post on automatic updates in Gnome.

Interestingly, the Gnome Blog states that Gnome will not install updates automatically. unattended-upgrades is a system package and overrides Gnome in Debian, which explains why Gnome notifies me of available updates, but they often disappear before I can install them, with the exception of Chrome, whose repository is not included in unattended-upgrades. NB unattended-upgrades is triggered to run within a randomised period, so the time that update notifications, whether those displayed by default in Gnome, or by the options I described in XFCE (Conky, Genmon), may appear for a few minutes or a few hours before disappearing if you have unattended-upgrades installed.

I hope this post helps anybody struggling, like me, to work out how automatic updates happen in Debian. Apologies for any confusion caused previously.