After a clean installation I can see the account login screen. Authentication is also successful. Finally the main application window is displayed as well as the "
Unexpected application error".
Rekordbox Agent can be started and I can shut it down by pressing Ctrl+C. Though I noticed that it keeps trying to fetch some configuration value which eventually fails. I'm not sure if the two are related, but it looks like a missing registry key initiates the config loading.
Code: Select all
[230208T164538.376+0100] E/tray ProcessUncleanExitError: QUERY command exited with code 1:
reg: Unable to find the specified registry key
at mkErrorMsg (C:\Program Files\Pioneer\rekordbox 6.6.10\rekordboxAgent-win32-x64\resources\app.asar\node_modules\winreg\l
ib\registry.js:111:12)
at ChildProcess.<anonymous> (C:\Program Files\Pioneer\rekordbox 6.6.10\rekordboxAgent-win32-x64\resources\app.asar\node_mo
dules\winreg\lib\registry.js:648:10)
at ChildProcess.emit (node:events:526:28)
at ChildProcess.emit (node:domain:475:12)
at maybeClose (node:internal/child_process:1092:16)
at Socket.<anonymous> (node:internal/child_process:451:11)
at Socket.emit (node:events:526:28)
at Socket.emit (node:domain:475:12)
at Pipe.<anonymous> (node:net:687:12)
006c:fixme:icon:NtUserDrawIconEx Error retrieving icon frame 0
006c:fixme:imm:ImeSetActiveContext (0000000000010026, 0): stub
006c:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000010026): stub
01f8:fixme:winsock:setsockopt Ignoring SO_RANDOMIZE_PORT
0158:fixme:file:ReplaceFileW Ignoring flags 2
[230208T164548.398+0100] I/auth AuthManager:002
[230208T164548.400+0100] I/auth Getting AWS ID-Token from Cloud-API...
[230208T164548.607+0100] I/auth Waiting refreshing credential...
[230208T164548.822+0100] I/auth Done.
[230208T164548.825+0100] I/auth Refreshing AWS Credentials (refresh)
[230208T164549.373+0100] I/auth Waiting refreshing credential...
[230208T164549.612+0100] I/auth Waiting refreshing credential...
[230208T164549.655+0100] I/notification Fetching the notifications...
[230208T164549.756+0100] I/auth UID Set: 6706962219824263b0cfbe61f24f4191
[230208T164549.938+0100] I/notification Done.
[230208T164549.940+0100] I/notification Config: fetchIntervalSec:43200 / Last => 2023-02-08T15:45:49+00:00 / Next => 2023-02-0
9T03:45:49+00:00
02b4:fixme:ole:CoInitializeSecurity 0000000000000000, -1, 0000000000000000, 0000000000000000, 0, 3, 0000000000000000, 0, 0000000000000000 stub
(node:260) UnhandledPromiseRejectionWarning: Error: Command failed: C:\users\geza\Temp\9eb86faf-9f8b-45d3-b830-c55896f7ed4d.tm
p.bat
The contents of the batch file above is like this:
Code: Select all
@echo off
wmic path win32_process get Commandline /format:csv | findstr rekordbox.exe
I tried to analyse this and run the
wmic command alone which fails immediately:
Code: Select all
wine wmic
002c:fixme:winediag:LdrInitializeThunk wine-staging 8.1 is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0080:fixme:wineusb:add_usb_device Interface 1 has 2 alternate settings; using the first one.
0080:fixme:wineusb:add_usb_device Interface 2 has 2 alternate settings; using the first one.
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
Error: Command line not supported
I don't know if it's related to the app crash, but definitely a clue.