On 12/18/17, Roger Price <deb...@rogerprice.org> wrote:
> Hi, command "inxi -S" reports
> Host: maria Kernel: 4.9.0-4-amd64 x86_64 (64 bit) Desktop: Xfce 4.12.3
>
> The user has defined $HOME/.config/autostart/xclock.desktop as
>
> [Desktop Entry]
> Name=Clock
> Comment=Clock with seconds hand
> Icon=xclock
> Exec=xclock -update 1 -geometry 200x200+150+400
> Terminal=false
> Type=Application
>
> When the user logs in, he gets multiple instances of xclock.
>
> root@maria ~ → ps -elf | grep -E "xclock|xfce4-session"
> 0 S rprice 1828 1757 0 80 0 - 84510 SyS_po 11:59 tty2
> 00:00:00 xfce4-session
> 0 S rprice 1861 1828 0 80 0 - 17225 SyS_po 11:59 tty2
> 00:00:00 xclock -xtsessionID
> 2c551690d-8efb-4da6-b355-e5df701247f2
> -update 1 -geometry 200x200+150+400
> 0 S rprice 1869 1828 0 80 0 - 17225 SyS_po 11:59 tty2
> 00:00:00 xclock -xtsessionID
> 2a3e8f976-91d6-4127-bcd2-53cf55e7036f
> -update 1 -geometry 200x200+150+400
> 0 S rprice 1870 1828 0 80 0 - 17225 SyS_po 11:59 tty2
> 00:00:00 xclock -xtsessionID
> 26ca134b7-27ad-4be3-adb9-24153b08bd35
> -update 1 -geometry 200x200+150+400
> 0 S rprice 1888 1828 0 80 0 - 17225 SyS_po 11:59 tty2
> 00:00:00 xclock -xtsessionID
> 238b91a2f-08bd-4734-9417-d283122ab160
> -update 1 -geometry 200x200+150+400
> 0 S rprice 1975 1828 0 80 0 - 17225 SyS_po 11:59 tty2
> 00:00:00 xclock -update 1 -geometry
> 200x200+150+400
>
> Why is this? Is there some way of avoiding these extra xclock's?
> The user's xosview.desktop produces only one copy of xosview, and
> xload.desktop produces only one xload.
Hi.. I don't have any answer but lurked along since I just
debootstrap'ed in another Stretch/XFCE4 combo the other day. I just
now installed inxi and received this:
0 S candyca+ 722 677 0 80 0 - 82264 SyS_po Dec14 ?
00:00:00 xfce4-session
It also incidentally echoed back the grep command.
Hadn't heard of xosview before, either. As such, I have no idea of its
significance in this case, but installed it, too. I love it. It's like
going back to the innocence of the 90's. :)
Ran the grep again after installing xosview, and feedback remained the
same. One different factor is that mine's been running for a couple
days. If I remember to, I'll run that again at an upcoming intended
reboot to see if things change. My guess would be that it wouldn't.
You know, as I write that last part, something came back to memory. My
Debian, forgot what combo now, went through a period of Thunar
surviving and thus staying somehow live/active through reboots. The
window wouldn't pop up, but Thunar was grep'able in my "ps aux"
queries I was running at that time.
It was purely by accident that I discovered Thunar was somehow
surviving reboots. I was having problems with something unrelated, and
there sat Thunar like it was open when it hadn't yet been used after a
fresh reboot. A Developer apparently caught it or accidentally fixed
it while addressing some other issue or feature because I haven't seen
that occur in a while now...
Cindy :)
--
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with duct tape *
