Error message logging in to 32-bit Xenialpup

[memo]

Hi all,

I have an error message that appears just now and was not before. it appears as soon as I login to the system. do not know what is the reason.

Hope you can help me solving it.

see the error in the attachment.

My system is Xenialpup 32 bit.

Kind regards,
Memo

[666philb]

hi memo,

welcome to the forums!

that's probably caused by a .desktop file left over from running the rambox appimage.
Have a look in ...
/root/.config/autostart
/etc/xdg/autostart

and delete anything rambox related you find in there

[mikewalsh]

Hallo, @memo . to the "kennels".

Looks familiar. I'm in 32-bit Xenialpup myself today. And I get a very similar error message myself.....not only here, but in every other Puppy I run, too.

Does the application still start, even though you get this error message?

In my case, I know exactly what causes it. I run a weather application called "Temps". Displays on the desktop when you click the tray icon, and looks just like a smartphone app....which it was originally developed as.

---------------------------------------------------------------------

Anyway. This thing is set to autostart, by sym-linking the executable into /root/Startup. However, every time it launches, it also re-writes its entry in /root/Startup/autostart.....and it renames the 'Exec' line to a different name than its own executable. It couldn't find itself even if it tried.....because its own code won't allow it to!

It's a bug in the app's code.....and the developer stopped supporting this thing nearly 4 years ago, so it's no use reporting it. Still launches & works well, even so.

--------------------------------------------------------------------

This is NOT a "Puppy" issue. It's almost certainly a code glitch in the application itself.....or as Phil says, a leftover .desktop file. Usually you can delete these things and they won't come back, but in the case of 'Temps' it re-creates the blasted thing at every launch....and even though it launches happily, it still pops-up this message to say it couldn't find itself..!!

Mike.

[Phoenix]

Could be worth setting a cron job to remove the file, but that sounds like taping it over.