UPDATE PACK 2 FEEDBACK THREAD

deb http://debian.linuxmint.com/incoming testing main contrib non-free
deb-src http://debian.linuxmint.com/incoming testing main contrib non-free
Forum rules
Before you post please read this

UPDATE PACK 2 FEEDBACK THREAD

Postby clem on Thu Jul 21, 2011 4:02 am

Update Pack 2 is being prepared and will make its way to incoming some time today. Stay tuned ;)

Rules:

- This thread is for users of the Linux Mint Debian Incoming repository only (deb http://debian.linuxmint.com/incoming testing main contrib non-free).
- This thread is for users of the Linux Mint Debian Incoming repository to report problems to the team, so that the team can relay them towards all LMDE users via the Update Manager.
- If you're pointing to the Debian repositories, do not post in here.
- If you're looking for support, answers or information, do not post in here.

When posting about a regression or tricky upgrade, please include the following:

- The package update which is problematic.
- If you can, analyse the cause of the problem and why it is happening.
- If you solved it or found a workaround, please post it as well.
- Include any information you think might help the team solve the problem for others, or that might help others to work around the problem.

Any post not following these rules will be deleted.

The Update Pack repositories were created to help people help each others identify regressions coming from Debian Testing and to give the team the opportunity to fix things at regular intervals. I'd like to thank all the people who will somehow act as guinea pigs while using the Incoming update-packs and thanks to whom users of the Latest update-packs will have an easier life.

Thanks for choosing Mint and thanks for helping out!
Image
User avatar
clem
Level 15
Level 15
 
Posts: 5545
Joined: Wed Nov 15, 2006 8:34 am

Linux Mint is funded by ads and donations.
 

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby clem on Thu Jul 21, 2011 5:16 am

Update Pack 2 is now live in Incoming. 244 updates available.
Image
User avatar
clem
Level 15
Level 15
 
Posts: 5545
Joined: Wed Nov 15, 2006 8:34 am

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby mfs on Fri Jul 22, 2011 4:34 am

Hi,

installation of update pack 2 worked without glitches. I've got 2 remarks:

- The issue concerning xserver and nvidia drivers is gone. So people should remove holds from the xserver packages to upgrade them.
- The issue with ugly-looking gtk3 apps like gnome-terminal and gcalctool still persists. So these holds should be kept. Alternatively, you could put the last 2.32 version of gnome-terminal and gcalctool into the repo and wait for better gnome3 support in debian testing.

mfs.
User avatar
mfs
Level 1
Level 1
 
Posts: 32
Joined: Wed Jul 21, 2010 1:44 pm

Re: UPDATE PACK 2

Postby ntdevman on Fri Jul 22, 2011 10:29 am

The installation succeded on my 64 bit Debian system (HP Pavilion dv6 laptop) , but the following errors and warnings were generated in the process:

Unpacking replacement libpng12-0 ...
Preparing to replace libcomerr2 1.41.12-4stable1 (using .../libcomerr2_1.42~WIP-2011-07-02-1_amd64.deb) ...
Unpacking replacement libcomerr2 ...
Processing triggers for doc-base ...
Processing 1 changed doc-base file...
Error in `/usr/share/doc-base/libpng12', line 25: all `Format' sections are invalid.
Note: `install-docs --verbose --check file_name' may give more details about the above error.
Registering documents with scrollkeeper...

Setting up microcode.ctl (1.17-13.1) ...
Local version: (none)
Remote version: 20110428
Downloading a new version of microcode.
microcode downloaded sucessfully
Applying Intel IA32 Microcode update... done.
update-rc.d: warning: microcode.ctl start runlevel arguments (S) do not match LSB Default-Start values (2 3 4 5)
update-rc.d: warning: microcode.ctl stop runlevel arguments (none) do not match LSB Default-Stop values (0 1 6)
Applying Intel IA32 Microcode update... done.

Installation finished. No error reported.

/usr/sbin/grub-setup: warn: Attempting to install GRUB to a partitionless disk or to a partition. This is a BAD idea..
/usr/sbin/grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
Installation finished. No error reported.

The update pack may want to mention that the Grub update may give this warning if you at some point told the original install to put Grub on "all" avai;able partitions. As for the libpng12, I'm npt sure what the cause or ramifications are, if any.

Keep up the good work.
ntdevman
Level 1
Level 1
 
Posts: 4
Joined: Sat Dec 26, 2009 4:01 pm

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby Fornhamfred on Fri Jul 22, 2011 11:33 am

Installed update with no problems but when trying to edit my grub.cfg file after any alteration the next boot screen shows only the latest lmde entry. No other versions of Mint or windows. Checking the file and it all seems OK. If I run update-grub again then all entries once again appear on the boot screen.

This is my file which excludes any other distro entries.
### BEGIN /etc/grub.d/10_linux ###
menuentry 'LinuxMint GNU/Linux, with Linux 2.6.39-2-686-pae' --class linuxmint --class gnu-linux --class gnu --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 52b4e4c5-e17e-43e8-a74e-1be130bf664d
echo 'Loading Linux 2.6.39-2-686-pae ...'
linux /boot/vmlinuz-2.6.39-2-686-pae root=UUID=52b4e4c5-e17e-43e8-a74e-1be130bf664d ro vga=792 splash quiet quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.39-2-686-pae
}
menuentry 'LinuxMint GNU/Linux, with Linux 2.6.39-2-686-pae (recovery mode)' --class linuxmint --class gnu-linux --class gnu --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 52b4e4c5-e17e-43e8-a74e-1be130bf664d
echo 'Loading Linux 2.6.39-2-686-pae ...'
linux /boot/vmlinuz-2.6.39-2-686-pae root=UUID=52b4e4c5-e17e-43e8-a74e-1be130bf664d ro single vga=792 splash quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.39-2-686-pae
}
menuentry 'LinuxMint GNU/Linux, with Linux 2.6.38-2-686' --class linuxmint --class gnu-linux --class gnu --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 52b4e4c5-e17e-43e8-a74e-1be130bf664d
echo 'Loading Linux 2.6.38-2-686 ...'
linux /boot/vmlinuz-2.6.38-2-686 root=UUID=52b4e4c5-e17e-43e8-a74e-1be130bf664d ro vga=792 splash quiet quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-2-686
}
menuentry 'LinuxMint GNU/Linux, with Linux 2.6.38-2-686 (recovery mode)' --class linuxmint --class gnu-linux --class gnu --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 52b4e4c5-e17e-43e8-a74e-1be130bf664d
echo 'Loading Linux 2.6.38-2-686 ...'
linux /boot/vmlinuz-2.6.38-2-686 root=UUID=52b4e4c5-e17e-43e8-a74e-1be130bf664d ro single vga=792 splash quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-2-686
}
menuentry 'LinuxMint GNU/Linux, with Linux 2.6.32-5-686' --class linuxmint --class gnu-linux --class gnu --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 52b4e4c5-e17e-43e8-a74e-1be130bf664d
echo 'Loading Linux 2.6.32-5-686 ...'
linux /boot/vmlinuz-2.6.32-5-686 root=UUID=52b4e4c5-e17e-43e8-a74e-1be130bf664d ro vga=792 splash quiet quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-686
}
menuentry 'LinuxMint GNU/Linux, with Linux 2.6.32-5-686 (recovery mode)' --class linuxmint --class gnu-linux --class gnu --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 52b4e4c5-e17e-43e8-a74e-1be130bf664d
echo 'Loading Linux 2.6.32-5-686 ...'
linux /boot/vmlinuz-2.6.32-5-686 root=UUID=52b4e4c5-e17e-43e8-a74e-1be130bf664d ro single vga=792 splash quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-686
}
### END /etc/grub.d/10_linux ###

Previously I have edited out the entries for the old kernels but if I do this I get the problem above. Deleting out the other distro entries does not cause the problem and the boot screen shows the entries as the file.


My system is a Dell Optilex 170L Pentium4 with Integrated Intel graphics and 1GB Ram
Fornhamfred
Level 6
Level 6
 
Posts: 1134
Joined: Wed Oct 31, 2007 3:38 pm
Location: Suffolk UK

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby lleiria on Fri Jul 22, 2011 8:58 pm

I updated my system with pack 2. Everything seems to be running well, but I received a lot (!!) of error messages:

Code: Select all
 facility `$all' which can not be true!

insserv:  loop involving service bootlogd at depth 4

insserv:  loop involving service samba at depth 12

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: There is a loop between service pcloudd_init and ifupdown-clean if started

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv:  loop involving service networking at depth 10

insserv: There is a loop between service plymouth and bootlogd if started

insserv: There is a loop between service pcloudd_init and mountall-bootclean if started

insserv:  loop involving service mountall-bootclean at depth 1

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: exiting now without changing boot order!

update-rc.d: error: insserv rejected the script header

dpkg: erro ao processar udev (--configure):

 subprocesso script post-installation instalado retornou erro do status de saída 1

A instalar exim4-base (4.76-2) ...

insserv: warning: script 'S99pcloudd_init' missing LSB tags and overrides

insserv: warning: script 'pcloudd_init_start' missing LSB tags and overrides

insserv: warning: script 'pcloudd_init' missing LSB tags and overrides

insserv: script pcloudd_init: service pcloudd_init already provided!

insserv: There is a loop at service pcloudd_init if started

insserv: There is a loop between service plymouth and checkroot if started

insserv:  loop involving service checkroot at depth 3

insserv:  loop involving service keyboard-setup at depth 2

insserv:  loop involving service hwclock at depth 6

insserv:  loop involving service hostname at depth 4

insserv: There is a loop between service plymouth and mountnfs if started

insserv:  loop involving service mountnfs at depth 10

insserv:  loop involving service portmap at depth 9

insserv: There is a loop between service plymouth and ifupdown if started

insserv:  loop involving service ifupdown at depth 7

insserv:  loop involving service ifupdown-clean at depth 6

insserv:  loop involving service mountnfs-bootclean at depth 12

insserv: There is a loop between service plymouth and mountall if started

insserv:  loop involving service mountall at depth 8

insserv:  loop involving service checkfs at depth 7

insserv:  loop involving service mtab at depth 6

insserv:  loop involving service module-init-tools at depth 6

insserv: There is a loop between service pcloudd_init and mountdevsubfs if started

insserv:  loop involving service mountdevsubfs at depth 2

insserv:  loop involving service udev at depth 1

insserv: There is a loop at service plymouth if started

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Max recursions depth 99 reached

insserv:  loop involving service vboxweb-service at depth 1

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv:  loop involving service bootlogd at depth 4

insserv:  loop involving service samba at depth 12

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: There is a loop between service pcloudd_init and ifupdown-clean if started

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv:  loop involving service networking at depth 10

insserv: There is a loop between service plymouth and bootlogd if started

insserv: There is a loop between service pcloudd_init and mountall-bootclean if started

insserv:  loop involving service mountall-bootclean at depth 1

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting pcloudd_init_start depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: exiting now without changing boot order!

update-rc.d: error: insserv rejected the script header

dpkg: erro ao processar exim4-base (--configure):

 subprocesso script post-installation instalado retornou erro do status de saída 1

dpkg: problemas com dependências impedem a configuração de avahi-daemon:

 avahi-daemon depende de dbus (>= 0.60); no entanto:

 O pacote dbus ainda não está configurado.

dpkg: erro ao processar avahi-daemon (--configure):

 problemas com dependências - a deixar por configurar

dpkg: problemas com dependências impedem a configuração de pulseaudio:

 pulseaudio depende de udev (>= 143); no entanto:

 O pacote udev ainda não está configurado.

dpkg: erro ao processar pulseaudio (--configure):

 problemas com dependências - a deixar por configurar

dpkg: problemas com dependências impedem a configuração de upower:

 upower depende de udev; no entanto:

 O pacote udev ainda não está configurado.

 upower depende de dbus; no entanto:

 O pacote dbus ainda não está configurado.

dpkg: erro ao processar upower (--configure):

 problemas com dependências - a deixar por configurar

dpkg: problemas com dependências impedem a configuração de libsane:

 libsane depende de udev (>= 0.88-1) | makedev (>= 2.3.1-58); no entanto:

 O pacote udev ainda não está configurado.

  O pacote makedev não está instalado.

dpkg: erro ao processar libsane (--configure):

 problemas com dependências - a deixar por configurar

dpkg: problemas com dependências impedem a configuração de pulseaudio-module-x11:

 pulseaudio-module-x11 depende de pulseaudio; no entanto:

 O pacote pulseaudio ainda não está configurado.

dpkg: erro ao processar pulseaudio-module-x11 (--configure):

 problemas com dependências - a deixar por configurar

dpkg: problemas com dependências impedem a configuração de pulseaudio-module-gconf:

 pulseaudio-module-gconf depende de pulseaudio; no entanto:

 O pacote pulseaudio ainda não está configurado.

dpkg: erro ao processar pulseaudio-module-gconf (--configure):

 problemas com dependências - a deixar por configurar

dpkg: problemas com dependências impedem a configuração de xserver-xorg-core:

 xserver-xorg-core depende de udev (>= 149); no entanto:

 O pacote udev ainda não está configurado.

dpkg: erro ao processar xserver-xorg-core (--configure):

 problemas com dependências - a deixar por configurar

dpkg: problemas com dependências impedem a configuração de exim4-daemon-light:

 exim4-daemon-light depende de exim4-base (>= 4.76); no entanto:

 O pacote exim4-base ainda não está configurado.

dpkg: erro ao processar exim4-daemon-light (--configure):

 problemas com dependências - a deixar por configurar

dpkg: problemas com dependências impedem a configuração de xserver-xorg-input-synaptics:

 xserver-xorg-input-synaptics depende de xorg-input-abi-12; no entanto:

  O pacote xorg-input-abi-12 não está instalado.

  O pacote xserver-xorg-core que disponibiliza xorg-input-abi-12 ainda não está configurado.

 xserver-xorg-input-synaptics depende de xserver-xorg-core (>= 2:1.9.99.903); no entanto:

 O pacote xserver-xorg-core ainda não está configurado.

dpkg: erro ao processar xserver-xorg-input-synaptics (--configure):

 problemas com dependências - a deixar por configurar

dpkg: problemas com dependências impedem a configuração de python-imaging-sane:

 python-imaging-sane depende de libsane (>= 1.0.11-3); no entanto:

 O pacote libsane ainda não está configurado.

dpkg: erro ao processar python-imaging-sane (--configure):

 problemas com dependências - a deixar por configurar

dpkg: problemas com dependências impedem a configuração de pulseaudio-module-zeroconf:

 pulseaudio-module-zeroconf depende de pulseaudio; no entanto:

 O pacote pulseaudio ainda não está configurado.

dpkg: erro ao processar pulseaudio-module-zeroconf (--configure):

 problemas com dependências - a deixar por configurar

dpkg: problemas com dependências impedem a configuração de pulseaudio-esound-compat:

 pulseaudio-esound-compat depende de pulseaudio; no entanto:

 O pacote pulseaudio ainda não está configurado.

dpkg: erro ao processar pulseaudio-esound-compat (--configure):

 problemas com dependências - a deixar por configurar

dpkg: problemas com dependências impedem a configuração de hplip:

 hplip depende de libsane (>= 1.0.11-3); no entanto:

 O pacote libsane ainda não está configurado.

dpkg: erro ao processar hplip (--configure):

 problemas com dependências - a deixar por configurar

dpkg: problemas com dependências impedem a configuração de sane-utils:

 sane-utils depende de libsane (>= 1.0.11-3); no entanto:

 O pacote libsane ainda não está configurado.

dpkg: erro ao processar sane-utils (--configure):

 problemas com dependências - a deixar por configurar

A processar 'triggers' para initramfs-tools ...

update-initramfs: Generating /boot/initrd.img-2.6.39-3.dmz.2-liquorix-686

Foram encontrados erros enquanto processava:

 binfmt-support

 dbus

 udisks

 at

 dbus-x11

 hplip-gui

 udev

 exim4-base

 avahi-daemon

 pulseaudio

 upower

 libsane

 pulseaudio-module-x11

 pulseaudio-module-gconf

 xserver-xorg-core

 exim4-daemon-light

 xserver-xorg-input-synaptics

 python-imaging-sane

 pulseaudio-module-zeroconf

 pulseaudio-esound-compat

 hplip

 sane-utils

lleiria@pc-principal ~ $

Some messages are in portuguese, sorry :-)

