In the duplicate of this bug (861827) I had uploaded a piece of log files that indicated as suspect the "(gtk-update-icon-cache:12763): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory" warning on apt/term.log.
I tried again today to perform a full upgrade via muon in a clean virtualbox environment (kubuntu 11.10 release). The only step that was different from my first attempt was that I installed at first the kde-window-manager - > the package on which my fist attempt stuck. Nevertheless, the upgrade process hanged in the middle. In the log files, the 'suspicious' GdkPixbuf-WARNING warning was NOT present and no errors were found at all. (apt/term.log, apt/history.log, dpkg.log).
I tried a second attempt of a full upgrade, disabling at first the nepomuk file indexer (because of the entries I found in~/ .xsession-errors). Same result - hanged in 54% . The GdkPixbuf-WARNING was not there again.
Thus, I conclude that the problem is 'somewhere' else (I have no idea where...)
SInce this bug is a stairway to hell for an unexcperienced user (following a simple intuitive step of a full upgrade clicking on a system notification, you get back a broken system ) I think that if no fix can be found, It would be better in the next release no package application that breaks the sytstem to be in the distribution.
In the duplicate of this bug (861827) I had uploaded a piece of log files that indicated as suspect the "(gtk-update- icon-cache: 12763): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/ i386-linux- gnu/gdk- pixbuf- 2.0/2.10. 0/loaders. cache': No such file or directory" warning on apt/term.log.
I tried again today to perform a full upgrade via muon in a clean virtualbox environment (kubuntu 11.10 release). The only step that was different from my first attempt was that I installed at first the kde-window-manager - > the package on which my fist attempt stuck. Nevertheless, the upgrade process hanged in the middle. In the log files, the 'suspicious' GdkPixbuf-WARNING warning was NOT present and no errors were found at all. (apt/term.log, apt/history.log, dpkg.log).
I tried a second attempt of a full upgrade, disabling at first the nepomuk file indexer (because of the entries I found in~/ .xsession-errors). Same result - hanged in 54% . The GdkPixbuf-WARNING was not there again.
Thus, I conclude that the problem is 'somewhere' else (I have no idea where...)
SInce this bug is a stairway to hell for an unexcperienced user (following a simple intuitive step of a full upgrade clicking on a system notification, you get back a broken system ) I think that if no fix can be found, It would be better in the next release no package application that breaks the sytstem to be in the distribution.