bantar
-
Posts
14 -
Joined
-
Last visited
Posts posted by bantar
-
-
11 minutes ago, dnalloheoj said:
@bantar Do you possibly have OneDrive disabled on your computer in any fashion? Or have you done anything in particular to disable certain built-in Windows features that you recall?
I think your issues are more related to a corrupt profile/install or the Windows Store specifically, personally. Basing that off what I was seeing when I was having the same issue, and yep, I had done plenty of fucky "hacks" in the past to do things like disable OneDrive for Business, etc.
Could try a wsreset, reinstalling the Store app, re-registering the Store App, clearing Store cache, etc. But why bother when a new profile would do all of that at once.
A windows reinstall would likely clear it up, but ideally there's a fix that doesn't require that. Might be worth trying to create a new user account (local admin rights), log out, log in as that user, download the Skip App again, install, see what happens. That said, it very possibly could be BitDefender + ASUS related (I feel like you chimed in that you had that installed? Maybe I'm wrong), and that a simple new profile wouldn't work, as those would likely follow you around since they get installed with SYSTEM permissions.
Worth noting that on some fresh installs/profiles/newly created VMs I've had to install 5293, and then download & install the version from the website. Even though it says 'Do you want to update' when installing the Website version, it stays at 5293, but works just fine afterwards.Seeing your profile issue noted prior to me installing, I chose to create a brand new profile. I installed on that profile, so I don't expect a corrupted profile. It exists for the sole purpose of testing Skip. I do have BitDefender installed, but nothing ASUS related. I'm on a Dell Laptop. It's easy enough to disable BitDefender to see if anything changes.
I've never downloaded the software from the website, because I didn't know where to look. Was looking on the forums page. I can try it when I get home.
I loaded 5276, and when poking around, it wanted to update to 5293. When that happened, no connections to the remote were possible. Downgraded to 5276 and it worked fine. I wonder what version is on the website? I'm guessing 5293. Secondly, I've not tried a clean install of 5293 either.
-
The download site is located here: https://flirc.tv/products/skip1s-remote?variant=43489094729960#spec2
-
8 hours ago, jason said:
Was that enabled, and if so, did disabling have any effect on remote detection in the skipapp?
There might be a disconnect, with respect to the issues that I'm reporting. I'm only seeing the app crash in the background. The detection of the remote is working with build 5276, but not with 5293. When I rolled back to 5276 remote detection returned.
With remote detection, I've seen these behaviors: 1) Start the app, connect the remote, detected. 2) Remote connected for some time, start the app, not detected. Disconnect and reconnect the app, remote is detected. I'm assuming that this is expected behavior, and if not, presented here. 3) When app crashes, for about 5 minutes (or less), the remote attempts to reconnect (hear the dings from windows as it connects/disconnects).
Do you need more from me given this clarification?
-
Part 3 of 3
-
Part 2 of 3
-
I'm using Bitdefender Total Security.
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class contents:
-
7 hours ago, jason said:
I don't see any crash logs to sentry for both of you
Is Sentry a debugging tool that we need to install? And to be clear, crash means the GUI disappeared. No error dialogs of any kind captured the moment. The only clue is a missing app. It's not running in the task list and each time, I'm finding a corresponding crash event in the windows logs. Other point to note, is that I've never seen it crash while actively using it.
-
One more observation.... After crashing, the remote would connect and reconnect multiple times, then eventually give up. Presented in case this is not normal behavior. I did try multiple cables and verified that neither of these cable connections were the cause of the connect/reconnect.
-
And a different crash:
Faulting application name: SkipApp.exe, version: 0.1.0.5276, time stamp: 0x63c45afd
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2364, time stamp: 0x5b7d4d22
Exception code: 0x00001007
Fault offset: 0x000000000010fe32
Faulting process id: 0x48dc
Faulting application start time: 0x01d92c84a4863d99
Faulting application path: C:\Program Files\WindowsApps\1ee3f564-2cd0-4ef3-af35-da985b1d7f00_0.1.0.5276_x64__sddpyax1dmvqm\SkipApp.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 321bfd1f-a5a0-4a4c-928c-370f79ae4500
Faulting package full name: 1ee3f564-2cd0-4ef3-af35-da985b1d7f00_0.1.0.5276_x64__sddpyax1dmvqm
Faulting package-relative application ID: App -
1 minute ago, bantar said:
Build 5726 connected and sync'd and turns the tv on and off!
But still crashes while not actively interacting with the app.
Faulting application name: SkipApp.exe, version: 0.1.0.5276, time stamp: 0x63c45afd
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2364, time stamp: 0x5b7d4d22
Exception code: 0xc000027b
Fault offset: 0x000000000010fe32
Faulting process id: 0x6a6c
Faulting application start time: 0x01d92c83d5b26768
Faulting application path: C:\Program Files\WindowsApps\1ee3f564-2cd0-4ef3-af35-da985b1d7f00_0.1.0.5276_x64__sddpyax1dmvqm\SkipApp.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 4c7e726e-e4f3-4d22-9bef-8b80920e4378
Faulting package full name: 1ee3f564-2cd0-4ef3-af35-da985b1d7f00_0.1.0.5276_x64__sddpyax1dmvqm
Faulting package-relative application ID: App -
Build 5726 connected and sync'd and turns the tv on and off!
-
EDIT: Updated crash data
First time install using build 5276 that later auto updated to 5293. Using Windows 10 22H2 Build 19045.2486 on a Dell Laptop. Created a new user profile just for this. App installed ok, loaded ok, seems to work ok, but the Remote never connects. Says Offline.
I found this error in the Windows Log:
Event 10016, DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user BRIAN-ON-THE-GO\FLIRC SID (S-1-5-21-3984057536-428044359-1120404447-1004) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.The App is crashing on occasion. So far, each time it happened, I was doing something else other than having the app in the foreground.
Faulting application name: SkipApp.exe, version: 0.1.0.5293, time stamp: 0x63c6dd76
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2364, time stamp: 0x5b7d4d22
Exception code: 0xc000027b
Fault offset: 0x000000000010fe32
Faulting process id: 0x690c
Faulting application start time: 0x01d92c7f9671a5d1
Faulting application path: C:\Program Files\WindowsApps\1ee3f564-2cd0-4ef3-af35-da985b1d7f00_0.1.0.5293_x64__sddpyax1dmvqm\SkipApp.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 4d9fb3cb-7227-404f-a82b-deeffe63bd60
Faulting package full name: 1ee3f564-2cd0-4ef3-af35-da985b1d7f00_0.1.0.5293_x64__sddpyax1dmvqm
Faulting package-relative application ID: AppThe remote makes a connecting sound when attached/detached from the PC. I do not see any updates on the app as if it is trying to connect.
-
On the 1st post of the latest app, it says: "New Beta can be downloaded on the front page. Minor changes to help those with USB issues." I don't see it. Maybe I don't know which home page.
Buried on page 7, I found this little gem: "When you are on the new user account, you should use the following build: 5276"
For now, I'm going to start with this build.
Skip App v0.9.4 Beta
in Beta Feedback
Posted
OK, finally installed 0.94 Build 5265. App is working ok, but after a while it crashes. I'm seeing the same 3 crashes when it happens. Happened twice now. This time, it has crashed while in the foreground, but not while actively making changes. See the crash logs screenshots and logfile.flirc20230124.log
flirc20230124.txt