Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Recommended Posts

On http://www.leadwerks.com/werkspace/page/tutorials/_/asset-browser-r5

 

Let’s open the root project folder of the project by right-clicking on the "TutorialProject" folder at the top of the directory tree, and selecting the Open Folder popup menu. A folder now opens on your computer that contains the entire game project.

 

The folder didn't open. I expected Nautilus or similar to open to the specified directory.

Link to post
Share on other sites

It seems as if xdg-open events or any other event calling for a binary directly, like when Firefox was called directly for web links do not really pass through. It used to work when there was still a stand-alone version of Leadwerks.

 

I investigated the situation with pstree and here is what it looks like:

 

bash-+-bash---steam-+-SteamChildMonit---3*[xdg-open---gvfs-open]
       |         |         |         |      |              |-SteamChildMonit-+-sh---Leadwerks-+-{Leadwerks}
       |         |         |         |      |              |                 |                `-{threaded-ml}
       |         |         |         |      |              |                 `-3*[xdg-open---gvfs-open]

 

The upper row of 3 xdg-open processes was when I started Leadwerks, clicked 3 objects that would cause an external program to open and, after nothing happened, closed the editor. As you can see those processes went up to SteamChildMonit and never made it passed that.

 

The second row of 3 xdg-open processes was the same thing just that I didn't close the editor this time. Same deal here.

 


|-lightdm-+-upstart-+-2*[steamChildMonit---3*[xdg-open---gvfs-open]]

 

This is after quitting the editor and Steam, see how both SteamChildMonit processes still exist.

 

Intentionally or not, I think Steam is somehow stopping these from getting executed.

 

EDIT1:

 

And here is the same thing for Blender (Steam):

 

steam-+-SteamChildMonit---sh---blender-+-5*[xdg-open---gvfs-open]

 

My locally installed Blender version opens the links in the splash screen just fine and so does the Steam version if it is launched directly instead of through Steam.

 

EDIT2:

 

NEOScavenger

SteamChildMonit---sh---NEOScavenger-+-6*[firefox]

Link to post
Share on other sites

That's a great find.

 

I manually kill -9'd all the steam related content in the current gnome-session, verified Leadwerks was no longer in pstree

 

Launched Leadwerks from the Applications|Games menu (Gnome), ran pstree (steam1.png), tried to do an open, pstree (steam2.png), closed Leadwerks, pstree (steam3.png).

 

I'm seeing the same as you.

 

NOTE: Though I attached them in order, the forum is showing the thumbnails out of order.

post-8596-0-29161900-1432404774_thumb.png

post-8596-0-66774500-1432404782_thumb.png

post-8596-0-70006800-1432404792_thumb.png

Link to post
Share on other sites

Checking the logs, these are the errors a single instance of gvfs-open (what xdg-open hands off to in Gnome/Unity environments) spits out reliably:

 

