Hello!
Stephan Sokolow has written on Sunday, 10 November, at 6:42:
>On 13-11-10 05:24 AM, Andrej N. Gritsenko wrote:
>> In fact, auto-restart might be needed only if some component crashes.
>> And also in fact, in many cases this does not work at all, because when
>> that happens, the possibility that conditions for the crash still present
>> is high so it crashes again and again. I'm not sure if auto-restart have
>> to be there at all.
[...skipped...]
>- Fiddling with PDF viewer windows has sometimes caused Openbox to crash
>persistently but somewhat unpredictably. Thanks to auto-restart, all my
>windows flicker and then I can get back to work.
Well, I don't know who restarts Openbox. I always believed if window
manager crashes then the whole session will crash as well. But you know,
since window manager is a core for all applications, it cannot be started
the same way as some application so it is irrelevant for the subject of
discission (i.e. autorestart for /etc/xdg/autostart/ items) in any case.
>- Rapidly opening and closing LibreOffice windows as part of splitting a
>.DOC into several dozen per-chapter HTML files can cause LXPanel to
>freeze or crash.
> In the former case (lxpanel freezes), I hit Win+Space to pull up
> gmrun (habit since I normally demand a run dialog with tab completion
> and command history) and type "killall -SEGV lxpanel" because it's
> easier than remembering or looking up the exact command to respawn it
> after SIGTERM causes lxsession to omit the auto-restart.
> In both cases (freeze or crash), I then usually have to hit Win+Space
> again and type "sh -c 'audtool shutdown; sleep 2; audacious &'"
> because LXPanel is the only panel which doesn't take responsibility
> for recovering tray icons and Audacious is one of a handful of apps
> (Audacious, neap, oDesk Team) which don't take responsibility for
> re-creating their tray icons and, since no Audacious devs use LXDE,
> their response is "Unless you want to provide a patch, it's a bug in
> LXPanel, not Audacious, since it works in Xfce, GNOME, KDE, etc."
Yes, I'm aware that lxpanel is somewhat buggy and sometimes crashes.
If I wasn't so busy with libmenu-cache/libfm/pcmanfm I would take part in
it. It seems as the most buggy core component of LXDE. It still has 129
bugreports in the bugtracker and I'm not sure if there are no other bugs
still unreported. :(
May be I should go for it after the LibFM/PCManFM 1.2.0 will get a
final release? Yes, I know, Qt will be ready sometime later, but for now
it is still raw and unusable for me so I still stick with pcmanfm and
lxpanel GTK+ versions (yes, I restart lxpanel manually when it crashes
and I don't use "start application" function of lxpanel, I use Xfce
starter instead, it is similar to lxpanel's one, but reliable and also
can remember history of commands).
Well, anyway, I still believe any autorestart is a workaround, which
is dirty and very bad thing to do, we have to fix core components instead
of workarounding bugs. :)
Well, how Xfce, GNOME, KDE, etc. handle similar issues? Do they also
autorestart core DE components?
>- Various PCManFM crashes I've encountered over the years.
About PCManFM I treat any crash as issue that should be fixed ASAP,
and that issue should never ever happen and I highly suggest never do
autorestart on it. Well, I know, it crashed before 1.0 as in a hell, but
now if it ever crashes, feel free to bomb me, it is simply an emergency
situation.
Cheers!
Andriy.
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Lxde-list mailing list
Lxde-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxde-list
