Gentoo notebook: Aggiornamento in difficoltà

[conoscenza]

prova a dare
emerge -DNu world

[Zievatron]

Al 38esimo pacchetto è finita così:

Codice: Seleziona tutto

collect2: ld returned 1 exit status
make[2]: *** [test-pager] Errore 1
make[2]: *** Attesa dei processi non terminati....
/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/../../../../x86_64-pc-linux-gnu/bin/ld: warning: libxcb-util.so.0, needed by /usr/lib64/libstartup-notification-1.so, not found (try using -rpath or -rpath-link)
/usr/lib64/libstartup-notification-1.so: undefined reference to `xcb_aux_get_screen'
collect2: ld returned 1 exit status
make[2]: *** [wnck-urgency-monitor] Errore 1
/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/../../../../x86_64-pc-linux-gnu/bin/ld: warning: libxcb-util.so.0, needed by /usr/lib64/libstartup-notification-1.so, not found (try using -rpath or -rpath-link)
/usr/lib64/libstartup-notification-1.so: undefined reference to `xcb_aux_get_screen'
collect2: ld returned 1 exit status
make[2]: *** [wnckprop] Errore 1
make[2]: Leaving directory `/var/tmp/portage/x11-libs/libwnck-2.31.0/work/libwnck-2.31.0/libwnck'
make[1]: *** [all-recursive] Errore 1
make[1]: Leaving directory `/var/tmp/portage/x11-libs/libwnck-2.31.0/work/libwnck-2.31.0'
make: *** [all] Errore 2
 * ERROR: x11-libs/libwnck-2.31.0 failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=x11-libs/libwnck-2.31.0'`,
 * the complete build log and the output of `emerge -pqv '=x11-libs/libwnck-2.31.0'`.
 * The complete build log is located at '/var/tmp/portage/x11-libs/libwnck-2.31.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/x11-libs/libwnck-2.31.0/temp/environment'.
 * Working directory: '/var/tmp/portage/x11-libs/libwnck-2.31.0/work/libwnck-2.31.0'
 * S: '/var/tmp/portage/x11-libs/libwnck-2.31.0/work/libwnck-2.31.0'

>>> Failed to emerge x11-libs/libwnck-2.31.0, Log file:

>>>  '/var/tmp/portage/x11-libs/libwnck-2.31.0/temp/build.log'

 * Messages for package media-libs/alsa-lib-1.0.25-r1:

 * Please try in-kernel ALSA drivers instead of the alsa-driver ebuild.
 * If alsa-driver works for you where a *recent* kernel does not, we want 
 * to know about this. Our e-mail address is alsa-bugs@gentoo.org
 * However, if you notice no sound output or instability, please try to 
 * upgrade your kernel to a newer version first.

 * Messages for package x11-proto/xcb-proto-1.7.1:

 * Please rebuild both libxcb and xcb-util if you are upgrading from version 1.6

 * Messages for package app-portage/gentoolkit-0.3.0.6-r3:

 * 
 * glsa-check since gentoolkit 0.3 has modified some output,
 * options and default behavior. The list of injected GLSAs
 * has moved to /var/lib/portage/glsa_injected, please
 * run 'glsa-check -p affected' before copying the existing checkfile.

 * Messages for package media-libs/freetype-2.4.9-r1:

 * The TrueType bytecode interpreter is no longer patented and thus no
 * longer controlled by the bindist USE flag.  Enable the auto-hinter
 * USE flag if you want the old USE=bindist hinting behavior.

 * Messages for package x11-libs/libXi-1.6.1:

 * Some special keys and keyboard layouts may stop working.
 * To fix them, recompile xorg-server.

 * Messages for package media-libs/mesa-8.0.3:

 * USE="bindist" was not set. Potentially patent encumbered code was
 * enabled. Please see patents.txt for an explanation.

 * Messages for package x11-libs/gtk+-2.24.10-r1:

 * Please install app-text/evince for print preview functionality.
 * Alternatively, check "gtk-print-preview-command" documentation and
 * add it to your gtkrc.

 * Messages for package x11-libs/libwnck-2.31.0:

 * ERROR: x11-libs/libwnck-2.31.0 failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=x11-libs/libwnck-2.31.0'`,
 * the complete build log and the output of `emerge -pqv '=x11-libs/libwnck-2.31.0'`.
 * The complete build log is located at '/var/tmp/portage/x11-libs/libwnck-2.31.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/x11-libs/libwnck-2.31.0/temp/environment'.
 * Working directory: '/var/tmp/portage/x11-libs/libwnck-2.31.0/work/libwnck-2.31.0'
 * S: '/var/tmp/portage/x11-libs/libwnck-2.31.0/work/libwnck-2.31.0'

 * GNU info directory index is up-to-date.
 * After world updates, it is important to remove obsolete packages with
 * emerge --depclean. Refer to `man emerge` for more information.

