I have recently used "localedef" command to add support for the multiple locales.
After doing that I noticed on my terminal for every "space, backslash, forward slash etc" it is showing UTF code like <0200> <002d> etc.
I really want to disable this behaviour as it is really difficult to read commands.
For more clarity please see attached screenshot.
Issue has been caused due to localedef I am able to confirm post getting a reply from Apple Support team.
As per the support team instruction I created a New User Account and checked terminal. With new account terminal worked well.
Best solution is
New User Account if we want avoid any manual effort.
Otherwise you should compare ENV variables of Old account and New account and fix the issue.
Related
Manually triggering update of an app when running windows in assigned access (Kiosk mode) doesn´t work.
I have read others facing the same issue and it feels like there is a bug in windows Kiosk mode. But maybe there is some reason for this behaviour?
I have an app that I sideload using an appinstaller file (my app consist of both a uwp part and a consol part linked with a bridge connection). The app works well in Kiosk mode besides the update part. If I enable automatic updates and link to a specific folder on my computer the automatic updates will work and update my app from the specific folder. However this way to update requires two restarts before it is automatically updated. I want to be able to manually trigger the update from within the app itself somehow and have it updated instantly.
I have tried to update using packagemanager using the function below. This works well in desktop but will always freeze in bluscreen with progressring if I run it in an account in Kiosk mode (assigned access).
PackageManager pm = new PackageManager();
pm.AddPackageByAppInstallerFileAsync(new Uri("C:\\myLocalPath"), AddPackageByAppInstallerOptions.ForceTargetAppShutdown, pm.FindPackageVolume("C:\\"));
I have also tried to restart the app using the command below in order to trigger the automatic update without the need to restart the entire computer. This also works well in desktop but will freeze in bluscreen if I am in a Kiosk account.
AppRestartFailureReason result = await CoreApplication.RequestRestartAsync("Restart");
Restarting the entire computer two times and enabling automatic updates will update the app without problems. Why is it not possible to use one of the methods above? Is this a bug in windows kiosk mode or is this really intended??
The same issue is also reported here:
problem-when-restart-app-on-kiosk-mode-windows-10
and here:
intune-kiosk-blue-screen-spinner-after-uwp-app-res
See my answer to how I made this work here:
The same problem described on microsoft docs
I don´t feel very confident with the whole assigned access and package installation concept. It works at the moment for me but my feeling is that it is not very stable. Many different ways of creating almost the same thing. The problem is that there are differences between the results depending on how you get there. For instance two assigne access accounts don´t behave the same if you created them differently. Also adding and removing both apps and accounts leaves trash that you don´t see but can cause problems.At least this is my feeling.
I am having a problem starting an X2go client session to an Ubuntu work station. Basically, the x2Go-agent does not scale down to fit my client's side screen resolution. Thus, I cannot reach Ubuntu control panels, switch between programs, etc.
I use the newest download of the x2Go windows client, version 4.0.2.0. I use session settings that worked previously, but we have had an update recently. First, I tried playing around with the session screen size, but none of the options gives a reasonable view. I searched for similar issues and found a bug entry that suggests disabling some NX-extension by commenting the line
X2GO_NXAGENT_DEFAULT_OPTIONS+=" -extension XFIXES"
in etc/x2go/x2goagent.options.
This is not possible for me without appropriate admin rights. Instead, I found out from the changelog that the above option can be overwritten from client-side, but it doesn't say how:
Introduce /etc/x2go/x2goagent.options to allow overriding x2goagent
options. This new configuration file specifies default options that
clients can override.
The man-page of the x2Go client doesn't tell, either. It doesn't seem that there is a command line option to redefine the variable during execution.
Here is my question: Does anyone know how to overwrite the above option from a windows x2go client side?
Thanks for your help!
As far as I know the problem is not fixable from the Windows side. But you can fix the issue by disabling "kcreen" in your KDE where the x2go server is running. See the following citation:
In general, this is not a bug. Using two applications that handle display resolution is not supported
I'm looking for a simple method to prevent Windows Update from installing drivers automatically. Exactly these steps:
http://support.microsoft.com/kb/2500967
Is there any method to do these steps just by modifying registry keys? Or even by doing it with help of a simple bat file?
I've just found an answer. The key I was looking for is located here:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching]
"SearchOrderConfig"=dword:00000000
To add this values to our registry, we can use that command in our batch file:
REGEDIT /S NameOfOurRegFile.reg
I don't know of a registry key, but why not change the windows update to download, but not install. Then you can review the updates and use right-click-hide to hide the driver updates.
I like to see the driver updates because that lets me know that I might want to go to the vendor site to look at the real driver info and decide if I need it or not. I then only install the driver (from the vendors site) if there are changes I need.
And since I have hidden it in update, I don't get bothered again until a new driver comes out.
Just a thought (vs. hacking your registry.)
One other consideration. In some cases, a registry hack might have some side consequences that confound you late when you can't figure out why something you thought should work, doesn't. Most support options don't consider registry hacks when trying to figure out why something doesn't work...
I can't comment, so here are some things to consider.
What you want to do will possibly look very much like a virus that wants to prevent things from being fixed. So if you do find a way, I strongly encourage you to test it with a number of AV apps - and then register it with them so they don't add it later.
You do have an option to check the version of the drivers in use for given hardware items. Then, if your app sees a new driver, it can at least warn the user that a new driver was installed (and log that fact) and to roll the update back if they have problems.
It's a late Sunday night and I decided to mess around with Facebook applications. Turns out they now offer you easy integration with heroku which, of course, I decided to try out.
I patiently waited for the toolbelt to download, installed it and, as usual, nothing will run for me without bit of a struggle.
So I did what I could, googled the problem I'm having and realized that the problem is most likely caused by the fact that my user folder contains non-latin characters.
To make sure that this is the problem, I created another user account, installed heroku toolbelt on it and it works just fine.
Are there any suggestions on how to get this to run without me having to work on the test account?
Thank you for your time!
edit
Forgot to ask wether it's possible to change the folder heroku uses?
edit
Still haven't found anything that would help me fixing this, is there really no way how to fix this?
I've attached the screenshot of error
I've stumbled on this post while being in much the same position. Here goes a solution:
Edit ...\Heroku\lib\heroku\helpers.rb such that def home-directory is as follows:
def home_directory
running_on_windows? ? (ENV['HEROKU_HOME'] || ENV['USERPROFILE']).gsub("\\","/") : ENV['HOME']
end
Now if you set the HEROKU_HOME environment variable to anything the Heroku toolbelt will use that as home. (FWIW: As I have run into this with other tools as well, I set up a link with US-ASCII-only letters to my standard home directory under Users.)
I think what you should do is run the heroku login command from the Git Bash client rather than from the default Windows command line. I have been using the heroku-toolbelt on Windows 7 for about a year now and have not encountered any such problem whatsoever. I had found a way to enable latin characters in the Windows command line sometime ago writing a program in CLIPS, but I don't quite remember how the command goes right now, or what configurations I did. However, if you don't have the standalone Git client installed you can always grab it from: http://git-scm.com.
The title says it. I'm looking for a way to determine exactly which file/registry key this executable is attempting to access. I have attempted to use Windows auditing capabilities and Process Monitor to determine where the failure is happening but, this failure does not produce audit failure events or show as access denial in Process Monitor.
Of course, If someone has experienced this and can provide a solution to resolve the error directly that would be almost as nice.
Background:
I am using moveuser.exe which is part of the Windows Server 2003 Resource Kit Tools to convert the security of local user profiles on a number Windows XP workstations.
Symptom:
Occasionally, moveuser.exe will fail to convert the security of a profile with the error "Error: 5 access denied". I have not been able to determine any commonality among the failing accounts or the computers they reside upon. A given computer may have host 6 profiles, 5 of which convert without issue and 1 which produces the error.
There are a few factors that I'm as sure as I can be about:
-The account I'm using to run moveuser.exe with has full Administrator rights to the local machine and the domain to which the profile security is being converted.
-The failure is not related to file permissions within the profile directory (the entire directory can be moved, renamed, deleted, or successfully converted via a workaround).
I've developed a reliable workaround for these cases but, it is fairly involved and I would much rather understand the root cause of this error and correct it pre-emptively.
My workaround (glad to share it, left out for brevity) seems to indicate that the failure is related to HKEY_LOCAL_MACHINE \ SOFTWARE\ Microsoft\ Windows NT \ CurrentVersion \ ProfileList registry keys but, I cannot determine exactly how/why.
Did you try to use the "regini" command line tool to grab registry permissions for the administrator account?
Use FileMon and RegMon (now Microsoft, formerly SysInternals, still free) to monitor what exactly is being accessed, how, and what rights/access are being requested.
I don't have a URL handy, but a Google search should be able to hook you up with these tools.
A couple items I would try. First, could it be that the user was logged in and the computer hasn't been rebooted. Microsoft has a product called UPHClent which helps in unloading unneeded user hives.
Next thing I wanted to know, is if you try rebooting before running the moveuser executable. This Conversation seems to indicate this would help with this kind of error.
Two days after posting this I got to the bottom of the problem. It turned out, just as Rob Haupt suggested to be related to a stuck user hive. The program I was running, moveuser, was reading the Refcount key found under HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows NT\ CurrentVersion\ ProfileList\ <SID>\ and ending immediately.
Setting Refcount to 0 solved the problem immediately
Pushing out UPHClean to all the target machines pre-emptively has all but elimated the problem and we were able to successfully convert profiles on several hundred machines over the last week.
An important note about UPHClean:
I'd tried installing it previously but, it didn't appear to help. I was too impatient, the UPHClean ReadMe revealed that the service just takes time to do its job.