System not start: Gave up waiting for suspend/resume device

I updated Ubuntu 16.04 to 18.04 and the computer is no longer started. Shows the black screen with two lines of text:

Gave up waiting for suspend/resume device /dev/sda5: clean, 654724/11321344 files, 11449255/45268224 blocks 

I can log in with [ctrl]+[alt]+[f2] to tty2, but once validated with username and password I receive the message:

[...] Could not find key with description: [228ce0775a82ad3] [...] Could not find valid key in user session keyring for sig specified in mount option: [228ce0775a82ad3] [...] Error parsing options; rc = [-2] 

I can start the graphical environment with startx and it seems that everything works correctly.

I tried several options I found on the network, but nothing worked. I have mainly done tests with the /etc/initramfs-tools/conf.d/resume file. Nothing.

Where can the problem be? How do I solve it?

Thanks, Josep

Magento 2 Magnifier using set the zoom product image at mobile device

I want to magnifier enable at the product details page using this way. but there magnifier enable at the desktop device.

 <var name="magnifier">         <var name="fullscreenzoom">20</var>  <!-- Zoom for fullscreen (integer)-->         <var name="top"></var> <!-- Top position of magnifier -->         <var name="left"></var> <!-- Left position of magnifier -->         <var name="width"></var> <!-- Width of magnifier block -->         <var name="height"></var> <!-- Height of magnifier block -->         <var name="eventType">hover</var> <!-- Action that atcivates zoom (hover/click) -->         <var name="enabled">false</var> <!-- Turn on/off magnifier (true/false) -->         <var name="mode">outside</var> <!-- Zoom type (outside/inside) -->   </var> 

Actually i want to enable magnifier at the mobile device.

Bitlocker, does additional authentication at startup with TPM device provide any extra security?

Will enabling additional authentication on startup provide any extra security with Bitlocker? At the moment, my laptop boots straight into a Windows login where I use a pin. If I chose to not use pin, and a complex password, would that provide the same level of security as authentication at startup?

Thanks,

Camera app works in emulator, not on physical device

I have made a camera app that takes photos using the Camera following this guide here. Then it uses the photo’s file to fill in various views, and adds my picture reference to my SQLite db.
Currently my app works on my emulator, but not on my actual device. Sometimes I am getting a warning on my device, that I may be doing too much work on my main thread. But perhaps there is another issue.

The issue: After calling the Android picture activity with takePictureIntent (under dispatchPictureIntent()), I take the picture and after I confirm saving the picture this is the log I get.

Any help is very much appreciated, and thank you community.

<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />     <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" /> 

My logs are in the case where i do not have maxSdkVersion 18 specified (as recommended). I have tried both ways with no difference.The issue: Any help is very much appreciated, and thank you community.

    @Override     protected void onActivityResult(int requestCode, int resultCode, Intent data) {         if (requestCode == REQUEST_IMAGE_CAPTURE && resultCode == RESULT_OK) {             File image = currentFile;             if(image.exists()) {                 Bitmap imageBitmap = BitmapFactory.decodeFile(currentPhotoPath);                 imageView.setImageBitmap(imageBitmap);                 imageView.setVisibility(View.VISIBLE);                 editText.setVisibility(View.VISIBLE);                 saveButton.setVisibility(View.VISIBLE);             }         }     }      private void dispatchTakePictureIntent() {         Intent takePictureIntent = new Intent(MediaStore.ACTION_IMAGE_CAPTURE);         // Ensure that there's a camera activity to handle the intent         if (takePictureIntent.resolveActivity(getPackageManager()) != null) {             // Create the File where the photo should go             File photoFile = null;             try {                 photoFile = createImageFile();             } catch (IOException ex) {                 Log.d(MyDatabaseHelper.TAG, "Error while trying to create File for photo");             }             // Continue only if the File was successfully created             if (photoFile != null) {                 Uri photoURI = FileProvider.getUriForFile(                         this,                         "com.jkim176.project1.fileprovider",                         photoFile);                 currentFile = photoFile;                 takePictureIntent.putExtra(MediaStore.EXTRA_OUTPUT, photoURI);                 startActivityForResult(takePictureIntent, REQUEST_TAKE_PHOTO);             }         }     }      private File createImageFile() throws IOException {         // Create an image file name         String timeStamp = new SimpleDateFormat("yyyyMMdd_HHmmss").format(new Date());         // prefix for description         currentTimeStamp = new SimpleDateFormat("yyyyMMdd").format(new Date());         currentImageFileName = "JPEG_" + timeStamp + "_";         // app-private media directory         File storageDir = getExternalFilesDir(Environment.DIRECTORY_PICTURES);         File image = File.createTempFile(                 currentImageFileName,  // prefix                 ".jpg",   // suffix                 storageDir     // directory         );          // Save a file: path for use with ACTION_VIEW intents         currentPhotoPath = image.getAbsolutePath();         return image;     } }  
D/ViewRootImpl@64ac3b9[AddMediaActivity]: ViewPostImeInputStage processPointer 0 D/ViewRootImpl@64ac3b9[AddMediaActivity]: ViewPostImeInputStage processPointer 1 D/ViewRootImpl@64ac3b9[AddMediaActivity]: MSG_WINDOW_FOCUS_CHANGED 0 D/SEM_CLIP_SemClipboardManager: isCocktailBarDisplayed : false D/OpenGLRenderer: endAllActiveAnimators on 0x778867d000 (RippleDrawable) with handle 0x779886cd60 D/ViewRootImpl@64ac3b9[AddMediaActivity]: mHardwareRenderer.destroy()#1 D/ViewRootImpl@64ac3b9[AddMediaActivity]: Relayout returned: oldFrame=[0,0][1440,2560] newFrame=[0,0][1440,2560] result=0x5 surface={isValid=false 0} surfaceGenerationChanged=true Application terminated.   

Cast to device working but not from chromecast or other applications

I have a strange behavior that I cannot find any explanations for. I currently have Windows 10 installed and my current setup allows me to use “Cast to Device” from the explorer contextual menu to project a file to a TV.

While this works great, the same is somehow not possible when using “Project to a second screen” menu since the device is not listed. The exact same behavior occurs when attempting to cast from Chrome or other applications such as VLC.

Can anyone explain what is so special about the Cast to Device from explorer; why would it work and not anywhere else. It almost seems like it has additional permissions of some kind.

Thanks!

Cannot boot Ubuntu due to usb device descriptor error

My device was working fine until I restarted it. I was trying to backup my files from my external harddrive before restarting the device. Now the message is : usb 1-1.5: device descriptor read/64, error 64 And I also have windows as it is dual boot system and windows is working just fine. I have also tried fsck /dev/sdb3 but I don’t know what should I write instead sdb3.

My USB device (camera) works but doesn’t have device-entry. How to find it?

My USB device (microscope camera) works with my MacBook (lite version of a microscope software) but doesn’t have device-entry, although it shows in the USB tree in system information and has location id I couldn’t find any difference in /dev before and after plugging it in and I need to find it because otherwise, I can’t manually map the device-entry from the native OS to a symlink in the bottle of the CrossOver application which is the full version of the microscope software which normally only runs on windows. The need for symlink is so the software has access to the USB device as CrossOver normally doesn’t connect directly to hardware ports or devices on the computer. (CrossOver is for running windows apps on Mac etc…)