I can confirm that the new package does prevent settings in dconf from
propagating into gconf on a dconf update after the package is installed
and the user is logged out and back in. I haven't used the new package
long enough to identify if there are any regressions, but it does seem
to fix this
** Also affects: gsettings-desktop-schemas (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I added my comments to bug 963125 regarding the dconf array keybindings
being converted to lists in gconf, where metacity expects strings.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
Adding packages gnome-settings-daemon and gsettings-desktop-schemas, as
a fix could be done in either.
The issue appears to be that dconf stores the keybindings in arrays of
strings, and when set there, gnome-settings-daemon will transition those
settings to gconf as defined by
I'm pretty new to dconf, so I'm making some assumptions which may be
incorrect. When dconf update is run as root, that only updates settings
which are either mandatory or defaults system-wide. Neither of those
changes should result in a change in the users home directory, and if a
user wasn't
This also exposes something else, which might be better as a separate
bug. wm-schemas.convert tries to convert metacity keybindings from
dconf to gconf. Unfortunately the types are different, so anything
accepted by dconf probably won't actually work once it's written to
gconf. This was exposed
Under what conditions would the gconf plugin for gsettings daemon
convert dconf settings into gconf? This is triggered by a dconf update
while a user is logged in, which seems a rare use case under normal
conditions. When is this plugin designed to operate normally, and could
that other normal
Martin, this new package looks good on Lucid. I went through the
testing procedure before the package, and the screen did not lock.
After installing the new package, without changing settings, the screen
did indeed lock.
Michael, thanks for taking a look at this.
--
You received this bug
I no longer work on the team responsible for maintaining this. I'll
leave it and see if anyone on Goobuntu Team cares to test it or speak
up. It may not be important to them anymore. However, this is really
easy to reproduce, should you want to test it yourself. I just don't
have anything
** Changed in: gnome-panel (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in ubuntu.
https://bugs.launchpad.net/bugs/660455
Title:
clock-applet continually crashing
--
Public bug reported:
Binary package hint: gnome-terminal
As reported by one of our users...
In Lucid, gnome-terminal doesn't support copying with smart Ctrl-C. This
is a functionality regression.
Hardy behavior:
- have text selected with the mouse = CRTL-C is Copy
- have no text selected with
The behavior is still the same in Maverick. The screen does not lock
when the screen is blanked, even if lock/black_screen is checked, or
lock/use_screensaver_settings is checked and screensaver lock is
enabled.
The gnome power manager manual also still has inaccurate information
regarding when
Public bug reported:
Binary package hint: gnome-power-manager
All settings I refer to here are gconf settings relative to /apps/gnome-
power-manager unless fully qualified.
If the value for timeout/sleep_display_ac (in seconds) is less than that
of /desktop/gnome/session/idle_delay (in minutes)
This does appear to be a regression since bug 76901, as when console-
setup gets installed by debootstrap, even with the USA layout and
variant, /etc/default/console/setup is getting
XKBOPTIONS=lv3:ralt_switch
** Also affects: console-setup (Ubuntu)
Importance: Undecided
Status: New
**
** Changed in: console-setup (Ubuntu)
Status: New = Confirmed
--
Right Alt key is always selected under key to choose 3rd level
https://bugs.launchpad.net/bugs/438520
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
The preferred applications help page says to use %s. Perhaps this is
just a documentation bug. I puzzled of this one for a while until I
came to the same conclusion.
--
Custom browser does not receive URL at %s
https://bugs.launchpad.net/bugs/312126
You received this bug notification because
The oem user gets removed at the end of the oem-config process. I'll
have to do some checking to see if a specific option breaks it, but I
notice that a standard (non-oem) install doesn't have the file at all,
so it seems like the oem-config process should remove that file upon
completion.
It appears that the problem is in the TimedLogin feature. If you set
TimedLoginEnable=true, you must also set a valid user in TimedLogin and
a valid delay in TimedLoginDelay. If either of those is not set, or if
the TimedLogin user is invalid, as was the case once oem was removed,
then the
After some more investigation, it turns out this is a problem only with
oem installs. After an oem install, you are left with
/etc/gdm/custom.conf with the following contents:
[daemon]
AutomaticLoginEnable=true
AutomaticLogin=oem
TimedLoginEnable=true
TimedLogin=oem
TimedLoginDelay=10
If I
The package in lucid-proposed breaks users who set disable_user_list to
true. The result is that you still get a Log In button (which the
changelog indicates shouldn't happen anymore) but when you click it, GDM
crashes. Reverting to the version in Lucid main resolved the issue.
--
gdm monitors
The package in lucid-proposed breaks users who set disable_user_list to
true. The result is that you still get a Log In button (which the
changelog indicates shouldn't happen anymore) but when you click it, GDM
crashes. Reverting to the version in Lucid main resolved the issue.
--
The new gdm
** Tags added: regression-proposed
--
Setting disable_user_list to true causes gdm to crash on clicking Log In
https://bugs.launchpad.net/bugs/579044
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs
See bug 579044 for details of the regression.
** Tags added: verification-failed
--
gdm monitors for $HOME/.face even when IncludeAll is false
https://bugs.launchpad.net/bugs/518810
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in
See bug 579044 for details of the regression.
** Tags added: verification-failed
--
The new gdm doesn't give an option to run /etc/X11/Xsession
https://bugs.launchpad.net/bugs/398300
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
referenced in SRU bug 518810 and 398300
--
Setting disable_user_list to true causes gdm to crash on clicking Log In
https://bugs.launchpad.net/bugs/579044
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs
just to make it a link: bug 398300
--
Setting disable_user_list to true causes gdm to crash on clicking Log In
https://bugs.launchpad.net/bugs/579044
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs
It looks like this bug has gone away. I don't know if it's fixed by
upstream, but my bug report never got attention.
--
User list search box should be disabled when user list is disabled.
https://bugs.launchpad.net/bugs/463026
You received this bug notification because you are a member of
The other related launchpad bug I filed is gone in Lucid now, however,
this bug, requiring that you click Log In before typing your username
is still present. With the other bug being fixed, this is no longer as
critical, but it's still a poor experience and in conflict with the
login experience
** Tags added: glucid
--
Passwords should not be required when creating accounts
https://bugs.launchpad.net/bugs/118800
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Tags added: glucid
--
GDM without user list requires that you click Log In.
https://bugs.launchpad.net/bugs/463029
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Tags added: glucid
--
User list search box should be disabled when user list is disabled.
https://bugs.launchpad.net/bugs/463026
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
** Tags added: glucid
--
Disabling user switching doesn't disable it completely
https://bugs.launchpad.net/bugs/363871
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I filed this bug upstream as
https://bugzilla.gnome.org/show_bug.cgi?id=600079
** Bug watch added: GNOME Bug Tracker #600079
https://bugzilla.gnome.org/show_bug.cgi?id=600079
--
User list search box should be disabled when user list is disabled.
https://bugs.launchpad.net/bugs/463026
You
This bug is already filed upstream, and has already been linked to this
bug. I just wanted a launchpad bug open to track the upstream bug.
--
GDM without user list requires that you click Log In.
https://bugs.launchpad.net/bugs/463029
You received this bug notification because you are a member
Public bug reported:
Binary package hint: gdm
If the gdm user list (face browser) is enabled, then beginning to type a
username locates the appropriate entry in the user list. If the user
list is disabled, this search box serves no purpose and should be
disabled. Since users are accustomed to
Public bug reported:
Binary package hint: gdm
If the GDM user list (face browser) is disabled, then the user is only
presented with a Log In button, rather than a username and password
entry field. Disabling the user list is a requirement in an enterprise
environment, and lacking the username
The Log In button which is related to this problem is filed as bug
463026
--
User list search box should be disabled when user list is disabled.
https://bugs.launchpad.net/bugs/463026
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm
Those bugs do not describe the issues we're seeing. I've filed two new
bugs at 463026 and 463029.
--
There's no simple way to disable the gdm face browser
https://bugs.launchpad.net/bugs/445123
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Sebastien,
I'm sorry my request bothered you and felt it wasted your time. My
intent was the opposite. I looked through the list of open GDM bugs and
did not see any that I felt accurately represented the issues I
described. I was considering opening new bugs for them, but since you
stated
That's an easier way to change the setting. Thanks.
Should a separate bug be filed for the issues with the login screen once
this is disabled? Or is that going to just be pushed back to upstream
gnome too? In an enterprise environment, the new login screen is really
sub-optimal.
--
There's
gconf-editor still shows up empty. I'm guessing this is related to
/var/lib/gdm/.gconf being empty. It seems to just use the values set in
/var/log/gdm/.gconf.{defaults,mandatory} I don't see how one goes about
adding values to an empty gconf-editor.
--
Unable to configure which users are
Can you please provide a link to the open bugs? I would like to track
them as well.
--
There's no simple way to disable the gdm face browser
https://bugs.launchpad.net/bugs/445123
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
I think the issue is that these options need to be set for the gdm user.
Setting them using gconftool-2 or gconf-editor does not make the changes
to the gdm user's gconf store. I even tried su gdm and running gconf-
editor, but it's empty. The gdm user doen't have a store apparently,
but depends
As mentioned in another bug, I managed to disable the face browser by
hand editing /var/lib/gdm/.gconf.defaults/%gconf-tree.xml There may be
an incantation of gconftool-2 which can edit this file in a more
friendly, but I haven't discovered it yet. But even then, the login
screen is not optimal.
44 matches
Mail list logo
