I installed the new firefox 1.5.0.5 packages and had a few issues. I had read a similar post on the nahant list. I would doubt that this is a centos-induced problem. The browser crashed when opening the extensions manager and also with a very simple webmail page. I have reverted to the firefox 1.0.8 packages and these problems have disappeared.
On 7/29/06, Barry Brimer lists@brimer.org wrote:
I installed the new firefox 1.5.0.5 packages and had a few issues. I had read a similar post on the nahant list. I would doubt that this is a centos-induced problem. The browser crashed when opening the extensions manager and also with a very simple webmail page.
If you upgraded directly from 1.0.8 to to 1.5.0.5, you probably need to reinstall all of your extensions. I recommend (1) write down what all of them are, (2) uninstall them all from your present firefox 1.0.8, (3) upgrade to 1.5.0.5, and finally (4) install extensions again.
Even upgrading from 1.5.0.2 (centosplus) to 1.5.0.5, I'd recommend reinstalling extensions. In my experience firefox always crashes on the first -- and sometimes also second and third -- launches after an upgrade when there are any extensions present.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, Jul 29, 2006 at 08:09:30PM -0700, Bart Schaefer wrote:
On 7/29/06, Barry Brimer lists@brimer.org wrote:
I installed the new firefox 1.5.0.5 packages and had a few issues. I had read a similar post on the nahant list. I would doubt that this is a centos-induced problem. The browser crashed when opening the extensions manager and also with a very simple webmail page.
If you upgraded directly from 1.0.8 to to 1.5.0.5, you probably need to reinstall all of your extensions. I recommend (1) write down what all of them are, (2) uninstall them all from your present firefox 1.0.8, (3) upgrade to 1.5.0.5, and finally (4) install extensions again.
Even upgrading from 1.5.0.2 (centosplus) to 1.5.0.5, I'd recommend reinstalling extensions. In my experience firefox always crashes on the first -- and sometimes also second and third -- launches after an upgrade when there are any extensions present.
No problema here upgrading from 1.5.0.2 to 1.5.0.5. No crashes, extensions working fine and all else.
[]s
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
On Sat, Jul 29, 2006 at 08:09:30PM -0700, Bart Schaefer wrote:
On 7/29/06, Barry Brimer lists@brimer.org wrote:
I installed the new firefox 1.5.0.5 packages and had a few issues. I had read a similar post on the nahant list. I would doubt that this is a centos-induced problem. The browser crashed when opening the extensions manager and also with a very simple webmail page.
If you upgraded directly from 1.0.8 to to 1.5.0.5, you probably need to reinstall all of your extensions. I recommend (1) write down what all of them are, (2) uninstall them all from your present firefox 1.0.8, (3) upgrade to 1.5.0.5, and finally (4) install extensions again.
Even upgrading from 1.5.0.2 (centosplus) to 1.5.0.5, I'd recommend reinstalling extensions. In my experience firefox always crashes on the first -- and sometimes also second and third -- launches after an upgrade when there are any extensions present.
No problema here upgrading from 1.5.0.2 to 1.5.0.5. No crashes, extensions working fine and all else.
I have created a new user on my system, which of course will build a new firefox profile, with no extensions. I have also moved the /usr/lib/mozilla/plugins directory to /usr/lib/mozilla/plugins.old and I have opened the browser with no themes, extensions, or plugins. Attempts to access the extensions manager or multiple Horde webmail systems cause the browser to crash.
I have launched firefox with strace and cleared the screen before trying to access the extensions menu.
Here is the result:
[{WIFEXITED(s) && WEXITSTATUS(s) == 136}], 0) = 32652 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 --- SIGCHLD (Child exited) @ 0 (0) --- waitpid(-1, 0xbfe5cbfc, WNOHANG) = -1 ECHILD (No child processes) sigreturn() = ? (mask now []) rt_sigaction(SIGINT, {SIG_DFL}, {0x8076033, [], SA_RESTORER, 0x74b8e8}, 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 read(255, "exitcode=$?\n\n## Stop addon scrip"..., 5247) = 91 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 open("/home/test/.mozilla/firefox/init.d/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOENT (No such file or directory) open("/usr/lib/firefox-1.5.0.5/init.d/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 3 fstat64(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 getdents64(3, /* 3 entries */, 4096) = 80 getdents64(3, /* 0 entries */, 4096) = 0 close(3) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 access("/home/test/.mozilla/firefox/init.d/K*", X_OK) = -1 ENOENT (No such file or directory) rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 access("/usr/lib/firefox-1.5.0.5/init.d/K*", X_OK) = -1 ENOENT (No such file or directory) rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 exit_group(136) = ? Process 32639 detached
I am not able to determine the cause based on this output, but someone else might be able to. I have no problem accessing the extensions manager in firefox 1.0.8.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, Jul 29, 2006 at 11:01:51PM -0500, Barry Brimer wrote:
I have launched firefox with strace and cleared the screen before trying to access the extensions menu.
try "strace -f", and see if you get anything.
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
I have launched firefox with strace and cleared the screen before trying to access the extensions menu.
try "strace -f", and see if you get anything.
Output of strace -f
[pid 339] gettimeofday({1154234295, 433719}, NULL) = 0 [pid 339] open("/usr/X11R6/lib/X11/fonts/Type1/l048016t.pfa", O_RDONLY) = 24 [pid 339] fcntl64(24, F_SETFD, FD_CLOEXEC) = 0 [pid 339] fstat64(24, {st_mode=S_IFREG|0644, st_size=72496, ...}) = 0 [pid 339] mmap2(NULL, 72496, PROT_READ, MAP_PRIVATE, 24, 0) = 0xb4931000 [pid 339] close(24) = 0 [pid 339] brk(0x8c95000) = 0x8c95000 [pid 339] open("/usr/share/fonts/default/Type1/n019004l.pfb", O_RDONLY) = 24 [pid 339] fcntl64(24, F_SETFD, FD_CLOEXEC) = 0 [pid 339] fstat64(24, {st_mode=S_IFREG|0644, st_size=99854, ...}) = 0 [pid 339] mmap2(NULL, 99854, PROT_READ, MAP_PRIVATE, 24, 0) = 0xb4918000 [pid 339] close(24) = 0 [pid 339] brk(0x8cb9000) = 0x8cb9000 [pid 339] brk(0x8cdc000) = 0x8cdc000 [pid 339] brk(0x8ccb000) = 0x8ccb000 [pid 339] access("/usr/lib/pango/1.4.0/modules/pango-arabic-fc.so", F_OK) = 0 [pid 339] open("/usr/lib/pango/1.4.0/modules/pango-arabic-fc.so", O_RDONLY) = 24 [pid 339] read(24, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`\17\0\000"..., 512) = 512 [pid 339] fstat64(24, {st_mode=S_IFREG|0755, st_size=10924, ...}) = 0 [pid 339] old_mmap(NULL, 9708, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 24, 0) = 0x5fc000 [pid 339] old_mmap(0x5fe000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 24, 0x2000) = 0x5fe000 [pid 339] close(24) = 0 [pid 339] open("/usr/share/fonts/bitmap-fonts/9x15B.pcf", O_RDONLY) = 24 [pid 339] fcntl64(24, F_SETFD, FD_CLOEXEC) = 0 [pid 339] fstat64(24, {st_mode=S_IFREG|0644, st_size=284372, ...}) = 0 [pid 339] mmap2(NULL, 284372, PROT_READ, MAP_PRIVATE, 24, 0) = 0xb48d2000 [pid 339] close(24) = 0 [pid 339] mmap2(NULL, 528384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb4851000 [pid 339] munmap(0xb4851000, 528384) = 0 [pid 339] --- SIGFPE (Floating point exception) @ 0 (0) --- Process 334 resumed Process 339 detached [pid 342] <... poll resumed> [{fd=7, events=POLLIN}], 1, -1) = -1 EINTR (Interrupted system call) [pid 345] <... futex resumed> ) = -1 EINTR (Interrupted system call) [pid 346] <... futex resumed> ) = -1 EINTR (Interrupted system call) [pid 343] <... futex resumed> ) = -1 EINTR (Interrupted system call) [pid 344] <... futex resumed> ) = -1 EINTR (Interrupted system call) [pid 342] +++ killed by SIGFPE +++ Process 342 detached [pid 345] +++ killed by SIGFPE +++ Process 345 detached [pid 346] +++ killed by SIGFPE +++ Process 346 detached [pid 343] +++ killed by SIGFPE +++ Process 343 detached [pid 344] +++ killed by SIGFPE +++ Process 344 detached Process 339 detached [pid 334] <... waitpid resumed> [{WIFSIGNALED(s) && WTERMSIG(s) == SIGFPE}], 0) = 339 [pid 334] fstat64(2, {st_mode=S_IFCHR|0666, st_rdev=makedev(1, 3), ...}) = 0 [pid 334] ioctl(2, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfed3e70) = -1 ENOTTY (Inappropriate ioctl for device) [pid 334] mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7d5f000 [pid 334] open("/usr/share/locale/locale.alias", O_RDONLY) = 3 [pid 334] fstat64(3, {st_mode=S_IFREG|0644, st_size=2528, ...}) = 0 [pid 334] mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7d5e000 [pid 334] read(3, "# Locale name alias data base.\n#"..., 4096) = 2528 [pid 334] read(3, "", 4096) = 0 [pid 334] close(3) = 0 [pid 334] munmap(0xb7d5e000, 4096) = 0 [pid 334] open("/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) [pid 334] open("/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) [pid 334] open("/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) [pid 334] open("/usr/share/locale/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) [pid 334] open("/usr/share/locale/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) [pid 334] open("/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) [pid 334] write(2, "/usr/lib/firefox-1.5.0.5/run-moz"..., 99) = 99 [pid 334] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 [pid 334] --- SIGCHLD (Child exited) @ 0 (0) --- [pid 334] waitpid(-1, 0xbfed43fc, WNOHANG) = -1 ECHILD (No child processes) [pid 334] sigreturn() = ? (mask now []) [pid 334] rt_sigaction(SIGINT, {SIG_DFL}, {0x8076033, [], SA_RESTORER, 0x74b8e8}, 8) = 0 [pid 334] rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 [pid 334] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 [pid 334] rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 [pid 334] stat64("core", 0xbfed4a30) = -1 ENOENT (No such file or directory) [pid 334] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 [pid 334] rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 [pid 334] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 [pid 334] rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 [pid 334] read(255, "\nexit $exitcode\n", 8192) = 16 [pid 334] rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 [pid 334] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 [pid 334] munmap(0xb7d5f000, 4096) = 0 [pid 334] exit_group(136) = ? Process 321 resumed Process 334 detached <... waitpid resumed> [{WIFEXITED(s) && WEXITSTATUS(s) == 136}], 0) = 334 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 --- SIGCHLD (Child exited) @ 0 (0) --- waitpid(-1, 0xbfff05ac, WNOHANG) = -1 ECHILD (No child processes) sigreturn() = ? (mask now []) rt_sigaction(SIGINT, {SIG_DFL}, {0x8076033, [], SA_RESTORER, 0x74b8e8}, 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 read(255, "exitcode=$?\n\n## Stop addon scrip"..., 5247) = 91 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 open("/home/test/.mozilla/firefox/init.d/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOENT (No such file or directory) open("/usr/lib/firefox-1.5.0.5/init.d/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 3 fstat64(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 getdents64(3, /* 3 entries */, 4096) = 80 getdents64(3, /* 0 entries */, 4096) = 0 close(3) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 access("/home/test/.mozilla/firefox/init.d/K*", X_OK) = -1 ENOENT (No such file or directory) rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 access("/usr/lib/firefox-1.5.0.5/init.d/K*", X_OK) = -1 ENOENT (No such file or directory) rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 exit_group(136) = ? Process 321 detached
On Sat, 2006-07-29 at 23:01 -0500, Barry Brimer wrote:
On Sat, Jul 29, 2006 at 08:09:30PM -0700, Bart Schaefer wrote:
On 7/29/06, Barry Brimer lists@brimer.org wrote:
I installed the new firefox 1.5.0.5 packages and had a few issues. I had read a similar post on the nahant list. I would doubt that this is a centos-induced problem. The browser crashed when opening the extensions manager and also with a very simple webmail page.
If you upgraded directly from 1.0.8 to to 1.5.0.5, you probably need to reinstall all of your extensions. I recommend (1) write down what all of them are, (2) uninstall them all from your present firefox 1.0.8, (3) upgrade to 1.5.0.5, and finally (4) install extensions again.
Even upgrading from 1.5.0.2 (centosplus) to 1.5.0.5, I'd recommend reinstalling extensions. In my experience firefox always crashes on the first -- and sometimes also second and third -- launches after an upgrade when there are any extensions present.
No problema here upgrading from 1.5.0.2 to 1.5.0.5. No crashes, extensions working fine and all else.
I have created a new user on my system, which of course will build a new firefox profile, with no extensions. I have also moved the /usr/lib/mozilla/plugins directory to /usr/lib/mozilla/plugins.old and I have opened the browser with no themes, extensions, or plugins. Attempts to access the extensions manager or multiple Horde webmail systems cause the browser to crash.
I have launched firefox with strace and cleared the screen before trying to access the extensions menu.
Make sure to run firefox as root once (I usually do that first, after the upgrade).
See if that helps ...
On Sun, Jul 30, 2006 at 09:53:18AM -0500, Johnny Hughes wrote:
have opened the browser with no themes, extensions, or plugins. Attempts to access the extensions manager or multiple Horde webmail systems cause the browser to crash. I have launched firefox with strace and cleared the screen before trying to access the extensions menu.
Make sure to run firefox as root once (I usually do that first, after the upgrade). See if that helps ...
This is apparently a widespread bug -- lots of problems with this update in RHEL4. See:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200622 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200601
and more.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sun, Jul 30, 2006 at 12:54:16PM -0400, Matthew Miller wrote:
On Sun, Jul 30, 2006 at 09:53:18AM -0500, Johnny Hughes wrote:
have opened the browser with no themes, extensions, or plugins. Attempts to access the extensions manager or multiple Horde webmail systems cause the browser to crash. I have launched firefox with strace and cleared the screen before trying to access the extensions menu.
Make sure to run firefox as root once (I usually do that first, after the upgrade). See if that helps ...
This is apparently a widespread bug -- lots of problems with this update in RHEL4. See:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200622 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200601
and more.
Maybe it is related to the gnome integration ? I said before I had no problems whatsoever, but I use IceWM here.
[]s
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
On Sun, Jul 30, 2006 at 12:54:16PM -0400, Matthew Miller wrote:
On Sun, Jul 30, 2006 at 09:53:18AM -0500, Johnny Hughes wrote:
have opened the browser with no themes, extensions, or plugins. Attempts to access the extensions manager or multiple Horde webmail systems cause the browser to crash. I have launched firefox with strace and cleared the screen before trying to access the extensions menu.
Make sure to run firefox as root once (I usually do that first, after the upgrade). See if that helps ...
This is apparently a widespread bug -- lots of problems with this update in RHEL4. See:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200622 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200601
fyi, after reading bug 200622, I followed the link to bug 139531, where I found the following workaround: set the MOZ_DISABLE_PANGO environment variable before starting firefox, eg for bash:
export MOZ_DISABLE_PANGO=yes
Cheers, Bryan Cardillo Penn Bioinformatics Core University of Pennsylvania
On 7/31/06, Bryan Cardillo dillo@pcbi.upenn.edu wrote:
fyi, after reading bug 200622, I followed the link to bug 139531, where I found the following workaround: set the MOZ_DISABLE_PANGO environment variable before starting
I'm one of the people who did NOT have (much) trouble upgrading. I got the now-expected (by me, anyway) two crashes on startup while all the extensions get reprocessed [*] and since then everything is fine.
One thing I noticed in taking a quick look at my system is that I have pango-devel installed as well as pango. That seems unlikely to make any difference, but it does add symlinks for the pango libraries under other names, so perhaps it's affecting dynamic linkage.
I am using gnome (in fact, it's the only desktop environment I have installed) so Rodrigo's speculation about that appears to be unfounded.
[*] or something; all I know is it doesn't happen if I remove extensions before upgrading and reinstall after, but I skipped that this time because it DIDN'T happen when going from 1.5.0.1 to 1.5.0.2 so I thought it might finally be fixed.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Jul 31, 2006 at 08:28:59AM -0700, Bart Schaefer wrote:
One thing I noticed in taking a quick look at my system is that I have pango-devel installed as well as pango. That seems unlikely to make any difference, but it does add symlinks for the pango libraries under other names, so perhaps it's affecting dynamic linkage.
pango-devel installed here too.
Version 1.6.0-9, but I think that will be the case for everyone.
And I didn't get those 2 initial crashes.
[]s
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
On Mon, 2006-07-31 at 12:38 -0300, Rodrigo Barbosa wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Jul 31, 2006 at 08:28:59AM -0700, Bart Schaefer wrote:
One thing I noticed in taking a quick look at my system is that I have pango-devel installed as well as pango. C<snip>
pango-devel installed here too.
pango-devel-1.6.0-9 here too.
Version 1.6.0-9, but I think that will be the case for everyone.
And I didn't get those 2 initial crashes.
No crashes here either.
<snip sig stuff>
On Mon, 2006-07-31 at 11:49 -0400, William L. Maltby wrote:
On Mon, 2006-07-31 at 12:38 -0300, Rodrigo Barbosa wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Jul 31, 2006 at 08:28:59AM -0700, Bart Schaefer wrote:
One thing I noticed in taking a quick look at my system is that I have pango-devel installed as well as pango. C<snip>
pango-devel installed here too.
pango-devel-1.6.0-9 here too.
Version 1.6.0-9, but I think that will be the case for everyone.
And I didn't get those 2 initial crashes.
No crashes here either.
<snip sig stuff>
pango-devel installed here too, but getting all the crash fun.
Doing 'export MOZ_DISABLE_PANGO=yes' prior to launching firefox from a terminal stops the crashes here and allows access to the extensions dialog box.
Regards
Phil
On Mon, 2006-07-31 at 16:56 +0100, Philip Wyett wrote:
On Mon, 2006-07-31 at 11:49 -0400, William L. Maltby wrote:
On Mon, 2006-07-31 at 12:38 -0300, Rodrigo Barbosa wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Jul 31, 2006 at 08:28:59AM -0700, Bart Schaefer wrote:
One thing I noticed in taking a quick look at my system is that I have pango-devel installed as well as pango. C<snip>
pango-devel installed here too.
pango-devel-1.6.0-9 here too.
Version 1.6.0-9, but I think that will be the case for everyone.
And I didn't get those 2 initial crashes.
No crashes here either.
<snip sig stuff>
pango-devel installed here too, but getting all the crash fun.
Doing 'export MOZ_DISABLE_PANGO=yes' prior to launching firefox from a terminal stops the crashes here and allows access to the extensions dialog box.
Regards
Phil
There is an update to freetype that fixes all the issues listed with extensions, wikipedia and gmail for me. Hopefully this will be pushed soon.
Regards
Phil
On 7/31/06, Philip Wyett philipwyett@blueyonder.co.uk wrote:
There is an update to freetype that fixes all the issues listed with extensions, wikipedia and gmail for me. Hopefully this will be pushed soon.
Aha! I have freetype-2.1.9-1.2.2.el4.rf from rpmforge. That's slightly newer than the base repo package.
On Mon, 2006-07-31 at 10:05 -0700, Bart Schaefer wrote:
On 7/31/06, Philip Wyett philipwyett@blueyonder.co.uk wrote:
There is an update to freetype that fixes all the issues listed with extensions, wikipedia and gmail for me. Hopefully this will be pushed soon.
Aha! I have freetype-2.1.9-1.2.2.el4.rf from rpmforge. That's slightly newer than the base repo package.
The package on the RH ftp in updates is 2.1.9-4 and has a lot of fixes in it.
Regards
Phil
On Mon, 2006-07-31 at 10:05 -0700, Bart Schaefer wrote:
On 7/31/06, Philip Wyett philipwyett@blueyonder.co.uk wrote:
There is an update to freetype that fixes all the issues listed with extensions, wikipedia and gmail for me. Hopefully this will be pushed soon.
Aha! I have freetype-2.1.9-1.2.2.el4.rf from rpmforge. That's slightly newer than the base repo package.
Ditto!
<snip sig stuff>
On Mon, 31 Jul 2006, Bart Schaefer wrote:
On 7/31/06, Philip Wyett philipwyett@blueyonder.co.uk wrote:
There is an update to freetype that fixes all the issues listed with extensions, wikipedia and gmail for me. Hopefully this will be pushed soon.
Aha! I have freetype-2.1.9-1.2.2.el4.rf from rpmforge. That's slightly newer than the base repo package.
It is actually identical and should not make a difference. The freetype package was introduced to provide better anti-aliasing but was in some cases worse. (See discussion on RPMforge mailinglist)
The fact that I still offer it is to correct that situation. (Hence the silly versioning)
Now I'm using that package with firefox 1.5.0.5 (and before 1.5.0.3) and have no problems with extensions and/or firefox. Which of course does not mean that freetype is not responsible for the problems. I just doubt that my freetype package is responsible though. The situation is more complex than that.
I'm sure people with the RHEL freetype package have the same problem, likewise people with the RPMforge freetype package (like me) have had no problems.
Kind regards, -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Jul 31, 2006 at 10:05:29AM -0700, Bart Schaefer wrote:
On 7/31/06, Philip Wyett philipwyett@blueyonder.co.uk wrote:
There is an update to freetype that fixes all the issues listed with extensions, wikipedia and gmail for me. Hopefully this will be pushed soon.
Aha! I have freetype-2.1.9-1.2.2.el4.rf from rpmforge. That's slightly newer than the base repo package.
freetype-2.1.9-1.rhel4.4 here
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
On Mon, 2006-07-31 at 17:26 -0300, Rodrigo Barbosa wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Jul 31, 2006 at 10:05:29AM -0700, Bart Schaefer wrote:
On 7/31/06, Philip Wyett philipwyett@blueyonder.co.uk wrote:
There is an update to freetype that fixes all the issues listed with extensions, wikipedia and gmail for me. Hopefully this will be pushed soon.
Aha! I have freetype-2.1.9-1.2.2.el4.rf from rpmforge. That's slightly newer than the base repo package.
freetype-2.1.9-1.rhel4.4 here
Thats the current base, there should be an update to 2.1.9-4 soon.
Regards
Phil
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Jul 31, 2006 at 09:41:07PM +0100, Philip Wyett wrote:
On Mon, 2006-07-31 at 17:26 -0300, Rodrigo Barbosa wrote:
On Mon, Jul 31, 2006 at 10:05:29AM -0700, Bart Schaefer wrote:
On 7/31/06, Philip Wyett philipwyett@blueyonder.co.uk wrote:
There is an update to freetype that fixes all the issues listed with extensions, wikipedia and gmail for me. Hopefully this will be pushed soon.
Aha! I have freetype-2.1.9-1.2.2.el4.rf from rpmforge. That's slightly newer than the base repo package.
freetype-2.1.9-1.rhel4.4 here
Thats the current base, there should be an update to 2.1.9-4 soon.
Well, I'm still not having firefox problems.
[]s
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
On Mon, 2006-07-31 at 17:41 -0300, Rodrigo Barbosa wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Jul 31, 2006 at 09:41:07PM +0100, Philip Wyett wrote:
On Mon, 2006-07-31 at 17:26 -0300, Rodrigo Barbosa wrote:
On Mon, Jul 31, 2006 at 10:05:29AM -0700, Bart Schaefer wrote:
On 7/31/06, Philip Wyett philipwyett@blueyonder.co.uk wrote:
There is an update to freetype that fixes all the issues listed with extensions, wikipedia and gmail for me. Hopefully this will be pushed soon.
Aha! I have freetype-2.1.9-1.2.2.el4.rf from rpmforge. That's slightly newer than the base repo package.
freetype-2.1.9-1.rhel4.4 here
Thats the current base, there should be an update to 2.1.9-4 soon.
Well, I'm still not having firefox problems.
[]s
Your quite lucky then. Just asking ... have you updated from the base firefox 1.0.8 or centosplus firefox 1.5.0.2?
Regards
Phil
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Jul 31, 2006 at 09:46:11PM +0100, Philip Wyett wrote:
On Mon, 2006-07-31 at 17:41 -0300, Rodrigo Barbosa wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Jul 31, 2006 at 09:41:07PM +0100, Philip Wyett wrote:
On Mon, 2006-07-31 at 17:26 -0300, Rodrigo Barbosa wrote:
On Mon, Jul 31, 2006 at 10:05:29AM -0700, Bart Schaefer wrote:
On 7/31/06, Philip Wyett philipwyett@blueyonder.co.uk wrote:
There is an update to freetype that fixes all the issues listed with extensions, wikipedia and gmail for me. Hopefully this will be pushed soon.
Aha! I have freetype-2.1.9-1.2.2.el4.rf from rpmforge. That's slightly newer than the base repo package.
freetype-2.1.9-1.rhel4.4 here
Thats the current base, there should be an update to 2.1.9-4 soon.
Well, I'm still not having firefox problems.
Your quite lucky then. Just asking ... have you updated from the base firefox 1.0.8 or centosplus firefox 1.5.0.2?
base 1.0.8 -> plus 1.5.0.2 -> updates 1.5.0.5
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
On Mon, 2006-07-31 at 17:47 -0300, Rodrigo Barbosa wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Jul 31, 2006 at 09:46:11PM +0100, Philip Wyett wrote:
On Mon, 2006-07-31 at 17:41 -0300, Rodrigo Barbosa wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Jul 31, 2006 at 09:41:07PM +0100, Philip Wyett wrote:
On Mon, 2006-07-31 at 17:26 -0300, Rodrigo Barbosa wrote:
On Mon, Jul 31, 2006 at 10:05:29AM -0700, Bart Schaefer wrote:
On 7/31/06, Philip Wyett philipwyett@blueyonder.co.uk wrote: >There is an update to freetype that fixes all the issues listed with >extensions, wikipedia and gmail for me. Hopefully this will be pushed >soon.
Aha! I have freetype-2.1.9-1.2.2.el4.rf from rpmforge. That's slightly newer than the base repo package.
freetype-2.1.9-1.rhel4.4 here
Thats the current base, there should be an update to 2.1.9-4 soon.
Well, I'm still not having firefox problems.
Your quite lucky then. Just asking ... have you updated from the base firefox 1.0.8 or centosplus firefox 1.5.0.2?
base 1.0.8 -> plus 1.5.0.2 -> updates 1.5.0.5
This seems to be common. Those who have updated from 1.0.8 are having the issues and those updating from a centosplus version are having less.
For those having issues, please wait for the freetype update and the project devs can deal with any issues from there.
Regards
Phil
On Mon, 2006-07-31 at 17:47 -0300, Rodrigo Barbosa wrote:
Well, I'm still not having firefox problems.
Your quite lucky then. Just asking ... have you updated from the
base
firefox 1.0.8 or centosplus firefox 1.5.0.2?
base 1.0.8 -> plus 1.5.0.2 -> updates 1.5.0.5
Same update path here - with Dag's freetype-2.1.9-1.2.2.el4.rf - no Firefox problems encountered since latest update.
[another] Phil
On Mon, 2006-07-31 at 17:21 -0400, Phil Schaffner wrote:
On Mon, 2006-07-31 at 17:47 -0300, Rodrigo Barbosa wrote:
Well, I'm still not having firefox problems.
Your quite lucky then. Just asking ... have you updated from the
base
firefox 1.0.8 or centosplus firefox 1.5.0.2?
base 1.0.8 -> plus 1.5.0.2 -> updates 1.5.0.5
Same update path here - with Dag's freetype-2.1.9-1.2.2.el4.rf - no Firefox problems encountered since latest update.
[another] Phil
I would say it is much preferred to keep with the official upgrade path and install CentOS updates only.
I understand people use dag for freetype for certain circumstances, but it is not the best method for an enterprise OS as freetype is a core library. For long term, keep the the base OS wherever possible. If you wish extra features for freetype, let me know and maybe I can roll a base + these features for centosplus.
Regards
Phil
On Mon, 2006-07-31 at 22:44 +0100, Philip Wyett wrote:
On Mon, 2006-07-31 at 17:21 -0400, Phil Schaffner wrote:
On Mon, 2006-07-31 at 17:47 -0300, Rodrigo Barbosa wrote:
Well, I'm still not having firefox problems.
Your quite lucky then. Just asking ... have you updated from the
base
firefox 1.0.8 or centosplus firefox 1.5.0.2?
base 1.0.8 -> plus 1.5.0.2 -> updates 1.5.0.5
Same update path here - with Dag's freetype-2.1.9-1.2.2.el4.rf - no Firefox problems encountered since latest update.
[another] Phil
I would say it is much preferred to keep with the official upgrade path and install CentOS updates only.
I understand people use dag for freetype for certain circumstances, but it is not the best method for an enterprise OS as freetype is a core library. For long term, keep the the base OS wherever possible. If you wish extra features for freetype, let me know and maybe I can roll a base + these features for centosplus.
Regards
Phil
OK ... I am cranking out that freetype update now ... hopefully it will fix all these issues ... without having to rebuild anything else :)
Thanks, Johnny Hughes
Johnny Hughes wrote:
(snip)
OK ... I am cranking out that freetype update now ... hopefully it will fix all these issues ... without having to rebuild anything else :)
Thanks, Johnny Hughes
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hey Johnny, Just to let you know the freetype update worked for me!!!!! :-P THANKS!!!
Lee Perez
On Tue, 2006-08-01 at 15:38 -0500, Lee Perez wrote:
Johnny Hughes wrote:
(snip)
OK ... I am cranking out that freetype update now ... hopefully it will fix all these issues ... without having to rebuild anything else :)
<snip Johnny sig stuff>
Hey Johnny, Just to let you know the freetype update worked for me!!!!! :-P THANKS!!!
Uh! Since I had intermittent success before, I didn't think! I got it this A.M, have started stuff up several times and NP so far.
Lee Perez
<snip sig stuff>
On Mon, 2006-07-31 at 22:44 +0100, Philip Wyett wrote:
I would say it is much preferred to keep with the official upgrade path and install CentOS updates only.
I understand people use dag for freetype for certain circumstances, but it is not the best method for an enterprise OS as freetype is a core library. For long term, keep the the base OS wherever possible. If you wish extra features for freetype, let me know and maybe I can roll a base + these features for centosplus.
Point taken, and for server systems I would completely agree. Stick very close to core EL OS. No CentOSplus or any other extras unless absolutely necessary. However, for an individual desktop/laptop it is often desirable to have additional functionality beyond what the strictly-enterprise system has to offer - thus the reason for the existence of CentOSplus and other 3rd party repos like Dag's or Karanbir's. Adding more packages to CentOSplus is highly desirable, but so are coordination, cooperation, and compatibility with other reliable repos.
No slight to the dedicated CentOSplus maintainers/packagers, but I see no dramatic difference between it and a fine trusted repo like Dag - which has served to add functionality for Red Hat, Fedora, and EL- compatible systems for years. This is not to say that I have never broken anything with Dag or other 3rd party packages - the old "if you break it you get to keep all the pieces" applies. Fixes or workarounds are generally forthcoming when problems are reported on FreshRPMS, RPMforge, or CentOS lists; and in this case using the Dag freetype and CentOSplus firefox packages seems to have circumvented the problems others have encountered.
RHEL-derived distros make a fine stable base for those Red Hat aficionados who wish to avoid the Fedora roller coaster ride, and judicious choice of repos and use of protectbase/includepkgs/exclude in yum config files is always highly recommended, but for a fully- functional desktop workstation or home system (particularly if you want multimedia capability), I find sticking with the Enterprise packages is not a viable option.
Regards, Phil
On Mon, 2006-07-31 at 11:49 -0400, William L. Maltby wrote:
On Mon, 2006-07-31 at 12:38 -0300, Rodrigo Barbosa wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Jul 31, 2006 at 08:28:59AM -0700, Bart Schaefer wrote:
<snip>
No crashes here either.
You folks jinxed me! :-))
I felt the need, started FF in a user that had not yet run the new version. Plugin update happened, all is good.
Later, tried to start it as the other user that had run it and as this recent user and both crash!
Strace -f shows some dnoent stuff saying it can't find .mozilla/.../init.d/K*
Huh? It's been running! I'll bet it's the "flakiness" I've been seeing for about a month now (I *think* it only hits during X activity, haven't had the patience to wait long enough to see).
Anyway, the common fix (here) is reboot. I've got a GD MS system I guess! ;-)
Yep! Firefox working great for both user's now.
There is no init.d under .mozilla here. Now I wish I'd saved it to a file, there were quite a few of the dnoent messages. *BIG* file it would be! <snip sig stuff>
On Sun, 30 Jul 2006, Johnny Hughes wrote:
On Sat, 2006-07-29 at 23:01 -0500, Barry Brimer wrote:
On Sat, Jul 29, 2006 at 08:09:30PM -0700, Bart Schaefer wrote:
On 7/29/06, Barry Brimer lists@brimer.org wrote:
I installed the new firefox 1.5.0.5 packages and had a few issues. I had read a similar post on the nahant list. I would doubt that this is a centos-induced problem. The browser crashed when opening the extensions manager and also with a very simple webmail page.
If you upgraded directly from 1.0.8 to to 1.5.0.5, you probably need to reinstall all of your extensions. I recommend (1) write down what all of them are, (2) uninstall them all from your present firefox 1.0.8, (3) upgrade to 1.5.0.5, and finally (4) install extensions again.
Even upgrading from 1.5.0.2 (centosplus) to 1.5.0.5, I'd recommend reinstalling extensions. In my experience firefox always crashes on the first -- and sometimes also second and third -- launches after an upgrade when there are any extensions present.
No problema here upgrading from 1.5.0.2 to 1.5.0.5. No crashes, extensions working fine and all else.
I have created a new user on my system, which of course will build a new firefox profile, with no extensions. I have also moved the /usr/lib/mozilla/plugins directory to /usr/lib/mozilla/plugins.old and I have opened the browser with no themes, extensions, or plugins. Attempts to access the extensions manager or multiple Horde webmail systems cause the browser to crash.
I have launched firefox with strace and cleared the screen before trying to access the extensions menu.
Make sure to run firefox as root once (I usually do that first, after the upgrade).
See if that helps ...
I tried running firefox as root once, and then again with my user and my test user. Both still exhibit the same problem.
On Sun, 2006-07-30 at 00:26 -0300, Rodrigo Barbosa wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, Jul 29, 2006 at 08:09:30PM -0700, Bart Schaefer wrote:
On 7/29/06, Barry Brimer lists@brimer.org wrote:
<snip>
The browser crashed when opening the extensions manager and also with a very simple webmail page.<snip>
If you upgraded directly from 1.0.8 to to 1.5.0.5, you probably need to reinstall all of your extensions. I recommend (1) write down what all of them are, (2) uninstall them all from your present firefox 1.0.8, (3) upgrade to 1.5.0.5, and finally (4) install extensions again.
Even upgrading from 1.5.0.2 (centosplus) to 1.5.0.5, I'd recommend reinstalling extensions. In my experience firefox always crashes on the first -- and sometimes also second and third -- launches after an upgrade when there are any extensions present.
No problema here upgrading from 1.5.0.2 to 1.5.0.5. No crashes, extensions working fine and all else.
Ditto. Plus IIRC (I don't *think* it was my wife's Win machine) it came out and upgraded my extensions when I first started? If not, to quote a former mother-in-law, "I must be losing my mind!".
[]s
Rodrigo Barbosa
<snip sig stuff>
On Sun, 30 Jul 2006, William L. Maltby wrote:
On Sun, 2006-07-30 at 00:26 -0300, Rodrigo Barbosa wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, Jul 29, 2006 at 08:09:30PM -0700, Bart Schaefer wrote:
On 7/29/06, Barry Brimer lists@brimer.org wrote:
<snip>
The browser crashed when opening the extensions manager and also with a very simple webmail page.<snip>
If you upgraded directly from 1.0.8 to to 1.5.0.5, you probably need to reinstall all of your extensions. I recommend (1) write down what all of them are, (2) uninstall them all from your present firefox 1.0.8, (3) upgrade to 1.5.0.5, and finally (4) install extensions again.
Even upgrading from 1.5.0.2 (centosplus) to 1.5.0.5, I'd recommend reinstalling extensions. In my experience firefox always crashes on the first -- and sometimes also second and third -- launches after an upgrade when there are any extensions present.
No problema here upgrading from 1.5.0.2 to 1.5.0.5. No crashes, extensions working fine and all else.
Ditto. Plus IIRC (I don't *think* it was my wife's Win machine) it came out and upgraded my extensions when I first started? If not, to quote a former mother-in-law, "I must be losing my mind!".
firefox did do the extension upgrade check with me as well.
Barry
On Sun, 2006-07-30 at 18:14 -0500, Barry Brimer wrote:
On Sun, 30 Jul 2006, William L. Maltby wrote:
On Sun, 2006-07-30 at 00:26 -0300, Rodrigo Barbosa wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, Jul 29, 2006 at 08:09:30PM -0700, Bart Schaefer wrote:
On 7/29/06, Barry Brimer lists@brimer.org wrote:
<snip>
The browser crashed when opening the extensions manager and also with a very simple webmail page.<snip>
If you upgraded directly from 1.0.8 to to 1.5.0.5, you probably need to reinstall all of your extensions. I recommend (1) write down what all of them are, (2) uninstall them all from your present firefox 1.0.8, (3) upgrade to 1.5.0.5, and finally (4) install extensions again.
Even upgrading from 1.5.0.2 (centosplus) to 1.5.0.5, I'd recommend reinstalling extensions. In my experience firefox always crashes on the first -- and sometimes also second and third -- launches after an upgrade when there are any extensions present.
No problema here upgrading from 1.5.0.2 to 1.5.0.5. No crashes, extensions working fine and all else.
Ditto. Plus IIRC (I don't *think* it was my wife's Win machine) it came out and upgraded my extensions when I first started? If not, to quote a former mother-in-law, "I must be losing my mind!".
firefox did do the extension upgrade check with me as well.
It is definitely a problem with some installs and not with others ... which is quite strange.
Hopefully we will be able to figure out what set of programs is causing the issues.
On 7/31/06, Johnny Hughes mailing-lists@hughesjr.com wrote:
It is definitely a problem with some installs and not with others ... which is quite strange.
Hopefully we will be able to figure out what set of programs is causing the issues.
I'm not sure if it'll help, but I wonder if it's worth getting a list of people (including those who upgraded without problems) to send in an ``rpm -qa'' and then try and track down the common packages with people who are having problems? (providing it is something caused by another package).
It might give some people clues to work with. Of course, someone needs to be responsible for gathering this information :)
Phil.
-
Barry Brimer -
Bart Schaefer -
Bryan Cardillo -
Dag Wieers -
Johnny Hughes -
Lee Perez -
Matthew Miller -
Phil Schaffner -
Philip Reynolds -
Philip Wyett -
Rodrigo Barbosa -
William L. Maltby