Author Topic: Error during setup aOpen as MD in 2.0.0.43  (Read 8078 times)

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Error during setup aOpen as MD in 2.0.0.43
« on: January 29, 2007, 09:35:55 pm »
I try to add aOpen mini PC as MD to the my Plutohome installation. It's detected but installation is freeze after some time. Here is a piece of PlutoInstallation.log:
Code: [Select]
The following NEW packages will be installed:
  pluto-mythtv-player
0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
Need to get 0B/1143kB of archives.
After unpacking 4465kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  pluto-mythtv-player
Authentication warning overridden.
Selecting previously deselected package pluto-mythtv-player.
(Reading database ... 27593 files and directories currently installed.)
Unpacking pluto-mythtv-player (from .../pluto-mythtv-player_2.0.0.43_i386.deb) ...
Setting up pluto-mythtv-player (2.0.0.43) ...
Restarting MythTV server: mythbackendNo /usr/bin/mythbackend found running; none killed.
.
.
Waiting 3 seconds so that myth backed is able to actually create the schema
Setting up mythtv configuration for this machine
mythbackend already running, use restart instead.
adduser: The group `public' does not exist.
dpkg: error processing pluto-mythtv-player (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 pluto-mythtv-player
E: Sub-process /usr/bin/dpkg returned an error code (1)
+ apt_err=100
+ [[ 100 != \0 ]]
+ apt-get -f -y install
Reading package lists...
Building dependency tree...
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Setting up pluto-mythtv-player (2.0.0.43) ...
ln: `/usr/lib/libXmu.so': File exists
Restarting MythTV server: mythbackendNo /usr/bin/mythbackend found running; none killed.
.
.
Waiting 3 seconds so that myth backed is able to actually create the schema
Removing old mythtv configuration for this machine
Setting up mythtv configuration for this machine
mythbackend already running, use restart instead.
adduser: The group `public' does not exist.
dpkg: error processing pluto-mythtv-player (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 pluto-mythtv-player
E: Sub-process /usr/bin/dpkg returned an error code (1)
+ apt-get -y --reinstall install pluto-mythtv-player
Reading package lists...
Building dependency tree...
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 4 not upgraded.
1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Setting up pluto-mythtv-player (2.0.0.43) ...
ln: `/usr/lib/libXmu.so': File exists
Restarting MythTV server: mythbackendNo /usr/bin/mythbackend found running; none killed.
.
.
Waiting 3 seconds so that myth backed is able to actually create the schema
Removing old mythtv configuration for this machine
Setting up mythtv configuration for this machine
mythbackend already running, use restart instead.
adduser: The group `public' does not exist.
dpkg: error processing pluto-mythtv-player (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 pluto-mythtv-player
E: Sub-process /usr/bin/dpkg returned an error code (1)
+ apt_err=100
+ [[ 100 != \0 ]]
+ echo 'Problem installing pluto-mythtv-player (100)'
+ exit 100
Problem installing pluto-mythtv-player (100)
***************************************************
***ERROR*** Processing of package 'Pluto MythTV Player' failed
***************************************************
Do you want to try again? [Y/n]:


Any help will be appreciated!

Also by some reason I cannot login to MD. It requests a password.

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Error during setup aOpen as MD in 2.0.0.43
« Reply #1 on: January 31, 2007, 04:13:53 pm »
after looking into your system, several scripts seem to have either not run or have been interrupted in the middle (they don't call 'exit' anywhere, so this situation is not possible).