Ld Launcher

[Rode Neagle]

Ijust realized I misread the launcher code. It creates a command that adds a launcher to the main area. The file browser extension invokes that command if there is no other widget open. So if you add your widget to the main area in your activate function, the file browser will notice there is something already there and will not create a launcher tab by default.

@jasongrout I am working with aafshar. I tried adding my extension to the MainAreaWidget inside the extension activate function but this resulted in some strange behaviour. More often than not, on page refresh, the launcher is rendered on the MainAreaWidget. However, every once in a while on page refresh, my extension is rendered onto the MainAreaWidget as intended.

Is this the proper implementation of your description above?

Unfortunately, this url did not open the desired testingworkspace workspace but opened just a launcher (I assume it just opened a default workspace). Is this the correct workflow to save and open a custom workspace?

Since the patch yesterday the game launcher won't open for me. It briefly flickers ("initializing") then disappears. I've tried repairing it, reinstalling the game and restating my computer but nothing fixed it. Does anyone else have this problem or know a way to fix it?

i think the launcher is probably already running but stuck, so you need to kill off the "Gw2-64.exe" process in task manager. its also possible the launcher is failing to patch itself due to permission issues, so make sure it can write to its directory (don't put it in program files, but on your desktop or user folder is fine).

For me the launcher window only appears after I kill the task in task manager. So I click gw2, nothing happens except my cursor telling me something is loading. No launcher appears. Go to task manager, end gw2 process (its a high power process). As soon as I do that the launcher appears like normal.

If I don't do the task manager process I can click on the gw2 icon and a process will appear for each time I click but no launcher window will open.

I still have that problem. Guild Wars 2 processes don't seem to close correctly when ending the application. You can do a workaround by killing all GW2 process manually, but I really hope this will get fixed sooner or later.

I have an ELVIS II MX board for ECPI university. About 4 weeks ago it stopped allowing me to launch the instrument launcher. I attempt to bring it up by clicking it and nothing happens. There is no error message or screen flash. It does not appear in the task manager at all. I had previously been using it since June of 2017. I have uninstalled and reinstalled the NI student edition and myDAQ software suite. This has not corrected the issue. There are no real specific instructions on my school site as to what to install other than "This download enables students to install the same NI software used in campus laboratories, on their own laptops and computers. By using the serial number below, students will be able to access Student Install Options for both Multisim and LabVIEW. " I am unsure how to resolve this issue.

if we talk about the epic launcher, there is no other app in this world that behaves worse than this. switching between tabs and menus takes ages. is incredible how bad it is and still no changes years later.

This issue is still present. When some of our staff try's launching a MS office file from drive it will only give the option to open with Google Sheets or Docs. I have to tell them to back out of the open with screen that come up with a preview and try again. This works 50% of the time. This just isn't expectable.

I will state, that this seems to be only happening on Windows 10 machines, since the December update to Chrome I haven't had any issues with my Windows 11 machine. I will have to ask around and see if this is 100% the case with Windows 10 only.

Unfortunately, this issue is also still present on Windows 11. We've checked all the updates for Windows and chrome, deleted caches etc. However we have at least one member of staff who can still open with MS and Adobe apps- but we can't find any difference in settings or OS and browser versions.

February '24. This is still not working for anyone in my team.

I've updated Chrome to the latest version available to me: 122.0.6261.58 (Official Build) (64-bit). I've uninstalled and reinstalled the extension (From the old Chrome Web store). The new Chrome Web store does not list the application launcher - could this be anything to do with the issue?

This is really frustrating for teams managing files in a Google Workspace environment through Chrome who also have to open certain files in native software, such as complex excel workbooks or InDesign files. Any ideas of what to try next?

Dear colleagues, we are facing this issue now and the funny things that it works for some people and it doesn't for others. I tried to update, reinstall etc.. but still it did not work. I know the process is tedious re this darned app launcher.

Hi all - myself and other colleagues are still having intermittent issues with the extension on both macOS and Windows. I'm running Win 11 Enterprise, Chrome Version 126.0.6478.127, and Google Drive Version 93.0.1.0. We've had this issue since 2023. Updates have consistently been installed over this time. We've even tried uninstalling and reinstalling the extension.

Anyone have luck resolving this? Thanks!

2) Setting the launcher to Node created on data-folder. This triggers my workflow once, but it fails because DamUpdateAsset is still running. (bad) Perhaps there is a way to add a wait to the launcher?

3) I tried appending my workflow to the end of DamUpdateAsset but the payload given to it becomes the "original" rendition, and I'd rather not have to jump up to the parent programatically. Also, this requires modifying or copying DamUpdateAsset, and changing the way AEM is set up OOTB.

Workflow Launcher have only 3 types of events available that too "jcr node events" and not sling ones so creating them would be difficult with a lot of trial and error and possibility multiple times invocation.

I think you should revisit decision not to write a sling event listener. It is much cleaner for your use case and you can listen to DAM_UPDATE_ASSET_WORKFLOW_COMPLETED event which is sent at the end of DamUpdateWorkflow and have a lot of power with programmatic filter and event topics to choose from for right time invocation and also payload path manipulation. This event listener can be backed up with good logging to allow comprehensive debugging.

I am attempting to follow along with the instructions in the posit workbench admin guide for enabling SSL for launcher (following RStudio Workbench Administration Guide - Overview). We have an existing install that works with a local cluster and I am trying to make the necessary changes without breaking everything.

This is somewhat baffling because we are passing in the exact same paths for the certificate files, I've attempted changing the permissions of the certificate files and their ownership but nothing seems to work.

Typically when we see this from the Launcher, it's due to permissions issues on the certificate files in question. Can you make sure that they are set with the proper permissions and ownership as described here?

-pro/job_launcher/configuration.html#ssl-considerations

If this doesn't help, please file a ticket at our premium support site ( -us/requests/new) and we can dig further into your specific configuration - should a generalizable solution be reached we'll be sure to return here and share that.

I have finally found a solution - the issue seems to occur based on the permissions of the folder containing the certificates (originally 600). Specifically chmod 655 /etc/rstudio/cert seemed to work for me, I'm guessing g+r and or o+r might be the missing piece but I have not investigated further.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.

I just launched Zwift on my PC and it started up as usual, joined Coco and then exited the ride. I think you should try a full re-install. Delete all the Zwift folders including in your documents folder. Save any custom workouts you have made first somewhere else or you will lose them. Then download the new launcher from the website and do a full re-install.

A fix for the crash at launch on macOS was pushed out today. Next time you start Zwift, you should receive a game update that fixes the crash at launch. Please reboot your Mac and restart Zwift.

For M1 / M2 Mac users specifically:

Q1: After the update / reboot - did he launch crash go away? Were you able to log in and start Zwift, in other words?

Q2: On the Pairing Screen - did you see a message like Accept network incoming message?

Q3: If yes, and you give permission to that message - does that message go away next time you restart Zwift?

I'm using both JMP v11 and v12 and my JMP default launcher is v12. Recently I have an add-in which is only available for JMP v11. However, when I installed the add-in, it automatically launched JMP v12 instead of JMPv11. Would you please share how to switch the default launcher from JMPv12 to v11 and backwards?

3a8082e126