Dual Boot Gone Wrong

I need help with my dual boot. I have Windows 10 and Ubuntu running on my 256 GB SSD. The way I have my computer set up is on SSD I have my OS running with my games, while anything else downloaded on WINDOWS 10 will be downloaded to my 1 TB HDD. I tried doing it to Ubuntu one but couldn’t manage it. Then something appeared telling me the storage that was meeting the maximum capacity. Then it just crash, and now every time I want to run Ubuntu this error appears. Thank you for your time and please help.

Here is a link to the picture for contexts. https://imgur.com/ydtjzfV

Recent Google Docs gone after uninstalling & reinstalling the app

I uninstalled Google Docs on my android phone yesterday evening to make space for updating Whatsapp, then reinstalled Google Docs half an hour later. Didn’t think anything of it as it all backs up into Google Drive. However, all my recent documents (everything after December 2018) are gone! They are nowhere to be found, not even in Google Drive! How can this be? I can see in my backups that Docs’ was last backup was on May 8th. However, not sure how to access that. Please help! Thank you in advance.

18.04.2 Emojis partially gone from Librewriter autocorrect

Completed a fresh install and update of 18.04.2 64-bit last week.

It’s perfectly fine. Except many emojis are gone from whatever Noto pack Librewriter uses. I’d like them back. Included below is a picture of the issue.

As you can see, it calls the location of the emoji just fine, but there doesn’t seem to be any data in that part of the font pack that Librewriter would care to display. Not a � but a tall empty rectangle replaces most my emojis.

This is also the case in all my .odt docs. They have an empty rectangle where the emojis used to be before this fresh install, update, and restart.

gedit displays emojis from Right Click > Insert Emoji just fine.

I have no idea what information you need, but i hope this is a good start.

example missing emojis

How can I fix the date formats which have gone wrong in 18.04 when setting first day of the week?

I recently upgraded from Ubuntu Studio 16.04 to 18.04. Some things got reset and need changing back to how I want.

I want the calendar to start on Sunday, and managed to get that done by editing en_GB locale file, making first weekday = 1.

But, now in all other programs, the date formats are in US format, e.g. May 03, 2019; but I want them back to the UK format of 3 May 2019.

Despite the en_GB locale file seeming to have all the right settings, I am now stuck with dates in US format, which is hard to read, e.g. 05/03/19 — is that 5th of March or 3rd of May?

So how can I get it have Sunday as first day of week, and all date formats in UK format (as it all was back in 16.04)?

Postgres – The cost has gone down but the time has increased, why?


TABLE STRUCTURE

CREATE TABLE schema.mylogoperation (   id_mylogoperation serial,   data DATE,   myschema VARCHAR(255),   column_var_2 VARCHAR(255),   user VARCHAR(255),   action TEXT,   column_var_1 TEXT,   log_old VARCHAR,   log_new VARCHAR   constraint pk_mylogoperation primary key (id_mylogoperation) )  WITH (oids = false); 

50 million rows

I tried to explain analyze

explain analyze SELECT     column_var_1,     column_var_2     column_var_3,     user,     action,     data,     log_old,     log_new FROM schema.mylogoperation WHERE     myschema = 'schema' AND column_var_2 IN ('mydata1', 'mydata2', 'mydata3') AND log_old <> log_new AND column_var_1 LIKE 'mydata%';  indexes ( pk_mylogoperation only) QUERY PLAN Seq Scan on myschema  (cost=0.00..713948.14rows=660 width=222) (actual time=380.308..4467.364 rows=48 loops=1)   Filter: (((log_old)::text <> (log_new)::text) AND (column_var_1 ~~ 'mydata%'::text) AND ((schema)::text = 'schema'::text) AND ((column_var_2)::text = ANY ('{mydata1,mydata2,mydata3}'::text[])))   Rows Removed by Filter: 12525296 Total runtime: 4467.425 ms 

Then i tried to create a some index for better performance

