[Bug 512200] Re: LXC does not work with lucid host and lucid container
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 see the container name next to the process, like this: c...@ph1 ~ $ lxc-ps --name guest-personal-tony CONTAINERPID TTY TIME CMD guest-personal-tony 4281 ?00:00:01 init guest-personal-tony 4318 ?00:00:00 syslog-ng guest-personal-tony 4319 ?00:00:00 syslog-ng guest-personal-tony 4370 ?00:00:00 crond guest-personal-tony 5768 pts/300:00:00 login guest-personal-tony 5769 pts/300:00:00 bash guest-personal-tony 25747 pts/300:00:00 su guest-personal-tony 25748 pts/300:00:00 bash guest-personal-tony 25851 pts/300:15:27 python guest-personal-tony 31858 ?00:00:00 dhcpcd guest-personal-tony 32503 ?00:00:00 git-daemon another way of seeing the processes is to look at the cgroup itself: c...@ph1 ~ $ cat /vps/var/cgroup/guest-personal-tony/tasks you will see a list of pids running within this cgroup cgroup is a psuedo filesystem, and everything you can do with containers/LXC can be managed by manipulating/echoing values into the files within a mounted cgroup. if you create a folder in a cgroup, you effectively begin a hierarchy of groups/aggregated processes, each with their own limits; notice that once you make a folder in a mounted cgroup, all the device files automagically appear inside it, ready to be manipulated. each process on the system must belong to one and only one node in the hierarchy. read this for a better understanding: http://www.mjmwired.net/kernel/Documentation/cgroups.txt to use lxc-console, you must enable tty's inside the container with this configuration option: lxc.tty = N where N is the number of tty's you want the container to have. lxc-* tools will connect a pty in the host to a tty in the container. the container is responsible for runny a getty or some kind of handler on the tty. if you enable 3 tty's, you can lxc-console into the container 3 independent times. i use an autologin binary and some agetty options to autologin as root anyone entering from the host. -- LXC does not work with lucid host and lucid container https://bugs.launchpad.net/bugs/512200 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/listinfo/ubuntu-bugs
[Bug 512200] Re: LXC does not work with lucid host and lucid container
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 for interfaces that are DHCP based on a bridge. i tried setting the bridge forward delay to zero: brctl setfd bridge name 0 but that doesn't seem to help, and i'm still investigating this. -- LXC does not work with lucid host and lucid container https://bugs.launchpad.net/bugs/512200 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/listinfo/ubuntu-bugs
[Bug 512200] Re: LXC does not work with lucid host and lucid container
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), and not lxc-start itself -- LXC does not work with lucid host and lucid container https://bugs.launchpad.net/bugs/512200 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/listinfo/ubuntu-bugs
[Bug 512200] Re: LXC does not work with lucid host and lucid container
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 should die, unless it was pid one in the container, then it will need a kill -9. after that you can: $ rmdir /cgroup/ubuntu-lucid so long as there are no more nested directories under /cgroup/ubuntu- lucid. -- LXC does not work with lucid host and lucid container https://bugs.launchpad.net/bugs/512200 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/listinfo/ubuntu-bugs
[Bug 512200] Re: LXC does not work with lucid host and lucid container
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 file is shared with the host (network stack, hostname, resources, etc) specifically in the rootfs case, newer revisions of lxc-* tools will not even allow you to get as far as you did (sharing the rootfs doesnt make sense for a system container). see this thread for more details: http://ubuntuforums.org/showthread.php?t=1382823 specifically this post: http://ubuntuforums.org/showpost.php?p=8736281postcount=10 where i referenced this bug report. -- LXC does not work with lucid host and lucid container https://bugs.launchpad.net/bugs/512200 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/listinfo/ubuntu-bugs
[Bug 457688] Re: libboost-python1.38 issues with __doc__ property in Python = 2.6.3
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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 457688] Re: libboost-python1.38 issues with __doc__ property in Python = 2.6.3
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 439511] Re: added IPv4 routes/settings are not saved
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 439511] Re: added IPv4 routes/settings are not saved
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112948] Re: Ekiga hangs when using pulseaudio
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 these symptoms: http://osdir.com/ml/debian-bugs-dist/2009-09/msg09233.html when pulseaudio is running, many operations within ekiga after connecting to a call result in the program hanging and consuming 100% CPU even just trying to open the preferences. -- Ekiga hangs when using pulseaudio https://bugs.launchpad.net/bugs/112948 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/listinfo/ubuntu-bugs
[Bug 439511] Re: added IPv4 routes/settings are not saved
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 anyone else!! (i also use an extensive /etc/hosts which is why i can use names like db1/db2/etc) START SCRIPT #!/bin/sh -e # Fix VPN IFACE=ppp0 if [ x$IFACE = x$1 ]; then case $2 in vpn-up) # reinstate the default gateway /sbin/route del default ppp0 /sbin/route add default gw 192.168.42.1 eth0 # add the network routes /sbin/route add -net 10.0.0.0 netmask 255.0.0.0 dev ppp0 /sbin/route add -net 192.168.0.0 netmask 255.255.255.0 dev ppp0 /sbin/route add -net 192.168.7.0 netmask 255.255.255.0 dev ppp0 # add the host routes /sbin/route add -net db1 netmask 255.255.255.255 dev ppp0 /sbin/route add -net db2 netmask 255.255.255.255 dev ppp0 /sbin/route add -net serv1 netmask 255.255.255.255 dev ppp0 ;; esac fi END SCRIPT -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 439511] [NEW] added IPv4 routes/settings are not saved
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 REPRODUCE: 1) click nm-applet, VPN Connections Configure VPN 2) add/edit a connection 3) click IPv4 tab Routes... 4) add a route, i added: 10.0.0.0 255.0.0.0 10.0.0.1 5) check any boxes, i checked Use this connection only for resources on its network 6) click OK, at this point if you click Routes... again, it will still be there 7) click Apply 8) go back into IPv4 Routes... for that connection 9) everything you just set is not there ** Affects: network-manager-pptp (Ubuntu) Importance: Undecided Status: New -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 439511] Re: added IPv4 routes/settings are not saved
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 408663] Re: python2.6 (python-visual) crashed with SIGSEGV in __cxa_allocate_exception()
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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 408663] Re: python2.6 (python-visual) crashed with SIGSEGV in __cxa_allocate_exception()
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 408663] Re: python2.6 (python-visual) crashed with SIGSEGV in __cxa_allocate_exception()
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, and make sure it works under python2.6; the ubuntu package currently segfaults in 2.5 also will probably compare the package contents as well -- 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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 408663] Re: python2.6 (python-visual) crashed with SIGSEGV in __cxa_allocate_exception()
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 perfectly. however, i could not get that package to work with a vanilla jaunty install, nor the official package on a vanilla karmic install. same result/sigsegv on both. tried the build-deps thinking maybe the package was simply missing something in the deps, even tried rebuilding the package that way, same result, segfault. since the guy that made those packages got it to work, it seems there is just a missing dependency or something. -- 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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 408663] Re: python2.6 (python-visual) crashed with SIGSEGV in __cxa_allocate_exception()
** 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: ProcStatus.txt http://launchpadlibrarian.net/29853422/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/29853423/Registers.txt ** Attachment added: Stacktrace.txt http://launchpadlibrarian.net/29853424/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://launchpadlibrarian.net/29853425/ThreadStacktrace.txt ** Visibility changed to: Public -- 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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263255] Re: nm-connection-editor crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
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() https://bugs.launchpad.net/bugs/263255 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/listinfo/ubuntu-bugs
[Bug 218887] Re: pidgin-libnotify don't work anymore
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: libnotify-Message: Unable to get session bus: Failed to execute dbus- launch to autolaunch D-Bus session not sure what the issue is but i just replace /usr/bin/pidgin with a script, and renamed pidgin to pidgin.real hope this helps. -- pidgin-libnotify don't work anymore https://bugs.launchpad.net/bugs/218887 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/listinfo/ubuntu-bugs
[Bug 218887] Re: pidgin-libnotify don't work anymore
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128803] Re: [Gutsy] very slow gnome startup
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 serious ones i have yet to figure out. the nice part about problems is it forces you to get personal with your machine and actually learn what the computer is doing rather than simply looking at a splash screen? if you can, put ubuntu back on the machine, all updates, then make a bootchart.. that little program was very useful in diagnosing problems because it visually attaches the time elapsed to individual processes. it has allowed me to explore the scripts in my system i did not even know about. sudo apt-get install bootchart the charts (pictures) will be in /var/log/bootchart/ make one of those during the 5 minute wait and maybe we can visually see the culprit in your specific installation. another possibility would be to disable usplash altogether, so you can see the output instead? an easy way to accomplish this: sudo apt-get install startupmanager then look under System Settings Start-up Manager good luck to ya -- [Gutsy] very slow gnome startup https://bugs.launchpad.net/bugs/128803 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 177570] Re: [hardy] two batteries display when left clicking on g-p-m
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 left clicking on g-p-m https://bugs.launchpad.net/bugs/177570 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178057] Re: [Hardy] Login sound plays during install
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 added everytime the login sound played. -- [Hardy] Login sound plays during install https://bugs.launchpad.net/bugs/178057 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128803] Re: [Gutsy] very slow gnome startup
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 now, nearly half the time. very nice thank you. -- [Gutsy] very slow gnome startup https://bugs.launchpad.net/bugs/128803 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128803] Re: [Gutsy] very slow gnome startup
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 have read about a bug with compiz that kills the (gnome?)panels as i described above--i still think this may be an underlying issue for many. on my specific machine, i can tell that all applets/panels are loading, but i just cant see ANYTHING until they are all completely loaded. modified bootcharts confirm this. i have read that others compiling the most recent versions of compiz do not encounter this either. i installed gnome over the top of xubuntu and still the problem persists. i may compile compiz from git and see if that takes care of it, not worried about upgrading to hardy, i always do a clean install. peace -- [Gutsy] very slow gnome startup https://bugs.launchpad.net/bugs/128803 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128803] Re: [Gutsy] very slow gnome startup
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 to virgin feisty install until hardy final. -- [Gutsy] very slow gnome startup https://bugs.launchpad.net/bugs/128803 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128803] Re: [Gutsy] very slow gnome startup
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 final with all updates as of 10 minutes ago. before i say anything about compiz/etc., i wanted to ask/point out a few things. first, while looking into this problem i noticed others having their gui desktop completely freeze after enabling/disabling certain startup apps and then attempting to press the logout button; additionally, some experienced this after mysterious errors earlier in the day but did not notice a problem until they tried to log out. i encountered this very thing when attempting to barebone my session down to essentials and pinpoint this 'slow' boot reason. i disabled all plugins to compiz using CCSM, except 'dbus' and 'workarounds'--additionally i disabled ALL startup options in PreferencesSessions (i will brief upon another possible bug regarding this in a moment). under this config i still got a brief moment (always2sec) of gnome-panels before everything goes black for 15-20 seconds. HOWEVER, when i tried to reboot using the logout button, my computer locked up. the source of the problem was due to 'Power Manager' being disabled in PreferencesSessions. my guess is the logout button is trying to query said program to try and determine if 'hibernate' or 'suspend' should be an available option on the logout screen. this bug is reproducible simply by disabling 'Power Manager' under PreferencesSessions, rebooting, and attempting to log out using the gui button. second, even though i had disabled ALL startup apps except 'Power Manager' , bootcharts would sometimes show these apps initiating. this may have been because i hard reset my laptop the time before because of the logout bug i described above. also i could not figure out how to disable the deskbar applet at all, but i am confident this has nothing to do with our issues. third, not related but someone might want to file a bug rep. in the appropriate place, nm-applet will occasionally place the 'Wireless key needed' dialog on the desktop of another user logged in, instead of the current user. i was logged in as a regular/desktop user and the dialog appeared on the poweruser that was logged in. i had to switch users to enter the WEP key. fourth, i noticed this EVERY time in compiz and only once with metacity; xsession will try and initialize gnome-volume-manager and gnome-power-manager only to by terminated within less than a second and reinitialized by either init or getty. bootchart: http://sweetsinsemilla.googlepages.com/compizdbus-workarounds-pwrMAN-slow_a.png which leads to my final ?'ion. fifth, why do some bootcharts show init starting many gnome-* apps, and other show getty? i viewed subsequent charts and there appeared to be no reason for the swapping...not sure the repercussions of this. lastly, gnome-settings-daemon and gnome-vfs-daemon will sometimes be initialized by dbus-daemon, other times by getty, and still others by init... does this even matter? this behaving was very sporadic in compiz but very consistent with metacity. some bootcharts: metacity: http://sweetsinsemilla.googlepages.com/metacity-pwrMAN-quick_and_nofreeze.png http://sweetsinsemilla.googlepages.com/metacity-noapps-quick_but_freeze.png http://sweetsinsemilla.googlepages.com/gutsy-20071115-2.png compiz: http://sweetsinsemilla.googlepages.com/compizdefault_plugins-pwrMAN-slow_an.png http://sweetsinsemilla.googlepages.com/gutsy-20071115-7.png (see bootchart @ #4) IN SHORT(kinda): i discovered many others to be having problems with the ubuntu package of compiz. i think the wrapper script 'compiz' is sending the wrong params to 'compiz.real'. i had no problems whatsoever when using metacity, with the exception of the logout bug, but that is independent of the window manager. all bootcharts showed the same boot times for both metacity and compiz (compiz a few sec longer for obvious reasons). basically, all my apps were loading and my desktop was there, i just couldnt see it until something 'snapped' it back, about the time it was completely loaded. the reason the gnome-panels showed for a brief period was because the window manager (compiz.real) had not yet been started. notice on that bootchart above, compiz.real starts less than 2 seconds after gnome-panel. i think this may be the problem for everyones 'slow startup'. its not really slow, compiz.real is being mis configured by the wrapper script (compiz) or something along that line, and the gui environment is temporarily killed when compiz.real is actualy initiated. sorry for the lengthy post; i want to solve this ;) -- [Gutsy] very slow gnome startup https://bugs.launchpad.net/bugs/128803 You received this bug notification because you are a member of Ubuntu Bugs, which
[Bug 128803] Re: [Gutsy] very slow gnome startup
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 output and also xsession- errors, is that my first error occurs JUST after gnome-panel loads for the first time (excluding a setuid error thru gtk+ that seems to arise from dbus?). on my laptop specifically (T43)---right after i log in--- the top and bottom gnome-panels load very quickly (no BG image yet), just like feisty. however, before they are populated with any icons, the screen/mouse flickers and the panels disappear. this is when i experience about 10-20 seconds of heavy disk i/o time as others have described. the interesting part about all that is the fact that nautilus is the very first thing that is loaded after the panels. others have claimed no problems when using xcfe or kde, so this (nautilus) seems to be contributing somehow? also, i have since read about similar issues regarding nautilus and gutsy specifically that did not exist in feisty. until then. -- [Gutsy] very slow gnome startup https://bugs.launchpad.net/bugs/128803 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128803] Re: [Gutsy] very slow gnome startup
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 T43 during the 15+sec freeze period. i recorded 85 sec. of time, approximately 65 beyond the point where gdm is initialized. like i said before, blank gnome-panels will come up after about 3-4 seconds (@36sec), then disappear almost IMMEDIATELY (notice how nautilus is initialized RIGHT after the panels in the chart). the heavy disk i/o seems to correlate VERY nicely with nautilus activity(until 51sec). Although the gap also matches well with dhcdbd activity-- --i tried a little fix someone posted about automatically setting resolv.conf to 0.0.0.0 to avoid dns issues...no change. am i waiting on my wireless card, before loading background/panel apps/etc. in this situation? im trying to gather info from the chart but its somewhat cryptic to my novice eyes but i hope it will be of some use. here is a link in case my attachment doesnt work: http://sweetsinsemilla.googlepages.com/gutsy-20071113-1.png ** Attachment added: bootchart for 85sec--beyond gdm http://launchpadlibrarian.net/10350656/gutsy-20071113-1.png -- [Gutsy] very slow gnome startup https://bugs.launchpad.net/bugs/128803 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128803] Re: [Gutsy] very slow gnome startup
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 nautilus...the pink areas are
where nautilus seems to be WAITING due to high disk i/o. the culprit
here seems to be some kind of change in the networking arena from feisty
to gutsy...be somewheres in nm-applet/dhcdbd/NetworkManager.
figure it out party ppl.
--
[Gutsy] very slow gnome startup
https://bugs.launchpad.net/bugs/128803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
