| 2008-10-27 11:19:47 |
Frédéric Nass |
bug |
|
|
added bug |
| 2008-10-27 11:19:47 |
Frédéric Nass |
bug |
|
|
added attachment 'firefox-error-console.txt' (firefox-error-console.txt) |
| 2008-10-27 18:26:31 |
Frédéric Nass |
description |
Binary package hint: firefox-3.0
Hi,
Description :
When firefox3 is launched, wheter a profil already exist or not OVER A NFSv4 /home SHARE, the firefox window opens very small. The only working button in the toolbar is the home button, loading home page succesfully when pushed. Then while browsing from this webpage, back and forward buttons stay greyed. URL bar is not usable, as Enter (Return) key is not operable, neither the green arrow is clickable. It has just no effect.
So firefox-3.0 over NFSv4 is almost unusable.
When using a NFSv3 share for the profile, or when using firefox with a local account and local storage, no problem at all. Everything is working a usual.
But when over new NFSv4 shares, Firefoxv3 is not working.
Package & Linux Distro description :
* Kubuntu Hardy up-to-thisdate (2008/10/27) on client side.
* Firefox-3.0 v3.0.3+build1+nobinonly-0ubuntu0.8.04.1
Server is an up-to-dated Debian Etch.
The problem appeared after upgrading main NFS server from Debian Sid 3.1 to Debian Etch 4.0. I could isolate this problem as everything works well with the same Ubuntu client and NFSv3 shares and not with NFSv4 Debian Etch shares.
On the server and client sides, rpcinfo -p shows :
Server :
program no_version protocole no_port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100021 1 udp 32776 nlockmgr
100021 3 udp 32776 nlockmgr
100021 4 udp 32776 nlockmgr
100021 1 tcp 50187 nlockmgr
100021 3 tcp 50187 nlockmgr
100021 4 tcp 50187 nlockmgr
391002 2 tcp 857 sgi_fam
100011 1 udp 879 rquotad
100011 2 udp 879 rquotad
100011 1 tcp 882 rquotad
100011 2 tcp 882 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 658 mountd
100005 1 tcp 661 mountd
100005 2 udp 658 mountd
100005 2 tcp 661 mountd
100005 3 udp 658 mountd
100005 3 tcp 661 mountd
Client :
program no_version protocole no_port
100000 2 tcp 111 portmapper
100024 1 udp 49896 status
100024 1 tcp 37670 status
100000 2 udp 111 portmapper
100021 1 tcp 33826 nlockmgr
100021 3 tcp 33826 nlockmgr
100021 4 tcp 33826 nlockmgr
On server, I get a lot of errors that says (dmesg) :
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
....
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
Seems like a NFS issue that has direct influence over the lastest Firefox v3. (No problem with Firefox v2.)
Hope you can help with this soon,
I'm sorry this might be a NFS configuration problem on client side, but from now it has a direct and extremly painfull influence over Firefox v3 as it remains unsuable...
Frédéric Nass,
Chef Exploitation, Service s2i,
Iut de Metz, Université de Metz.
PS : more log to come... |
Binary package hint: firefox-3.0
Hi,
Description :
When firefox3 is launched, wheter a profil already exist or not OVER A NFSv4 /home SHARE, the firefox window opens very small. The only working button in the toolbar is the home button, loading home page succesfully when pushed. Then while browsing from this webpage, back and forward buttons stay greyed. URL bar is not usable, as Enter (Return) key is not operable, neither the green arrow is clickable. It has just no effect. Same troubles when firefox launched in "safe-mode".
So firefox-3.0 over NFSv4 is almost unusable.
When using a NFSv3 share for the profile, or when using firefox with a local account and local storage, no problem at all. Everything is working a usual.
But when over new NFSv4 shares, Firefoxv3 is not working.
Package & Linux Distro description :
* Kubuntu Hardy up-to-thisdate (2008/10/27) on client side.
* Firefox-3.0 v3.0.3+build1+nobinonly-0ubuntu0.8.04.1
Server is an up-to-dated Debian Etch.
The problem appeared after upgrading main NFS server from Debian Woody 3.1 to Debian Etch 4.0. I could isolate this problem as everything works well with the same Ubuntu client and NFSv3 shares and not with NFSv4 Debian Etch shares.
On the server and client sides, rpcinfo -p shows :
Server :
program no_version protocole no_port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100021 1 udp 32776 nlockmgr
100021 3 udp 32776 nlockmgr
100021 4 udp 32776 nlockmgr
100021 1 tcp 50187 nlockmgr
100021 3 tcp 50187 nlockmgr
100021 4 tcp 50187 nlockmgr
391002 2 tcp 857 sgi_fam
100011 1 udp 879 rquotad
100011 2 udp 879 rquotad
100011 1 tcp 882 rquotad
100011 2 tcp 882 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 658 mountd
100005 1 tcp 661 mountd
100005 2 udp 658 mountd
100005 2 tcp 661 mountd
100005 3 udp 658 mountd
100005 3 tcp 661 mountd
Client :
program no_version protocole no_port
100000 2 tcp 111 portmapper
100024 1 udp 49896 status
100024 1 tcp 37670 status
100000 2 udp 111 portmapper
100021 1 tcp 33826 nlockmgr
100021 3 tcp 33826 nlockmgr
100021 4 tcp 33826 nlockmgr
On server, I get a lot of errors that says (dmesg) :
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
....
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
Seems like a NFS issue that has direct influence over the latest Firefox v3. (No problem with Firefox v2.)
Hope you can help with this soon,
I'm sorry this might be a NFS configuration problem on client side, but from now it has a direct and extremly painfull influence over Firefox v3 as it remains unsuable...
Frédéric Nass,
Chef Exploitation, Service s2i,
Iut de Metz, Université de Metz.
PS : more log to come... |
|
| 2008-10-27 19:55:18 |
Frédéric Nass |
description |
Binary package hint: firefox-3.0
Hi,
Description :
When firefox3 is launched, wheter a profil already exist or not OVER A NFSv4 /home SHARE, the firefox window opens very small. The only working button in the toolbar is the home button, loading home page succesfully when pushed. Then while browsing from this webpage, back and forward buttons stay greyed. URL bar is not usable, as Enter (Return) key is not operable, neither the green arrow is clickable. It has just no effect. Same troubles when firefox launched in "safe-mode".
So firefox-3.0 over NFSv4 is almost unusable.
When using a NFSv3 share for the profile, or when using firefox with a local account and local storage, no problem at all. Everything is working a usual.
But when over new NFSv4 shares, Firefoxv3 is not working.
Package & Linux Distro description :
* Kubuntu Hardy up-to-thisdate (2008/10/27) on client side.
* Firefox-3.0 v3.0.3+build1+nobinonly-0ubuntu0.8.04.1
Server is an up-to-dated Debian Etch.
The problem appeared after upgrading main NFS server from Debian Woody 3.1 to Debian Etch 4.0. I could isolate this problem as everything works well with the same Ubuntu client and NFSv3 shares and not with NFSv4 Debian Etch shares.
On the server and client sides, rpcinfo -p shows :
Server :
program no_version protocole no_port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100021 1 udp 32776 nlockmgr
100021 3 udp 32776 nlockmgr
100021 4 udp 32776 nlockmgr
100021 1 tcp 50187 nlockmgr
100021 3 tcp 50187 nlockmgr
100021 4 tcp 50187 nlockmgr
391002 2 tcp 857 sgi_fam
100011 1 udp 879 rquotad
100011 2 udp 879 rquotad
100011 1 tcp 882 rquotad
100011 2 tcp 882 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 658 mountd
100005 1 tcp 661 mountd
100005 2 udp 658 mountd
100005 2 tcp 661 mountd
100005 3 udp 658 mountd
100005 3 tcp 661 mountd
Client :
program no_version protocole no_port
100000 2 tcp 111 portmapper
100024 1 udp 49896 status
100024 1 tcp 37670 status
100000 2 udp 111 portmapper
100021 1 tcp 33826 nlockmgr
100021 3 tcp 33826 nlockmgr
100021 4 tcp 33826 nlockmgr
On server, I get a lot of errors that says (dmesg) :
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
....
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
Seems like a NFS issue that has direct influence over the latest Firefox v3. (No problem with Firefox v2.)
Hope you can help with this soon,
I'm sorry this might be a NFS configuration problem on client side, but from now it has a direct and extremly painfull influence over Firefox v3 as it remains unsuable...
Frédéric Nass,
Chef Exploitation, Service s2i,
Iut de Metz, Université de Metz.
PS : more log to come... |
Binary package hint: firefox-3.0
Hi,
Description :
When firefox3 is launched, whether a profile already exist or not OVER A NFSv4 /home SHARE, the firefox window opens very small. The only working button in the toolbar is the home button, loading home page successfully when pushed. Then while browsing from this web page, back and forward buttons stay greyed. URL bar is not usable, as Enter (Return) key is not functional, neither the green arrow is clickable. It has just no effect. Same behavior when firefox is launched in "safe-mode".
So firefox-3.0 over NFSv4 is almost unusable.
When using a NFSv3 share for the profile, or when using firefox with a local account and local storage, no problem at all. Everything is working as expected.
But when over new NFSv4 shares, Firefoxv3 is not working.
Package & Linux Distro description :
* Kubuntu Hardy up-to-thisdate (2008/10/27) on client side, with Firefox-3.0 v3.0.3+build1+nobinonly-0ubuntu0.8.04.1
* Debian Etch up-to-date on server side.
The problem appeared after upgrading user's NFS+LDAP server from Debian Woody 3.1 to Debian Etch 4.0. I could isolate this problem as everything works well with the same Ubuntu client and NFSv3 shares and not with NFSv4 Debian Etch shares.
On the server and client sides, rpcinfo -p shows :
Server :
program no_version protocole no_port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100021 1 udp 32776 nlockmgr
100021 3 udp 32776 nlockmgr
100021 4 udp 32776 nlockmgr
100021 1 tcp 50187 nlockmgr
100021 3 tcp 50187 nlockmgr
100021 4 tcp 50187 nlockmgr
391002 2 tcp 857 sgi_fam
100011 1 udp 879 rquotad
100011 2 udp 879 rquotad
100011 1 tcp 882 rquotad
100011 2 tcp 882 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 658 mountd
100005 1 tcp 661 mountd
100005 2 udp 658 mountd
100005 2 tcp 661 mountd
100005 3 udp 658 mountd
100005 3 tcp 661 mountd
Client :
program no_version protocole no_port
100000 2 tcp 111 portmapper
100024 1 udp 49896 status
100024 1 tcp 37670 status
100000 2 udp 111 portmapper
100021 1 tcp 33826 nlockmgr
100021 3 tcp 33826 nlockmgr
100021 4 tcp 33826 nlockmgr
On server, I get a lot of errors that says (dmesg) :
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
....
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
Seems like a NFS issue that has direct influence over the latest Firefox v3. (No problem with Firefox v2.)
Hope you can help with this soon,
I'm sorry this might be a NFS configuration problem on client side, but from now it has a direct and extremly painfull influence over Firefox v3 as it remains unusable...
Frédéric Nass,
Chef Exploitation, Service s2i,
Iut de Metz, Université de Metz.
PS : more log to come... |
|
| 2008-10-28 18:57:35 |
Frédéric Nass |
description |
Binary package hint: firefox-3.0
Hi,
Description :
When firefox3 is launched, whether a profile already exist or not OVER A NFSv4 /home SHARE, the firefox window opens very small. The only working button in the toolbar is the home button, loading home page successfully when pushed. Then while browsing from this web page, back and forward buttons stay greyed. URL bar is not usable, as Enter (Return) key is not functional, neither the green arrow is clickable. It has just no effect. Same behavior when firefox is launched in "safe-mode".
So firefox-3.0 over NFSv4 is almost unusable.
When using a NFSv3 share for the profile, or when using firefox with a local account and local storage, no problem at all. Everything is working as expected.
But when over new NFSv4 shares, Firefoxv3 is not working.
Package & Linux Distro description :
* Kubuntu Hardy up-to-thisdate (2008/10/27) on client side, with Firefox-3.0 v3.0.3+build1+nobinonly-0ubuntu0.8.04.1
* Debian Etch up-to-date on server side.
The problem appeared after upgrading user's NFS+LDAP server from Debian Woody 3.1 to Debian Etch 4.0. I could isolate this problem as everything works well with the same Ubuntu client and NFSv3 shares and not with NFSv4 Debian Etch shares.
On the server and client sides, rpcinfo -p shows :
Server :
program no_version protocole no_port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100021 1 udp 32776 nlockmgr
100021 3 udp 32776 nlockmgr
100021 4 udp 32776 nlockmgr
100021 1 tcp 50187 nlockmgr
100021 3 tcp 50187 nlockmgr
100021 4 tcp 50187 nlockmgr
391002 2 tcp 857 sgi_fam
100011 1 udp 879 rquotad
100011 2 udp 879 rquotad
100011 1 tcp 882 rquotad
100011 2 tcp 882 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 658 mountd
100005 1 tcp 661 mountd
100005 2 udp 658 mountd
100005 2 tcp 661 mountd
100005 3 udp 658 mountd
100005 3 tcp 661 mountd
Client :
program no_version protocole no_port
100000 2 tcp 111 portmapper
100024 1 udp 49896 status
100024 1 tcp 37670 status
100000 2 udp 111 portmapper
100021 1 tcp 33826 nlockmgr
100021 3 tcp 33826 nlockmgr
100021 4 tcp 33826 nlockmgr
On server, I get a lot of errors that says (dmesg) :
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
....
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
Seems like a NFS issue that has direct influence over the latest Firefox v3. (No problem with Firefox v2.)
Hope you can help with this soon,
I'm sorry this might be a NFS configuration problem on client side, but from now it has a direct and extremly painfull influence over Firefox v3 as it remains unusable...
Frédéric Nass,
Chef Exploitation, Service s2i,
Iut de Metz, Université de Metz.
PS : more log to come... |
Binary package hint: firefox-3.0
Hi,
Description :
When firefox3 is launched, whether a profile already exist or not OVER A NFSv4 /home SHARE, the firefox window opens very small. The only working button in the toolbar is the home button, loading home page successfully when pushed. Then while browsing from this web page, back and forward buttons stay greyed. URL bar is not usable, as Enter (Return) key is not functional, neither the green arrow is clickable. It has just no effect. Same behavior when firefox is launched in "safe-mode".
So firefox-3.0 over NFSv4 is almost unusable.
When using a NFSv3 share for the profile, or when using firefox with a local account and local storage, no problem at all. Everything is working as expected.
But when over new NFSv4 shares, Firefoxv3 is not working.
Package & Linux Distro description :
* Kubuntu Hardy up-to-thisdate (2008/10/27) on client side, with Firefox-3.0 v3.0.3+build1+nobinonly-0ubuntu0.8.04.1
* Debian Etch up-to-date on server side.
The problem appeared after upgrading user's NFS+LDAP server from Debian Sarge 3.1 to Debian Etch 4.0. I could isolate this problem as everything works well with the same Ubuntu client and NFSv3 shares and not with NFSv4 Debian Etch shares.
On the server and client sides, rpcinfo -p shows :
Server :
program no_version protocole no_port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100021 1 udp 32776 nlockmgr
100021 3 udp 32776 nlockmgr
100021 4 udp 32776 nlockmgr
100021 1 tcp 50187 nlockmgr
100021 3 tcp 50187 nlockmgr
100021 4 tcp 50187 nlockmgr
391002 2 tcp 857 sgi_fam
100011 1 udp 879 rquotad
100011 2 udp 879 rquotad
100011 1 tcp 882 rquotad
100011 2 tcp 882 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 658 mountd
100005 1 tcp 661 mountd
100005 2 udp 658 mountd
100005 2 tcp 661 mountd
100005 3 udp 658 mountd
100005 3 tcp 661 mountd
Client :
program no_version protocole no_port
100000 2 tcp 111 portmapper
100024 1 udp 49896 status
100024 1 tcp 37670 status
100000 2 udp 111 portmapper
100021 1 tcp 33826 nlockmgr
100021 3 tcp 33826 nlockmgr
100021 4 tcp 33826 nlockmgr
On server, I get a lot of errors that says (dmesg) :
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
....
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
lockd: cannot monitor 10.10.2.1
Seems like a NFS issue that has direct influence over the latest Firefox v3. (No problem with Firefox v2.)
Hope you can help with this soon,
I'm sorry this might be a NFS configuration problem on client side, but from now it has a direct and extremly painfull influence over Firefox v3 as it remains unusable...
Frédéric Nass,
Chef Exploitation, Service s2i,
Iut de Metz, Université de Metz.
PS : more log to come... |
|
| 2008-10-28 19:09:32 |
Alexander Sack |
firefox-3.0: status |
New |
Invalid |
|
| 2008-10-28 19:09:32 |
Alexander Sack |
firefox-3.0: statusexplanation |
|
|
|