CREATE INDEX idx_mylogoperation_1    ON schema.mylogoperation (myschema, column_var_2);  reindex table schema.mylogoperation; analyze schema.mylogoperation;  pk_mylogoperation + idx_mylogoperation_1 QUERY PLAN Index Scan using idx_mylogoperation_qry1 on mylogoperation  (cost=0.56..589836.84 rows=658 width=223) (actual time=331.679..4997.507 rows=48 loops=1)   Index Cond: (((myschema)::text = 'schema'::text) AND ((column_var_2)::text = ANY ('{mydata1,mydata2,mydata3}'::text[])))   Filter: (((log_old)::text <> (log_new)::text) AND (column_var_1 ~~ 'mydata%'::text))   Rows Removed by Filter: 7441986 Total runtime: 4997.580 ms 

Then i tried again to create a some index for better performance

CREATE INDEX idx_mylogoperation_2 ON schema.mylogoperation USING gin (column_var_1 gin_trgm_ops);  reindex table schema.mylogoperation; analyze schema.mylogoperation;  pk_mylogoperation + idx_mylogoperation_1 + idx_mylogoperation_2 QUERY PLAN Bitmap Heap Scan on idx_mylogoperation_var_1  (cost=1398.58..2765.08 rows=663 width=222) (actual time=5303.481..5303.906 rows=48 loops=1)   Recheck Cond: (column_var_1 ~~ 'mydata%'::text)   Filter: (((log_old)::text <> (log_new)::text) AND ((myschema)::text = 'schema'::text) AND ((column_var_2)::text = ANY ('{mydata1,mydata2,mydata3}'::text[])))   Rows Removed by Filter: 248   ->  Bitmap Index Scan on idx_mylogoperation_var_1  (cost=0.00..1398.41 rows=1215 width=0) (actual time=5303.203..5303.203 rows=296 loops=1)         Index Cond: (column_var_1 ~~ 'mydata%'::text) Total runtime: 5303.950 ms 

Why did the cost decrease but the time increased? I do not want to make changes to select, just in the database structure.

Anyone else think Digital Point has gone crap?

It seems that Digital Point has gone to crap. It used to be a great place, very helpful and busy. Having logged in for the first time in years around 8 months ago, I have had nothing but crap from a bunch of moderators who act like the owners bitches.

Two auctions, won by buyers, no payment AWOL. Reported, nothing done.

These new mods are basically a load of BS.

I'm through with Digital Point, now how to I delete my account?

LG G5 – Fingerprint Scanner gone

I have an issue with the LG G5. I bought it like 3 weeks ago and used it very carefully. Now just while using the fingerprint scanner went away. it said restart the phone. After restart even the option is gone.

The same issue is reported here as well but no solution: http://forums.androidcentral.com/lg-g5/683019-fingerprint-options-missing.html

Can anyone help me please? Thanks

Is it possible decrypt Android 8 encryption, if the device encryption key is gone (but with a known PIN and KEK)?

main question is in the title. Some clarification though:

When you factory reset your encrypted phone, the old device encryption key (DEK a) gets deleted and a new encryption key (DEK b) is being generated, which is used to encrypt the device. The DEK is stored in the TEE (correct?). In this case, the PIN before the factory reset was the default android password (default_password).

Since flash-storage is difficult to erase, let’s assume the old key encryption key (KEK) for the DEK (a) has been found. The default android password is known (default_password).

Given the process, on how android gets from the DEK to the KEK…

Previously, we encrypted the master key with a key generated by applying scrypt to the user’s password and the stored salt. In order to make the key resilient against off-box attacks, we extend this algorithm by signing the resultant key with a stored TEE key. The resultant signature is then turned into an appropriate length key by one more application of scrypt. This key is then used to encrypt and decrypt the master key. To store this key:[…]

…is it possible to decrypt the old data? Now, obviously, the KEK can’t decrypt the DEK, because it’s not there anymore (DEK (a) has been deleted), but is it possible to derive the lost DEK (a) with a given PIN (default_password) and the found KEK of the old encryption?

I found this thread already, but i’m not sure if the answer fits my question.

The scrypt KDF is designed to be slow and sufficiently memory-hard to make it difficult to parallelise on common compute platforms (e.g. CUDA). Also notice that they said “one more application of scrypt”; the DEK is already transformed via scrypt, hence it is made infeasible to try to “crack” the DEK by deriving it repeatedly against candidate passwords.