+1 broken on intrepid 64-bit server
replaced with libgpac0.4.4_0.4.4-0.3ubuntu1~gutsy1_amd64.deb
works properly now.
please update/fix ASAP!
--
MP4Box buffer overflow detected
https://bugs.launchpad.net/bugs/273075
You received this bug notification because you are a member of Ubuntu
Bugs, whi
+1 broken on intrepid 64-bit server
replaced with libgpac0.4.4_0.4.4-0.3ubuntu1~gutsy1_amd64.deb
works properly now.
please update/fix ASAP!
--
MP4Box buffer overflow detected
https://bugs.launchpad.net/bugs/273075
You received this bug notification because you are a member of Ubuntu
Bugs, whi
the reason why only 1 of the 6 seems to be having the
issue. I downgraded the kernel from linux-image-2.6.27-10-server to
linux-image-2.6.27-7-server, still doesn't matter.
I'll pay someone to figure this out ASAP. This is wrecking my hosting
business right now... mike503 AT gmail.com
--
Public bug reported:
(note: mtaylor told me to submit this as a bug)
"skip-name-resolve" is not included in /etc/mysql/my.cnf, and probably
should be.
** Affects: mysql-dfsg-5.0 (Ubuntu)
Importance: Undecided
Status: New
--
skip-name-resolve is not included in default my.cnf
http
Not afaik. I'm still waiting. I have a custom compiled gpac 0.4.5-1 and
it works fine against the ubuntu libraries, but I had to compile the
gpac (mp4box) myself. It seems to have fixed it.
libgpac-dev 0.4.4-0.3ubuntu4
libgpac0.4.40.4.4-0.3ubuntu4
my-gpac0.4.5-1
Can this package's spo
I don't understand what xmlrpc has to do with gpac... at least the gpac
package, maybe the gpac libs need it, but that's quite odd.
Sounds like the xmlrpc bug has a fix already for it, so why can't we get
both of them pushed through?
--
MP4Box buffer overflow detected
https://bugs.launchpad.net/
Does not work using VMware server 1.0.9 downloaded from vmware directly.
It compiles, using the vmware-any-any-update or vmware-update for the
kernel and such. However, remote connectivity still triggers the PAM
errors.
I have tried on both 9.04 and 8.10 Ubuntu 64-bit, roughly the same
message on
I will say this
I tried 9.04, could not get it to work. Same with 8.10.
However, I did 8.04.2, and it worked, out of the box, without even
requiring the vmware patch / vmware-update-update thingy. I can connect
remotely to it too, without tweaking pam at all even.
This is vmware server 1.0.9 dow
Actually, can you give us the download location of the .deb? Sorry, I
don't know where to find it.
I will at least diff it, see if I am comfortable doing it, and possibly
try it out.
--
gitosis not working after upgrade to 9.04
https://bugs.launchpad.net/bugs/368895
You received this bug notific
Please someone check this out!
I would try, but my gitosis repository is actually -extremely-
important, and if I try this out on production I would be raked over hot
coals (and I have no development setup to try this on)
It should be a -very- simple fix to test.
--
gitosis not working after up
Here is the debianb ug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508469
And yes - changing the shebang to force python2.5 fixes this, thank god.
This should be marked as CRITICAL as out of the box gitosis is broken on
jaunty now.
I am not sure if the fix to the debian package will resolv
Here is the debian bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508469
And yes - changing the shebang to force python2.5 fixes this, thank god.
This should be marked as CRITICAL as out of the box gitosis is broken on
jaunty now.
I am not sure if the fix to the debian package will resolv
alright. then how do we push the priority on this to be officially in
the ubuntu repo?
--
gitosis not working after upgrade to 9.04
https://bugs.launchpad.net/bugs/368895
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
I don't want to be rude but there is a workaround out there. Is it that
hard to get it fixed and in the repo? I'd do it myself if these packages
weren't such a pain and I had access. Right now I'm stuck in limbo
having to hold back certain packages and having to compile some on my
own...
I wish th
This has been an issue for me for a long time using intrepid too.
I have not upgraded to jaunty yet.
Kernel versions on only *one* machine seem to not start nlockmgr.
broken machine:
[r...@lvs01 etc]# rpcinfo -p
program vers proto port
102 tcp111 portmapper
100024
This has been an issue for me for a long time using intrepid too.
I have not upgraded to jaunty yet.
Kernel versions on only *one* machine seem to not start nlockmgr.
broken machine:
[r...@lvs01 etc]# rpcinfo -p
program vers proto port
102 tcp111 portmapper
100024
This has been an issue for me for a long time using intrepid too.
I have not upgraded to jaunty yet.
Kernel versions on only *one* machine seem to not start nlockmgr.
broken machine:
[r...@lvs01 etc]# rpcinfo -p
program vers proto port
102 tcp111 portmapper
100024
I'm using the latest Intrepid packages of everything. NFS seems to work
great on everything but one box and one box only, still. Using the
"nolock" mount flag workaround appeared to fix it at first, but wound up
freezing up again after a while.
I had to go back to using 2.6.24-16-server on that on
Jorge: that bug is marked as fixed, and the only bug that I can tell
from the gitosis package in 9.04 is the shebang. Changing that by itself
manually has everything working properly still.
According to all the other notes the Debian package works great too, not
sure why it can't be promoted/etc
Public bug reported:
Binary package hint: collectd
On all my machines it seems to be using a TON of cpu, which in turn
actually makes it somewhat useless for monitoring :)
root 5110 50.4 0.0 300960 2092 ?Sl 13:31 188:36
collectd -C /etc/collectd/collectd.conf -f
These are quad-
i noticed my load was over 1.0 - which is odd. this machine shouldn't be
showing much load. i realized collectd was running on this one.
18:30:55 up 7:54, 2 users, load average: 1.07, 0.89, 0.78
killall -9 collectd
18:31:46 up 7:55, 2 users, load average: 1.05, 0.92, 0.79
18:33:10 up 7
It should just be a standard Ubuntu collectd.conf... and no, it's only
reporting for the host its running on.
[EMAIL PROTECTED] nginx]# grep -v ^# /etc/collectd/collectd.conf
FQDNLookup true
LoadPlugin battery
LoadPlugin cpu
LoadPlugin df
LoadPlugin disk
LoadPlugin entropy
LoadPlugin interface
L
22 matches
Mail list logo