LMDE 32 bits, liquorix kernel, desktop computer with intel core 2 duo processor, 3 GB ram, Intel graphic card.
I don't understand what is wrong, maybe you can help?
Image
lleiria
Level 2
Level 2
 
Posts: 63
Joined: Sun Nov 07, 2010 2:07 pm

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby scottlinux on Fri Jul 22, 2011 10:15 pm

64bit, no issues other than I had to issue sudo apt-get dist-upgrade from the terminal. (Or is this expected?)

Using nvidia-glx and nvidia-kernel-dkms - all is well! Thanks,
scottlinux
Level 1
Level 1
 
Posts: 27
Joined: Sun May 15, 2011 12:00 am

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby leonidas on Sat Jul 23, 2011 3:31 am

Applied update pack 2 and everything is alright here.

Only one small thing:

The new LMDE-Updater (mintupdate-debian) shows the update-pack information, i.e. the number of the newest update pack available and the number of the latest update pack used by the system.
The latter does not increase if you apply the update pack not by the updater itself, but by the terminal, using apt-get.

For example here i have LMDE XFCE 64bit with activated "incoming" repo. Yesterday (2011.07.22) i dared to apply all updates by apt-get dist-upgrade (i did it even though there is not yet any information about update pack 2 in the update pack info, and my system runs as stable as before). The updater now still shows: "Latest Update Pack used by this system: 1".
Last edited by leonidas on Sat Jul 23, 2011 4:31 pm, edited 3 times in total.
leonidas
Level 1
Level 1
 
