45 replies to this topic

[littlesat]

But why is only vu effected and no other trend...?

Note commented out that line is just a work-a-eound

Edited by littlesat, 14 July 2015 - 21:59.

[betacentauri]

Yeah, setting home shouldn't have that effect. And I also cannot really believe it's a driver issue. Do you guys have installed VU hbbtv plugin?

[Erik Slagter]

That's a very interesting question. I have it installed on my duo2 and no problems.

 

I still suspect it's some 3rd party plugin that's causing this (as is often the case).

[littlesat]

I think a sharp notice....

[ims]

Ultimo without any problem... or it is on new models only ? 

[Erik Slagter]

Neither on duo2.

[athoik]

I haven't see any problem also on my boxes.

 

Is it posible someone that has such a problem to use /tmp as HOME instead of /root in enigma2.sh?

export HOME=/tmp
 

Edited by athoik, 21 July 2015 - 16:47.

[christophecvr]

 

I haven't see any problem also on my boxes.

 

Is it posible someone that has such a problem to use /tmp as HOME instead of /root in enigma2.sh?

export HOME=/tmp
 

By vuduo2 and or dm8000 no problem.

 

using /tmp as home is not a good idea since on reboot all settings are gone then .

[athoik]

using /tmp as home is not a good idea since on reboot all settings are gone then .

The problem some people have is when they are restarting enigma2. So /tmp entries will be there during restart.

[christophecvr]

The most applications do set the specific application settings and or caches into the users home dir.

The temporary which are supposed to be gone when performing a reboot into /tmp.

 

By this way the use off hard targetting (which is a very bad idea) must not be used in code.

 

Ok for an stb it's not 100 % standard just cause we running as root user.

 

Enigma2 is the graphical interface and at the same time an application. It also starts a lot off other applications example gstreamer and ...

 

Problem was that enigma2 does start when the user enviroment is not known yet (only at boot time). If You restart enigma2 whitout reboot the user enviroment will be known.

 

If enigma2 is started whitout a known home dir , The applications do so waht space things concerning there caches and user related settings.

If later on You just only restart enigma2 everything is screwed double settings and caches. and ......

 

By setting like You did export de HOME=/home/root   is a bright solution.

 

But perhaps make it.

if [ -d /home/root ]; then
	export HOME=/home/root
	cd /home/root
fi

[christophecvr]

I also checked on vuduo2.

 

Full reboot exact 60 seconds.

 

Enigma2 restart 13 seconds.

[christophecvr]

Note :

 

One thing could also cause problems.

 

If there is no hdd, and the epg.dat.

 

I've found this somewhere in my notes from a couple off years ago.

Since my vuduo2 does not have a hdd a do have a usb stick which a give the label hdd .

 

usb stick formated on my (linux pc). With gparted. ext 4.

[christophecvr]

@Dimitrij

 

You should try  into enigma2.sh  the setting :

    if [ -d /home/root ]; then
    	export HOME=/home/root
    	cd /home/root
    fi

Big change that this solve all.

 

For the rest old plugins needs to be checked on the use off there $home directory.  If they use hard targetting (which is really wrong). The plugin needs to be corrected to us $HOME

[2boom]

@Dimitrij

 

You should try  into enigma2.sh  the setting :

    if [ -d /home/root ]; then
    	export HOME=/home/root
    	cd /home/root
    fi

duo2 -  36 sec

[Dimitrij]

    if [ -d /home/root ]; then
    	export HOME=/home/root
    	cd /home/root
    fi

test user

DUO 1min 25sec

[christophecvr]

Well for 2boom , if its a full reboot in 36 seconds wawwh ver very good.

 

Dimitrij (sorry i do not have a vuduo so I can't check but for a full reboot on such a slow device 1 min 25 seconds is not bath at all)

 

and if it hangs somewhere during boot it will be much much longer.

 

I'm shure that all start problems are only due to a bad (not adapted plugin) most probably a thirt party .

[vasilich07]

Well for 2boom , if its a full reboot in 36 seconds wawwh ver very good.

 

 

 

 

This Enigma2 restart...

I have to duo2, same result - 37 sec

[janejak]

My box duo2 Enigma2 restart 30 sek full reboot 55 sek orginal setting

if [ -x /usr/bin/showiframe ]; then
    if [ -f /etc/enigma2/backdrop.mvi ]; then
        /usr/bin/showiframe /etc/enigma2/backdrop.mvi
    elif [ -f /etc/enigma2/bootlogo.mvi ]; then
        /usr/bin/showiframe /etc/enigma2/bootlogo.mvi
    elif [ -f /usr/share/bootlogo.mvi ]; then
        /usr/bin/showiframe /usr/share/bootlogo.mvi
    fi
fi
 

[2boom]

Well for 2boom , if its a full reboot in 36 seconds wawwh ver very good.

this is not a complete restart, restart enigma2 only

 

if you return as it was before all of the changes

 

if [ -d /home/root ]; then

    cd /home/root

fi

http://sourceforge.n...81e5198702b383/

 

the enigma2 restart is 10 sec

[christophecvr]

 

Well for 2boom , if its a full reboot in 36 seconds wawwh ver very good.

this is not a complete restart, restart enigma2 only

 

if you return as it was before all of the changes

 

if [ -d /home/root ]; then

    cd /home/root

fi

http://sourceforge.n...81e5198702b383/

 

the enigma2 restart is 10 sec

 

Then the problem is a third party plugin. Gues hbb tv.

 

But with export HOME=/home/root 

cd /home/root ,

 

duo2 by me 11 seconds for enigma2 restart.

 

Big change that one off the third party plugins uses wrong /home  dir.

 

I'm well working with gst-1 image.

 

Perhaps it can be changed to use this export HOME=/home/root only by gst-1 images and the old whitout that rule by gst-0.10 images