[conoscenza]

bene.
Dai
etc-update (-5 se necessario)
emerge --depclean
emerge --sync
emerge -DNu world

[Zievatron]

Questa volta ha fallito al secondo pacchetto.

Codice: Seleziona tutto

collect2: ld returned 1 exit status
make[2]: *** [wnckprop] Errore 1
/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/../../../../x86_64-pc-linux-gnu/bin/ld: warning: libxcb-util.so.0, needed by /usr/lib64/libstartup-notification-1.so, not found (try using -rpath or -rpath-link)
/usr/lib64/libstartup-notification-1.so: undefined reference to `xcb_aux_get_screen'
collect2: ld returned 1 exit status
make[2]: *** [test-pager] Errore 1
make[2]: Leaving directory `/var/tmp/portage/x11-libs/libwnck-2.31.0/work/libwnck-2.31.0/libwnck'
make[1]: *** [all-recursive] Errore 1
make[1]: Leaving directory `/var/tmp/portage/x11-libs/libwnck-2.31.0/work/libwnck-2.31.0'
make: *** [all] Errore 2
 * ERROR: x11-libs/libwnck-2.31.0 failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=x11-libs/libwnck-2.31.0'`,
 * the complete build log and the output of `emerge -pqv '=x11-libs/libwnck-2.31.0'`.
 * The complete build log is located at '/var/tmp/portage/x11-libs/libwnck-2.31.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/x11-libs/libwnck-2.31.0/temp/environment'.
 * Working directory: '/var/tmp/portage/x11-libs/libwnck-2.31.0/work/libwnck-2.31.0'
 * S: '/var/tmp/portage/x11-libs/libwnck-2.31.0/work/libwnck-2.31.0'

>>> Failed to emerge x11-libs/libwnck-2.31.0, Log file:

>>>  '/var/tmp/portage/x11-libs/libwnck-2.31.0/temp/build.log'

 * Messages for package x11-libs/libwnck-2.31.0:

 * ERROR: x11-libs/libwnck-2.31.0 failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=x11-libs/libwnck-2.31.0'`,
 * the complete build log and the output of `emerge -pqv '=x11-libs/libwnck-2.31.0'`.
 * The complete build log is located at '/var/tmp/portage/x11-libs/libwnck-2.31.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/x11-libs/libwnck-2.31.0/temp/environment'.
 * Working directory: '/var/tmp/portage/x11-libs/libwnck-2.31.0/work/libwnck-2.31.0'
 * S: '/var/tmp/portage/x11-libs/libwnck-2.31.0/work/libwnck-2.31.0'

 * Regenerating GNU info directory index...
 * Processed 89 info files.
 * After world updates, it is important to remove obsolete packages with
 * emerge --depclean. Refer to `man emerge` for more information.

[conoscenza]

emerge --depclean
revdep-rebuild
emerge -DNu world

riporta tutti e tre gli output.

[Zievatron]

Codice: Seleziona tutto

darkstar / # emerge --depclean

 * Depclean may break link level dependencies. Thus, it is
 * recommended to use a tool such as `revdep-rebuild` (from
 * app-portage/gentoolkit) in order to detect such breakage.
 * 
 * Always study the list of packages to be cleaned for any obvious
 * mistakes. Packages that are part of the world set will always
 * be kept.  They can be manually added to this set with
 * `emerge --noreplace <atom>`.  Packages that are listed in
 * package.provided (see portage(5)) will be removed by
 * depclean, even if they are part of the world set.
 * 
 * As a safety measure, depclean will not remove any packages
 * unless *all* required dependencies have been resolved.  As a
 * consequence, it is often necessary to run `emerge --update
 * --newuse --deep @world` prior to depclean.

