Unable to Read Askpass Response From '/usr/libexec/openssh/gnome-ssh-askpass'

Anybody:

Welcome to CSE 20289 Systems Programming, which (as the syllabus states) is a class that "introduces students to the Unix programming environment where they volition explore various command line utilities, files, processes, memory management, system calls, data structures, networking, and concurrency". What this means is that y'all will outset larn how to effectively utilize a modernistic Unix programming environment so you will written report how to develop applications that take advantage of organisation level abstractions such as files, processes, and sockets.

Grade Overview

Last semester, well-nigh of you took the CSE 20311 Fundamentals of Computing grade where you learned how to program in the C++ language. After playing the Game of Life, generating anagrams, and building fractals, yous should be capable of programming in a compiled language using conditional statements, loops, functions, and classes. Moreover, you should exist somewhat familiar with strings, arrays, and those crazy pointers.

In this grade, we will build on this foundational noesis by exploring the Unix programming environment in guild to go a better thought of how a computer works and how to build applications that apply dissimilar aspects of traditional software and hardware systems. The semester tin exist broken down into the following sections:

Using the Shell

We will begin by learning how to utilize the Unix beat and and then how to etch multiple Unix utilities into pipelines and then shell scripts.
Python Scripting

Next, we will explore scraping, visualizing, and processing information using Python. Along the way, we will discuss functional programming, parallel computing, and distributed calculating and use these techniques to beast-force crack passwords.
C Programming

After Spring Break, we will descend downwardly the software stack to C and hash out retentivity management and data representation as well as revisiting pointers, strings, arrays, and studying some information structures.
System Calls

Finally, we will build our ain Unix applications that accept advantage of organization level abstractions such every bit files, processes, and sockets through the employ of system calls. All of this exploration will culminate in a HTTP client and server.

Moreover, throughout the course, we volition frequently examine the wisdom and power of the Unix Philosophy:

Write programs that do one thing and do it well.
Write programs to piece of work together.
Write programs to handle text streams, because that is a universal interface.

Each week there volition be a reading consignment meant to requite you a context and reference into what we volition be roofing that upcoming week and a homework consignment that will provide y'all an opportunity apply the material in (hopefully) interesting ways. Of course, there are three exams to assess your mastery of the material.

TL;DR

For this week, you need to read near using the command line and Git, and and then setup your GitLab repository. There is nothing to submit.

Readings

The readings for Friday, January 18 are:

The Linux Command Line
- Chapter i - What is the Shell?
- Chapter 2 - Navigation
- Chapter three - Exploring the System
- Chapter 4 - Manipulating Files and Directories
- Affiliate v - Working With Commands
Git Handbook

Note, although we volition exist using GitLab instead of GitHub, most of the documentation for git, including this handy cheatsheet works on either platform.
Pro Git
- Chapter 1 - Getting Started
- Chapter 2 - Git Nuts
- Chapter 3 - Git Branching

The focus of the readings is to review the basics of using the Unix shell, which near of yous used in CSE 20311 Fundamentals of Calculating last semester, and to introduce you to Git, which we will be using throughout the semester.

In improver to reading the above chapters, it is recommended that yous piece of work through the following tutorials:

Command Line Crash Course

This is a tutorial on using the command line interface on various operating systems (you lot should focus on the Unix shell).
Learn Git Branching

This is an interactive tutorial on branching in Git.

The Hands-on Imperative

To become the about out of your reading, you lot should be typing commands into a terminal and playing around with the things you reading.

Passively reading volition non be as fruitful equally actively reading and trying out things y'all are exploring.

Boosted Resources

The following are additional resources that you lot may find useful:

Unix Shell

Learning the Shell
Survival guide for Unix newbies

Git

gittutorial
Outset using Git on the command line

GitLab

Normally, y'all would have quiz to complete after each reading. For this first consignment, even so, yous but need to create your own private assignments Git repository on GitLab past post-obit the instructions below:

Assignments Repository

The assignments repository will be used for your private weekly reading and homework assignments. It must be kept private and simply shared with the instructional staff.

The grade projects will exist collaborative, so we will create separate repositories for those assignments.

Chore 0: Create GitLab Account

The first step is to create a GitLab account if you don't take 1 already. GitLab is a code hosting repository like to Bitbucket and GitHub. We will be using GitLab this semester since it provides for unlimited private repositories and no restrictions on the number of collaborators. Too, GitLab has built-in for continuous integration which will be using later in this grade.

To create an account, get to https://gitlab.com/users/sign_in and follow the prompts there.

Job ane: Fork Assignments Repository

In one case you are signed up and have logged in, go to the class assignments repository located at: https://gitlab.com/nd-cse-20289-sp19/cse-20289-sp19-assignments and click on the Fork push. This will create a copy of the original assignments repository to your personal GitLab account.

