[ale] Fedora 27 no window manager

[Robert Tweedy]

It looks like it's a known bug with the update of the soundtouch package
from 1.9.x to 2.0.0
(https://bugzilla.redhat.com/show_bug.cgi?id=1601724). I ran into a
similar issue on my Fedora 27 install where dnf complained that it
couldn't upgrade "gstreamer1-plugins-bad" because it interfered with the
soundtouch 1.9 package, and it couldn't upgrade to soundtouch 2.0.0
because it interfered with the "gstreamer1-plugins-bad" package.

Tried removing soundtouch 1.9 just to see what it would do, but backed
out of the command as soon as it said it wanted to remove everything but
the kitchen sink and systemd to satisfy dependencies. Ultimately decided
to just skip updates this week and try again next Friday.

-Robert

On 07/20/2018 08:16 PM, Jim Kinney via Ale wrote:
> dnf group-list
> Then dnf group-install the appropriate group to get X desktop. Don't
> know if you use kde, gnome or others. You can also do group-remove,
> then group-install.
>
> Check /var/log/yum or dnf log for what was done prior to all of this.
> Try reinstalling the prior removed package.
>
> On July 20, 2018 5:57:35 PM EDT, Pete Hardie <pete.hardie at gmail.com>
> wrote:
>
>     Oh, and X -configure crashes
>
>     On Fri, Jul 20, 2018, 17:38 Jim Kinney via Ale <ale at ale.org
>     <mailto:ale at ale.org>> wrote:
>
>         Or just run X -configure to build a config file.
>
>         What package was fubarred? I run fedora 27/28 systems and have
>         only had issues with packages from repos other than fedora and
>         rpmfusion.
>
>         On July 20, 2018 5:21:46 PM EDT, Steve Litt via Ale
>         <ale at ale.org <mailto:ale at ale.org>> wrote:
>
>             On Fri, 20 Jul 2018 17:13:53 -0400
>             Pete Hardie via Ale <ale at ale.org <mailto:ale at ale.org>> wrote:
>
>                 A cry for help. Was updating this evening, and dnf
>                 said there was one package with a conflict and gave
>                 dnf options to resolve it. I followed that and halfway
>                 through the box reset, and now I can't get it back to
>                 graphical mode. Systemd has made it harder for me to
>                 diagnose, so the batsignal is lit 
>
>
>             Try using startx to start X. Note you must have a ~/.xinitrc file for
>             this to work. Here's my (rather overly complex) ~/.xinitrc:
>
>             #!/bin/sh
>             xrdb -load /home/slitt/.Xdefaults
>             boolean false exec /usr/bin/openbox-session
>
>             Let us know whether this works.
>
>             SteveT
>
>             Steve Litt
>             Author: The Key to Everyday Excellence
>             http://www.troubleshooters.com/key
>             Twitter: http://www.twitter.com/stevelitt
>
>             ------------------------------------------------------------------------
>
>             Ale mailing list
>             Ale at ale.org <mailto:Ale at ale.org>
>             https://mail.ale.org/mailman/listinfo/ale
>             See JOBS, ANNOUNCE and SCHOOLS lists at
>             http://mail.ale.org/mailman/listinfo
>
>
>         -- 
>         Sent from my Android device with K-9 Mail. All tyopes are
>         thumb related and reflect authenticity.
>         _______________________________________________
>         Ale mailing list
>         Ale at ale.org <mailto:Ale at ale.org>
>         https://mail.ale.org/mailman/listinfo/ale
>         See JOBS, ANNOUNCE and SCHOOLS lists at
>         http://mail.ale.org/mailman/listinfo
>
>
> -- 
> Sent from my Android device with K-9 Mail. All tyopes are thumb
> related and reflect authenticity.
>