I am aware that I'm not a typical contributor on Github. The Raspberries are used just for some electronic experiments and my LINUX knowledge is at best rudimentary. Lacking experience is replaced by tenacity and a capacity for suffering... Anyway, picframe is currently running on a Pi 3B with legacy Buster OS for about one year. Pictures are managed with SSH and SFTP. This machine doesn't stop either and nobody is interested to stop it. But of course I got interested when I learned that picframe is running now on bullseye 64 bit. So I am currently studying Pi 3B+ with bullseye OS...
Wolfgang Männel has suggested to turn to this Github account. The system in question is a Pi 3B+, administrated via SSH. It is embedded in a larger network of Linux- and Windows machines and addressed as Tronic with user Ozelot. After three days and a minimum of six installation attempts picframe is running. Now, however, it is virtually unstoppable. The guide to systemd has been applied repeatedly but picframe doesn't react.
In an older print-out from thedigitalpictureframe.com (not existing any longer in the current web site) a hint was found that with 'picframe -h' keys codes were forwarded but searching the Pi 3B+ directories has not yielded a suitable file. It is difficult to believe that a nice piece of code like picframe can only be terminated by pulling the plug...
May I ask the experts to give me a hint or two?
At least picframe is running - but not the 'conventional' way. It started only after booting to GUI by entering 'start_picframe.sh' from the home directory (that had to be added to $PATH) separatedly via terminal. There are further issues but for the moment picframe is running now on picframe works, pictures can be transfered from and to the computer - that's well worth the time and effort. It makes the (at least our) world a bit nicer - and this is well worth a big 'Thank you' to all those having made this possible.
Hello everybody,
I am aware that I'm not a typical contributor on Github. The Raspberries are used just for some electronic experiments and my LINUX knowledge is at best rudimentary. Lacking experience is replaced by tenacity and a capacity for suffering... Anyway, picframe is currently running on a Pi 3B with legacy Buster OS for about one year. Pictures are managed with SSH and SFTP. This machine doesn't stop either and nobody is interested to stop it. But of course I got interested when I learned that picframe is running now on bullseye 64 bit. So I am currently studying Pi 3B+ with bullseye OS...
Wolfgang Männel has suggested to turn to this Github account. The system in question is a Pi 3B+, administrated via SSH. It is embedded in a larger network of Linux- and Windows machines and addressed as Tronic with user Ozelot. After three days and a minimum of six installation attempts picframe is running. Now, however, it is virtually unstoppable. The guide to systemd has been applied repeatedly but picframe doesn't react.
In an older print-out from thedigitalpictureframe.com (not existing any longer in the current web site) a hint was found that with 'picframe -h' keys codes were forwarded but searching the Pi 3B+ directories has not yielded a suitable file. It is difficult to believe that a nice piece of code like picframe can only be terminated by pulling the plug...
May I ask the experts to give me a hint or two?
At least picframe is running - but not the 'conventional' way. It started only after booting to GUI by entering 'start_picframe.sh' from the home directory (that had to be added to $PATH) separatedly via terminal. There are further issues but for the moment picframe is running now on picframe works, pictures can be transfered from and to the computer - that's well worth the time and effort. It makes the (at least our) world a bit nicer - and this is well worth a big 'Thank you' to all those having made this possible.
Cordials pings from my personal CPU NCG4613