[Bug 608953] [NEW] package seamonkey-browser 1.1.17 nobinonly-0ubuntu1 failed to install/upgrade:

2010-07-22 Thread Ken McCoy
Public bug reported: Binary package hint: seamonkey upgrade to Ubuntu 9.04 from 8.10 consistent errors for seamonkey firefox w/synaptic upgrade mgr ProblemType: Package Architecture: i386 Date: Thu Jul 22 18:33:48 2010 DistroRelease: Ubuntu 9.10 ErrorMessage: ErrorMessage: subprocess

[Bug 608953] Re: package seamonkey-browser 1.1.17 nobinonly-0ubuntu1 failed to install/upgrade:

2010-07-22 Thread Ken McCoy
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/52337881/Dependencies.txt ** Attachment added: VarLogDistupgradeAptlog.gz http://launchpadlibrarian.net/52337882/VarLogDistupgradeAptlog.gz ** Attachment added: VarLogDistupgradeApttermlog.gz

[Bug 591737] [NEW] package firefox-3.5 3.5.9 nobinonly-0ubuntu0.9.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2010-06-09 Thread Ken McCoy
Public bug reported: Binary package hint: firefox-3.5 Ubuntu 9.10 upgraded through synaptic Failed to upgrade Firefox or SeaMonkey; I receive the same or similar error on subsequent synaptic updates ProblemType: Package Architecture: i386 Date: Wed Jun 9 09:19:32 2010 DistroRelease: Ubuntu

[Bug 591737] Re: package firefox-3.5 3.5.9 nobinonly-0ubuntu0.9.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2010-06-09 Thread Ken McCoy
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/50012446/Dependencies.txt ** Attachment added: Dmesg.txt http://launchpadlibrarian.net/50012447/Dmesg.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/50012448/DpkgTerminalLog.txt **

Re: [Bug 591737] Re: package firefox-3.5 3.5.9 nobinonly-0ubuntu0.9.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2010-10-08 Thread Ken McCoy
OK, thanks! On 10/08/2010 11:41 AM, Jean-Baptiste Lallement wrote: We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to