Lubuntu 14.04 LTS
Aere at Dvorak-Keyboards.com
Sat Apr 19 00:36:21 UTC 2014
On 04/18/2014 02:14 PM, farinet at arcor.de wrote:
> Finally, 'do-release-upgrade' passed through fine (some questions
> though, cfr.below)
> First one real nice thing in lubuntu 14.04, *FINALLY* suspend in my
> samsung 535u3c seems to work fine. As well as lid_closed. Might be a
> result of the new kernel or of the new fglrx driver (13.35.1 oder
> 13.35.0 i had before). Anyway ... ;-)
> During the installation i got this msg:
> (gtk-update-icon-cache-3.0:4275): GdkPixbuf-WARNING **: Cannot open
> pixbuf loader module file
> '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Datei
> oder Verzeichnis nicht gefunden
> This likely means that your installation is broken.
> Try running the command
> gdk-pixbuf-query-loaders >
> to make things work again for the time being.
> I did as the installer proposed. As far as i remember that's something
> related to Gtk2 and Gtk3 (?) Now, effectively i do not see any such
> error while using lubuntu 14.04
> And then this msg:
> Neue Version der Konfigurationsdatei
> /etc/laptop-mode/conf.d/usb-autosuspend.conf wird installiert ...
> Error for wireless request "Set Power Management" (8B2C) :
> SET failed on device wlan0 ; Operation not supported.
> * Laptop mode
> enabled, not active
> [I translate: New version of config file /etc/laptop-mode/conf.d
> /usb-autosuspend.conf will be installed ...
> .... ]
> Now, since the pm seems to work correctly i won't have to worry would i?
> And then, during the boot i get this (which is new respect to 13.10):
> Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
> Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
> Skipping profile in /etc/apparmor.d/disable: usr.sbin.squid3
> What does that mean? And should i have to correct something in relation
> to that?
I've seen the pixbuf error message in the upgrades of prior systems, and
have worried about that as well.
But in using the systems upgraded with that error occurring, I have not
been able to recognize what is 'broken'. The systems seem to work fine.
More information about the Lubuntu-users