(gvfs-open:29475): GLib-GObject-CRITICAL **: /usr/src/packages/BUILD/glib2.0-2.32.3/./gobject/gtype.c:2722: You forgot to call g_type_init()
(gvfs-open:29475): GLib-GObject-CRITICAL **: g_type_interface_add_prerequisite: assertion `G_TYPE_IS_INTERFACE (interface_type)' failed
(gvfs-open:29475): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed
(gvfs-open:29475): GLib-GObject-CRITICAL **: /usr/src/packages/BUILD/glib2.0-2.32.3/./gobject/gtype.c:2722: You forgot to call g_type_init()
(gvfs-open:29475): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed
(gvfs-open:29475): GLib-GObject-CRITICAL **: /usr/src/packages/BUILD/glib2.0-2.32.3/./gobject/gtype.c:2722: You forgot to call g_type_init()
(gvfs-open:29475): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed

 

Might be an issue with gvfs-open after all, I had a KDE user before who had no issues opening external links through Steam.

 

Is this a bug to report to Valve?

 

Probably.

Link to post
Share on other sites

And another KDE user is seeing the same issue. Yeah, Josh; Would be great if you reported this to Valve through your arcane Steamworks dev means. Their public Steam for Linux github issue tracker sadly has become a place where reports go to die.

Link to post
Share on other sites

On http://www.leadwerks.com/werkspace/page/tutorials/_/workshop-r11

 

To install an item from the Workshop, first you need to open the Workshop browser.

 

It doesn't actually say how to do that. I figured it would be from Workshop:Browse, but that doesn't do anything.

 

I found this bug:

http://www.leadwerks.com/werkspace/topic/11378-linux-in-editor-workshop-browser-doesnt-work/page__hl__browse workshop

 

But since it is read-only, I assume it was closed based on Firefox launching.

I have Firefox, Chrome, Opera, Chromium, Firefox Dev Edition, and a couple others... none of them launched.

 

As a temporary workaround, in Steam, go to Installed, Leadwerks, find the button for the Steam Workshop.

 

I don't think the prior bug should be read-only. It's still outstanding.

Link to post
Share on other sites

I think this has to do with XDG calls being ignored. Originally, this was hard-coded to open FF, now it opens the Steam client, except that the calls are ignored in Ubuntu 15.

Link to post
Share on other sites

I think this has to do with XDG calls being ignored. Originally, this was hard-coded to open FF, now it opens the Steam client, except that the calls are ignored in Ubuntu 15.

 

I actually had that on 14.04 as well, have you reported it too Steam/ Valve yet? It's almost guaranteed to be their fault in some way.

Link to post
Share on other sites

I actually had that on 14.04 as well, have you reported it too Steam/ Valve yet? It's almost guaranteed to be their fault in some way.

 

I wonder what their own UI is doing differently. When you close Leadwerks, it opens their UI with an ad. If you click details, it opens the browser fine.

Link to post
Share on other sites

 

I'm not actually able to monitor that thread, as it is private.

 

Can you confirm that Blender on Steam also has this problem, when it is launched from the Steam client?

 

I installed Blender from Steam. Haven't used their UI in over a decade. Steps to test whether it has the same problem?

Link to post
Share on other sites

Yes, the issue exists with Blender and every other program that calls for any external program when run through Steam.

 

You can test it by clicking the links on the splash image that comes up when Blender starts.

Link to post
Share on other sites

Yes, the issue exists with Blender and every other program that calls for any external program when run through Steam.

 

You can test it by clicking the links on the splash image that comes up when Blender starts.

 

Confirmed.

 

Clicking the manual, it did not open.

I did see ps showed these:

 

malachi 17031 17011 0 18:32 ?		00:00:00 /bin/sh /usr/bin/xdg-open http://www.blender.org/manual
malachi 17033 17031 0 18:32 ?		00:00:00 gvfs-open http://www.blender.org/manual

 

Killing off Blender and those, I managed to successfully launch the manual from the command line using the same command:

 

malachi@hydra:~$ /bin/sh /usr/bin/xdg-open http://www.blender.org/manual
(process:17282): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
malachi@hydra:~$ echo $?
0

 

And

 

malachi@hydra:~$ /usr/bin/xdg-open http://www.blender.org/manual
(process:17181): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
malachi@hydra:~$ echo $?
0

 

Maybe it has something to do with the g_slice_set_config failed assertion.... but in both those cases, the manual did launch in the browser...

Link to post
Share on other sites
  • 1 month later...

That's probably because you have just overwritten PATH, try PATH=\"$PATH:$SYSTEM_PATH\" in that define to keep what was in PATH before.

 

If that doesn't work you probably will have to change xdg-open inside the system() command to /usr/bin/xdg-open which is the standard path for that binary on just about every Linux distro there is.

 

BTW: That Steam group is not visible to those that aren't Steamworks devs.

Link to post
Share on other sites
Guest
This topic is now closed to further replies.
×
×
  • Create New...