Issue in make debug terminal

[PranabNandy]

I am able to successfully close the make gdb terminal
but when I am trying to close make debug terminal with ctrl+a followed by x, nothing is happening

[streetdogg]

ctrl+a x has been consistently working for me. There are some ways listed here too: https://superuser.com/questions/1087859/how-to-quit-the-qemu-monitor-when-not-using-a-gui

If not, I recommend killing the qemu process from another terminal. Try these:

1. ps -aux | grep qemu
   1. Look for qemu-system-riscv32 -S -M virt -nographic -bios none -kernel main.elf -gdb tcp::1234 and copy the process number.
2. kill <process id>

---

See if attached screenshot is useful -

[PranabNandy]

Thank you for the information.

Another problem now I am facing like CodeSpace is not opening now

[streetdogg]

@PranabNandy - Sure. I'd really appreciate it if you could add some data that makes it easy to help. Be detailed about the steps to reproduce the issue.

[PranabNandy]

Previously I was able to open the Code Space
Now only this screen is coming
No other thing is happening for me

[PranabNandy]

When I am trying to follow the steps to set up the lab in linux machine
I am not getting the same colour terminal as you are showing the video.
when I am executing this command
sudo chown -R c-ninja .
I am writing sudo user password still it is not accepting

[streetdogg]

Previously I was able to open the Code Space Now only this screen is coming No other thing is happening for me

This usually takes some time. But it should show some output.

When I am trying to follow the steps to set up the lab in linux machine I am not getting the same colour terminal as you are showing the video. when I am executing this command sudo chown -R c-ninja . I am writing sudo user password still it is not accepting

What password did you use? The password to be used is c. The terminal colors for you seem different because your terminal theme may be different. That is alright. Can you try using c as the password for the c-ninja user?

[PranabNandy]

This usually takes some time. But it should show some output.

• It's been like 30 mins I opened the window but it stuck to the same screen

What password did you use? The password to be used is c. The terminal colors for you seem different because your terminal theme may be different. That is alright. Can you try using c as the password for the c-ninja user?

• Actually I did not use the password c. Now it is working

Thank you

[PranabNandy]

One more thing I would like to mention, while executing this command wget -P ~ https://git.io/.gdbinit, I was facing this issue

Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 49.44.79.236, ::ffff:49.44.79.236
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|49.44.79.236|:443...

I followed this Link to resolve it
https://www.debugpoint.com/failed-connect-raw-githubusercontent-com-port-443/

But the ip address 185.199.108.133 they are using is not working for me

Then I checked the IP address in the video which is 185.199.111.133, it worked for me.

[streetdogg]

that's odd, but I am glad it's working for you now. Would you say we can conclude this issue?

[PranabNandy]

In conclusion, I would say Codespace is not opening for me. Even though it opened for the first day.

I installed the Docker Image in my local machine and everything is working fine there.

[streetdogg]

can you delete and recreate the codespace? I was under the impression that it would work for all. Would really appreciate your help with more data on this, it might help others who don't have a powerful machine and high-speed internet.

[PranabNandy]

I deleted the codespace and recreated it but still, it did not open for me.

I even deleted the repo and forked it again still, the same problem is there.

[streetdogg]

Very strange. I think it would be good to take up with the GitHub support team. This looks beyond us at the moment.

[PranabNandy]

Ok Sure.
Thank you for your kind support.
I think we can close this issue.