Calculating dependencies... done!
 * Dependencies could not be completely resolved due to
 * the following required packages not being installed:
 * 
 *   >=xfce-base/xfce4-appfinder-4.9 pulled in by:
 *     xfce-base/xfce4-meta-4.8
 * 
 *   >=xfce-base/xfce-utils-4.8 pulled in by:
 *     xfce-base/xfce4-session-4.8.2
 * 
 * Have you forgotten to do a complete update prior to depclean? The
 * most comprehensive command for this purpose is as follows:
 * 
 *   emerge --update --newuse --deep --with-bdeps=y @world
 * 
 * Note that the --with-bdeps=y option is not required in many
 * situations. Refer to the emerge manual page (run `man emerge`)
 * for more information about --with-bdeps.
 * 
 * Also, note that it may be necessary to manually uninstall
 * packages that no longer exist in the portage tree, since it may
 * not be possible to satisfy their dependencies.

revdep-rebuild, dopo aver riemerso 9 pacchetti, si è concluso così:

Codice: Seleziona tutto

>>> No outdated packages were found on your system.

 * GNU info directory index is up-to-date.
 * Portage could not find any version of the following packages it could build:
 * xfce-base/xfce4-session:0
 * (Perhaps they are masked, blocked, or removed from portage.)
 * Try to emerge them manually.
 * Build finished correctly. Removing temporary files...
 * You can re-run revdep-rebuild to verify that all libraries and binaries
 * are fixed. Possible reasons for remaining inconsistencies include:
 *   orphaned files
 *   deep dependencies
 *   packages installed outside of portage's control
 *   specially-evaluated libraries

Codice: Seleziona tutto

