New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MPM crashes with --require=@ #263
Comments
Please check the output of:
|
This gives me in the console only: In the initexmf.log I see: A side note: Or do I have a thinko here? |
Yes, this is the new behavior (see #128). |
Thanks for the pointer, I commented there. However, what about the crash? Can I help you more by getting more info somehow about the crash? |
Thank you, I think I have enough info. This will be fixed. |
This has been fixed now, i.e., |
Thank you |
Packages.txt
mpm.exe --admin --verbose --require=@Packages.txt
result: crash after some seconds of waiting
In the log file I see:
2019-02-11 02:37:51,511+0100 INFO mpmcli - starting: mpmcli 2.9.6888 (MiKTeX 2.9.6960)
2019-02-11 02:37:51,511+0100 INFO mpmcli - Operating on the shared (system-wide) MiKTeX setup
2019-02-11 02:37:52,135+0100 FATAL mpmcli - Cannot start MiKTeX package manager.
2019-02-11 02:37:52,135+0100 FATAL mpmcli - Info: hr="Die Klasse ist nicht f�r die Unterst�tzung der Aktivierung mit erh�hten Rechten konfiguriert.
But I have admin permissions, the MikTeX diagnose says:
SystemAdmin: yes
RootPrivileges: yes
AdminMode: yes
see below.
I did not call cmd explicitly to assure special admin permissions for it. Even if this is necessary, MiKTeX must not crash but issue an error.
MiKTeX: 2.9.6960
OS: Windows 7 Professional, 64-bit, Service Pack 1, build 7601
SharedSetup: yes
PathOkay: yes
LastUpdateCheck: 2019-02-11 00:45:41
LastUpdate: 2019-02-10 21:54:59
SystemAdmin: yes
RootPrivileges: yes
AdminMode: yes
Root0: C:\ProgramData\MiKTeX\2.9
Root1: C:\Program Files (x86)\MiKTeX 2.9
CommonInstall: C:\Program Files (x86)\MiKTeX 2.9
CommonConfig: C:\ProgramData\MiKTeX\2.9
CommonData: C:\ProgramData\MiKTeX\2.9
The text was updated successfully, but these errors were encountered: