| 2009-12-15 05:56:02 |
quequotion |
bug |
|
|
added bug |
| 2010-02-25 17:45:09 |
quequotion |
attachment added |
|
xulrunner-1.9.1.postinst http://launchpadlibrarian.net/39784788/xulrunner-1.9.1.postinst |
|
| 2010-05-14 14:53:05 |
quequotion |
description |
Binary package hint: xulrunner-1.9.1
Excuse me for posting with such little technical detail, but there's a reason for that.
I made a botched attempt to partially upgrade from Jaunty to Karmic and then back down again.
Going both ways I ran into trouble with xulrunner-1.9.1.
I have also run into this problem on a clean install of Karmic while dist-upgrading.
Specifically, xulrunner never finishes installing... it gives a configuration message and stops there forever.
If I killall xulrunner-bin, the rest of the installation process goes on, but it breaks xulrunner, firefox, yelp, desktopcouch, and several other packages depending on what's installed at the time.
apport claims (at the end of dist-upgrade, after killing xulrunner-bin) that it will NOT log anything as this is the result of a "previous failure" of which I also find no logging.... this is interesting for me because I've never actually seen a message from apport appear while not using apport...
I have attempted to compensate by forced purge of xulrunner and all dependent packages, but that doesn't seem like a decent solution to me.
Which reminds me: xulrunner cannot be removed either, except by dpkg with --force-all. Otherwise it tries to configure itself to infinity again. |
Binary package hint: xulrunner-1.9.1, xulrunner-1.9.2
, xulrunner never finishes installing... it gives a configuration message and stops there forever.
If I killall xulrunner-bin, the rest of the installation process goes on, but it breaks xulrunner, firefox, yelp, desktopcouch, and several other packages depending on what's installed at the time.
apport claims (at the end of dist-upgrade, after killing xulrunner-bin) that it will NOT log anything as this is the result of a "previous failure" of which I also find no logging.... this is interesting for me because I've never actually seen a message from apport appear while not using apport...
I have attempted to compensate by forced purge of xulrunner and all dependent packages, but that doesn't seem like a decent solution to me.
Which reminds me: xulrunner cannot be removed either, except by dpkg with --force-all. Otherwise it tries to configure itself to infinity again.
|
|
| 2010-05-14 14:53:47 |
quequotion |
xulrunner-1.9.1 (Ubuntu): status |
New |
Confirmed |
|
| 2010-05-14 14:54:48 |
quequotion |
description |
Binary package hint: xulrunner-1.9.1, xulrunner-1.9.2
, xulrunner never finishes installing... it gives a configuration message and stops there forever.
If I killall xulrunner-bin, the rest of the installation process goes on, but it breaks xulrunner, firefox, yelp, desktopcouch, and several other packages depending on what's installed at the time.
apport claims (at the end of dist-upgrade, after killing xulrunner-bin) that it will NOT log anything as this is the result of a "previous failure" of which I also find no logging.... this is interesting for me because I've never actually seen a message from apport appear while not using apport...
I have attempted to compensate by forced purge of xulrunner and all dependent packages, but that doesn't seem like a decent solution to me.
Which reminds me: xulrunner cannot be removed either, except by dpkg with --force-all. Otherwise it tries to configure itself to infinity again.
|
Binary package hint: xulrunner-1.9.1, xulrunner-1.9.2
xulrunner never finishes installing... it gives a configuration message and stops there forever.
If I killall xulrunner-bin, the rest of the installation process goes on, but it breaks xulrunner, firefox, yelp, desktopcouch, and several other packages depending on what's installed at the time.
apport claims (at the end of dist-upgrade, after killing xulrunner-bin) that it will NOT log anything as this is the result of a "previous failure" of which I also find no logging.... this is interesting for me because I've never actually seen a message from apport appear while not using apport...
I have attempted to compensate by forced purge of xulrunner and all dependent packages, but that doesn't seem like a decent solution to me.
Which reminds me: xulrunner cannot be removed either, except by dpkg with --force-all. Otherwise it tries to configure itself to infinity again.
|
|
