@Al Zhukov, I use g-s-d 2.32.0-0ubuntu3 version from Karl's PPA as well and I
still have this bug with "Different Layouts for different windows" enabled. But
the frequency of bug is much lower - now I see it once per day (actually I
catched it 3 times after g-s-d ubuntu3 version installed). I re
Little update - If I kill g-s-d while bug appears and quickly start it
again, the layout switching still continue. If I wait some time(~20
secs) before starting g-s-d again - the switching gone away. (using
g-s-d 2.32.0-0ubuntu3 now)
And, I agree with some of the previous posters - that's the *sto
I've got this bug again, with gnome-settings-daemon 2.32.0-0ubuntu3. Everything
the same as with unpatched version, occasionally caught, 50-80% CPU usage,
increasing memory usage, fast layouts switching.
I attached to g-s-d process by gdb, but cannot find what info to look without
knowing g-s-d
> I can't use gnome-terminal hotkeys(in particular Ctrl+Shift+C and
> Ctrl+Shift+V) after update,
Do not confirm. Still work for me with gnome-settings-daemon 2.32.0-0ubuntu3
Menu layout switching works(but still issues with menu labels sync).
Will wait a couple of hours for the bug.
As a quick
I second that - the bug still exist (but I got it once, under heavy swapping
and memory usage) and switching layout from menu doesn't work(even more, the
icon image doesn't correspond the selected item in dropdown menu).
I've installed patched g-s-d from the link above and restarted g-s-d.
--
K
@Karl, maybe it helps (or, in contrary, confuses more)) - I succeeded to
trigger it with 'Separate layout for each window' disabled 3 times - and
all 3 times it was a moment of high memory and disk usage(active
swapping actually). Three times with same conditions is a reason to
think it wasn't an o
New update with video of the bug.
I was running the system with '"Use different layouts for different windows"
disabled for a 5 days and everything was fine. So, to reproduce the bug I've
enabled this option again and continued my normal work. The bug have appeared
in a half of an hour and I cap
> But, please note that the kbd indicator applet itself does _NOT_ change, ie
> it says I am using "US" layout even if it's not true!
Another possibility of this is _very_ fast switching, so you even can't
recognize it changes. I saw such high speed switching for flags - it were
cycling so rapid
Little update on "Use different layouts for different windows" disable method -
I've disabled it three days ago, bug seems to gone, but appeared two times -
and both times under the heavy system load. I.e. when CPU and memory usage got
high up to 100% due to some reasons the layouts start switch
@Rich Wales, copied flag icons(from internet) to ~/.icons/flags and set
the option /desktop/gnome/peripherals/keyboard/indicator/showFlags to
true, but I don't think it matters, cause people reported this bug with
text indicator as well.
--
Keyboard layout automatically changes
https://bugs.launc
Yes, not only indicator text/flags does switch, but also layouts are
switching, so if you have, for example two layouts - English and
Russian, with letters 'q' and 'й' on the same key - and want to enter
'qq', the output will be 'qйqййqqййqйqq`. The indicator image(I
use country flags image
I found three duplicates of this bug:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/636619
https://bugs.launchpad.net/ubuntu/+bug/630347
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/633346
In my case(Maverick 10.10, latest updates) I have three la
Sorry, I have to correct myself:
There's no assertion anymore.
Instead, gnome-settings-daemon does load correctly on boot if and only
if there's no monitor connected to the VGA port on boot (notebook).
--
[lucid] gnome-settings-daemon crashed with SIGSEGV in gnome_bg_draw()
https://bugs.launchp
The issue is gone since yesterday (02/17) - gnome-settings-daemon now
runs correctly on boot.
However, it still reports the failed assertion.
--
[lucid] gnome-settings-daemon crashed with SIGSEGV in gnome_bg_draw()
https://bugs.launchpad.net/bugs/522639
You received this bug notification because
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/39267768/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/39267769/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/39267770/Disassembly.txt
** Attachm
Public bug reported:
For a few days now the Gnome desktop shows up in some default style
after booting and I find the following in dmesg:
[ 47.974605] gnome-settings-[1789]: segfault at 7fcb18b12000 ip
7fcb21b1f0c4 sp 7fffd05aa050 error 7 in libgnome-
desktop-2.so.17.0.1[7fcb21b09000+28
** This bug is no longer a duplicate of bug 224636
Asus brightness keys only toggle between the lowest two levels
** Package changed: gnome-power-manager (Ubuntu) => ubuntu
--
display brightness asus; function keys not working
https://bugs.launchpad.net/bugs/368506
You received this bug notif
On karmic alpha 2 the flickering is the same. The brightness keys are reacting
but both keys randomly do nothing (but flickering) or switch with the following
behaviour:
Using the "brightness up" key I randomly get the darkest or the
almost-brightest setting.
With the "brightness down" key I get
This happens on my Asus x5dij, too.
However, i think the issue with the brightness-keys has nothing to do with
gnome-power-manager, since I incidentally discovered a workaround (see
#399675).
Also, setting the brightness by writing to
/sys/devices/virtual/backlight/acpi_video0/brightness works
19 matches
Mail list logo
