Cannot see the Lunii panel

[SirDedale]

Hi everyone,

Using Beta 2 and a LUNII-1 (China). For some reason, I cannot see the left panel for the Lunii. I see the packs and can add / edit. I also see the messages in the web app that an event is happening as well as in the console:

2021-02-04 11:14:16,731 [INFO ] [s.d.LibUsbActivePollingWorker]: Active polling lost the device. Firing event.
2021-02-04 11:14:16,736 [INFO ] [s.w.s.StoryTellerService]: Device 2.x unplugged
2021-02-04 11:14:26,791 [INFO ] [s.d.LibUsbActivePollingWorker]: Active polling found a new device. Firing event.
2021-02-04 11:14:26,795 [DEBUG] [s.d.f.FsStoryTellerAsyncDriver]: Lunii FS mount point:

Could you guide me on what I miss? I think this is due to my FW but I'm not sure. Also, using W10 and Edge and Chromium (same issue),

Thank you!

[marian-m12l]

@SirDedale If think you did not configure the lunii partition mount point in the script (studio-windows.bat), which is required with firmware 2.x

[viccho]

hello
Can you explain, more or less, step by step, what to do to configure the lunii partition mount point in the script.
I don't where to found and to how tu use FS_MOUNTPOINT. I'm on windows 10.
thank you :)

[viccho]

Well, i found that i've to go inside the studio-win.bat file to tell the mount path.
The thing is that i'm am a very begineer et here what i'm doing : my lunii is on the H:, so i've open the .BAT with notepad and wrote FS_MOUNTPOINT= H:\ and save.
Now, the whane i launch the .bat, nothing appens. ...thank you for your help :)

[viccho]

sorry, i found. there was no space.... FS_MOUNTPOINT=H:\

[marian-m12l]

@viccho The latest beta release solves this by detecting the mountpoint. No need to configure FS_MOUNTPOINT anymore.

[ylippi]

Hi,
I installed today the last studio version on my ubuntu 10.04. I think I configured it as expected with FS_MOUNTPOINT pointing to /home/MyLogin/LUNII but when launching studio the panel does not appear on left side.
When I turn off the lunii device, a popup appear in blue: 'Fabrique à histoire débranchée"
So it seems the device is well recognised by studio...

here an extract of the STDOUT when un/plugging the lunii device:

2021-03-07 01:03:44,508 [INFO ] [s.d.LibUsbDetectionHelper]: Hotplug event callback (0c45:6840): 2
2021-03-07 01:03:44,509 [INFO ] [s.w.s.StoryTellerService]: Device 2.x unplugged
2021-03-07 01:05:06,326 [INFO ] [s.d.LibUsbDetectionHelper]: Hotplug event callback (0c45:6840): 1
2021-03-07 01:05:06,327 [DEBUG] [s.d.f.FsStoryTellerAsyncDriver]: Lunii FS mount point: /media/MyLogin/LUNII

Here is the STOUT from the begining because there are some warnings and ERROR.
May be it could help finding what is wrong?
Regards
Yannick

