Thomas Bechtold and friends, the lxc-ps command i think is buggy, and
the -n flag doesnt work, try using --name instead. the output you are
seeing is NOT inside the container, it is the same as what you would see
if you simply typed ps. if the process was running in a
container/cgroup you would
bodhi.zazen, im not sure if ubuntu has the latest lxc-* tools, the -d
problem you having could be related to that, because i run all my
containers with that option. however, i have noticed my container's (i
can't confirm this for ubuntu based containers yet) networking does not
come up right away
also this probably should be handled more gracfully on lxc-*'s part, but
the resource busy is a consequence of killing the lxc-start process,
and thus the cgroups dont get cleanup up properly. make sure you kill
the process lxc-start STARTED, i.e. /sbin/init (it will be the pid+1 of
lxc-start),
to elaborate on the resource busy issue... you need to remove/kill the
running processes from the cgroup in order to remove the folder.
view the tasks with:
$ cat /cgroup/ubuntu-lucid/tasks
all the pids assigned to this cgroup
$ kill -15 all the pids assigned to above cgroup
most processes
there could be other problems, but you need to define a config file with
lxc-create (the -f option). specifically you need the option:
lxc.rootfs = wherever you just debootstrapped
to be defined. otherwise, the rootfs will be the shared with the host.
anything that is not defined in the config
i can confirm that building the trunk boost libraries solves this issue.
boost 1.40.0rc1 was not sufficient
--
libboost-python1.38 issues with __doc__ property in Python = 2.6.3
https://bugs.launchpad.net/bugs/457688
You received this bug notification because you are a member of Ubuntu
Bugs,
additionally, all demos in python-visual 5.11 and 5.13 work fine with
boost svn, so this is most definately not a vpython issue.
--
libboost-python1.38 issues with __doc__ property in Python = 2.6.3
https://bugs.launchpad.net/bugs/457688
You received this bug notification because you are a
this is confirmed working, thank you
--
added IPv4 routes/settings are not saved
https://bugs.launchpad.net/bugs/439511
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
has this fix been pushed out? i have latest updates and the bug
persists. just making sure.
--
added IPv4 routes/settings are not saved
https://bugs.launchpad.net/bugs/439511
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
im running karmic all updates as of ten minutes ago...
the only way i have been able to get ekiga to work (echo test) is to
kill pulseaudio before starting it. pasuspender -- ekiga doesnt do
the trick. other gnome apps work fine like sound-
recorder/banshee/flash/etc.
additionally, i receive
as a workaround, i am using a script to do this for me. place/name the
script:
/etc/NetworkManager/dispatcher.d/99vpnfix
and chmod +x it. dont forget to edit the interfaces/network
addresses/host addresses/etc to reflect YOUR actual network!! these
values are what i need and don't apply to
Public bug reported:
Binary package hint: network-manager-pptp
this is a fresh Karmic install, x86_64, all updates as of ten minutes
ago.
i use a vpn/pptp connection to connect to work. i am trying to add a
route to the connection via the interface, but it is not saved after
clicking apply
forgot to mention i get the same behavior on my x86 laptop
--
added IPv4 routes/settings are not saved
https://bugs.launchpad.net/bugs/439511
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
same problem, fresh installation on both an x86 laptop and an x86_64
desktop
still segfaults
--
python2.6 (python-visual) crashed with SIGSEGV in __cxa_allocate_exception()
https://bugs.launchpad.net/bugs/408663
You received this bug notification because you are a member of Ubuntu
Bugs, which
probably not a bug against python itself
** Package changed: python2.6 (Ubuntu) = python-visual (Ubuntu)
--
python2.6 (python-visual) crashed with SIGSEGV in __cxa_allocate_exception()
https://bugs.launchpad.net/bugs/408663
You received this bug notification because you are a member of Ubuntu
since no deps had been intoduced, i force installed the package from
Debian (the Debian package does not install to python 2.6 dirs), and ran
visual-python under python2.5
worked perfectly on ubuntu karmic
i will rebuild the package from debian to mirror the dependencies in the
ubuntu package,
also according to people on the mailing list this package:
https://gutefee.massey.ac.nz/moin/Python/3D?action=AttachFiledo=viewtarget
=python-visual_5.11-1_i386.deb
was built from karmic sources with build-dep/buildpackage'ed into a
working jaunty package for himself, and he claims it works
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/29853419/CoreDump.gz
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/29853420/Disassembly.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/29853421/ProcMaps.txt
** Attachment added:
affirmative same result.
although i was trying to open/configure custom routes for a NOT YET
SAVED pptp connection.
nm-applet crashes with sigseg
intrepid beta i386 full updated as of 10/6
--
nm-connection-editor crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
i had this annoying problem for weeks. i did however, after much
searching, find a fix--
/usr/bin/dbus-launch /usr/bin/pidgin
starting pidgin in that way will all libnotify-plugin to work as expected. the
error when trying to enable libnotify while running from terminal is:
forgot to mention... seems to work fine in gnome or xfce AFTER
installing gnome. i only get this issue after a fresh install of
xubuntu hardy.
--
pidgin-libnotify don't work anymore
https://bugs.launchpad.net/bugs/218887
You received this bug notification because you are a member of Ubuntu
if you want it free youve got to be willing to spend some time wrestling
with it..
luckily ubuntu has worked very well on the several machines i have
installed it on, for myself and others. however every single one of
them had quirks, some of which took a LONG time to figure out, and other
less
mine also shows two batteries as some have already confirmed.
however, it is interesting to note that on the live cd i started with
two batteries, but by the end of the install power-manager was reporting
six separate batteries, all with different charges.
--
[hardy] two batteries display when
i can confirm this for hardy alpha 4 on IBM T43 laptop.
also, after each sound was played, additional entries were added in the
playback sections of Preferences Sound. the added entries were Intel
ICH6, and Intel ICH6 IEC 958, which i guess correspond to my specific
card. another entry was
agreed that tip/link from Jean-François worked very well.
i still get the flashing gnome-panels and am seeking a solution to that,
the readahead hack sped everything up.. i would make a bootchart but i
have changed things, but the blackout after my gnome-panels dissapears
is less than 10 seconds
i since ditched feisty and went back to messing with gutsy. gutsy is in
all a very good developmental release and i hope to see splendiferous
things from hardy.
this time however i installed xubuntu.
i enabled compiz/emerald/NetworkManager, and have not had any of the
problems described herein.
i just installed hardy alpha 1...problem persists in the same way.
again gnome panels appear right away just like feisty, only to be near
immediately killed, then reappear 10+ seconds later. occurs in the same
way as gutsy, but maybe to be expected since this is only alpha 1.
i will be reverting
ok.
i have been restarting my computer all day testing different
configurations and looking at many, many...many post-gdm bootcharts...
in fact i triggered 2 'force checks' on my laptop so i rebooted at least
60 times haha
anyway, i have a few interesting things to report. i am running Gutsy
i too have a somewhat slow bootup time; nothing to the severity of many
minutes, but still, a significant increase when compared to feisty.
i am running a IBM T43 laptop, and also gutsy is installed on a DELL
INSPIRON B130. same problem with both.
one thing i do notice after looking @ ps
ok.
nice little bootchart program, wouldve been nice if i could have done
this a little easier tho...
anyways i modified the running parameters of the bootchart program so it would
not stop running when it gdm/init.d was processed, that way we could get a look
at what all was happening on my
forgot to add one little thing...soo tired...
i tried disabling gnome-at-visual (in session preferences {assistive
technology/AT}) because the chart showed a strange 2 seconds of zombie
time after login... but this did not do anything. also i seem to have
misinterpreted the chart referring to
31 matches
Mail list logo
