Linux Lite Forums
LL Update appearing when function is unbound? - Printable Version

+- Linux Lite Forums (https://www.linuxliteos.com/forums)
+-- Forum: Software - Support (https://www.linuxliteos.com/forums/forumdisplay.php?fid=5)
+--- Forum: Other (https://www.linuxliteos.com/forums/forumdisplay.php?fid=20)
+--- Thread: LL Update appearing when function is unbound? (/showthread.php?tid=2380)



LL Update appearing when function is unbound? - Duckeenie - 11-09-2015

I'm not sure if I've broken something or this is a bug but lately I've been noticing lite update appearing when I try to execute an unbound function.


It does it when I try to open unbound file-types in Thunar. It also does it when I select help from the menu of medit.





Re: LL Update appearing when function is unbound? - Valtam - 11-09-2015

Can you screenshot Lite Control Center please.


Re: LL Update appearing when function is unbound? - Duckeenie - 11-09-2015


[Image: 9AIbQW5.png]

Thanks Jerry.


Re: LL Update appearing when function is unbound? - Duckeenie - 11-10-2015

Extra Info: medit's help file does actually exist /usr/share/medit/help/index.html and the mime type for html is set to Chrome.


Re: LL Update appearing when function is unbound? - Valtam - 11-10-2015

Have no idea at this stage why it's doing this, sorry Duckeenie.


Re: LL Update appearing when function is unbound? - Duckeenie - 11-10-2015

@Jerry: Just logged into the machine using a different user account and the problem doesn't exist there.

Anyway...If it's nothing reasonably obvious then don't worry Jerry, you can't be expected to spend all day solving problems that users unwittingly create for themselves. Smile


Re: LL Update appearing when function is unbound? - Valtam - 11-10-2015

I don't think you created it, it may even be something in our code that we've overlooked. It's just difficult to say exactly what it is.


Re: LL Update appearing when function is unbound? - JmaCWQ - 11-13-2015

Just had this happen for the first time in a while too.
Not sure if this is any help in finding the cause or not but here's some info on it.

I have an unbound file named current.gpx, it's a 2.9 kb GPS eXchange file, part of a Garmin GPS install.
When I right click & Open With Other Application I get the message: "We will now fetch the updates list, Click Yes to continue or No to abort".
Clicking No results in the following System Log entries:

Code:
Nov 13 17:10:19 home-MS-N014 sudo:     home : TTY=unknown ; PWD=/home/home/Desktop/Garmin/GPX ; USER=root ; COMMAND=/usr/scripts/updates-gui /home/home/Desktop/Garmin/GPX/current.gpx
Nov 13 17:10:19 home-MS-N014 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 13 17:10:22 home-MS-N014 sudo: pam_unix(sudo:session): session closed for user root


Clicking Yes it then updates the Software Sources & checks for updates (via the GUI not Terminal, which I cancelled once checked) with these log entries:

Code:
Nov 13 17:22:33 home-MS-N014 sudo:     home : TTY=unknown ; PWD=/home/home/Desktop/Garmin/GPX ; USER=root ; COMMAND=/usr/scripts/updates-gui /home/home/Desktop/Garmin/GPX/current.gpx
Nov 13 17:22:33 home-MS-N014 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 13 17:31:38 home-MS-N014 sudo:     root : TTY=unknown ; PWD=/home/home/Desktop/Garmin/GPX ; USER=root ; COMMAND=/usr/bin/apt-get update
Nov 13 17:31:38 home-MS-N014 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 13 17:32:29 home-MS-N014 sudo: pam_unix(sudo:session): session closed for user root
Nov 13 17:32:34 home-MS-N014 sudo:     root : TTY=unknown ; PWD=/home/home/Desktop/Garmin/GPX ; USER=root ; COMMAND=/usr/bin/dpkg --clear-avail
Nov 13 17:32:34 home-MS-N014 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 13 17:32:34 home-MS-N014 sudo: pam_unix(sudo:session): session closed for user root
Nov 13 17:34:28 home-MS-N014 sudo: pam_unix(sudo:session): session closed for user root


From memory I think the way I got around it in the past was to right click & Properties on the file, change what it opens with from No Application Selected to the desired program.

Also from memory but I'm not 100% sure, I think this issue started with the introduction of the GUI for updates.