Public bug reported:
Binary package hint: sendpage-server
When installing the sendpage-server package ('apt-get install
sendpage-server'), the configuration process attempts to start the
sendpage-server service. This process hangs after producing the output below:
[EMAIL PROTECTED]:~/web_tap_support# apt-get install sendpage-server
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
sendpage-server
0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
Need to get 0B/23.0kB of archives.
After unpacking 143kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously deselected package sendpage-server.
(Reading database ... 72700 files and directories currently installed.)
Unpacking sendpage-server (from .../sendpage-server_0.9.14-5_all.deb) ...
Setting up sendpage-server (0.9.14-5) ...
Starting Sendpage: (18090: alert) Cannot initialize modem 'default'
(18090: alert) no functioning modems!
sendpage.
It stays like this until ctrl-c is pressed, after which it produces:
dpkg: error processing sendpage-server (--configure):
subprocess post-installation script killed by signal (Interrupt)
Errors were encountered while processing:
sendpage-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
This error happens (I think) because there's a section in the default config
file /etc/sendpage/sendpage.cf called [modem:default] saying there's a modem on
/dev/ttyS0, which is not the case on my system. Perhaps the default config
file should not include default setting. I don't think sendpage should be
started until some modems have been defined by the user.
** Affects: sendpage (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
/etc/init.d/sendpage-server fails to start as part of install config process
https://launchpad.net/bugs/62807
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
