The TL;DR for the below. To upgrade to the released 0.26 version for 12.10
mentioned in #9 you need to (note, this was done on a fairly recent clean
install of 12.10 server amd64, although with a restored db backup from an old
0.25 install that had blown a disk, so the db was already populated):
Public bug reported:
After updating to the 12.10 development release, I can no longer use
mythweb, any attempt to visit th emythweb page results in the following
warning + error in my apache logs:
[Sun Sep 09 15:03:04 2012] [error] [client x.x.x.x] PHP Warning: Unknown:
function '0' not found o
I installed the kernel build posted by Chris in #15, logged in as an
LDAP user with KRB5 auth and a kerberised nfs4 home directory, then left
the machine unattended for >24 hours. Under these conditions the X
session would be locked up when I returned to the machine and the nfs
mount inaccessable (
I can confirm as well that using the kernel from #18 and performing the
same steps as before fails to generate the bug and everything seems to
work correctly.
Thanks as well!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
After a little bit of googling, it's possible this could be related to
this thread: http://www.spinics.net/lists/linux-nfs/msg24949.html
As soon as the process hangs and the log messages start I'm seeing a
constant 5-9 mbit of network traffic in both directions between the
client and server. Looki
That kernel has given some different behaviour. Now when open the file
in lyx I get the following messages repeating over and over in the
syslog:
Apr 15 10:19:10 desktop kernel: [ 82.651314] NFS: nfs4_reclaim_open_state:
Lock reclaim failed!
Apr 15 10:19:10 desktop kernel: [ 82.652566] NFS: n
To add more information to this. If I start Lyx on its own (i.e. just
'lyx' at the command line, no file selected), then it starts fine.
However if I then try to open a file I get the same behaviour as above.
The above was triggered when doing 'lyx somefile.lyx' at the command
line. This is probabl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981278
Title:
BUG: unable to handle kernel paging request at ffb8
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
Public bug reported:
This was triggered by starting lyx, killing and trying again seemed to
reproduce the error. Lyx would partially start, then hang.
This was done as an LDAP/Kerberos user on a machine with an Kerberised
NFS4 mounted home directory.
ProblemType: KernelOops
DistroRelease: Ubuntu
I'm guessing the change linked to in #33 that fixes this is:
* Remove 90qt-a11y: Qt accessibility is not stable enough in Oneiric to be
enabled by default for all applications. A patch for unity-2d specifically
enables accessibility for it so that the desktop remains accessible.
(LP:
10 matches
Mail list logo