Posts: 1
Joined: Sat Jul 23, 2011 3:27 am

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby asermax on Sat Jul 23, 2011 4:33 am

The gdebi (and gdebi-core) update from this update pack have the same problem that gcalc and system-monitor, it regress to an uglier interface.
I had to downgrade it back to the debian-stable repository version 0.6.4 to get the minty look back.

Also, althought i'm not completly sure if it's related to this update pack (but i suspect it's), i found that the path to the library libnss3.so is not properly configured into the openjdk nss.cfg file. I discovered this when I ran into an error when trying to start the JDownloader java app.
To solve this problem, you have to edit the file /etc/java-6-openjdk/security/nss.cfg, replacing the line that says "nssLibraryDirectory = /usr/lib" for "nssLibraryDirectory = /usr/lib/i386-linux-gnu" ( or "nssLibraryDirectory = /usr/lib/x86_64-linux-gnu" for x64 ). -> Credits to http://www.unnaki.com/2011/07/libnss3-so-error-on-debian-wheezy/

Other than that, the updates seems to be very safe :]

I'm running LMDE x64 with the lastest Liquorix kernel (2.6.39-3.dmz.2-liquorix-amd64)
asermax
Level 1
Level 1
 
Posts: 14
Joined: Mon Jun 27, 2011 9:31 pm
Location: Córdoba, Argentina

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby Elmacus on Sat Jul 23, 2011 9:21 am

