I haven't had any crashes anymore since I upgraded to kernel
3.3.0-030300rc2-generic.
Added tag kernel-fixed-upstream-v3.3-rc2
Nico
** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream-v3.3-rc2
--
You received this bug notification because you are a member of Ubuntu
I've been running the 3.3 kernel for a few days now and so far didn't
experience any freezes. If it still didn't crash by the end of the week
I'm calling it 'kernel-fixed-upstream'
Nico
On Wed, Feb 1, 2012 at 18:46, Nico De Ranter
nico.deran...@gmail.comwrote:
I've only received this portable
Public bug reported:
OS: Ubuntu 11.04
Kernel: Ubuntu 2.6.38-13.54-generic 2.6.38.8
hardware: Fujitsu Lifebook A531 with 1 extra external screen connected
Very frequently (often multiple times a day) the system seems to freeze. The
mouse is still active but I can't select anything. Switching
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924905
Title:
System hangs with 'plane 1 assertion failure, should be off on pipe A
but is still active'
To manage notifications about this bug go
I've only received this portable in October so I never tried any other
Ubuntu release on it.
I'll try installing a newer kernel and let you know the result (it may take
a while however as this is my work-portable)
Nico
On Wed, Feb 1, 2012 at 18:33, Joseph Salisbury
I had the same issue. In my case I got the could not update
ICEauthority error message at every logon. After switching both the
server (/etc/exports) and client (/etc/auto.net) to NFSv4 the error
message dissappeared. Big thanks to James for the suggestion!
--
You received this bug
The procedure described at
https://sites.google.com/site/lightrush/random-1/updatenvidiabinarydriverinubuntulucidormaverickviappa
worked for me!
Nico
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looking at the log files on the server I actually see a number of non-
fatal mount.nfs4 crashes during the day (see attachment).
The actual crashes seem to be related to nfsd if I interpret the output
from /var/log/messages (excerpt attached) correctly.
I can't match the crashes to any specific
** Attachment added: excerpt from dmesg
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/790220/+attachment/2306751/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790220
** Attachment added: excerpt from /var/log/messages
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/790220/+attachment/2306755/+files/messages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm seeing the same type of crashes on our home directory server. The
server is crashing once a week on average since about June. The server
is runnin 10.4 amd64 with the latest patches applied. I don't have
access to the server at the moment. I'll try to post more logs next
week.
Hardware:
Support for the Quadro 600 is apparently only available starting with
the nvidia driver 260.1912 according to the nvidia website. 10.04LTS
has 195.36.24.
Is there a way to upgrade the nvidia drivers on 10.4 LTS to 260.1912 or
higher?
This is really blocking me as I only get a black screen when
I have exactly the same problem on Lucid 10.4.2. I tried setting up an
encrypted ~/Private directory using ecrypts-setup-private as I don't
want the whole homedir to be encrypted. I can mount the directory, the
first time I do ls ~/Private I can see the content but after that ls
shows an empty
The problem does not appear on Fedora using autofs 5.0.5 so it looks
like this is an Ubuntu specific bug.
Please note that the description for this bug report is misleading as
autofs doesn't do failover (as far as I know). However it is supposed
to be able to automaticaly choose an available
I changed the title of this bug report from
NFS automount failover doesn't work
to
NFS automount using replicated servers doesn't work
as I believe it better reflects the problem and saying 'failover' in
combination with may put of the maintainers as autofs isn't supposed to
do real
The problem does not appear on Fedora using autofs 5.0.5 so it looks
like this is an Ubuntu specific bug.
Please note that the description for this bug report is misleading as
autofs doesn't do failover (as far as I know). However it is supposed
to be able to automaticaly choose an available
I changed the title of this bug report from
NFS automount failover doesn't work
to
NFS automount using replicated servers doesn't work
as I believe it better reflects the problem and saying 'failover' in
combination with may put of the maintainers as autofs isn't supposed to
do real
I'm having the same issue using autofs 5.0.4-3.1ubuntu5.1 on lucid.
When using NFS3 specifying replicated servers does work, when using NFS4 it
doesn't. If I run automount manually with verbose and debugging enabled I see
the
following output when trying to access /usr/local:
I just verified the problem still exists on Maverick running autofs5
5.0.5-0ubuntu2.
Same scenario: if I list only 1 server the automount works fine, if I
add a second server the mount fails completely without leaving any logs.
--
You received this bug notification because you are a member of
I'm having the same issue using autofs 5.0.4-3.1ubuntu5.1 on lucid.
When using NFS3 specifying replicated servers does work, when using NFS4 it
doesn't. If I run automount manually with verbose and debugging enabled I see
the
following output when trying to access /usr/local:
I just verified the problem still exists on Maverick running autofs5
5.0.5-0ubuntu2.
Same scenario: if I list only 1 server the automount works fine, if I
add a second server the mount fails completely without leaving any logs.
--
You received this bug notification because you are a member of
I second that. Please fix this in the lucid (10.4.1 LTS) branch!
Nico
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/574719
Title:
scan-build broken
--
ubuntu-bugs mailing list
Reloading autofs in /etc/rc.local doesn't work for me as my /usr/local
is also automounted and seems to be busy at that time which makes autofs
restart freeze.
@Lars Kellogg-Stedman: thanks, that does seem to work for me although I
wonder what the side effects might be. If I understand this
Reloading autofs in /etc/rc.local doesn't work for me as my /usr/local
is also automounted and seems to be busy at that time which makes autofs
restart freeze.
@Lars Kellogg-Stedman: thanks, that does seem to work for me although I
wonder what the side effects might be. If I understand this
Public bug reported:
Binary package hint: krb5-auth-dialog
My PC was left running over the weekend. When I came back top shows krb5
-auth-dialog is now using 23.7% of my 4GB of memory. Seems awfully big
for an applet.
I'm also using a Dell T7400. I am able to install and boot 9.10, however
since the install I'm getting the same type of error messages in my log
files:
Nov 6 08:51:30 bottlenose kernel: [86478.151170] sd 8:0:0:0: [sda] Sense Key :
Recovered Error [current] [descriptor]
Nov 6 08:51:30
Any idea when I can expect this fix in Jaunty?
--
cannot change password
https://bugs.launchpad.net/bugs/334795
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
FYI: This problem occurs when updatedefaultentry in /boot/grub/menu.lst
is set to true. Setting to false again allows update-grub to run again.
--
update-grub fails when default is saved
https://bugs.launchpad.net/bugs/193439
You received this bug notification because you are a member of Ubuntu
Apparently the upgrade from dapper to edgy removed nfs-common from my system.
Reinstalling it fixed the read-only problem.
Case closed.
--
openoffice opens files read-only fromn nfs mounted partition
https://launchpad.net/bugs/68937
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: openoffice.org
After upgrading from dapper to Edgy OpenOffice refuses to open files
from an nfs-mounted filesystem in read/write mode. In stead it opens
them read-only. When I try to open the same file in the same location
with gnumeric I can write to
30 matches
Mail list logo
