@matsonfamily: To replace indicator-applet with indicator-applet-
complete:,
1) Install indicator-applet-complete.
2) Remove both indicator-applet (the mail icon) and indicator-session (the
on-off button) from the gnome panel.
(Right click on icon, and choose Remove From Panel from the
I am also affected by this bug. Running fully-updated Maverick beta
(upgraded from Lucid).
Super+m (configured via gnome-keybinding-properties for toggle-
maximization) was my single most used keyboard shortcut until indicator-
applet took it over last week when I upgraded to Maverick beta.
*** This bug is a duplicate of bug 558581 ***
https://bugs.launchpad.net/bugs/558581
I can't really tell if there is a new Ubuntu policy to have a set of
non-configurable keyboard shortcuts reserved for certain programs (like
the indicator-applet). I see open bugs on both sides of the issue
*** This bug is a duplicate of bug 558581 ***
https://bugs.launchpad.net/bugs/558581
Just an additional note, since I have reported this as a bug to gnome-
control-center:
I am affected by this bug under both compiz and metacity when I try to
set Super+m or Super+s via
** Summary changed:
- Super+m key combo conflicts with default compiz key combo to invert screen
+ Indicator-applet forcibly overrides Super+m key combo
--
Indicator-applet forcibly overrides Super+m key combo
https://bugs.launchpad.net/bugs/558581
You received this bug notification because you
There is a similar bug reported for pinyin input (as a wishlist).
I think the gist of both of these bug reports is that m17n is not an
adequate default input method for either Chinese or Japanese. Trying to
use m17n for either of these languages gives the user the impression
that iBus is broken.
Indeed, I was very surprised to find that Launchpad policy allows me to
edit the summary. I really would have expected that only the original
poster, whoever has the bug assigned and the site admin could change it.
But hey, I'm new around here.
As long as I was allowed to, I thought that
Non-patch workaround:
If you only suffer from indicator-applet overriding super+m and don't
care about super+s, you can replace indicator-applet with indicator-
applet-complete, and get super+m back. (indicator-applet-complete
only uses super+s) This avoids running a locally-patched version of
Inconsistent behavior:
Interestingly, after I tried the above workaround, I reverted back to
indicator-applet + indicator-applet-session just to check the
consistency of the workaround, and I found that indicator-applet no
longer overrode super+m on my system.
After switching back and forth
I have my keyboard shortcut set to Alt+Release+Alt_R (i.e. hold down
Alt_L and then hit Alt_R). In gnome-terminal, I have to hit Alt_R
*twice* to turn iBus on or off. In all other programs, once is enough.
Alt-grave doesn't work for me either, even if I hit grave twice.
IBus responds
Public bug reported:
Binary package hint: ibus
System: Ubuntu 10.10 (beta) fully updated
Packages:
ibus 1.3.7-1ubuntu3
indicator-applet 0.4.6-0ubuntu1
indicator-applet-complete 0.4.6-0ubuntu1
Clicking on Preferences on the ibus panel widget's menu should
consistently display the
Same issue exists with 1.3.10-1 on Ubuntu 10.10 beta.
--
Tenth candidate can't be selected with 0 key
https://bugs.launchpad.net/bugs/515549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I second Paul's suggestion, and encourage you to bring it up on the
mailing list.
Aside from the question of hearing damage, having a max-volume button
that you might hit accidentally presents other dangers, such as creating
a disturbance in public spaces/offices where low volume may be
Public bug reported:
Binary package hint: indicator-sound
Ubuntu 10.10 (beta), fully updated.
packages:
indicator-sound 0.4.7-0ubuntu2
rhythmbox 0.13.1-0ubuntu5
Expected behavior:
Song titles are displayed in full in the indicator-sound menu, word-wrapped if
necessary.
Observed
A more complete solution:
1. Pick a directory from which mysqld should be allowed to load files.
Perhaps somewhere writable only by your DBA account and readable only by
members of group mysql?
2. sudo aa-complain /usr/sbin/mysqld
3. Try to load a file from your designated loading directory:
Solved.
The problem is 50% a minor flaw in mount.ecryptfs and 50% user error.
* mount.ecryptfs: As of ecryptfs-utils version 81-0ubuntu3, if you mount
interactively (i.e. mount -t ecryptfs /path1/private /path2/public) and
ask to use FNEK, mount.ecryptfs will suggest the wrong key when it
Correction to #7: I was using Karmic amd64 LiveCD, not Jaunty.
--
mounting eCryptfs: [-2] No such file or directory when trying to mount
encrypted home
https://bugs.launchpad.net/bugs/455709
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
After much searching around, I found your article in Linux Magazine:
http://www.linux-mag.com/id/7568/3/
The instructions there work for me. So I have a workaround. On the
other hand, in your article the chroot environment contains the entire
original system. The original poster seems to only
I get the same problem. Working with Jaunty amd64, my home directory
mounts fine when it is all done automatically, but when I try to do it
by hand (as root from the latest Jaunty LiveCD as part of a system
diagnostic run), I get the results described in #4 above: Filenames
decrypted properly,
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34407816/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/34407817/XsessionErrors.txt
--
grep {,m} construction gives error: malformed repeat count
Public bug reported:
Binary package hint: grep
grep 2.5.4-4 on Karmic amd64
According to the manual page:
{,m} The preceding item is matched at most m times.
But:
a...@ike:~$ echo 23:45.67 | grep '[0-9]\{,2\}:[0-9]\{2\}\.[0-9]\{2\}'
grep: malformed repeat count
a...@ike:~$ echo 23:45.67 |
Public bug reported:
I don't understand... I am filling out this form because ubuntu-bug
asked me to. But this form then asks me to run ubuntu-bug again, and it
gives me the same information and asks me to fill out this form again.
I'm in a recursive bug report loop!
So, I'm giving you the
** Attachment added: Log files requested on bug report form.
http://launchpadlibrarian.net/34141770/logs.tar.gz
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/34141771/AlsaDevices.txt
** Attachment added: AplayDevices.txt
Similar behavior: resume takes 13.040 seconds on my GA P55-UD3R (Intel i5, 4GB,
NVIDIA 9600GT with proprietary drivers).
Most of the time (9 seconds) is taken waiting for the hard drive to softreset.
(1.5TB Seagate attached to Gigabyte GSATA2).
--
suspend_test_finish slow resume warning
** Attachment added: dmesg.log.gz
http://launchpadlibrarian.net/34159303/dmesg.log.gz
--
suspend_test_finish slow resume warning
https://bugs.launchpad.net/bugs/452734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
25 matches
Mail list logo
