I don't think Compiz is relevant here. My computer isn't running Compiz
— its display manager is GDM3 as best I can tell. (ri...@richw.org, the
original reporter of this bug)
** Package changed: compiz (Ubuntu) => gdm3 (Ubuntu)
--
You received this bug notification because you are a member of
NOT working for me (Ubuntu 14.04, iPhone 4S running iOS 7.1.2).
I'm not getting the trust loop problem, but I am getting Unhandled
Lockdown error (-20) and cannot mount the iPhone in order to upload
photos into Shotwell.
I've tried the suggestion to make the /var/lib/lockdown directory
publicly
I, for one, am *not* willing to sacrifice the keyboard layout indicator.
If a user is using multiple layouts, the indicator is essential, and
removing it is (IMO) a significant regression from Lucid (where the
layout indicator worked just fine).
So, then, is this a bug in gnome-settings-daemon?
From the perspective of a naive (or not-so-naive) Ubuntu user who is
probably not aware of exactly which software component is doing which
keyboard layout-related task, all they will notice is that the indicator
icon breaks when they upgrade to Maverick.
If there is some reason why the Lucid
Just on a wild guess, I launched Add to Panel and added the Indicator
Applet — and a US flag (corresponding to my currently active keyboard
layout) showed up in the panel along the top of the screen.
Although (re-)adding the indicator applet seems to have fixed the
problem, there is still the
If this bug report is invalid w/r/t the indicator application, please
advise what needs to be done in order for the problem to be addressed.
It would (IMO) by a very bad thing if this problem were to be neglected,
and if Maverick were to be released without anything being done, on
account of the
I installed a set of flag icons (us.png, etc.) in ~/.icons/flags, and I
enabled /desktop/gnome/peripherals/keyboard/indicator/showFlags in
gconf-editor, but this did no good — in fact, it made the static
keyboard icon go away entirely (replaced with a generic I can't find
any icon to display here
@divan: Could you clarify exactly how you set up your keyboard layout
indicator to show country flags?
One problem I've been having (at the same time as this random layout
switching bug) is that I am no longer seeing any indication of my
current keyboard layout at all. All I am now seeing is an
*** This bug is a duplicate of bug 531173 ***
https://bugs.launchpad.net/bugs/531173
Appears to be a duplicate of bug #531173.
** This bug has been marked a duplicate of bug 531173
New Lucid keyboard layout indicator does not indicate current layout
* You can subscribe to bug 531173 by
I see an icon that looks like a little keyboard, but it doesn't indicate
the current keyboard layout any longer (via an abbreviation like USA
or Rus) the way it used to. I can do a left-click on the icon and get
a list of radio buttons allowing me to see/change the layout, but
nothing shows the
Public bug reported:
Binary package hint: gnome-settings-daemon
I'm using multiple keyboard layouts. The current layout for the
currently active window used to be identified with an abbreviation
(e.g., USA or Rus) along the top of the screen.
When I went from Lucid to Maverick beta, however,
Let's all PLEASE keep it civil. We can disagree on technical or policy
issues without engaging in personal attacks (or perpetuating a toxic
atmosphere by responding in kind to what we may perceive as personal
attacks by others). Thanks.
--
[Master] Window Control buttons:
Unfortunately, Mark Shuttleworth has said (see comment #564) that this
decision is final and that no complaints or negative votes would make
any difference.
--
[Master] Window Control buttons: position/order/alignment
https://bugs.launchpad.net/bugs/532633
You received this bug notification
I've been seeing this bug in Karmic for some time now.
--
gnome-screensaver bad password timeout
https://bugs.launchpad.net/bugs/314545
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
desktop-bugs
I've been seeing this bug in Karmic for a long time. Ctrl-alt-backspace
does NOT kill X. Ctrl-alt-delete does NOT reboot.
--
Unable to unlock the screensaver
https://bugs.launchpad.net/bugs/181065
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
This bug (or a very similar bug) is alleged to have been fixed for Lucid
(bug #524860).
--
gnome-screensaver bad password timeout
https://bugs.launchpad.net/bugs/314545
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in
This bug (or a very similar bug) is alleged to have been fixed for Lucid
(bug #524860).
--
Unable to unlock the screensaver
https://bugs.launchpad.net/bugs/181065
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in
I still say that placement of the buttons on the left is wrong.
But if you absolutely insist on doing this, there needs to be a user-
visible option in the preferences GUI to allow someone to reposition the
buttons via a check-box. Expecting people to launch gconf-editor from
the Run Application
Not for me, it doesn't. I upgraded a new Hardy system to Intrepid
today, and it's started demanding Enter login password to unlock
keyring after doing an autologin. It wasn't doing that in 8.04.1
before I did the upgrade.
This new system was going to be for my mother, who is not very computer-
And the pam-keyring-tool workaround didn't work for me either. I was
still being prompted for the login password.
However, it looks like I was finally able to get rid of the unlock
keyring prompt by using pam-keyring-tool -c and entering an empty
password (just hit ENTER) for the new password.
This appears to be the same problem as bug #173721.
The workaround described in
http://wiki.linuxquestions.org/wiki/Swap_Caps_Lock_and_Ctrl appears to
fix it for me -- though, of course, this doesn't explain the strange bug
with the preferences control panel option not working.
--
caps lock as
I believe the relevant file with the settings from the keyboard
preferences control panel is:
$HOME/.gconf/desktop/gnome/peripherals/keyboard/kbd/%gconf.xml
Here's what it looks like on my freshly installed 8.04.01 system (where
the caps lock - control setting in the control panel is not
I'm seeing this same problem today, on a freshly installed, patched-up-
to-date 8.04.1 desktop system.
--
caps lock as additional control broken on intrepid
https://bugs.launchpad.net/bugs/287714
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
NOT running amd64. My machine is an amd64, but I'm running 32-bit:
Linux liberation 2.6.20-16-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 i686
GNU/Linux
--
Rich Wales === Palo Alto, CA, USA === [EMAIL PROTECTED]
http://www.richw.org === http://en.wikipedia.org/wiki/User:Richwales
Please forgive my denseness, Hadriw, but I'm really not sure I
understand what you were trying to say. It sounded like you were saying
a solution to this problem can be found by googling for the words totem
ubuntu stream flow, but when I looked for those words (without the
quotes), I got a bunch
I get an internal data flow error if I drag the progress bar (e.g., to
skip commercials). I'm running Feisty, i386, and trying to play an MPEG
file that was produced by tivodecode. If I just sit back and let the
file play without interruption, it works fine. This happens on many
MPEG files, not
Public bug reported:
Binary package hint: gnome-cups-manager
My office just got a Xerox WorkCentre Pro C2636. I tried to add this
printer to a Feisty workstation, but there doesn't appear to be a
driver. Add a Printer shows drivers for numerous Xerox printers --
including four WorkCentre
27 matches
Mail list logo
