@Kai, you need to remove my repository and run with maverick proposed
@Anton, can you experiment and find more detail here, I think it's not
cycling through them correctly.
--
Regression: Multiple Keyboard Layouts unusable: continuously changes layout +
100% CPU usage [updated]
@Matvei - Read omment #31
Seems to work?
--
Keyboard menu title needlessly has both icon and label
https://bugs.launchpad.net/bugs/620331
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.
--
desktop-bugs
Extender, does that disable layout switching?
--
Keyboard menu title needlessly has both icon and label
https://bugs.launchpad.net/bugs/620331
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.
--
*** This bug is a duplicate of bug 653681 ***
https://bugs.launchpad.net/bugs/653681
** This bug has been marked a duplicate of bug 653681
There are 4 separate applications for configuration of different keyboard
items
* You can subscribe to bug 653681 by following this link:
In order to 'fix' this please follow the instructions here;
https://bugs.launchpad.net/ayatana-ubuntu/+bug/628015/comments/9
this will leave you with just a single icon e.g. [GB]
--
Keyboard menu title needlessly has both icon and label
https://bugs.launchpad.net/bugs/620331
You received this
@Victor after speaking with tedg in august he had assured me that it was
in libindicator but didn't give me a bug number :/ I am certain however
that the bug can't be in gsd because I tried nuking the error in a
variety of ways which all led to either the error going in the opposite
direction off
https://bugs.launchpad.net/ayatana-ubuntu/+bug/584669 is affected by
this bug, this is *partly* worked around by calling
appindicator.set_menu() *AFTER* submenus have been appended to the menu.
However, a bug still exists in that the wrong widget is passed to the
callback and therefore the
When clicking add appointment evolution has to be opened, we can't jump
to the add appointment dialog (which would be nice), if evolution isn't
configured the setup dialog will appear.
The same will result from the change made to the date menu item,
In the end I think this is more of an evolution bug than indicator-
datetime, evolution should respect it's own command line parameters when
opening regardless of whether or not it starts with a wizard.
** Changed in: indicator-datetime (Ubuntu)
Status: New = Opinion
** Changed in:
Public bug reported:
Binary package hint: gnome-power-manager
It seems that gnome power manager has stopped detecting my battery on my
Macbook Pro 5,2
The laptop no-longer reliably responds to lid close events, and there
are probably other related issues
** Affects: gnome-power-manager
Can you tell me if you have menu icons turned on? I've discovered other
leaks associated with that feature.
We don't intend to *ship* it that way, but lots of legacy configuration
has remained static.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Yeah, I realised that this still wasn't fixed a while ago, I'll add it
to my things bug ted about.
--
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/621633
Title:
This seems like it's a bug which has been fixed elsewhere, mterry
pointed me at a couple of branches and I'll add them here.
** Branch linked: lp:~mterry/libappindicator/toggle-state-is-int
** Branch linked: lp:~mterry/appmenu-gtk/toggle-state-is-int
--
You received this bug notification
** Changed in: indicator-application (Ubuntu)
Status: Triaged = In Progress
--
bluetooth devices menu item not working in bluetooth indicator
https://bugs.launchpad.net/bugs/558841
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
after much digging I've managed to determine that this is probably some
kind of race condition between the bluetooth_client_get_model not
returning a fully populated model with all the devices in it and the
subsequent call to device_changed and how the NULL default_iter in there
is used in
Will test with using gobject.connect_after as sometimes it fixes things
like this
--
bluetooth devices menu item not working in bluetooth indicator
https://bugs.launchpad.net/bugs/558841
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Tracing this down even further I find that it might be related to the
same problem present in the ibus indicator in that an object must be
visible to emit signals. If this is the case then this is a deeper
problem related to the dbus menu stuff which requires more digging into.
--
bluetooth
Sure, I'll take a poke at it
--
Untranslated string in menu option of Brasero's tray icon, albeit it's
translated in Launchpad
https://bugs.launchpad.net/bugs/553423
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in ubuntu.
--
Thanks for reporting this one, I had a feeling it *might* happen I'll
have a poke at it.
** Changed in: gnome-settings-daemon (Ubuntu Maverick)
Status: Triaged = In Progress
--
keyboard indicator does not react to layout changes
https://bugs.launchpad.net/bugs/531290
You received this
Sebastien, I've tested this and confirm that *sometimes* the number
doesn't get displayed.
If you switch back and forth enough times it will start displaying the
number too. I'm really not sure why this would happen. I'll dig into it
a little bit further.
Might also be related to
setting with setxkmap breaks the list entirely... This doesn't appear to
be limited to just the app indicators
--
keyboard indicator does not react to layout changes
https://bugs.launchpad.net/bugs/531290
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
@Martin, I have a new patch on the way, which looks a lot better from my
point of view, and it will hook up to external signals and therefore
should work via the keyboard shortcuts. I'll upload this package to my
ppa when I've finished building it.
--
keyboard indicator does not react to layout
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: (unassigned) = Karl Lattimer (karl-qdh)
--
[Maverick] Move keyboard layouts out of the submenu
https://bugs.launchpad.net/bugs/620571
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
/620571 -
FIXED
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/620334 -
FIXED
New patch on the way
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) = Karl Lattimer
(karl-qdh)
** Changed in: ayatana-ubuntu
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Fix Released = In Progress
--
Port the keyboard indicator in gsd to use the app. indicator protocol
https://bugs.launchpad.net/bugs/599844
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Patch added: Updated app indicators patch
https://bugs.launchpad.net/ayatana-ubuntu/+bug/599844/+attachment/1503008/+files/06_use_application_indicator.patch
--
Port the keyboard indicator in gsd to use the app. indicator protocol
https://bugs.launchpad.net/bugs/599844
You received this
This bug has been fixed in:
https://bugs.launchpad.net/ayatana-ubuntu/+bug/599844
The package will be available shortly from the ppa:
https://launchpad.net/~karl-qdh/+archive/ppa
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed = Fix Released
--
[Maverick] Move keyboard
This bug has been fixed in:
https://bugs.launchpad.net/ayatana-ubuntu/+bug/599844
The package will be available shortly from the ppa:
https://launchpad.net/~karl-qdh/+archive/ppa
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Triaged = Fix Released
--
indicator variants in a
This bug has been fixed in:
https://bugs.launchpad.net/ayatana-ubuntu/+bug/599844
The package will be available shortly from the ppa:
https://launchpad.net/~karl-qdh/+archive/ppa
** Changed in: gnome-settings-daemon (Ubuntu Maverick)
Status: In Progress = Fix Released
--
keyboard
The package will be available shortly from the ppa:
https://launchpad.net/~karl-qdh/+archive/ppa
--
Port the keyboard indicator in gsd to use the app. indicator protocol
https://bugs.launchpad.net/bugs/599844
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Update to the patch to use the smallest possible indicator size XXX when
only 3 letter labels are used.
** Patch added: Slight update
https://bugs.launchpad.net/ayatana-ubuntu/+bug/599844/+attachment/1503232/+files/06_use_application_indicator.patch
--
Port the keyboard indicator in gsd to
Vish has already made one that's currently used by ibus as the default
icon, having two identical icons may end up being confusing if someone
uses both. We've got a further discussion about the icon here;
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/620331
--
Port the
This is an updated patch which *kinda* fixes the remaining problem.
Instead of hiding/showing the menu item, we're setting it
sensitive/insensitive which appears to not change anything really
drastic except the visible checkmenuitem is now always visible and
always sensitive when you expect it to
I have been testing this since I released the last update yesterday, the
issue is actually an off by one error, if you check it, it's cycling
backwards through the options with the keyboard shortcut, off by one.
Now I'm not 100% sure where this is happening, and it's pretty damn
weird all in all,
*** This bug is a duplicate of bug 621633 ***
https://bugs.launchpad.net/bugs/621633
** This bug has been marked a duplicate of bug 621633
Keyboard indicator does not update the current layout in its menu when
switching through a keyboard shortcut
--
[Maverick] Indicator menu has wrong
** Changed in: gnome-power-manager (Ubuntu)
Status: Triaged = In Progress
--
Battery status line too long
https://bugs.launchpad.net/bugs/619816
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed = In Progress
--
Keyboard indicator does not update the current layout in its menu when
switching through a keyboard shortcut
https://bugs.launchpad.net/bugs/621633
You received this bug notification because you are a member
Testing a new patch now.
One of the items on https://wiki.ubuntu.com/BatteryStatusMenu#Items
couldn't be fixed, which was the X (estimating…) - the problem here is
that gnome-power-manager is actually pretty sensible in that it will
always have a time remaining available to display. The other
Attached is the updated patch for gnome-power-manager including the new
strings.
I have an updated build of the package building in my ppa;
https://launchpad.net/~karl-qdh/+archive/ppa which will hopefully be
accepted and built soon :)
I _REALLY_ need someone else to test this :( unfortunately I
Currently depends on this bug; https://bugs.launchpad.net/ubuntu/+source
/gnome-settings-daemon/+bug/621633
--
Port the keyboard indicator in gsd to use the app. indicator protocol
https://bugs.launchpad.net/bugs/599844
You received this bug notification because you are a member of Ubuntu
this bug is now firmly sitting in the realm of *NOT EVEN FUNNY* I cannot
locate a single point in the code where the group would be set
incorrectly, I've added in various elements to try and catch the error
but can't find anything in particular that's off by one... The menu just
doesn't seem to
Turns out this is a bug elsewhere in libindicator or libappindicator and
a fix will be released soon.
--
Keyboard indicator does not update the current layout in its menu when
switching through a keyboard shortcut
https://bugs.launchpad.net/bugs/621633
You received this bug notification because
** Changed in: gnome-settings-daemon (Ubuntu)
Status: In Progress = Invalid
--
Keyboard indicator does not update the current layout in its menu when
switching through a keyboard shortcut
https://bugs.launchpad.net/bugs/621633
You received this bug notification because you are a member
The last comment refers to a bug which isn't in gsd, apparently
according to tedg a release for a fix is due.
** Changed in: ayatana-ubuntu
Status: In Progress = Fix Released
** Changed in: ayatana-ubuntu
Status: Fix Released = Fix Committed
--
Port the keyboard indicator in gsd
The screenshot here is the desired outcome. However, the background
rectangle and the two letter name for the layout are slightly more
difficult. Requiring some investigation into all the available
abbreviations and a solution to deal with the overall size of the text
and an API change to
added more detailed conditions to the strings and removed some erroneous
strings.
** Patch added: updated patch
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/619816/+attachment/1517608/+files/12-add-appindicators.patch
--
Battery status line too long
** Changed in: brasero (Ubuntu)
Status: Triaged = In Progress
--
Untranslated string in menu option of Brasero's tray icon, albeit it's
translated in Launchpad
https://bugs.launchpad.net/bugs/553423
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: (unassigned) = Karl Lattimer (karl-qdh)
--
revert old behavoir of keyboard layout indicator: we wants use flags!
https://bugs.launchpad.net/bugs/623435
You received this bug notification because you are a member of Ubuntu
Desktop Bugs
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/623435
--
please drop icon from keyboard indicator
https://bugs.launchpad.net/bugs/620331
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = In Progress
--
please drop icon from keyboard indicator
https://bugs.launchpad.net/bugs/620331
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in
I've started working on a patch which will show the flag. If successful,
we may be able to come up with something like [FLAG] 1,2,3,4 for
different layouts.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = In Progress
--
revert old behavoir of keyboard layout indicator: we
** Patch added: updated patch, slight logic rework
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/619816/+attachment/1517872/+files/12-add-appindicators.patch
--
Battery status line too long
https://bugs.launchpad.net/bugs/619816
You received this bug notification
** Patch added: time in seconds not minutes
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/619816/+attachment/1517927/+files/12-add-appindicators.patch
--
Battery status line too long
https://bugs.launchpad.net/bugs/619816
You received this bug notification because you
** Patch added: updated patch, use HH:MM as the format, rather than a sentence
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/619816/+attachment/1517996/+files/12-add-appindicators.patch
--
Battery status line too long
https://bugs.launchpad.net/bugs/619816
You received
** Patch added: updated patch, no preceding zeros
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/619816/+attachment/1518075/+files/12-add-appindicators.patch
--
Battery status line too long
https://bugs.launchpad.net/bugs/619816
You received this bug notification because
** Patch added: updated patch, no preceding zeros - real patch, last was a dud
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/619816/+attachment/1518077/+files/12-add-appindicators.patch
--
Battery status line too long
https://bugs.launchpad.net/bugs/619816
You received
** Changed in: ayatana-ubuntu
Status: New = Fix Released
--
Battery status line too long
https://bugs.launchpad.net/bugs/619816
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs
I have a working patch which I'll be uploading to bug
https://bugs.launchpad.net/ayatana-ubuntu/+bug/599844 soon.
This will show the flags adjacent to the full label.
--
revert old behavoir of keyboard layout indicator: we wants use flags!
https://bugs.launchpad.net/bugs/623435
You received
** Patch added: updated patch introduces support for show_flags gconf key
https://bugs.launchpad.net/ayatana-ubuntu/+bug/599844/+attachment/1531609/+files/06_use_application_indicator.patch
--
Port the keyboard indicator in gsd to use the app. indicator protocol
** Changed in: gnome-settings-daemon (Ubuntu)
Status: In Progress = Fix Committed
--
revert old behavoir of keyboard layout indicator: we wants use flags!
https://bugs.launchpad.net/bugs/623435
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I have a working patch which I'll be uploading to bug
https://bugs.launchpad.net/ayatana-ubuntu/+bug/599844 soon.
This will show the flags adjacent to the full label. It's a workaround
to the ugly keyboard icon described.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: In Progress =
** Changed in: ayatana-ubuntu
Status: New = Fix Committed
--
please drop icon from keyboard indicator
https://bugs.launchpad.net/bugs/620331
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.
--
msgid matches perfectly the string in brasero-app-indicator, does this
bug still manifest itself?
--
Untranslated string in menu option of Brasero's tray icon, albeit it's
translated in Launchpad
https://bugs.launchpad.net/bugs/553423
You received this bug notification because you are a member
Ok, well, I'll try to implement the second option suggested by MPT which
is to have the option in the control centre to hide the indicator as we
can't really hide the icon and leave the label without breaking ABI atm.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Fix Committed = In
Oh, there is one other option, we have SVG/PNG icons created and drop
the label instead?
This would fit more with MPT's plan, although some complication could
arise with the numbering of multiple layouts from the same country.
--
please drop icon from keyboard indicator
Check your gconf key for;
/desktop/gnome/peripherals/keyboard/general/disable_indicator
That's the only reason I see for it not being visible.
I'm assuming it's functional, as in you can switch layouts?
--
Keyboard menu missing from the panel
https://bugs.launchpad.net/bugs/627392
You received
** Changed in: rhythmbox (Ubuntu)
Status: Confirmed = In Progress
--
Music-Close menu item and Ctrl-W do nothing
https://bugs.launchpad.net/bugs/526552
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in ubuntu.
--
** Summary changed:
- Music-Close menu item and Ctrl-W do nothing
+ Ensure rhythmbox is compliant with the sound menu specifications
--
Ensure rhythmbox is compliant with the sound menu specifications
https://bugs.launchpad.net/bugs/526552
You received this bug notification because you are a
From IRC
(09:31:26) klattimer: xkl_engine_save_state triggers a state-changed
signal, which then calls a function which xkl_engine_save_state's again,
ad infinitum
This is most likely the cause, I'm looking into this and also a memory
leak which may be one and the same bug.
Therefore is linked
Bug fix for this is in the following bug; https://bugs.launchpad.net
/ayatana-ubuntu/+bug/599844
I tested how this bug manifested itself to me, (changing layouts with
keyboard shortcut while in screensaver dialog) and it seems to be OK,
I'll obviously keep it running and see if it does manifest
** Patch added: Patch to prevent memory leak/infinite loop
https://bugs.launchpad.net/ayatana-ubuntu/+bug/599844/+attachment/1533927/+files/12-add-appindicators.patch
--
Port the keyboard indicator in gsd to use the app. indicator protocol
https://bugs.launchpad.net/bugs/599844
You received
** Patch added: The correct patch to fix the above issue this time
https://bugs.launchpad.net/ayatana-ubuntu/+bug/599844/+attachment/1533967/+files/06_use_application_indicator.patch
--
Port the keyboard indicator in gsd to use the app. indicator protocol
This minor update means that if show_flags is enabled the indicator will
only show an icon. This emulates exactly the behavior of the
notification-area icon as it currently exists upstream.
The reason for this is that the complaint of too much space being used
is perfectly valid, and this makes
Completing the indicator as specified will only require implementing
symbolic svg icons for the flags which as previously discussed will
not actually be flags, but instead two letters inside of a box.
See the bug regarding this here; https://bugs.launchpad.net/ayatana-
ubuntu/+bug/628015
--
** Patch added: Fixes the last couple of niggles in the visibility
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/558841/+attachment/1618072/+files/01_use_app_indicator.patch
--
bluetooth devices menu item not working in bluetooth indicator
Attached ayan's test case to demonstrate the menu memory leak
** Attachment added: menu testing app
https://bugs.launchpad.net/indicator-application/+bug/569273/+attachment/1621727/+files/menu-test.tar.bz2
--
memory leak in gnome-power-manager
https://bugs.launchpad.net/bugs/569273
You
from valgrinding the above test (not for the feint of heart I warn you)
the following results are observed;
==24310== 181,440 bytes in 180 blocks are possibly lost in loss record 3,196 of
3,198
==24310==at 0x4C2732A: memalign (vg_replace_malloc.c:581)
==24310==by 0x4C27383:
the gslice leak was bogus, this bug is effectively fixed as the
hashtable leak was the only major one
--
memory leak in gnome-power-manager
https://bugs.launchpad.net/bugs/569273
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: gnome-power-manager (Ubuntu)
Assignee: (unassigned) = Karl Lattimer (karl-qdh)
--
In systray, battery state stay as estimating...
https://bugs.launchpad.net/bugs/633552
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I tried matching the heuristics up with this properly, there are
conditions where there's no time remaining and only a percentage, gnome
power manager is supposed to take data of the percentage over time and
estimate the time remaining, so in theory the time remaining would
eventually be updated,
I'm considering this as a safe default, the problem is that for most
people it will be estimating during that period. This makes me think
that there's something not quite right internally in gpm or that certain
batteries are just a little unpredictable.
Switching it to the percentage is a quick
* Sorry the formatting errors were missed during testing.
* Dropping the percentage was part of the ui spec provided by mpt.
* The continuous estimating was an oversight, in that it didn't happen in
testing. I can only assume some batteries don't get a time estimation at all.
In order to
mpt should have a say on 1h23m style formatting, and we'd need to ask
someone familiar with internationalisation about any implications of it.
--
Battery status line too long
https://bugs.launchpad.net/bugs/619816
You received this bug notification because you are a member of Ubuntu
Desktop
The attached patch changes the output to 0h04m in the menu and now once
again says 0 hours 30 mins in the preferences
I've also made the xhxxm string translatable, but this needs to be
picked up by translators, possibly too late for that :/
I can remove the string change and go back to 0:04
i've attached an updated patch to https://bugs.launchpad.net/ayatana-
ubuntu/+bug/619816
this should fix the problem, some discussion still necessary around that
patch
--
In systray, battery state stay as estimating...
https://bugs.launchpad.net/bugs/633552
You received this bug notification
@Maxim, my battery is also not removable :/ macbook pro
@David, the question is, what should the translations be for time in the
following format %dh%02dm (e.g. 1h02m), the default translation could be
%d:%02d (1:02)
--
Battery status line too long
https://bugs.launchpad.net/bugs/619816
You
Computerjy could you run a valgrind for me?
valgrind --leak-check=full gnome-power-manager ./outfile.valgrind 21
should do it, with the output redirected to outfile.valgrind. Run it for
a long enough period so you believe you're experiencing a leak then hit
ctrl+c which will end the logging
Can someone confirm what is exactly happening here?
Does it suddenly change to a different layout and remain at that layout?
Does it continuously change quite rapidly?
--
Keyboard layout automatically changes
https://bugs.launchpad.net/bugs/625793
You received this bug notification because you
shoo what version of gnome-settings-daemon do you have?
I reproduced this once, fixed what I thought was the bug and released
the fix.
--
Keyboard layout automatically changes
https://bugs.launchpad.net/bugs/625793
You received this bug notification because you are a member of Ubuntu
Desktop
As I introduced the patch which caused it I confirm it's in gnome-
settings-daemon. Now there was one thing definitely causing this bug and
I fixed that, there is a possible second cause of the same kind of
behaviour and it sounds plausible that this would occur during window
changes.
Thanks for
I'm looking through the code and can't see a possibility of changing the
popup group item rapidly, so there's other possibilities as to what is
triggering it, I'm repeatedly changing layouts to test it, and it's
pretty hard to trigger I need something which is confirmed to reproduce
the bug always
** Changed in: indicator-application
Status: Invalid = Incomplete
--
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, which is subscribed to
I managed to trigger the loop but not the changing icon, so there's hope
for the bug yet. Still curious as to where it might be originating from
though :/
** Changed in: indicator-application
Status: Incomplete = Confirmed
** Changed in: indicator-application
Status: Confirmed = In
I just had the bug appear without actively changing layout, when I
changed windows and the layout should have remained the same.
I'm really not sure as to the cause of it, but I'll keep digging...
--
Keyboard layout automatically changes + 100% CPU usage [updated]
Yeah as K-9 said I kinda have enough useful info here, the problem is
figuring out the trigger state. I have a few ideas as to what's
happening and one way that I think might fix it.
Effectively the problem is when the XklState changes in a certain way,
the state change causes a couple of
I've produced a hillbilly patch which isn't ideal but *could* fix this
problem, essentially the change prevents a state change signal from
being processed twice, and then causing an infinite loop. It does this
using a really crack-smoking-flag, which I'm not happy with but might
just do the job.
@Yura, there are two sources of signals to change layout, from Xklavier
- layout changed outside of gsd; and the menu item has been changed.
Both of these signals need to change the indicator, either the menu, the
label or both.
When the signal arrives from gsd's indicator we need to tell
@Yura because the bug is caused by the application indicators patch
--
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, which is subscribed to
@Rich, please don't angrily comment without reading the previous
comments.
I am *presently* working on fixing this bug, and think my present patch
works or at least has been for a while. I have *ALL* the debugging
information that I need, which if you read the previous comments you'd
see there's
@everyone: Sorry for the lateness of the patch upload, had a little
trouble with my laptop/wifi but the patch has been uploaded to my PPA
and will be building shortly.
my ppa address is ppa:karl-qdh/ppa
It *seems* to work well, in that I haven't seen the bug reappear since I
started testing the
1 - 100 of 125 matches
Mail list logo