>>> Installing (26 of 26) app-text/poppler-0.18.4-r1
 * After upgrading app-text/poppler you may need to reinstall packages
 * linking to it. If you're not a portage-2.2_rc user, you're advised
 * to run revdep-rebuild

 * Messages for package sys-apps/dbus-1.6.2:

 * To start the D-Bus system-wide messagebus by default
 * you should add it to the default runlevel :
 * `rc-update add dbus default`
 * 
 * Some applications require a session bus in addition to the system
 * bus. Please see `man dbus-launch` for more information.
 * 
 * You must restart D-Bus `/etc/init.d/dbus restart` to run
 * the new version of the daemon.
 * Don't do this while X is running because it will restart your X as well.

 * Messages for package net-print/cups-1.5.2-r4:

 * Your usb printers will be managed via libusb. In this case, 
 * cups-1.5.2 requires the USB_PRINTER support disabled.
 * Please disable it:
 *     CONFIG_USB_PRINTER=n
 * in /usr/src/linux/.config or
 *     Device Drivers --->
 *         USB support  --->
 *             [ ] USB Printer support
 * Alternatively, just disable the usb useflag for cups (your printer will still work).
 * For information about installing a printer and general cups setup
 * take a look at: http://www.gentoo.org/doc/en/printing-howto.xml
 * Network browsing for printers is now switched off by default in the config file.
 * To (re-)enable it, edit /etc/cups/cupsd.conf and set "Browsing On", 
 * afterwards re-start or reload cups.

 * Messages for package x11-libs/gtk+-3.2.4-r1:

 * Please install app-text/evince for print preview functionality.
 * Alternatively, check "gtk-print-preview-command" documentation and
 * add it to your settings.ini file.

 * Messages for package net-misc/openssh-5.9_p1-r4:

 * Starting with openssh-5.8p1, the server will default to a newer key
 * algorithm (ECDSA).  You are encouraged to manually update your stored
 * keys list as servers update theirs.  See ssh-keyscan(1) for more info.
 * Remember to merge your config files in /etc/ssh/ and then
 * reload sshd: '/etc/init.d/sshd reload'.
 * Please be aware users need a valid shell in /etc/passwd
 * in order to be allowed to login.

 * Messages for package sys-fs/udev-171-r6:

 * 
 * udev-171 does not support Linux kernel before version 2.6.32!
 * 
 * persistent-net does assigning fixed names to network devices.
 * If you have problems with the persistent-net rules,
 * just delete the rules file
 * 	rm /etc/udev/rules.d/70-persistent-net.rules
 * and then reboot.
 * 
 * This may however number your devices in a different way than they are now.
 * 
 * If you build an initramfs including udev, then please
 * make sure that the /sbin/udevadm binary gets included,
 * and your scripts changed to use it,as it replaces the
 * old helper apps udevinfo, udevtrigger, ...
 * 
 * mount options for directory /dev are no longer
 * set in /etc/udev/udev.conf, but in /etc/fstab
 * as for other directories.
 * 
 * If you use /dev/md/*, /dev/loop/* or /dev/rd/*,
 * then please migrate over to using the device names
 * /dev/md*, /dev/loop* and /dev/ram*.
 * The devfs-compat rules have been removed.
 * For reference see Bug #269359.
 * 
 * Rules for /dev/hd* devices have been removed
 * Please migrate to libata.
 * 
 * For more information on udev on Gentoo, writing udev rules, and
 *          fixing known issues visit:
 *          http://www.gentoo.org/doc/en/udev-guide.xml

 * Messages for package sys-apps/util-linux-2.20.1-r2:

 * The agetty util now clears the terminal by default.  You
 * might want to add --noclear to your /etc/inittab lines.

 * Messages for package sys-kernel/gentoo-sources-3.3.8:

 * If you are upgrading from a previous kernel, you may be interested
 * in the following document:
 *   - General upgrade guide: http://www.gentoo.org/doc/en/kernel-upgrade.xml

 * Messages for package app-text/poppler-0.18.4-r1:

 * After upgrading app-text/poppler you may need to reinstall packages
 * linking to it. If you're not a portage-2.2_rc user, you're advised
 * to run revdep-rebuild
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

 * Regenerating GNU info directory index...
 * Processed 90 info files.
 * After world updates, it is important to remove obsolete packages with
 * emerge --depclean. Refer to `man emerge` for more information.

[conoscenza]

dai:
rc-update add dbus default
reboot
e poi
revdep-rebuild

[Zievatron]

dai:
rc-update add dbus default

Perchè?

Codice: Seleziona tutto

darkstar / # rc-update add dbus default
 * rc-update: dbus already installed in runlevel `default'; skipping

[conoscenza]

Era scritto qui:

To start the D-Bus system-wide messagebus by default
* you should add it to the default runlevel :
* `rc-update add dbus default`

forse bastava:
/etc/init.d/dbus restart
e poi
revdep-rebuild

[Zievatron]

Mi risponde così:

Codice: Seleziona tutto

darkstar / # /etc/init.d/dbus restart
 * Caching service dependencies ...                                       [ ok ]
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: sysfs failed to start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: udev-mount failed to start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: sysfs failed to start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: udev-mount failed to start
 * ERROR: cannot start udev as sysfs would not start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: sysfs failed to start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: udev-mount failed to start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: sysfs failed to start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: udev-mount failed to start
 * ERROR: cannot start udev as sysfs would not start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: fsck failed to start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: sysfs failed to start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: udev-mount failed to start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: sysfs failed to start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: udev-mount failed to start
 * ERROR: cannot start udev as sysfs would not start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: sysfs failed to start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: udev-mount failed to start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: sysfs failed to start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: udev-mount failed to start
 * ERROR: cannot start udev as sysfs would not start
 * You are attempting to run an openrc service on a
 * system which openrc did not boot.
 * You may be inside a chroot or you may have used
 * another initialization system to boot this system.
 * In this situation, you will get unpredictable results!
 * If you really want to do this, issue the following command:
 * touch /lib64/rc/init.d/softlevel
 * ERROR: fsck failed to start
 * ERROR: cannot start localmount as fsck would not start
 * ERROR: cannot start dbus as fsck would not start