Task 2: Configure Repository Settings

Next, you will configure the assignments repository then that it is individual. That is, merely yous and the instructional staff should have access to it. To exercise this, click on the Settings gear on the bottom left-manus side of the project page, and and then select General.

You volition then be taken to the Project settings page for the repository. Aggrandize the Permissions section and set your Project Visibility to Private and then gyre down and click the green Save Changes push button.

Afterwards, expand the General project settings settings and add your name and netid to the Projection description. In one case you accept made these changes, make certain you gyre down and click on the Save changes push button.

Task three: Add Instructional Staff

Next, you will ensure that the instructional staff has access to your repository by clicking on the Settings gear on the bottom left-mitt side of the project page and select Members.

This volition take you to the page to add new users to the project. Y'all will need to add all of the instructional staff as role of your project (both instructors and all the teaching assistants):

Alex Ayala (@aayala4)
Catalina Vajiac (@catvajiac)
Conor Nailos (@cnailos)
Edoardo Bianchi (@ebianchi98)
Emily Strout (@estrout)
Grace Milton (@gmilton)
Jack Collins (@JaCollins)
Joo Yun (Rosa) Kim (@jkim63)
Kathleen Capella (@kcapella)
Kyle Miller (@myle_killer)
Logan Yokum (@lyokum)
Michael Moynihan (@mmoyniha)
Peter Bui (@pbui)
William Diederich (@wdiederi)

Each instructional staff member should be given Developer access and an expiration date of 2019-06-01.

Task iv: Clone Repository

In one case you take a private fork of the assignments repository and have configured it properly, you should clone it to your local workspace. This workspace tin can either exist on the student machines, a virtual automobile, or your personal machine.

To do this, copy the URL from the Projection summary page and perform the clone command using Git on your desired platform. You lot will now have a local clone of the repository you can piece of work with:

                        # Example on a student machine            $ git clone https://pbui@gitlab.com/pbui/cse-20289-sp19-assignments.git            # Clone the remote repository to the student machine            Cloning into            'cse-20289-sp19-assignments'...            (gnome-ssh-askpass:31733): Gtk-WARNING **: cannot open display: mistake: unable to            read            askpass response from            '/usr/libexec/openssh/gnome-ssh-askpass'            Countersign            for            'https://pbui@gitlab.com':  remote: Counting objects:            47,            done. remote: Compressing objects:            100%            (7/7),            done. remote: Total            47            (delta            0), reused            0            (delta            0)            Unpacking objects:            100%            (47/47),            washed. Checking connectivity...            done

Username

If yous try to do a git clone and see a 401 unauthorized error, exist sure to include your GitLab username in the URL:

              $ git clone https://$USERNAME@gitlab.com/$USERNAME/cse-20289-sp19-assignments.git

SSH_ASKPASS Workaround

If you endeavour to practice a git clone on the pupil machines and information technology starts but fails to inquire y'all for a countersign, try running this command get-go:

This will force Git to use the terminal to ask you for your password rather than popup a window.

Task five: Commit First Modify

Your concluding task is to practise using Git by editing the README.md file in the assignments repository such that the Proper noun and NetID fields are completed (i.e. supersede "Domer McDomerson" and "dmcdomer"). You should commit your modify and so button them to GitLab.

                        # Example on a student machine            $            cd            cse-20289-sp19-assignments            # Go into the assignments directory            $ nano README.medico            # Edit the README.dr. file            $ git add README.md            # Marker the file for recording            $ git commit -m            "Update README"            # Tape the change            [master c550fa1]            Update README            i            file inverse,            ii            insertions(+),            2            deletions(-)            $ git push            # Ship your local changes to GitLab            (gnome-ssh-askpass:1030): Gtk-Alert **: cannot open display: error: unable to            read            askpass response from            '/usr/libexec/openssh/gnome-ssh-askpass'            Password            for            'https://pbui@gitlab.com':  Counting objects:            5,            done. Delta pinch using upward to            12            threads. Compressing objects:            100%            (iii/iii),            done. Writing objects:            100%            (3/3),            325            bytes |            0            bytes/southward,            washed. Total            iii            (delta            ii), reused            0            (delta            0)            To https://pbui@gitlab.com/pbui/cse-20289-sp19-assignments.git   2d0303d..c550fa1  master -> master

The following is a video demonstration of the process of cloning your GitLab repository and committing your outset change.

Markdown

The README.doctor files are annotated using Markdown. This is a simple obviously text formatting style that tin be translated into HTML.

For a more complete case of what yous can do with Markdown, bank check out the reference provided by GitLab. To view the result of the translation, you lot tin utilize the provided mdview.sh script.

haleyafriallifuld.blogspot.com

Source: https://www3.nd.edu/~pbui/teaching/cse.20289.sp19/reading00.html