UP4 dependency issues

[jan_goyvaerts]

Just writing to signal trouble for the update of UP4: There seems to be a dependency problem somewhere.

less /etc/apt/sources.list
deb http://packages.linuxmint.com/ debian main upstream import
deb http://debian.linuxmint.com/latest testing main contrib non-free
deb http://debian.linuxmint.com/latest/security testing/updates main contrib non-free
deb http://debian.linuxmint.com/latest/multimedia testing main non-free

# Added to install xvidcap
# deb http://www.debian-multimedia.org stable main non-free

# Google software repository
deb http://dl.google.com/linux/deb/ stable non-free main

# deb http://ftp.debian.org/debian unstable main contrib non-free
# deb-src http://ftp.debian.org/debian unstable main contrib non-free

sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
libgconf2-4 : Depends: libgconf-2-4 (= 3.2.3-3) but it is not installed
Depends: gconf-service but it is not installed
E: Unmet dependencies. Try using -f.

sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
gconf-defaults-service gconf-service gconf2 gconf2-common libgconf-2-4
The following NEW packages will be installed:
gconf-service libgconf-2-4
The following packages will be upgraded:
gconf-defaults-service gconf2 gconf2-common
3 upgraded, 2 newly installed, 0 to remove and 1015 not upgraded.
8 not fully installed or removed.
Need to get 0 B/3,658 kB of archives.
After this operation, 1,623 kB of additional disk space will be used.
Do you want to continue [Y/n]?
Reading changelogs... Done
Setting up initscripts (2.88dsf-22) ...
insserv: warning: script 'K01vmware' missing LSB tags and overrides
insserv: warning: script 'S50vmware-USBArbitrator' missing LSB tags and overrides
insserv: warning: script 'vmware-USBArbitrator' missing LSB tags and overrides
insserv: warning: script 'vmware' missing LSB tags and overrides
insserv: There is a loop at service rmnologin if started
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting vmware-USBArbitrator depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv: loop involving service portmap at depth 6
insserv: There is a loop between service rmnologin and mountnfs if started
insserv: loop involving service mountnfs at depth 7
insserv: loop involving service networking at depth 6
insserv: There is a loop between service rmnologin and mountall-bootclean if started
insserv: loop involving service mountall-bootclean at depth 6
insserv: loop involving service mountall at depth 5
insserv: There is a loop between service vmware-USBArbitrator and cryptdisks if started
insserv: loop involving service cryptdisks at depth 3
insserv: loop involving service cryptdisks-early at depth 2
insserv: loop involving service fuse at depth 12
insserv: There is a loop between service rmnologin and mountall if started
insserv: loop involving service checkfs at depth 8
insserv: There is a loop between service vmware-USBArbitrator and checkroot if started
insserv: loop involving service checkroot at depth 5
insserv: loop involving service hostname at depth 4
insserv: There is a loop between service rmnologin and ifupdown-clean if started
insserv: loop involving service ifupdown-clean at depth 6
insserv: There is a loop between service rmnologin and udev if started
insserv: loop involving service udev at depth 1
insserv: There is a loop at service vmware-USBArbitrator if started
insserv: loop involving service mountoverflowtmp at depth 11
insserv: There is a loop between service rmnologin and mountoverflowtmp if started
insserv: loop involving service mountdevsubfs at depth 3
insserv: loop involving service mountkernfs at depth 1
insserv: loop involving service vmware-USBArbitrator at depth 1
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing initscripts (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
initscripts
E: Sub-process /usr/bin/dpkg returned an error code (1)

Maybe it's related to the errors of apt-get update

W: Failed to fetch http://debian.linuxmint.com/latest/dist ... /InRelease

W: Failed to fetch http://debian.linuxmint.com/latest/secu ... /InRelease

W: Failed to fetch http://debian.linuxmint.com/latest/mult ... /InRelease

W: Failed to fetch http://debian.linuxmint.com/latest/dist ... elease.gpg Unable to connect to debian.linuxmint.com:http:

W: Failed to fetch http://debian.linuxmint.com/latest/secu ... elease.gpg Unable to connect to debian.linuxmint.com:http:

W: Failed to fetch http://debian.linuxmint.com/latest/mult ... elease.gpg Unable to connect to debian.linuxmint.com:http:

W: Some index files failed to download. They have been ignored, or old ones used instead.

[Paco]

Exactly same error here!

Although I could make the apt-get update complete, I have the same error with usbarbitrator. So there are many broken packages, some removed and waiting to install

I tried apt-get -f install, searched vmware in aptitude in order to delete it (no luck this time)...

Any clues?

Thanks in advance...

[jan_goyvaerts]

I guess we can't do anything else but wait for the dependencies to be fixed.

What is most annoying is that chrome doesn't work any more. It relies on libgconf. Which is missing now.

I hope the computer can still reboot safely...

[Paco]

I'm trying this solution

http://communities.vmware.com/thread/337769

Also find this thread, http://crunchbanglinux.org/forums/topic ... et-errors/ deactivating services. But I cannot install rcconf now.

I'll post the results...

[lmdeman]

AFAIK the vmware workstation 8.0.2 (player 4.0.2) installer borks the iniscripts system (version 7 (3) did not). I had similar problems trying to install a debian package which required to plug into the initscripts (can't remember which package). I solved by uninstalling vmware first, then completing the package installation. You may reinstall vmware when the system is fully updated. Note that vmware has its own installer so you will have to type something like:

Code: Select all

sudo vmware-installer --uninstall-product PRODUCT

Replace PRODUCT with your vmware product. You may list your products with:

Code: Select all

vmware-installer --list-products

Remember you will have to uninstall/reinstall vmware 8 each time you need to install/upgrade a package that requires initscripts, at least until they fix the installer bug.
I don't know which vmware product / version you have installed so the problem above may affect you or it may not.
The other problems are likely to be related to the server congestion, so i'd suggest to apt-get dist-upgrade only when the apt-get update completes succesfully.

Hope it helps.

[lmdeman]

@Paco
Sorry, didn't get your last post...
I'm glad you found it yourself.

[Paco]

well... I've tried the first solution I posted... seems to work but...

...I've lost emerald, compiz, mint-update, libreoffice (¿why?), gdm... buff!

apt-get update seems to work. Dist-upgrade says my system is up to date... So I think it's safer to remove vmware as you suggest.

Thanks!

[jan_goyvaerts]

I could make it work - sort of.

1. Uninstall vmware player

Code: Select all

sudo vmware-installer -u vmware-player

2. Force install

Code: Select all

sudo apt-get -f install

3. Regular update / upgrade

Code: Select all

sudo apt-get update
sudo apt-get upgrade

4. Reboot

5. Reinstall VMWare player

I had to specify my default terminal program and file manager though.

[zerozero]

...I've lost emerald, compiz, mint-update, libreoffice (¿why?), gdm... buff!

Dist-upgrade says my system is up to date...
Thanks!

Paco,
can you post the output of this command in your system

Code: Select all

amadeu@zerozero:~$ apt-cache policy libreoffice mintupdate-debian mintupdate gdm gdm3

as a reference here's on mine (on incoming that atm is exactly the same as latest)

Code: Select all

amadeu@zerozero:~$ apt-cache policy libreoffice mintupdate-debian mintupdate gdm gdm3
mintupdate-debian:
  Installed: 1.0.5
  Candidate: 1.0.5
  Version table:
 *** 1.0.5 0
        700 http://packages.linuxmint.com/ debian/main amd64 Packages
        100 /var/lib/dpkg/status
mintupdate:
  Installed: (none)
  Candidate: 4.3.3
  Version table:
     4.3.3 0
        700 http://packages.linuxmint.com/ debian/main amd64 Packages
gdm:
  Installed: (none)
  Candidate: (none)
  Version table:
gdm3:
  Installed: 3.0.4-4
  Candidate: 3.0.4-4
  Version table:
 *** 3.0.4-4 0
        500 http://debian.linuxmint.com/incoming/ testing/main amd64 Packages
        100 /var/lib/dpkg/status
libreoffice:
  Installed: 1:3.4.5-5
  Candidate: 1:3.4.5-5
  Version table:
 *** 1:3.4.5-5 0
        500 http://debian.linuxmint.com/incoming/ testing/main amd64 Packages
        100 /var/lib/dpkg/status
amadeu@zerozero:~$ 

[Paco]

apt-cache policy libreoffice mintupdate-debian mintupdate gdm gdm3

Code: Select all

mintupdate-debian:
  Instalados: 1.0.5
  Candidato:  1.0.5
  Tabla de versión:
 *** 1.0.5 0
        700 http://packages.linuxmint.com/ debian/main amd64 Packages
        100 /var/lib/dpkg/status
mintupdate:
  Instalados: (ninguno)
  Candidato:  4.3.3
  Tabla de versión:
     4.3.3 0
        700 http://packages.linuxmint.com/ debian/main amd64 Packages
gdm:
  Instalados: (ninguno)
  Candidato:  (ninguno)
  Tabla de versión:
gdm3:
  Instalados: 3.0.4-4
  Candidato:  3.0.4-4
  Tabla de versión:
 *** 3.0.4-4 0
        500 http://debian.linuxmint.com/latest/ testing/main amd64 Packages
        100 /var/lib/dpkg/status
libreoffice:
  Instalados: 1:3.4.5-5
  Candidato:  1:3.4.5-5
  Tabla de versión:
 *** 1:3.4.5-5 0
        500 http://debian.linuxmint.com/latest/ testing/main amd64 Packages
        100 /var/lib/dpkg/status

I've reinstalled all the apps, the only one that doesn't work is emerald (http://download.tuxfamily.org/shames/de ... /unstable/) and compiz gave me some problems, so I've deleted the two. Now I'm back with xfcwm4 and xfce composition for docky. It works nice...

[zerozero]

that output looks exactly like i was expecting it to look (now), if some of the apps was removed during the upgrade there was a glitch in your upgrade path (but not so serious because you could fix it)

also i see here in this topic a couple references about

Code: Select all

apt upgrade

in my opinion a release like lmde should/has to be maintained with

Code: Select all

apt dist-upgrade

[jan_goyvaerts]

Isn't LMDE supposed to be a single release; a non-stop stream of updates ?

That's why I would expect update/upgrade to do the trick.

What would be the difference then ?

[zerozero]

Isn't LMDE supposed to be a single release; a non-stop stream of updates ?

yes.

What would be the difference then ?

upgrade
Used to install the newest versions of all packages currently installed on the system from the sources enumerated in /etc/apt/sources.list(5). Packages currently installed with new versions available are retrieved and upgraded; under no circumstances are currently installed packages removed, nor are packages that are not already installed retrieved and installed. New versions of currently installed packages that cannot be upgraded without changing the install status of another package will be left at their current version. An update must be performed first so that apt-get knows that new versions of packages are available.

dist-upgrade
In addition to performing the function of upgrade, this option also intelligently handles changing dependencies with new versions of packages; apt-get has a "smart" conflict resolution system, and it will attempt to upgrade the most important packages at the expense of less important ones, if necessary.
The /etc/apt/sources.list(5) file contains a list of locations from
which to retrieve desired package files. See also apt_preferences(5) for a mechanism for over-riding the general settings for individual packages.

so basically, oversimplifying with upgrade you end up running in circles and loosing the train. only with dist-upgrade you can keep up with the pace.

[jan_goyvaerts]

Very well.

Thanks !