Hi!
martin f krafft schrieb:
Fatal server error: Caught signal 11. Server aborting
This is a segmentation fault, which could be caused by anything, including bad memory.
Does it only ever happen when you try fbrun? When exactly?
fbrun is the only thing that behaves like this (since the upgrade to
fluxbox-0.9.11). Except for... well, as I wrote, restarting fluxbox from the RootMenu gives a similar result. At first, it looks like a usual
restart, but then X crashes and leaves the end of .xsession-errors as
follows:
Failed to read: session.forcePseudoTransparency Setting default value Failed to read: session.tabPadding Setting default value Failed to read: session.focusTabMinWidth Setting default value Failed to read: session.appsFile Setting default value Failed to load groupfile: X connection to :0.0 broken (explicit kill or server shutdown).
As one may notice, this is exactly what happens at the startup of fluxbox, just that in this case, the X server is killed after "Failed to load groupfile". What is that groupfile? /etc/group? BTW, same thing happens when I used Openbox temporarily and then switched back to fluxbox. I don't know whether this problem is still related to fbrun's one, but I'd be happy to solve either one.
Bye Tobias
--
Those who would give up Essential Liberty to purchase a
little Temporary Safety, deserve neither Liberty nor Safety.
-- Benjamin Franklin (1706 - 1790)
signature.asc
Description: OpenPGP digital signature
