Last week, I saw a dropdown next to the login field for Ubuntu with a few "boot options" or something like that, one of them being Kodi. I was curious and wanted to see what it was so I picked Kodi and rebooted. Nothing happened, and I forgot about it.
Today I had to reboot for another reason and Ubuntu is now booting into a fullscreen version of kodi (Kodibuntu?) with seemingly no way to exit. I can't alt-tab, I can't open a terminal (neither ctrl-alt-t or f1/f4 work). I looked in the system settings and I see no way to revert it. I can see that my document's are still there using Kodi's file browser but can't access any of them. I really need this fixed today, please help.
Check out this documentation on kodibuntu for how to swap back
you can exit the full screen version of kodibuntu by following the steps outlined in the link above.
Sorry if this is unclear but a screenshot would be useful to know what screen you're on.
Related
I have a Theia IDE built in a docker.
Every time I launch a new docker and open a python file for the first time, I got some annoying pop-up:
A new tab: Python - Get Started
A pop up: Linter pylint not installed
Both have a Do not show again option. However, it does not work in my use case because every time a user connects, he will get a new Docker.
I tried to look in the settings and preferences but could not find where to disable these pop-ups.
I also tried to look at the settings files (launch.json for example) after having clicked the Do not show again button but nothing change.
The perfect solution for me would be to add a line in the launch.json file to tell Theia to never display those pop-up in the first place but I am not sure it is possible.
If you know a way to do it (in the launch.json or another way) I would be pleased to hear it!
If you know how to do it in VS code I would also be pleased to hear about it as Theia took a lot from VS code
Thanks!
I finally found the answer by observing which files were changed last on the docker.
I found out that you have to write "python.showStartPage": false in /home/theia/.theia/settings.json
However, it was not enough, I also had to add some lines in /home/theia/.theia/plugin-storage/global-state.json.
I don't know which lines exactly as I just copied-pasted the full file from a previous execution. But I would guess that it is one of the lines beginning with gettingStarted.overrideCategory
I am VERY NEW to learning JavaScript, and I was looking for a simple way to test my basic JavaScript, without using the chrome developer tools inside my Chrome Browser. I thought it might be faster than hoping back and fourth to a browser and typing things in the browser's console.
I thought the extension "Debugger for Chrome" would aid in this, but I don't think it's what I want, or I can't figure out how to use it(very new to this)?
I am trying to uninstall it, and I just get a perpetual 'Uninstalling' icon, but it never actually uninstalls(pic attached below). It's been like that for a half hour in the background. I've tried restarting vscode and my PC, and I can't seem to get it out of my editor.
https://i.imgur.com/ip1dDB9.png
I even tried to delete vsCode completely, including the registry items I could get at, after reinstall I had the same error. Restarts of PC also didn't help. But for some reason, this morning after starting up my PC, I was able to remove the extension.
So my issue is resolved, not onto figuring out easier ways to debug with vsCode.
This Javascript error keeps showing up on my desktop, and when i delete it another one will pop up.
Can anybody with knowledge about this please help me?
Oh the image is on Danish so yeah. Translated it says that there was a script-error with the script, and asks if i still want to play the script on this site.
Solution Found
Go to Control Panel
Go to Programs and Functions
See if there is any program that refers to the url-error-message you got, and if there is, delete it.
Note If the program is a program that you need to have for running your system or just an important program, don't delete it, there could be other ways to fix it.
Other ways to fix it
1. Start up the installer that you used to install the program, if there is a button that says "Repair software/program" or something like that; tap the button.
If there isn't a button that says "Repair software/program" (or something like that); try to install the program again.
Bounty Update
I am leaving the question essentially the same, but I just want to point out at the beginning here that I'm most interested in help trying to get the socket between flash (Adobe Animate) and the native debugger working again, as I believe that is the issue I'm having. Or is it a socket between flash and Windows?
Original Question
I've apparently turned something off? Even when I write really bad code (like trying to call a function that isn't there or divide an integer into a fraction), the flash player boots, shows a background color and stops there. No messages in the output window or compiler errors window. If I fix my code, it all runs fine, but for about 30 minutes (ever since I started trying to work with bitmaps for a sprite sheet) I get no runtime errors no matter what kind of mistake I type in my code. Anyone know how to turn it back on?
I've checked my actionscript settings and I have both warning mode and strict mode checked on.
Could it be a socket issue? I admit I have little to no experience working with sockets and only a surface understanding of what that even means. I've added the socket tag. If someone can see that this is clearly nothing to do with sockets, by all means, I'll remove the tag.
UPDATE: 6/22/16
I just reinstalled Adobe Animate CC 2015.2 and no change. I'll try compiling it in flash builder when I get a chance to help pigeon hole the problem. (Edit 6/24: flash builder worked! But my trial version expired the next day so is no longer a viable option).
And I just tried something in the command prompt in Windows 10 as an administrator:
netsh winsock reset catalog
netsh int ip reset reset.log hit
which I found another user on flashdevelop.org used to fix a similar issue, but no change.
And I just tried debugging in Flash Builder. It worked fine (debugger caught bugs) but my trial version expired the next day.
update 6/24
I've tried launching debugger for AIR from within the Adobe Animate CC IDE and it works fine if there are no bugs; it fails to do anything visible (no Iphone emulator, no swf window) if I put a typo or error in the code.
I also just deleted winsock and winsock2, rebooted Windows, then reinstalled winsock and winsock2. No change.
update 6/25
Just tried a system restore in Windows to set all my files and settings and drivers etc. to the way it was a week and a half ago... Also completely uninstalled all Adobe products and reinstalled. No change. I can only imagine that wiping my hard drive and reinstalling Windows would do the trick, but come on, it hasn't come to that has it?
As VC.One suggested, I checked the compile error window (cannot believe I didn't check before! Maybe when I checked before there were no compile errors... Only runtime errors?) and the errors are showing up there. Does this mean that it's catching compile errors but just not runtime errors?
When you force/test a runtime error... make sure you check
Compiler Errors (ALT+F2) and also Output (F2). By Output I mean the window that shows traces (and runtime issues). One of those two should have some feedback for you.
A possible solution is to save a new Workspace. So with those windows for Compiler Errors and Output both open (or tabbed, I tab them next to my Timeline) go to Window (in top options like File/Edit/Debug etc) and choose Workspace, then into that you choose New Workspace. Give it a name in the pop-up and okay everything.
Flash should always load that current workspace (next time, go to Workspace option again, check that your specified workspace [by name] has a tick next to it...).
Possible pitfalls:
1 - Use the debug player
2 - Make sure there isn't somewhere a try/catch enclosing the portion of code that triggers the event that may lead to an error
3 - Socket issue: may be exported in debug mode but swf cannot connect to debugger (it waits in a blank state for 60 seconds I guess)
4 - Does it compile ok? If there are compilation errors you may get an SWF anyway but then it will not start
...
Because my work will get lighter for the next month or so, I decided to mess around with OS's, just to see how they work. I found this website, and I'm trying to run the code he provided. I am following the instructions exactly (to the best of my ability), but when I go to try booting with QEMU, I get this text:
SeaBios (version-blahblah)
Booting from Hard Disk...
Boot failed: could not read the boot disk.
Booting from Floppy...
And it never actually boots. I am relatively new to Ubuntu, and hoping that somebody would be able to point me towards where I made a mistake. I hope this is enough information to diagnose my error, and thanks in advance!
EDIT: Alright, I tried another tutorial which took me through very similar steps (but with slightly different code), and I still had the same issue. I also booted MikeOS from the floppy image it comes with, and it worked fine.
EDIT 2: Aaaaah! I just realized that when I pressed Ctrl+C, the text that was supposed to appear appeared for just a moment, then went away, along with QEMU. What can I do to make the text appear sooner? I've tried moving the infinite loop to after the display command, but to no avail.
I want to start by saying that I didn't read the entire page you provided (as I don't have enough time). However, the error that you cannot boot from HDD, regardless of the OS, usually (always in my previous experiences) means that either the MBA (Master Boot Record) is messed up/incorrect or you don't have a partition with a boot flag on it.
When I have some time I'll look deeper into that page and see if i can find exactly what the problem could be.
Do you have the bytes 0x55, 0xAA at offset 510 of your MBR?