Have been running update pack 2 on 64 bit, not a single problem to report yet.
LMDE 64 bit. Use my advices on your own risk, it might be wrong on your system.
Laptop LMDE SID, Desktop home LMDE Testing, Desktop work LMDE UP4.
"If you can't apt-get something, it isn't useful or doesn't exist"
User avatar
Elmacus
Level 2
Level 2
 
Posts: 60
Joined: Mon Mar 07, 2011 9:44 am

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby rkdb on Sat Jul 23, 2011 12:36 pm

Same here, 32 bit.
Good work!
User avatar
rkdb
Level 1
Level 1
 
Posts: 7
Joined: Sat Jul 23, 2011 12:31 pm

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby Paco on Sat Jul 23, 2011 1:57 pm

64bits and with the nvidia drivers from testing: some nvidia packages get updated:

ALL OK !

System: Kernel 2.6.39-3.dmz.2-liquorix-amd64 x86_64 (64 bit) Distro Linux Mint Debian Edition
CPU: Dual core AMD Athlon 64 X2 6000+ (-MCP-) cache 2048 KB flags (lm nx sse sse2 sse3 svm) bmips 3999.18
Clock Speeds: (1) 1000.00 MHz (2) 1000.00 MHz
Graphics: Card nVidia GT216 [GeForce GT 220] X.Org 1.10.2.902 Res: 2304x1024@50.0hz
GLX Renderer GeForce GT 220/PCI/SSE2 GLX Version 3.3.0 NVIDIA 275.09.07 Direct Rendering Yes
Audio: Card-1 nVidia High Definition Audio Controller driver HDA Intel BusID: 02:00.1
Card-2 VIA VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) driver HDA Intel BusID: 80:01.0
Sound: Advanced Linux Sound Architecture Version 1.0.24
Network: Card Atheros L1 Gigabit Ethernet driver atl1 v: 2.1.3 BusID: 04:00.0
Disks: HDD Total Size: 1000.2GB (79.8% used) 1: /dev/sda WDC_WD5000AAKS 500.1GB
2: /dev/sdb SAMSUNG_HD501LJ 500.1GB
Partition: ID:/ size: 28G used: 11G (41%) fs: ext4 ID:/home size: 136G used: 107G (83%) fs: ext4
ID:/boot size: 461M used: 109M (25%) fs: ext4 ID:swap-1 size: 10.00GB used: 0.00GB (0%) fs: swap
Sensors: System Temperatures: cpu: 36.0C mobo: 39.0C gpu: 0.0:56C
Fan Speeds (in rpm): cpu: 3096 sys-1: 0 sys-2: 0
Info: Processes 159 Uptime 8 min Memory 743.4/3963.6MB Runlevel 2 Client Shell inxi 1.4.23
Paco
Level 1
Level 1
 
