https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244894
--- Comment #3 from Guido Falsi <madpi...@freebsd.org> --- (In reply to Chris Hutchinson from comment #2) > I've not been a fan of using pkg. But felt it might be > time to give it another chance. So *everything* is straight > from FreeBSD. That is; the kernel, and world are that which > came from the install medium, and everything else is straight > from pkg(8). SO I guess you're using packages from the quarterly set. One test worth a try would be to upgrade to the latest package set and check if the bug still happens. > So. I decided to test against slim; > pkg install icewm > echo icewm-session>~/.xinitrc > bounce box > login via slim. Which presents the IceWM desktop. Everything > works fine. IceWM still works. So I think we can rule out slim. This is not completely true. If xfce4-session dumps core it's probable it has a bug somewhere, but this bug could be triggered by slim, and not triggered by another display manager. So while your test proves that slim does it's job for IceWM it does not prove that slim is not doing something wrong which upsets xfce4-session. Please try with another display manager. I can try making a test with a setup similar to yours in a virtual machine, but even if I can reproduce your bug I'm not an xfce4 developer. I'd suggest you file a bug report upstream, but then again without a backtrace of the crash they can do very little. Understanding what is going wrong without a backtrace is like divination. > I have no ports(7) or source tree on this box. Are you suggesting > that I build everything from source? Is there no flag I can > append to xfce4-session that might make more noise in the log(s) > and perhaps provide more clues? If you want to extract some backtrace information which could at least indicate in which part of the code xfce-session is crashing there is no other option than building it with debug enabled. I can try to reproduce your bug and in that case build with debugging enabled and test that. But it will require time, at least some days, providing I can reproduce the bug. And no, I don't know of any special flag, in fact I know relatively little about xfce4-session, of which I'm just a user actually. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-xfce@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xfce To unsubscribe, send any mail to "freebsd-xfce-unsubscr...@freebsd.org"
