[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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs,
[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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