Posts: 22
Joined: Thu Feb 24, 2011 5:09 am

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby andrew5859 on Sun Jul 24, 2011 1:42 am

I'm noticing on really wierd intervals, that my laptop will freeze for about a minute or so, especially while posting in the forums. This has happened after implimenting update pack 2.....the blinking cursor will disappear and nothing will move. Not sure what's causing this.



Cheers
Andrew
Dell Latitude D810/2.26Ghz Intel/2GB Crucial/250GB WD/nVidia Quadro FX 1400 256MB/Intel Pro Wireless 2200BG
Win7 Bus 32 bit/LMDE-Sid-MATE 32/64 Tracking Sid


Image
User avatar
andrew5859
Level 4
Level 4
 
Posts: 418
Joined: Fri Mar 26, 2010 12:58 pm
Location: Boardman, Ohio USA

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby clem on Sun Jul 24, 2011 4:06 am

Update Pack 2 is now available in latest.
Image
User avatar
clem
Level 15
Level 15
 
Posts: 5545
Joined: Wed Nov 15, 2006 8:34 am

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby secipolla on Sun Jul 24, 2011 10:17 am

mfs wrote:- The issue with ugly-looking gtk3 apps like gnome-terminal and gcalctool still persists. So these holds should be kept. Alternatively, you could put the last 2.32 version of gnome-terminal and gcalctool into the repo and wait for better gnome3 support in debian testing.

