ubuntu 18.04 nvidia driver issues

First: I have tried for MANY hours and numerous fixes to try to get this to work. So I am sorry that this is filled with questions that have been asked multiple times. Second: I am not very good with linux, so please excuse my ignorance

  • I could not get an external monitor to be recognized, so I installed nvidia driver 390 as it was recommended
  • Monitor still was not recognized, so I opened x server and it looked like this: xserver
  • one of the fixes for xserver was to purge nvidia drivers and reinstall (390 again), so I did
  • now my system is booting to a black screen, and only works in recovery mode
  • I tried newer drivers, including one downloaded directly from nvidia (418 I believe), that installation failed. So I downloaded it through the terminal. Still black screen
  • secure boot is disabled in the bios
  • my system is set up for dual boot on two separate SSDs
  • ever since upgrading to 18.04 my computer will not shut down properly or reboot, it gets to the end of the process and never powers off. I wiped the drive and did a fresh install of Ubuntu, but still isnt working (apparently this can be an issue stemming from the graphics card driver as well). This i can live with, black screens I cannot

Thoughts, feelings, suggestions? Helps would be appreciated!

More screenshots for fun: something somethingelse recommended

Is my database schema going to work? Tracking git issues

My boss wants an automated weekly report on how many git issues have been moved to and from various “lanes” (pipelines) on a virtual kanban board. I wrote a quick python script to get that data using Github and Zenhub APIs, and now I’d like to write that data to disk.

My current plan is to run this script once an hour, and write to a transaction table when I see that an issue has changed pipelines. Here’s a diagram of my current schema: db schema

So my question is, will this schema be able to support a large number of entries in the Transactions table? This will be tracking somewhere between 1,000 – 10,000 issues, with 50 – 1,000 transactions a day.

Some things worth mentioning:

  • There can be two or more issues with the same IssueNumber and different repoIDs (issues are assigned a number when opened starting from 1). So I’d like to use both RepoID and IssueNumber as the primary key for Issues table.
  • I might have the one-to-many arrows backwards, for example I’m trying to say that one RepoID can correspond to many entries in the Issues table but each entry only corresponds to one RepoID.

I’ve never really designed a database before and there aren’t really coworkers that can help me, so I would appreciate any advice or criticism on this schema.

Monitoring and detecting AdSense issues on your site

Our Ads Monitor service can continuously track AdSense ads displayed on your site and timely inform you of potential revenue affecting issues.

It works with the Ads Monitor agent that periodically visits your site as a regular user from a desktop or a mobile device and captures displayed ads. The service analyses the ads and reports to you in a convenient daily or weekly email digest. On the Ads Monitor site you can review the ads for any time period and…

Monitoring and detecting AdSense issues on your site

Monitoring and detecting AdSense issues on your site

Our Ads Monitor service can continuously track AdSense ads displayed on your site and timely inform you of potential revenue affecting issues.

It works with the Ads Monitor agent that periodically visits your site as a regular user from a desktop or a mobile device and captures displayed ads. The service analyses the ads and reports to you in a convenient daily or weekly email digest. On the Ads Monitor site you can review the ads for any time period and…

Monitoring and detecting AdSense issues on your site

MacBook 2.1 late 2006 issues with installation of Ubuntu 18.04

I rescued an old MacBook 2.1 late 2006 13″ from my job. After a deep search of couple days I found this video https://www.youtube.com/watch?v=NIsF96jx87A&t=539s who help me to install ubuntu 16.02 on my old macbook laptop. Now, I’ve been trying to install ubuntu 18.04, unfortunately after the installation ( it looks like everything went well during this process) after first reboot the laptop cannot start the OS, first started with a black screen and when I forced pushing the turn on botton, I can see the system loading the OS again, but the screen goes to a pink-violet screen and the OS never comes up.

I really want to make an use of this old laptop and see if i can upgrade the Ubuntu version,I will appreciate if someone can help me.

Thank you!

Ubuntu 19.04 on a Microsoft Laptop – Keyboard & Touchscreen issues

I just installed Ubuntu 19.04 from a USB-Stick to my Microsoft Laptop and I noticed that my Keyboard doesn’t work (during the installation & afterwards). While installing I just plugged in a USB-Keyboard, but I would like to be able to use the internal keyboard. The same goes for the Touchscreen (doesn’t work at all).

I have seen a post about a similar issue but for Linux 18: Installed Ubuntu 18.04 on Microsoft Surface Book, and keyboard does not work. (only external keyboard)

Hope someone can help me out here.

Thank you! Jakob

What are the possible issues and Highlighted features of Magento2.3.2

Magento Commerce 2.3.2 Release Notes has released on June 29.

Patch code and release notes published on June 25, 2019. Release notes last updated on July 8, 2019.

  1. What are the highlighted features in this version directly as a list
  2. What are the possible Issues
  3. what are the differences between this version and the previous version.

Facing issues on updating magento in magento cloud, updating magento to latest version of magento 2.3.2

Right now we are working on updating magento to latest version of magento 2.3.2 right now we are runing 2.2.7.

I following the guide for 2.3 branch found at https://devdocs.magento.com/guides/v2.3/cloud/project/project-upgrade.html

I have taken following steps :

Step1: Update ece-tools version

On local workstation, perform an update using Composer

composer update magento/ece-tools

Add, commit, and push code changes.

git add -A && git commit -m “Update magento/ece-tools” && git push origin

Step2: Back up the database

Create a local backup of the remote database.

magento-cloud db:dump

