But still work to be done...
On 10/22/18 11:30 AM, Johnny Hughes wrote:
On 10/19/2018 04:43 AM, Robert Moskowitz wrote:
I am assuming this is with the generic image?
I did not know we now had an easy way to install epel, I was using the instructions on the wiki. Could you share your epel.repo content?
Finally I am guessing the machiattobin as an x64 arm? Which would point toward an x32 issue, so something that the x64 image and groups are different from the x32 image.
Thanks for sharing this!
On 10/19/18 12:49 AM, Skorpeo Skorpeo wrote:
I was able to install xfce on a machiattobin via:
yum install epel-release
See note below about epel-release
yum groupinstall xfce
just my two cents
On Thu, Oct 18, 2018 at 2:04 PM Johnny Hughes <johnny@centos.org mailto:johnny@centos.org> wrote:
On 10/18/2018 03:07 PM, Robert Moskowitz wrote: > > > On 10/18/18 3:55 PM, Johnny Hughes wrote: >> On 10/18/2018 02:43 PM, Robert Moskowitz wrote: >>> >>> On 10/18/18 3:32 PM, Johnny Hughes wrote: >>>> On 10/18/2018 12:36 PM, Robert Moskowitz wrote: >>>>> Some progress >>>>> >>>>> On 10/17/18 8:30 PM, Robert Moskowitz wrote: >>>>>> Johnny, >>>>>> >>>>>> I have this new keyboard with a poorly positioned Del key, and I >>>>>> deleted your message in such a way that it seems to be gone. So I >>>>>> went to the archive and pulled it up there. >>>>>> >>>>>> yum group install Xfce "X Window System" >>>>>> >>>>>> Helped. It added 6 packages plus 21 dependencies: >>>>>> >>>>>> Installing for group install "X Window System": >>>>>> plymouth-system-theme armv7hl 0.8.9-0.31.20140113.el7.centos >>>>>> base 31 k >>>>>> spice-vdagent armv7hl 0.14.0-15.el7 base 66 k >>>>>> xorg-x11-drivers armv7hl 7.7-6.el7 base 8.3 k >>>>>> xorg-x11-server-Xorg armv7hl 1.19.5-5.el7 base 1.2 M >>>>>> xorg-x11-utils armv7hl 7.5-22.el7 base 107 k >>>>>> xvattr armv7hl 1.3-27.el7 base 22 k >>>>>> >>>>>> But I am now at the situation where the login fails and I end up >>>>>> right >>>>>> back at the login page. I looked at the message log and see the >>>>>> following: >>>>> ..... >>>>> >>>>> I have had some help in private exchanges and have done the following: >>>>> >>>>> yum install avahi gnome-backgrounds >>>>> systemctl enable avahi-daemon >>>>> systemctl start avahi-daemon >>>>> >>>>> this took care of a number of errors, but why gnome-backgrounds for >>>>> Xfce >>>>> to deal with the message: >>>>> >>>>> Oct 17 20:17:39 ct-c7 journal: Failed to load background >>>>> 'file:///usr/share/backgrounds/gnome/adwaita-lock.jpg': Error opening >>>>> file /usr/share/backgrounds/gnome/adwaita-lock.jpg: No such file or >>>>> directory >>>>> >>>>> But still a couple of unresolved errors that are stopping the login: >>>>> >>>>> =============private exchange===================== >>>>> >>>>> >>>>>> Oct 18 10:45:34 ct-c7 journal: Some code accessed the property >>>>>> 'AuthList' on >>>>>> the module 'authList'. That property was defined with 'let' or >>>>>> 'const' inside >>>>>> the module. This was previously supported, but is not correct >>>>>> according to the >>>>>> ES6 standard. Any symbols to be exported from a module must be >>>>>> defined with >>>>>> 'var'. The property access will work as previously for the time >>>>>> being, but >>>>>> please fix your code anyway. >>>>> gnome-shell --- a nasty piece of work, and one the Gnome Mafia >>>>> want to cram down our throats >>>>> >>>>> Fedora next ship was blocked by this for a while .... >>>>> definitely file a bug and carp publicly >>>>> >>>>> >>>>> =============end private exchange===================== >>>>> >>>>> So to publicly carp... >>>>> >>>>> I even tried installing gnome-shell: >>>>> >>>>> # yum install gnome-shell >>>>> Loaded plugins: fastestmirror >>>>> Loading mirror speeds from cached hostfile >>>>> * base: mirror.siena.edu <http://mirror.siena.edu> >>>>> * centos-kernel: mirror.siena.edu <http://mirror.siena.edu> >>>>> * extras: mirror.siena.edu <http://mirror.siena.edu> >>>>> * updates: mirror.siena.edu <http://mirror.siena.edu> >>>>> Package gnome-shell-3.26.2-5.el7.armv7hl already installed and latest >>>>> version >>>>> Nothing to do >>>>> >>>>> So what does it want? This is a bug... >>>>> >>>>> And along with the above message is: >>>>> >>>>> Oct 18 10:45:36 ct-c7 org.gnome.Shell.desktop: Window manager >>>>> warning: "XF86RFKill" is not a valid accelerator >>>>> >>>>> This is also a bug to file with a need for that the accelerator not >>>>> be called when the modules is absent, as on arm? >>>>> >>>>> So I think I am getting closer to running Xfce, but stumbling along >>>>> the way. >>>>> >>>>> All help on the above greatly appreciated. >>>>> >>>>> >>>> The good (and bad :D) news is .. I have tried to install xfce on my >>>> cubbietruck plus .. and I have hit the same issue. >>>> >>>> I am going to try to get it working now. >>>> >>>> If I get it working, I'll post the solution. >>> thanks for digging into this. I was looking for a x86 box to do a >>> 'standard' minimal install and then install Xfce and see what was being >>> dropped on the box. Thing is, where do I have an x86 box here other >>> than my notebook? >> I am quite sure the issue is some pieces GNOME need to be installed to >> make everything work. >> >> I am going to try 2 things: >> >> 1) a gnome desktop install .. but afterwards only use xfce > > I can confirm that this works. It is how I got my first working Xfce, > see my post back on 10-14 9:34am EDT. This does work .. so we really just need to figure out the minimum number of packages to make this work. BTW . firefox is absolutely not usable with a 2GB cubietruck_plus in xfce. If someone wanted to seriously use this setup, it would not be on this machine. > >> 2) try with mate and lightdm and not gdm for the main screen .. then use >> xfce or mate > > It would be nice to use lightdm rather than gdm on arm. Fedora is, but > then I found some bugs on lightdm that have since been fixed (otherwise > F29 would not be in beta, as it was a blocker or something like that). > > I looked at mate, but had already adjusted to xfce thanks to it > appearing in the first Fedora-arm images. > > > I'll see if I can figure out what is missing to make xfce work with a minimal install.Robert, try this:
yum group install Core Base Xfce "X Window System"
I took things in small steps.
I did a fresh image install, firstboot, created my userID, did a 'yum update' and power cycled.
On this secondboot, I first:
yum group install Base
Install 73 Packages (+117 Dependent packages)
Then
yum group install Core Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirror.genesisadaptive.com * centos-kernel: mirror.genesisadaptive.com * extras: mirror.genesisadaptive.com * updates: mirror.genesisadaptive.com Maybe run: yum groups mark install (see man yum) No packages in any requested group available to install or update
I suspect if I did them in reverse order, Core may have installed something.
Then
yum group install "X Window System"
Install 10 Packages (+64 Dependent packages)
Now I needed epel for Xfce, so based on that previous note I tried:
yum install epel-release
and no such package, so I used the instructions from the wiki to set up epel repo. Once that was done, there was an epel-release that comes from the epel repo...
Now finally
yum group install Xfce
Install 20 Packages (+186 Dependent packages)
At this point I powered off. I connected my kybd/mouse and hdmi monitor. Powered up and could log in! With a few caveats:
No background. Looks like a backlit black. No screensaver app undersettings. Still get screen blanking via the Power Manager app. But cannot get screen lock with just this. Desktop font looks funky like it is basic Courier.
But I can live with just this. For now. :) Screensaver is important.
Next is to set up vncserver, which should be easy. Also a separate test is to repeat, but skip the boot set to get into console, and go directly to vncserver to see how this would work with a headless system, like the odroid HC1.
Meanwhile here is the log messages that were generated during the login process:
Oct 23 11:53:07 ct-c7 dbus[590]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' Oct 23 11:53:07 ct-c7 systemd: Starting Fingerprint Authentication Daemon... Oct 23 11:53:07 ct-c7 dbus[590]: [system] Successfully activated service 'net.reactivated.Fprint' Oct 23 11:53:07 ct-c7 fprintd: Launching FprintObject Oct 23 11:53:07 ct-c7 journal: D-Bus service launched with name: net.reactivated.Fprint Oct 23 11:53:07 ct-c7 journal: entering main loop Oct 23 11:53:08 ct-c7 systemd: Started Fingerprint Authentication Daemon. Oct 23 11:53:16 ct-c7 systemd: Created slice User Slice of rgm. Oct 23 11:53:16 ct-c7 systemd: Starting User Slice of rgm. Oct 23 11:53:16 ct-c7 systemd-logind: New session 2 of user rgm. Oct 23 11:53:16 ct-c7 systemd: Started Session 2 of user rgm. Oct 23 11:53:16 ct-c7 systemd: Starting Session 2 of user rgm. Oct 23 11:53:16 ct-c7 gdm: Failed to remove greeter program access to the display. Trying to proceed. Oct 23 11:53:16 ct-c7 gnome-session: gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' killed by signal 15 Oct 23 11:53:16 ct-c7 gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' killed by signal 15 Oct 23 11:53:16 ct-c7 gnome-session: gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.XSettings.desktop' killed by signal 15 Oct 23 11:53:16 ct-c7 gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.XSettings.desktop' killed by signal 15 Oct 23 11:53:17 ct-c7 gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.A11yKeyboard.desktop' killed by signal 15 Oct 23 11:53:17 ct-c7 gnome-session: gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.A11yKeyboard.desktop' killed by signal 15 Oct 23 11:53:17 ct-c7 gnome-session: gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.A11ySettings.desktop' killed by signal 15 Oct 23 11:53:17 ct-c7 gnome-session: gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.Clipboard.desktop' killed by signal 15 Oct 23 11:53:17 ct-c7 gnome-session: gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.Housekeeping.desktop' killed by signal 15 Oct 23 11:53:17 ct-c7 gnome-session: gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.ScreensaverProxy.desktop' killed by signal 15 Oct 23 11:53:17 ct-c7 gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.A11ySettings.desktop' killed by signal 15 Oct 23 11:53:17 ct-c7 gnome-session: gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.Sharing.desktop' killed by signal 15 Oct 23 11:53:17 ct-c7 gnome-session: gnome-session-binary[679]: WARNING: Lost name on bus: org.gnome.SessionManager Oct 23 11:53:17 ct-c7 gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.Clipboard.desktop' killed by signal 15 Oct 23 11:53:17 ct-c7 gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.Housekeeping.desktop' killed by signal 15 Oct 23 11:53:17 ct-c7 gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.ScreensaverProxy.desktop' killed by signal 15 Oct 23 11:53:17 ct-c7 gnome-session-binary[679]: WARNING: Application 'org.gnome.SettingsDaemon.Sharing.desktop' killed by signal 15 Oct 23 11:53:17 ct-c7 gnome-session-binary[679]: WARNING: Lost name on bus: org.gnome.SessionManager Oct 23 11:53:17 ct-c7 journal: Cannot open display: Oct 23 11:53:17 ct-c7 journal: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Oct 23 11:53:20 ct-c7 spice-vdagent[1485]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Oct 23 11:53:20 ct-c7 org.a11y.Bus: Activating service name='org.a11y.atspi.Registry' Oct 23 11:53:21 ct-c7 org.a11y.Bus: Successfully activated service 'org.a11y.atspi.Registry' Oct 23 11:53:21 ct-c7 org.a11y.atspi.Registry: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Oct 23 11:53:37 ct-c7 journal: No devices in use, exit Oct 23 11:53:39 ct-c7 systemd-logind: Removed session c1. Oct 23 11:53:39 ct-c7 systemd: Removed slice User Slice of gdm. Oct 23 11:53:39 ct-c7 systemd: Stopping User Slice of gdm.
Perhaps someone can figure out what all this means and if there are other problems than those I listed above.