Am Freitag, den 19.03.2010, 23:14 -0400 schrieb Marty Jack: > I looked at the LXTerminal crash and it is because it cannot bind to > the communication socket that it creates in /tmp. Maybe SELinux is > preventing this. In any event the code is not resilient to any > failure in setting that socket up, which should be fixed, but maybe > there is a way to solve the underlying problem so it would not be > triggered.
Is the name of the socket predictable or can we move it to a subdir of /tmp? If we were to use a subdir, it should be pretty easy to apply a special SELinux context. > lxterminal -e seems to work okay if you run something like alsamixer > that stays running, but not something like ls that exits immediately. I hadn't noticed that one but I think you are right. > As to what changed in background color handling so that some people > are reporting black instead of the color they selected, I do not know. > Works fine when I tested it on Openbox and Compiz. Should find out > from the customer what window manager it is. Background settings work fine here. > I should also mention how helpful those backtraces are with the panel > bugs. Great, thanks a lot for taking care of the bugs. When we started using the automatic bug reporting tool it produced a lot of useless backtraces without debuginfo, but now things seem to work properly. Nevertheless it's a lot of work for me as a maintainer, I have ~ open ABRT bugs. Keep on the good work, it's highly appreciated. Regards, Christoph ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