when i run this command in my terminal i get ‘magento-cloud’ is not recognized as an internal or external command, operable program or batch file.

Back up code and media.

php bin/magento setup:backup –code [–media]

To back up Staging or Production environment database before deploying

php vendor/bin/ece-tools db-dump

Step3: Complete the upgrade

I have PHP 7.1.30 version

Before completing the upgrade, update the autoload property I follow all the steps giving in https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html#update-autoload

set the upgrade version using

composer require magento/product-community-edition 2.3.2 –no-update

Then Update the project

composer update

After composer update i get some error

Your requirements could not be resolved to an installable set of packages.

Problem 1

- magento/magento-cloud-metapackage 2.2.7 requires magento/product-enterprise-edition 2.2.7 -> satisfiable by magento/product-enterprise-edition[2.2.7] but these conflict with your requirements or minimum-stability.  - magento/magento-cloud-metapackage 2.2.7 requires magento/product-enterprise-edition 2.2.7 -> satisfiable by magento/product-enterprise-edition[2.2.7] but these conflict with your requirements or minimum-stability.  - Installation request for magento/magento-cloud-metapackage >=2.2.7 <2.2.8 -> satisfiable by magento/magento-cloud-metapackage[2.2.7]. 

Can you please guide me how can i solve this issue..

Thanks in advance.

My composer.json is

{ "name": "magento/project-enterprise-edition", "description": "eCommerce Platform for Growth (Enterprise Edition)", "type": "project", "version": "2.3.2", "license": [     "OSL-3.0",     "AFL-3.0" ], "repositories": {     "repo": {         "type": "composer",         "url": "https://repo.magento.com"     },     "amasty": {         "type": "composer",         "url": "https://composer.amasty.com/enterprise/"     } }, "require": {     "magento/magento-cloud-metapackage": ">=2.2.7 <2.2.8",     "gene/bluefoot": "^1.0",     "amasty/promo": "^2.2",     "sashas/bug-from-email": "^2.0",     "amasty/shopby": "^2.11",     "amasty/label": "^1.10",     "connectpos/rest-api": "^1.1",     "magento/product-community-edition": "2.3.2",     "magento/product-enterprise-edition": "2.3.2" }, "config": {     "use-include-path": true }, "autoload": {     "psr-4": {         "Magento\Framework\": "lib/internal/Magento/Framework/",         "Magento\Setup\": "setup/src/Magento/Setup/",         "Magento\": "app/code/Magento/",         "Zend\Mvc\Controller\": "setup/src/Zend/Mvc/Controller/"     },     "psr-0": {         "": [             "app/code/",             "generated/code/"         ]     },     "files": [         "app/etc/NonComposerComponentRegistration.php"     ],     "exclude-from-classmap": [         "**/dev/**",         "**/update/**",         "**/Test/**"     ] }, "autoload-dev": {     "psr-4": {         "Magento\Sniffs\": "dev/tests/static/framework/Magento/Sniffs/",         "Magento\Tools\": "dev/tools/Magento/Tools/",         "Magento\Tools\Sanity\": "dev/build/publication/sanity/Magento/Tools/Sanity/",         "Magento\TestFramework\Inspection\": "dev/tests/static/framework/Magento/TestFramework/Inspection/",         "Magento\TestFramework\Utility\": "dev/tests/static/framework/Magento/TestFramework/Utility/"     } }, "minimum-stability": "alpha", "prefer-stable": true, "extra": {     "magento-force": true,     "magento-deploystrategy": "copy" }, "require-dev": {     "allure-framework/allure-phpunit": "~1.2.0",     "friendsofphp/php-cs-fixer": "~2.13.0",     "lusitanian/oauth": "~0.8.10",     "magento/magento-coding-standard": "~1.0.0",     "magento/magento2-functional-testing-framework": "~2.3.14",     "pdepend/pdepend": "2.5.2",     "phpunit/phpunit": "~6.5.0",     "sebastian/phpcpd": "~3.0.0",     "squizlabs/php_codesniffer": "3.3.1" }} 

Issues with time in Ubuntu 18.04

I’m noticing that there’s an issue with the time in my computer. It’s changing from 8:xx AM to 02:xx constantly. I used the following command timedatectl to see the actual time of the system.

I wonder if there’s a bug or something going on with this, as it’s a strange behavior

issue_time

diego@diego-G5-5587:~$   timedatectl                       Local time: vie 2019-07-12 08:17:48 CST                   Universal time: vie 2019-07-12 14:17:48 UTC                         RTC time: vie 2019-07-12 14:17:41                        Time zone: America/Tegucigalpa (CST, -0600)        System clock synchronized: yes systemd-timesyncd.service active: yes                  RTC in local TZ: no diego@diego-G5-5587:~$   timedatectl                       Local time: vie 2019-07-12 02:18:00 CST                   Universal time: vie 2019-07-12 08:18:00 UTC                         RTC time: vie 2019-07-12 14:17:52                        Time zone: America/Tegucigalpa (CST, -0600)        System clock synchronized: yes systemd-timesyncd.service active: yes                  RTC in local TZ: no diego@diego-G5-5587:~$   ^C diego@diego-G5-5587:~$   timedatectl                       Local time: vie 2019-07-12 08:23:20 CST                   Universal time: vie 2019-07-12 14:23:20 UTC                         RTC time: vie 2019-07-12 14:23:14                        Time zone: America/Tegucigalpa (CST, -0600)        System clock synchronized: yes systemd-timesyncd.service active: yes                  RTC in local TZ: no