Is anyone interested at looking at this? The segfault is most certainly
a high importance bug and makes this package unusable. I'm having to
resort to using mayavi2 which is not nearly as usable. I also note that
Debian mayavi works fine, which adds a basis for comparison.
--
mayavi segfaults on
** Attachment added: "gdb backtrace"
http://launchpadlibrarian.net/26076040/gdb-bt.txt
--
mayavi segfaults on startup
https://bugs.launchpad.net/bugs/368651
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: mayavi
I am using Ubuntu 9.04, i386. Mayavi package version 1.5-5. Upon
attempting to start mayavi with no command line options, mayavi
segfaults. I've also observed this on a 64-bit installation as well.
I've attached a gdb backtrace which indicates the
Public bug reported:
Binary package hint: ntp
It appears that ntpd synchronises the clock when starting, but then
fails to continue to update the time. I've also found my syslog is
filled with these messages from ntpd:
Apr 25 21:11:26 nott ntpd[1121]: bind() fd 22, family 10, port 123, scope 2,
Some info from apport:
ProblemType: Bug
Architecture: i386
Date: Sun Apr 25 22:17:54 2010
Dependencies:
adduser 3.110ubuntu7
base-files 5.0.0ubuntu7
base-passwd 3.5.21
coreutils 7.4-2ubuntu1
debconf 1.5.27ubuntu2
debconf-i18n 1.5.27ubuntu2
debianutils 2.30ubuntu3
dpkg 1.15.4ubuntu2.1
find
I'm running 10.04 and have had no issues. This bug specifically relates
to to the issue that was caused by a broken upstart config file.
Checking the source package right now, I see that the problem causing
this bug is still fixed. Can I suggest you open a different bug against
runit if you still c
I've since upgraded to Lucid Lynx and am unable to reproduce.
--
ntpd constantly complains about being unable to create socket
https://bugs.launchpad.net/bugs/569919
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
The version in karmic-proposed works fine for me.
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
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
https:/
Regardless, we seem to have a fix and Karmic's been released. Is there
someway we can get this fix pushed to the package?
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I'm having difficulty understanding what this script accomplishes. If it
it co-exists with the existing init script, then when
'/etc/init.d/resolvconf start' does finally run, ${RUNDIR}/interface
will be deleted again, which is not what we wanted.
If it's meant to act as a replacement for the star
Ulf Klose,
the 2.0.0-1ubuntu3.1 package does precisely that. It defines a new
config file with the runlevels on one line.
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I can confirm this bug appearing on an i386 karmic install upgraded from
jaunty.
On my system, editing /etc/init/runsvdir.conf so that
start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5
was replaced by
start on runlevel [2345]
seems to have fixed it.
--
runsvdir
Without a full specification of the conf file, it's impossible to say
for certain. I couldn't find one, but I did find this:
http://upstart.ubuntu.com/wiki/ComplexEventConfig?highlight=((CategorySpec))
which suggests with the foo and bar example that multiple "start on"
lines should be supported.
Public bug reported:
Binary package hint: udev
For earlier kernels, dvb devices will be given names of the format
/dev/dvb0.dvr0 instead of /dev/dvb/adapter0/dvr0. This effectively makes
the dvb devices useless as nothing expects to find them in those
locations.
This udev rule provides a workaro
Public bug reported:
Binary package hint: udev
Similar to bug #460388, changes to udev cause issues when karmic is
used with earlier kernels. Using a 2.6.18-16-generic kernel (latest one
I could find before the one in karmic) under karmic, I was unable to get
the sound card devices to appear wit
Just to note, running /etc/init.d/networking restart will have the same
effect. I'm now using karmic, and due to an ordering issue between
resolvconf and networking startup I find myself having to restart
networking just so that machine has the correct DNS settings then
killing arpwatch.
--
arpwa
** Tags added: packaging
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
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
https://lists.ubuntu.com/mailman
Impact: runit is a collection of tools for process supervison. The bug
causes runsvdir not to start. This causes all services managed by runit
not to start defeating the entire purpose of the tool.
Patch Description: The bug appears to occur because of upstart not
accepting multiple "start on runl
As this bug seems to have reappeared in maverick, and it's also
affecting me (again) I've changed its status to incomplete.
** Changed in: ntp (Ubuntu)
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
My last message didn't get a reply, so I've prepared a debdiff against
the package currently in precise. It incorporates the name clash fix, as
well as one for building with the -Werror=format-security flag which I
believe may occur under Ubuntu.
--
You received this bug notification because you
Debdiff attached to this comment. Unfortunately, I don't have a
"precise" system to verify compilation on.
** Attachment added: "monotone_1.0-3_to_1.0-3ubuntu1.debdiff.gz"
https://bugs.launchpad.net/ubuntu/+source/monotone/+bug/934977/+attachment/2937816/+files/monotone_1.0-3_to_1.0-3ubuntu1.d
Certainly. Can you point me to an appropriate wiki page telling me
where/how to upload a revised version? From your last messafe, I assume
it should be numbered 1.0-3ubuntu1 but I've noticed different numbering
conventions on whether the fix is confirmed valid, etc.
--
You received this bug notif
So, the issue is apparently already fixed in upstream development by the
following commit:
https://code.monotone.ca/p/monotone/source/commit/da62cad10eda55aa233ac124273f3db4f541137a/
So either that can be used to build a patch, or if people prefer I could
have a go at getting a version with this
I've filed this bug upstream here
https://code.monotone.ca/p/monotone/issues/203/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/934977
Title:
monotone version 1.0-3 FTBFS on i386 in precise
To mana
monotone 1.0-2ubuntu0.1 with libbotan1.8.13 1.8.13-1.1 confirmed working
here as well.
Francis
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/882265
Title:
libbotan-1.8.13.so was shipped in libbotan
At the time of writing, I still don't seem to be able to find the
updated botan in oneiric-proposed. Is it just being slow to build?
Using "http://archive.ubuntu.com/ubuntu oneiric-proposed main restricted
universe multiverse" on an amd64 system.
--
You received this bug notification because you
Are you actually using the monotone-server package?
--
package monotone-server 0.40-7 failed to install/upgrade: subprocess
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/671022
You received this bug notification because you are a member of Ubuntu
Bugs, whi
It's possible /var/run is being erased on boot or placed in a tmpfs
filesystem which is a bug that was fixed in the monotone packaging a
while back.
Try:
mkdir /var/run/monotone
dpkg --configure -a
as root obviously.
--
package monotone-server 0.40-7 failed to install/upgrade: subprocess
post
monotone-viz uses to communicate
with it has changed. This means the current version of monotone-viz in maverick
is useless with the current version of monotone in there (0.47-2).
Changelog entries since current maverick version 1.0.2-1:
monotone-viz (1.0.2-2) unstable; urgency=low
[Francis Russell
I've created a debdiff against the version of runit in maverick that
should fix this issue. Building and testing the modified package would
be appreciated.
** Patch added: "runit_2.1.1-4ubuntu2.debdiff"
http://launchpadlibrarian.net/52846785/runit_2.1.1-4ubuntu2.debdiff
--
runit doesn't stop
I've added a debdiff that should fix this issue here:
https://bugs.launchpad.net/ubuntu/+source/runit/+bug/245728
It's against the runit source package in maverick. Any testing or
feedback would be appreciated.
--
does not terminate at computer shutdown
https://bugs.launchpad.net/bugs/539567
Yo
I've added a debdiff that should fix this issue here:
https://bugs.launchpad.net/ubuntu/+source/runit/+bug/245728
It's against the runit source package in maverick. Can you confirm that
the runsvdir process itself was still active in single user mode? The
current package behaviour should have res
Hi there,
I was wondering if you were still able to replicate this problem in
lucid? The current behaviour looks like it should result in the runsv
processes remaining but the runsvdir process being killed.
I've added a debdiff against the runit source package in maverick here:
https://bugs.laun
Hi,
I've revised the patch slightly because it didn't work properly when the
/etc/service folder used symlinks. Also, there appears to be no benefit
to using both pre-stop and post-stop scripts compared to just telling
the runsv processes to force-shutdown after the runsvdir process is
killed.
**
34 matches
Mail list logo