I'm not using LMDE but it looks to me that such a "solution" is (very much) worse than the problem itself.
If you have gnome-themes-standard installed you could use the Adwaita theme or just try to create a gtk3 folder for the theme you're using (cp from the Adwaita folder and tweak as needed).
secipolla
Level 4
Level 4
 
Posts: 356
Joined: Sun Sep 05, 2010 5:19 pm

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby kwisher on Sun Jul 24, 2011 12:40 pm

So far my 32-bit system that has been installed long before the new Update Packs came to be is running fine with no update problems since enabling the new repo's.

Just did a fresh 32-bit install on a Dell laptop yesterday. After the initial install, I enabled the new repos after the first reboot. I then did a dist-updrade. When rebooting after the upgrade I was not able to access the GUI desktop. Rebooted into a recovery console and did a "apt-get -f install" to finish installing. Rebooted and GUI desktop was then accessible. Opened a terminal and did a dist-upgrade again. Rebooted and was now running fine with all the latest updates. Can't wait until the new ISO's become available. :D

One thing I did notice is that the "Login Screen" app will not allow you to unlock it to make changes. I even tried starting it with gksu and still no luck. The same problem is present on my system. I wanted to change the new install on the Dell laptop to auto login as this system will be used by an elderly couple.
The instructions suggested Windows XP or better, so I installed Linux :)
User avatar
kwisher
Level 5
Level 5
 
