[Bug 1227173] Re: On every startup Onboard asks for enabling accessibility
I observe the same behaviour as in comment #19. Clean installation 13.10x64, up to date. cat .xsession-errors Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: at-spi2-registryd uruchamia się ponownie zbyt szybko, zatrzymano and .xsession-errors.oldcat .xsession-errors.old Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie init: at-spi2-registryd uruchamia się ponownie zbyt szybko, zatrzymano init: Proces gnome-settings-daemon main (1834) został zakończony ze stanem 1 init: Proces gnome-session main (1910) został zakończony ze stanem 1 init: Proces unity-panel-service main (1922) został zakończony ze stanem 1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1227173 Title: On every startup Onboard asks for enabling accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1227173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 764358] [NEW] Unable to select data entry rows on initial set up
Public bug reported: Binary package hint: evolution Ubuntu 10.10 Netbook Acer aspire One On trying to set up the Evolution software I found I could not click on the data entry rows on mouse over. The whole pane jumped, I guess it could not fit on the whole screen. What I had to do was rapidly click to get out of the set up stage entering data where i could and then once it had finished I was able to go back and edit the account settings. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: evolution 2.30.3-1ubuntu7.3 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic i686 Architecture: i386 Date: Mon Apr 18 09:10:33 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcEnviron: SHELL=/bin/bash LANG=en_GB.utf8 SourcePackage: evolution ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/764358 Title: Unable to select data entry rows on initial set up -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 764358] Re: Unable to select data entry rows on initial set up
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/764358 Title: Unable to select data entry rows on initial set up -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 151536] Re: Hangs on login and uses 100% cpu
well one of my pc doesnt hang on login, but evolution-data-(server i guess) process is topping 100% of cpu power, when i do evolution --force-shutdown, everything gets back to normal. im on 8.04beta. Maybe it has something to do with wireless card ? -- Hangs on login and uses 100% cpu https://bugs.launchpad.net/bugs/151536 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 204623] Re: evolution-data-server-2.22 high cpu utilization
after fresh install on one of my pc's the problem occurrs too - but only on one of them... the one with wireless pc ( i saw ppl mentioning wireless connection in other reports so i guess it may be important) -- evolution-data-server-2.22 high cpu utilization https://bugs.launchpad.net/bugs/204623 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 187383] Re: System monitor causes Xorg to consume 100% CPU
can also confirm the bug on 2 pc one running 8.04beta with gf 8800gts other one is running beta on ati radeon 9600pro. -- System monitor causes Xorg to consume 100% CPU https://bugs.launchpad.net/bugs/187383 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
