[Bug 624087] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()

2010-09-18 Thread MaksimKa
I catch this bug when ejected flash drive without unmounting it. -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED() https://bugs.launchpad.net/bugs/624087 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubunt

[Bug 641440] Re: gnome-settings-daemon consumes too much memory

2010-09-30 Thread MaksimKa
Same here, and when this happens, keyboard layot сhanges randomly, like this: фsввапдfвoвлsзoфіpв -- gnome-settings-daemon consumes too much memory https://bugs.launchpad.net/bugs/641440 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gno

[Bug 641440] Re: gnome-settings-daemon consumes too much memory

2010-09-30 Thread MaksimKa
Also when i am killing gnome-settings-daemon keyboard layots are ok, but theme of gnome is reset to similar as in 10.04 -- gnome-settings-daemon consumes too much memory https://bugs.launchpad.net/bugs/641440 You received this bug notification because you are a member of Ubuntu Desktop Bugs, whic

[Bug 641440] Re: gnome-settings-daemon consumes too much memory

2010-09-30 Thread MaksimKa
Desktop became such : http://img823.imageshack.us/img823/7827/81829395.png -- gnome-settings-daemon consumes too much memory https://bugs.launchpad.net/bugs/641440 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in u

[Bug 625793] Re: Keyboard layout automatically changes + 100% CPU usage [updated]

2010-10-02 Thread MaksimKa
Same here. Also at my side if i kill gnome-settings-daemon and then start it again keyboard layots will be changing again. -- Keyboard layout automatically changes + 100% CPU usage [updated] https://bugs.launchpad.net/bugs/625793 You received this bug notification because you are a member of Ubun

[Bug 641440] Re: gnome-settings-daemon consumes too much memory

2010-10-02 Thread MaksimKa
I think this is a duplicate of https://bugs.launchpad.net/indicator- application/+bug/625793 -- gnome-settings-daemon consumes too much memory https://bugs.launchpad.net/bugs/641440 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-se

[Bug 625793] Re: Keyboard layout automatically changes + 100% CPU usage [updated]

2010-10-04 Thread MaksimKa
Here is video from the TS. I've uploaded it to youtube. Quality is very poor, but still it is posible to see thet keyboard layot switching rapidly. http://www.youtube.com/watch?v=ETePpA5GBUU -- Keyboard layout automatically changes + 100% CPU usage [updated] https://bugs.launchpad.net/bugs/625793

[Bug 625793] Re: Keyboard layout automatically changes + 100% CPU usage [updated]

2010-10-04 Thread MaksimKa
Join to stee1rat. What exact debug info do you need? I am not either developer or maintainer, but i am ready to update the ticket with any info you need. Yesterday i cought this bug when was changing layot in google chromium browser. I can't predict when this happens again. -- Keyboard layout aut

[Bug 625793] Re: Keyboard layout automatically changes + 100% CPU usage [updated]

2010-10-04 Thread MaksimKa
In my case icon isn't changing. It just still on some layot and that's it. (i don't use login window) -- Keyboard layout automatically changes + 100% CPU usage [updated] https://bugs.launchpad.net/bugs/625793 You received this bug notification because you are a member of Ubuntu Desktop Bugs, whic

[Bug 625793] Re: Keyboard layout automatically changes + 100% CPU usage [updated]

2010-10-04 Thread MaksimKa
I just launched the system, opened Empathy and opened some contact. Tried to change layot about 100 times, no result. Then i've opened chromium and changed layot that's it. Or g-s-d was already blocked ( before i pressed ctrl-shift and after launched chromium) or it is has been blocked after i p

[Bug 625793] Re: Keyboard layout automatically changes + 100% CPU usage [updated]

2010-10-04 Thread MaksimKa
also i've started manually g-s-d and each layot changing(or windows changing) it show me this message: mak...@maksim-desktop:~$ Unable to find a synaptics device. (gnome-settings-daemon:2057): libappindicator-CRITICAL **: app_indicator_set_label: assertion `IS_APP_INDICATOR (self)' failed (gnome

[Bug 625793] Re: Regression: Multiple Keyboard Layouts unusable: continuously changes layout + 100% CPU usage [updated]

2010-10-12 Thread MaksimKa
I don't see this update. How much time should pass after you upload it? (Maverick-proposed enabled, and i tried local update server and global update server) -- Regression: Multiple Keyboard Layouts unusable: continuously changes layout + 100% CPU usage [updated] https://bugs.launchpad.net/bugs/

[Bug 625793] Re: Regression: Multiple Keyboard Layouts unusable: continuously changes layout + 100% CPU usage [updated]

2010-10-12 Thread MaksimKa
Thanks Chris, right now i've download the fixed GSD. Will test tomorrow and will update the ticket -- Regression: Multiple Keyboard Layouts unusable: continuously changes layout + 100% CPU usage [updated] https://bugs.launchpad.net/bugs/625793 You received this bug notification because you are a

[Bug 625793] Re: Regression: Multiple Keyboard Layouts unusable: continuously changes layout + 100% CPU usage [updated]

2010-10-14 Thread MaksimKa
@Anton, Same here it often happens when screen is locked. I see layot is USA and tape my pass, but it says wrong password. Then i should change layot again until i see USA. After this i can login. -- Regression: Multiple Keyboard Layouts unusable: continuously changes layout + 100% CPU usage [up

[Bug 144851] Re: gnome-power-manager crashed with SIGSEGV in g_cclosure_marshal_VOID()

2011-07-12 Thread MaksimKa
Fix doesn't work for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/144851 Title: gnome-power-manager crashed with SIGSEGV in g_cclosure_marshal_VOID() To manage n