Posts: 635
Joined: Wed Mar 05, 2008 12:54 pm
Location: Greentown, Indiana USA

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby wyrdoak on Sun Jul 24, 2011 1:03 pm

gksu gedit /etc/gdm3/daemon.conf

and underneath
[daemon]
Add the next lines:
CODE: SELECT ALL
[daemon]
AutomaticLoginEnable=true
AutomaticLogin=username


change username to the username used for logon.
-Dell Mini Netbook-Atom CPU-N270-1.60ghz; 16gbs mini ePCI PATA SSD
RAM- 1gbs-(Maya-Xfce) LInux 3.2.0.57-generic(i686)
SolydX (32bit)
User avatar
wyrdoak
Level 6
Level 6
 
Posts: 1313
Joined: Thu May 19, 2011 1:32 pm
Location: USA

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby phs on Tue Jul 26, 2011 12:33 pm

lost touchpad tapping after upgrade to Update Pack 2
using ThinkPad T61

EDIT
fixed tapping using tutorial here --
http://community.linuxmint.com/tutorial/view/424
phs
Level 1
Level 1
 
Posts: 1
Joined: Tue Jul 26, 2011 12:27 pm

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby m4daredsun on Fri Jul 29, 2011 12:48 pm

I recently to make my LMDE point to incoming. I updated from command and therefore applied all updates.

Now major problem so far, but I do have the issue with some apps looking ugly (gnome system monitor, terminal, gdebi).

Is there a simple way to revert back these applications to some older version?
The only limiting factor of the Linux operating system is its user - Linus Torvalds
User avatar
m4daredsun
Level 2
Level 2
 
Posts: 83
Joined: Thu Mar 04, 2010 5:31 pm

Re: UPDATE PACK 2 FEEDBACK THREAD

Postby dbkblk on Sat Jul 30, 2011 9:39 am

About the GTK3 theme problem, i might say something stupid but why don't anyone create a GTK3 theme of Mint-X ? With a gtk2 and a gtk3 folder, the gnome 3 parts could at least be integrated with the default theme !
dbkblk
Level 1
Level 1
 
Posts: 32
Joined: Thu Dec 16, 2010 10:31 am

Linux Mint is funded by ads and donations.
 
Next

Return to Linux Mint Debian Incoming

Who is online

Users browsing this forum: No registered users and 1 guest