On 27.03.15 01:50, Volker Kuhlmann wrote:
> I prefer to use yast-x11 on the cubieboard, it takes a looong time to
> start but then runs OK (over ssh). There are 2 problems with it:
> 
> 1) The software management shows 37 autoinstall packages, including
> alsa-oss, bash-doc, glibc-extra, openssh-helpers, perl-HTML-Tidy,
> unzip-doc.
> zypper up shows nothing to do, as does yast-ncurses, and both show the
> locked packages apache2-mod_perl mariadb php5
> 
> Why does yast-x11 want to install a pile of stuff that is definitely ot
> needed by anything, like the -doc packages?
> Why is this difference in behaviour between x11/ncurses versions?
> 
> 2) No keyboard input is accepted anywhere in yast.
> 
> This stdout/err of yast-x11 says why:
> 
> libEGL warning: DRI2: could not open /dev/dri/card0 (No such file or 
> directory)
> xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb
> Qt: Failed to create XKB context!
> Use QT_XKB_CONFIG_ROOT environmental variable to provide an additional search 
> path, add ':' as separator to provide several search paths and/or make sure 
> that XKB configuration data directory contains recent enough contents, to 
> update please see http://cgit.freedesktop.org/xkeyboard-config/ .
> 
> Ooops, no X11 keyboard input installed! To fix:
> 
>   zypper in xf86-input-keyboard    (another 27 packages)
> 
> I installed yast-x11 with
> 
>   zypper in yast2-x11 yast2-control-center-qt libyui-qt6 xauth
> 
> which installs ca 265 rpms, so something is missing a dependency on
> basic keyboard input. Or is this intentional? Otherwise I'll file a bug.
> I don't expect this to be specific to armv7hl, though it's triggered
> there because it's a smaller minimal system to start with.

Reading through this, maybe you want to start off with an image that
already provides all the gfx that you need? We have XFCE, E17 and LXQT
images available for pretty much any board that come with a lot more
packages preinstalled.


Alex
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to