Hi,
> " == sean <seandarcy2@xxxxxxxxx> writes:
> >
> > sean> I installed xfce to see if it was a gnome/kde problem. Here's
> > sean> what shows on the xfce console:
> >
> >>> (==) Using config file: "/etc/X11/xorg.conf" /usr/bin/startxfce4: X
> >>> server already running on display :0 Agent pid 4100 which: no
> >>> xfce4-session in
> >>> (/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/usr/NX/bin:/root/bin)
> >>> (xfce-mcs-manager:4103): libxfce4mcs-CRITICAL **:
> >>> mcs_manager_add_channel_from_file: assertion `filename != NULL &&
> >>> strlen (filename) > 0' failed /etc/xdg/xfce4/xinitrc: line 106:
> >>> 4105 Segmentation fault xfwm4 --daemon ** Message: Cannot connect
> >>> to session manager /etc/xdg/xfce4/xinitrc: line 123: 4108
> >>> Segmentation fault xfcalendar /etc/xdg/xfce4/xinitrc: line 123:
> >>> 4110 Segmentation fault $panel
> >
> > sean> So X appears to start - Fedora logo comes up; no error on
> > sean> Xorg.0.log.
> >
> > sean> But no gui's will start - not gnome,kde or xfce. Does this mean
> > sean> X isn't starting correctly so that the gui's can start? If not,
> > sean> what happens between X coming up and the gui's starting?
> >
> > sean> metacity? Is there any way to cause metacity to do verbose
> > sean> logging?
> >
> > sean> Again, is there any way to get more verbose and clearer logs.
> >
> > sean> Or any other hints?
> >
> > Well, not sure on gnome or KDE, but the above Xfce output looks like
> > the problem is the Seg faults when trying to start up. :(
> >
> > Several other things to try:
> >
> > - If you create a new fresh user, can they login ok?
> > (This would point to it being you users gtk theme, fonts setup or the
> > like).
> >
>
> Yes! I can login as a new user. Switched xorg.conf back to using xfs,
> and that worked to.
>
> ( Oddly, when I logout as the new user, I'm left at console 7 with a
> black screen and a blinking cursor at top left. console 1, witch I have
> to manually switch to, shows the usual X shutdown stuff.)
>
> > - Could be some package leftover from your rawhide install causing
> > issues, perhaps a 'yum list extras' to identify any packages that are
> > not in repositories you have currently enabled?
> >
> > - Could you try and run xfwm4 under a debugger?
> > 0) yum --enable-repo=core-debuginfo install xfwm4-debuginfo
> yum --enablerepo=extras-debuginfo ........ :)
>
> > 1) Run X from a console, "xinit /usr/X11R6/bin/xterm &"
> > 2) Switch to a console (Ctrl+Alt+F1)
> > 3) Set the display "export DISPLAY=:0.0"
> > 4) run "gdb /usr/bin/xfwm4"
> > 5) if/when it crashes, run 'bt' and send me the backtrace.
> >
>
> Well, it appears to be font related. I hope you can figure out what the
> font problems is though.
Does
rm -f ~/.fonts.cache-2 \
~/.rh-fontconfig/.fonts.cache-2 \
~/.fonts/fonts.cache-2
fix things up?
--Ray
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