cp: impossible d'évaluer '/home/MyLogin/studio/web-ui/target/agent/studio-agent-0.3.0-beta.3-SNAPSHOT-jar-with-dependencies.jar': Aucun fichier ou dossier de ce type
cp: impossible d'évaluer '/home/MyLogin/studio/web-ui/target/agent/studio-metadata-0.3.0-beta.3-SNAPSHOT-jar-with-dependencies.jar': Aucun fichier ou dossier de ce type
2021-03-07 00:30:29,879 [INFO ] [s.w.s.StoryTellerService]: Setting up story teller driver
2021-03-07 00:30:29,900 [DEBUG] [s.d.r.RawStoryTellerAsyncDriver]: Registering hotplug listener
2021-03-07 00:30:29,905 [INFO ] [s.d.LibUsbDetectionHelper]: Initializing libusb...
2021-03-07 00:30:29,963 [INFO ] [s.d.LibUsbDetectionHelper]: Hotplug is supported. Registering hotplug callback(s)...
2021-03-07 00:30:29,973 [DEBUG] [s.d.LibUsbAsyncEventsWorker]: Starting worker thread to handle libusb async events...
2021-03-07 00:30:30,003 [DEBUG] [s.d.f.FsStoryTellerAsyncDriver]: Registering hotplug listener
2021-03-07 00:30:30,005 [INFO ] [s.d.LibUsbDetectionHelper]: Initializing libusb...
2021-03-07 00:30:30,011 [INFO ] [s.d.LibUsbDetectionHelper]: Hotplug is supported. Registering hotplug callback(s)...
2021-03-07 00:30:30,013 [INFO ] [s.d.LibUsbDetectionHelper]: Hotplug event callback (0c45:6840): 1
2021-03-07 00:30:30,016 [DEBUG] [s.d.LibUsbAsyncEventsWorker]: Starting worker thread to handle libusb async events...
2021-03-07 00:30:30,047 [DEBUG] [s.d.f.FsStoryTellerAsyncDriver]: Lunii FS mount point: /media/MyLogin/LUNII
2021-03-07 00:30:30,464 [INFO ] [s.w.MainVerticle]: Opening URL in default browser...
2021-03-07 00:30:31,538 [WARN ] [i.v.c.i.BlockedThreadChecker]: Thread Thread[vert.x-eventloop-thread-0,5,main]=Thread[vert.x-eventloop-thread-0,5,main] has been blocked for 2562 ms, time limit is 2000 ms
Gtk-Message: 00:30:31.963: Failed to load module "canberra-gtk-module"
2021-03-07 00:30:32,187 [INFO ] [i.v.c.i.l.c.VertxIsolatedDeployer]: Succeeded in deploying verticle
2021-03-07 00:30:39,576 [ERROR] [s.w.MainVerticle]: Exception thrown
java.nio.channels.ClosedChannelException
	at io.netty.channel.AbstractChannel$AbstractUnsafe.newClosedChannelException(AbstractChannel.java:957)
	at io.netty.channel.AbstractChannel$AbstractUnsafe.write(AbstractChannel.java:865)
	at io.netty.channel.DefaultChannelPipeline$HeadContext.write(DefaultChannelPipeline.java:1367)
	at io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:717)
	at io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:764)
	at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:790)
	at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:758)
	at io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:767)
	at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:790)
	at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:758)
	at io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:767)
	at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:790)
	at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:758)
	at io.vertx.core.net.impl.ConnectionBase.write(ConnectionBase.java:124)
	at io.vertx.core.net.impl.ConnectionBase.writeToChannel(ConnectionBase.java:205)
	at io.vertx.core.http.impl.Http1xServerConnection.writeToChannel(Http1xServerConnection.java:267)
	at io.vertx.core.net.impl.ConnectionBase.sendFileRegion(ConnectionBase.java:417)
	at io.vertx.core.net.impl.ConnectionBase.sendFile(ConnectionBase.java:444)
	at io.vertx.core.http.impl.Http1xServerConnection.sendFile(Http1xServerConnection.java:456)
	at io.vertx.core.http.impl.HttpServerResponseImpl.doSendFile(HttpServerResponseImpl.java:514)
	at io.vertx.core.http.impl.HttpServerResponseImpl.sendFile(HttpServerResponseImpl.java:433)
	at io.vertx.core.http.HttpServerResponse.sendFile(HttpServerResponse.java:365)
	at io.vertx.core.http.HttpServerResponse.sendFile(HttpServerResponse.java:351)
	at io.vertx.ext.web.handler.impl.StaticHandlerImpl.lambda$sendFile$11(StaticHandlerImpl.java:457)
	at io.vertx.ext.web.handler.impl.StaticHandlerImpl.wrapInTCCLSwitch(StaticHandlerImpl.java:266)
	at io.vertx.ext.web.handler.impl.StaticHandlerImpl.sendFile(StaticHandlerImpl.java:392)
	at io.vertx.ext.web.handler.impl.StaticHandlerImpl.lambda$null$0(StaticHandlerImpl.java:231)
	at io.vertx.ext.web.handler.impl.StaticHandlerImpl.getFileProps(StaticHandlerImpl.java:299)
	at io.vertx.ext.web.handler.impl.StaticHandlerImpl.lambda$sendStatic$1(StaticHandlerImpl.java:208)
	at io.vertx.core.impl.ContextImpl.lambda$null$0(ContextImpl.java:330)
	at io.vertx.core.impl.ContextImpl.executeTask(ContextImpl.java:369)
	at io.vertx.core.impl.EventLoopContext.lambda$executeAsync$0(EventLoopContext.java:38)
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500)
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:834)
2021-03-07 00:30:43,540 [WARN ] [i.v.c.i.BlockedThreadChecker]: Thread Thread[vert.x-eventloop-thread-0,5,main]=Thread[vert.x-eventloop-thread-0,5,main] has been blocked for 2905 ms, time limit is 2000 ms

[vpoulailleau]

ubuntu 10.04 is pretty old, I assume you wanted to say ubuntu 20.04.

With what you provided, we can see that the problem is the value of FS_MOUNTPOINT

You can try the following command in a terminal:

ls /media/$USER

with and without your lunii device connected.

With the difference of output, you can guess the name of the directory where the device is mounted. The directory may vary when changing of lunii device.

I have two possible values for the lunii devices I own, but many lunii devices uses the first path:

FS_MOUNTPOINT=/media/vincent/LUNII
FS_MOUNTPOINT=/media/vincent/93CC-9604

Note that vincent is the name of my Linux user (echo $USER in a terminal to find yours).

[ylippi]

Hi,
Yes I use ubuntu 20.04, sorry..
Thanks for your help! The mount dir for me is simply "disk".
And now I can see the lunii bar on studio.
THanks a lot
Yannick