Arkisto, marraskuu 2018

My new WD100EMAZ produced the same warning

30. marraskuuta 2018 klo 17.22
Sijainti: Muut: Super User
Avainsanat: tekniikka, Western Digital

My new WD100EMAZ (from an Elements enclosure) produced the same warning. Must be something that WD do with these at the factory. I had yet to write anything to the drive, and I was going to repartition it anyway, so I just created a new GPT.

Vastaa viestiin sen kontekstissa (Super User)

In Finnish a bat is ”lepakko”, which means ”a bat”.

29. marraskuuta 2018 klo 16.00
Sijainti: Videosivustot: YouTube
Avainsanat: kieli

In Finnish a bat is ”lepakko”, which means ”a bat”.

JK, actually the meaning is something like ”the flutterer”. But no rodents in the name.

Vastaa viestiin sen kontekstissa (YouTube)

So I did a little more digging, and found that this first cropped up in Ubuntu 17.10

25. marraskuuta 2018 klo 17.54
Sijainti: Vianhallintajärjestelmät: Mozilla Bugzilla
Avainsanat: Firefox, Ubuntu

So I did a little more digging, and found that this actually first cropped up in Ubuntu 17.10.

I then ran mozregression (back on 18.04, my main desktop) and here’s what it found:

7:12.48 INFO: Last good revision: 64bab5cbb9b63808d04babfbcfba3175fd99f69d (2017-10-25)
7:12.48 INFO: First bad revision: aa958b29c149a67fce772f8473e9586e71fbdb46 (2017-10-26)
7:12.48 INFO: Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=64bab5cbb9b63808d04babfbcfba3175fd99f69d&tochange=aa958b29c149a67fce772f8473e9586e71fbdb46

After that ”There are no build artifacts on inbound for these changesets (they are probably too old).”

As this was my first time ever using mozregression, I have no idea how useful that was, but if there’s some way I can narrow this down further, I’d be happy to.

Vastaa viestiin sen kontekstissa (Mozilla Bugzilla)

I’m using Ubuntu 18.04, and that appears to be crucial here

21. marraskuuta 2018 klo 18.27
Sijainti: Vianhallintajärjestelmät: Mozilla Bugzilla
Avainsanat: Firefox, Ubuntu

Adrian: Thanks for taking a look! I’m using Ubuntu 18.04, and that appears to be crucial here: I created a 16.04 VM, installed all in-release updates (including Firefox 63), and just as you, was unable to reproduce the issue. I then upgraded the VM to 18.04 and the bug immediately manifested again.

Vastaa viestiin sen kontekstissa (Mozilla Bugzilla)

Thanks Olivier, I’ve now added the link to my upstream report.

17. marraskuuta 2018 klo 15.14
Sijainti: Vianhallintajärjestelmät: Launchpad

Thanks Olivier, I’ve now added the link to my upstream report.

Vastaa viestiin sen kontekstissa (Launchpad)

I first reported this against 62 in Launchpad

17. marraskuuta 2018 klo 15.13
Sijainti: Vianhallintajärjestelmät: Mozilla Bugzilla
Avainsanat: Firefox, Launchpad, Ubuntu

I first reported this against 62 in Launchpad: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798103

Firefox was since updated to 63 in Ubuntu and the issue remains.

Vastaa viestiin sen kontekstissa (Mozilla Bugzilla)

Text highlight mismatch in view-source when layout.css.devPixelsPerPx is >= 1.2

17. marraskuuta 2018 klo 15.11
Sijainti: Vianhallintajärjestelmät: Mozilla Bugzilla
Avainsanat: Firefox

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0

Steps to reproduce:

1. Open `about:config`, find `layout.css.devPixelsPerPx` and change the value from default (-1.0) to 1.2.
2. Open a view-source view with long lines: `view-source:https://www.youtube.com/user/10asti10`
3. hit Ctrl+f, search for rss
4. using the LMB, try selecting some text, then copy and paste it somewhere

Actual results:

After step 3, the highlighted text on the page is not ”rss”. The highlight doesn’t even adhere to letter widths (screenshot 1).

After step 4, the pasted text is not even close to what you’ve selected to copy.

Expected results:

For the search to hightlight an occurence of ”rss”, and for the pasted text to correspond to what I’ve selected from the view-source view.

Vastaa viestiin sen kontekstissa (Mozilla Bugzilla)

Today I received two new copies of the ”Important updates to your Flickr account” email

14. marraskuuta 2018 klo 16.41
Sijainti: Muut: flickr
Avainsanat: Flickr, saavutettavuus, Yahoo!

Last week, after receiving the ”Important updates to your Flickr account” notification email I deleted my Flickr account, associated with my Yahoo account. Today I received two new copies of the ”Important updates to your Flickr account” email. I tried to access the old Flickr account to make sure it has been deleted, but logging in with my Yahoo account only creates a new Flickr account, which is not what I want.

What I want is to have no more email messages sent to me from Flickr.

I also tried logging in using my Gmail address (which also appears to have a Yahoo account associated with it), but opening flickr.com after that also just creates a new Flickr account every time. I keep deleting these accounts, only to be handed a new one every time I go back to flickr.com.

Back in April-May, I received altogether 5 separate messages informing me about the SmugMug ownership business, so something’s clearly not right with your emailing system, or with the records you have of me.

Your email messages should follow the semi-standard practice of including a footer with a clear explanation of why exactly am I receiving the email and what I should do if I wish to stop receiving them. The ToS and Community Guidelines links (currently in the footer) are all but useless in this context.

 

Vastaa viestiin sen kontekstissa (flickr)

Näytti koskevan myös tv-sisältöjen syötteitä

12. marraskuuta 2018 klo 20.54
Sijainti: Blogit: Yle Areena -blogi
Avainsanat: Yle Areena

Kiitos selonteosta, ihmettelinkin tätä. Näytti koskevan myös tv-sisältöjen syötteitä, niistäkin tuli tänään uusintoja.

Vastaa viestiin sen kontekstissa (Yle Areena -blogi)

Cover2 also appears to exhibit this in single post view

6. marraskuuta 2018 klo 14.34
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: WordPress

My test blog is running WP 5.0-beta3-43867 with Gutenberg 4.3.0-alpha-0841246 (from Daniel Bachhuber’s nightly), and the theme I’m using is Cover2 (Github here), which also appears to exhibit this in single post view.

I’ve narrowed it down to this function (called from header.php), where the gutenberg_parse_blocks() call triggers the issue.

I’m not saying I’m 100 % sure it’s Gutenberg and not the theme(s) at fault here, but I just thought I’d post this just in case it helps to find out either way.

Vastaa viestiin sen kontekstissa (Github)

Vanhempia »