still having problems with upgrade/dist-upgrade, now the output on the terminal is saying some packages are missing and system? is broken and it it's fresh in stall an d no it's not a fresh install but a 4 day old re-install.

Bug #1291355 reported by Brian J Slease
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

(gtk-update-icon-cache-3.0:2796): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

This likely means that your installation is broken.
Try running the command
  gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.
Processing triggers for gnome-menus (3.10.1-0ubuntu1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
Processing triggers for mime-support (3.54ubuntu1) ...
Processing triggers for ureadahead (0.100.0-16) ...
ureadahead will be reprofiled on next reboot
Setting up libgdk-pixbuf2.0-common (2.30.6-1) ...
Setting up libgdk-pixbuf2.0-0:amd64 (2.30.6-1) ...
Setting up libtumbler-1-0 (0.1.30-1) ...
Setting up systemd-shim (6-2bzr1) ...
Setting up gir1.2-gdkpixbuf-2.0 (2.30.6-1) ...
Setting up gnome-system-tools (3.0.0-3ubuntu4) ...
Setting up gnome-time-admin (3.0.0-3ubuntu4) ...
Setting up kerneloops-daemon (0.12+git20090217-3ubuntu6) ...
update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match kerneloops Default-Stop values (1)
Setting up tumbler-common (0.1.30-1) ...
Setting up tumbler (0.1.30-1) ...
Setting up xfburn (0.5.0-0ubuntu1) ...
Processing triggers for libc-bin (2.19-0ubuntu2) ...
brian@brian-Satellite-L775D:~$ sudo apt-get dist-uprade
E: Invalid operation dist-uprade
brian@brian-Satellite-L775D:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  linux-headers-3.13.0-5 linux-headers-3.13.0-5-generic
  linux-image-3.13.0-5-generic linux-image-extra-3.13.0-5-generic
  python-apport python-keyring python-launchpadlib python-lazr.restfulclient
  python-lazr.uri python-oauth python-problem-report python-secretstorage
  python-simplejson python-wadllib
Use 'apt-get autoremove' to remove them.
The following packages have been kept back:
  usb-modeswitch-data
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
brian@brian-Satellite-L775D:~$ apt-get autoremove
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
brian@brian-Satellite-L775D:~$ ubuntu-bug

(process:3318): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
brian@brian-Satellite-L775D:~$

This is my latest output from the terminal about 5 minutes ago before I posted this bug report.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.216
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: XFCE
Date: Wed Mar 12 08:50:18 2014
InstallationDate: Installed on 2014-03-08 (3 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Brian J Slease (javacat53) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Confirmed
Revision history for this message
unconfused (unconfused) wrote :

(gtk-update-icon-cache-3.0:12489): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

This likely means that your installation is broken.
Try running the command
  gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.

Revision history for this message
Brian J Slease (javacat53) wrote : Re: [Bug 1291355] Re: still having problems with upgrade/dist-upgrade, now the output on the terminal is saying some packages are missing and system? is broken and it it's fresh in stall an d no it's not a fresh install but a 4 day old re-install.

On 03/12/2014 12:28 PM, unconfused wrote:
> (gtk-update-icon-cache-3.0:12489): GdkPixbuf-WARNING **: Cannot open
> pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
> pixbuf-2.0/2.10.0/loaders.cache': No such file or directory
>
> This likely means that your installation is broken.
> Try running the command
> gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
> to make things work again for the time being.
>
Here is the outcome of the above:

brian@brian-Satellite-L775D:~$ sudo
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
[sudo] password for brian:
sudo: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache:
command not found
brian@brian-Satellite-L775D:~$

Brian

Revision history for this message
Manfred Hampl (m-hampl) wrote :

You messed up the command.

I recommend you try

gdk-pixbuf-query-loaders | sudo tee /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache

But make sure that you issue that as one command (by using copy/paste from https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1291355 and not by copying from your e-mail text).

Changed in ubuntu-release-upgrader (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Brian J Slease (javacat53) wrote :

What does this mean your 'Changed in status report?
Just curious since I sent this report in a week or so ago and I did what
Manfred said to do, it seems all is working fairly fine, a few hiccups
but start up, logon, seems to be okay. nothing else seems wrong at this
moment. your Status says Confirmed => Incomplete.

Again what does this mean to me?

Brian Slease.

On 03/17/2014 12:46 PM, Brian Murray wrote:
> ** Changed in: ubuntu-release-upgrader (Ubuntu)
> Status: Confirmed => Incomplete
>

Revision history for this message
Manfred Hampl (m-hampl) wrote :

@Brian: The status of a bug is usually set to 'Incomplete' if there is the need for further information to be provided by the person who has reported the bug.

In your case this is most probably due to your last comment telling "it seems all is working fairly fine...".
The question now is: Is there still something going wrong? And if it is, what exactly is not going the way you expect it to go?

Maybe reading http://www.chiark.greenend.org.uk/~sgtatham/bugs.html helps a bit in identifying what information you could provide to support effective work on this bug.

Revision history for this message
Brian J Slease (javacat53) wrote :

On 03/18/2014 03:15 AM, Manfred Hampl wrote:
> @Brian: The status of a bug is usually set to 'Incomplete' if there is
> the need for further information to be provided by the person who has
> reported the bug.
>
> In your case this is most probably due to your last comment telling "it seems all is working fairly fine...".
> The question now is: Is there still something going wrong? And if it is, what exactly is not going the way you expect it to go?
>
> Maybe reading http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
> helps a bit in identifying what information you could provide to support
> effective work on this bug.
>
The only thing that has happened once yesterday and twice today is that
when I turn on the computer in the morning and go to my xubuntu side
(!4.04) my cursor/pointer still gets 'frozen' when I'm trying to log on
with my password. The third time the cursor was almost 'frozen' but I
always use my finger to try to move it around to see if it's 'fozen'
everyday to 'unstick it' per se.

Everyday I update/upgrade through apt-get command and the updates are
many but the upgrades/dist-upgrades are getting not as many as there was
as of a week ago or less. I don't know if this is good or bad due to
the fact it's still in the pre-release stage. (Trusty Tahr/Xubuntu 14.04).

Manfred please let me know if this is a good or bad thing concerning the
lessor amounts of the upgrades or if this a normal thing as the launch
date gets closer to April 17th release date of this version. I'm
sticking though the whole thing.

Thank you
Brian Slease

Revision history for this message
Brian J Slease (javacat53) wrote :

On 03/18/2014 06:14 AM, Brian J Slease wrote:
>
> On 03/18/2014 03:15 AM, Manfred Hampl wrote:
>> @Brian: The status of a bug is usually set to 'Incomplete' if there is
>> the need for further information to be provided by the person who has
>> reported the bug.
>>
>> In your case this is most probably due to your last comment telling "it seems all is working fairly fine...".
>> The question now is: Is there still something going wrong? And if it is, what exactly is not going the way you expect it to go?
>>
>> Maybe readinghttp://www.chiark.greenend.org.uk/~sgtatham/bugs.html
>> helps a bit in identifying what information you could provide to support
>> effective work on this bug.
>>
> The only thing that has happened once yesterday and twice today is
> that when I turn on the computer in the morning and go to my xubuntu
> side (!4.04) my cursor/pointer still gets 'frozen' when I'm trying to
> log on with my password. The third time the cursor was almost
> 'frozen' but I always use my finger to try to move it around to see if
> it's 'fozen' everyday to 'unstick it' per se.
>
> Everyday I update/upgrade through apt-get command and the updates are
> many but the upgrades/dist-upgrades are getting not as many as there
> was as of a week ago or less. I don't know if this is good or bad due
> to the fact it's still in the pre-release stage. (Trusty Tahr/Xubuntu
> 14.04).
>
> Today, the 19th of March my updates went okay but upgrade for the
> first time in a week gave me a error report about some packages not
> being installed and asked me if I was 'root' again. I always am in
> 'root' or 'sudo'.

Brian Slease
>
>

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]

Changed in ubuntu-release-upgrader (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.