Still happening. Tried the apparmor fix but that didn't help.
Then found the line about skip-bdb and removed that and it fixed it.
--
package mysql-server-5.1 5.1.37-1ubuntu4 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
Still happening. Tried the apparmor fix but that didn't help.
Then found the line about skip-bdb and removed that and it fixed it.
--
package mysql-server-5.1 5.1.37-1ubuntu4 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
The most recent mysql 5.1 upgrade has caused this bug for the last few
weeks now. I've reported it now as aaport popped up and I remembered my
launchpad login.
I did try removing and reinstalling mysql but this didn't fix the issue,
as it's my development box I'm not too bothered. I'll try some
The most recent mysql 5.1 upgrade has caused this bug for the last few
weeks now. I've reported it now as aaport popped up and I remembered my
launchpad login.
I did try removing and reinstalling mysql but this didn't fix the issue,
as it's my development box I'm not too bothered. I'll try some
I can confirm installed from package manager, seg faulting when trying
to open a database. Also if booted with a default schema it seg faults
immediately. In both case I'm trying to connect to a network server.
Not got it set up with a local server yet so can't test it on that.
--
mySQL Query
Public bug reported:
Binary package hint: firefox
I'm running Ubuntu Edgy on my dev box, ran the upgrades this morning and now
firefox Seg Faults on boot.
I did the following:
[EMAIL PROTECTED]:~$ firefox --verbose
FIREFOX_DSP=
APPLICATION_ID=firefox
CMDLINE_DISPLAY=
DISPLAY=:0.0
OPTIONS=-a
Ok ignore the libmozjs.so bit, I think that's because the firefox script
isn't being used so the LD_LIBRARY_PATH isn't set. Problem is the
--verbose isn't being passed to firefox-bin and I can't find the core
dump anywhere.
Any ideas where to look? I've checked / ~/ and /usr/lib/firefox.
--
When I first booted the browser it reported two extension had been
updated, Colorzilla and Deepest Sender. Did some searching and found the
--safe-mode switch started in that and disabled extensions.
Re enabled all but Colorzilla and it's working fine so this extension
appears to be the issue.
