[Bug 1343261] [NEW] User accounts with id higher than 60000 are not shown in Trusty
Public bug reported: Version: 0.6.35-0ubuntu7 This bug is visible in lightdm, but it's actually a problem in Trusty's accountsservice. The code in user-classify.c forces the user account to be between 1000 and 6. Any accounts higher than 6 are considered systems accounts and not shown in lightdm. In Utopic this is fixed by modifying the code to not take into account any maximum, but rather use the minimum and then filter "nobody" and "nobodynfs". Editing login.defs is possible but is not enough, because in that case, nobody isn't filtered. The patch is quite small and can be backported to Trusty without much issue. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1343261 Title: User accounts with id higher than 6 are not shown in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1343261/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1016103] Re: evince unable to save changes to toolbar
I disagree with the assesment. Users under GNOME 3 have also the issue
that settings cannot be saved, and the fix is to add this line to
/etc/apparmor.d/usr.bin.evince:
@{HOME}/.config/evince/* rwl,
Regardless of how weird the path to the home is, if it correctly maps to
@{HOME} then it shouldn't be a problem for apparmor.
** Changed in: evince (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1016103
Title:
evince unable to save changes to toolbar
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1016103/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292451] Re: screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked
So, when will 7.2.1 be released? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292451 Title: screensaver re-locks itself after unlocking if the configured screen- off timer goes off while screen is locked To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292451/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1159959] Re: Cursor moves with "Disable touchpad while typing"
This bug was already present at least in Precise, 12.04. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1159959 Title: Cursor moves with "Disable touchpad while typing" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1159959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1218979] Re: Touchpad "disable while typing" option is ignored
*** This bug is a duplicate of bug 1159959 *** https://bugs.launchpad.net/bugs/1159959 This was already the case in Precise 12.04 ** This bug has been marked a duplicate of bug 1159959 Cursor moves with "Disable touchpad while typing" -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1218979 Title: Touchpad "disable while typing" option is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1218979/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1004515] Re: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted
** Description changed: - I noticed this in my logs. It's not obviously broken anything, but - segfaults are bad so I thought it worth reporting. + [Impact] + libaccountsservice contains a double free which under certain circumstances will cause accounts-daemon to segfault, and under other circumstances will cause gdm to segfault when a user account is added or removed. + + [Test case] + In a precise machine with kerberos authentication, adding a new user via "sudo adduser test" will cause an X session running under GDM to crash with a segfault. + + Once the patch is applied, running the same command line should not + affect a running X session. For the test to have value, the session + needs to have been started after the new accountsservice packages were + installed. + + [Possible regressions] + This is just one line removing a double free that has been applied upstream for 16 months, so the code itself should be fine. To be certain that everything is alright, not only gdm but also lightdm should be tested. + + [Original description] + I noticed this in my logs. It's not obviously broken anything, but segfaults are bad so I thought it worth reporting. May 25 14:16:16 e102475-lin gdm-session-worker[2198]: AccountsService-WARNING: SetLanguage call failed: not access to HOME yet so language not saved May 25 14:16:17 e102475-lin kernel: [ 6288.041531] accounts-daemon[2200]: segfault at 596fa6 ip 7f283fad1e40 sp 7fff221eb4e0 error 4 in libc-2.15.so[7f$ M - --- + --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 Package: accountsservice 0.6.15-2ubuntu9 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=en_GB.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Tags: precise third-party-packages Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2011-11-09 (197 days ago) UserGroups: adm fuse sbuild sudo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1004515 Title: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1004515/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 867565] Re: gnome-terminal crashed with SIGSEGV in g_object_notify()
I searched a bit and found several duplicates of this bug (now merged).
The ways of reproducing are many, but are always related to working with
tabs. Detaching a tab, dragging and dropping a tab between two windows,
etc. In my case, one time it happened when closing a window with no
tabs while keeping two other windows with tabs.
The GNOME upstream bug says it's related to accessibility, which I guess
it's due to the "accessible-value" property that we see in the
backtrace.
The line that is segfaulting is 1154 from this function:
1148: void
1149: g_object_notify (GObject *object,
1150: const gchar *property_name)
1151: {
1152: GParamSpec *pspec;
1153:
1154: g_return_if_fail (G_IS_OBJECT (object));
1155: g_return_if_fail (property_name != NULL);
The macros expand to:
#define G_IS_OBJECT(object) (G_TYPE_CHECK_INSTANCE_TYPE ((object),
G_TYPE_OBJECT))
#define G_TYPE_CHECK_INSTANCE_TYPE(instance, g_type)(_G_TYPE_CIT
((instance), (g_type)))
# define _G_TYPE_CIT(ip, gt) (G_GNUC_EXTENSION ({ \
GTypeInstance *__inst = (GTypeInstance*) ip; GType __t = gt; gboolean __r; \
if (!__inst) \
__r = FALSE; \
else if (__inst->g_class && __inst->g_class->g_type == __t) \
__r = TRUE; \
else \
__r = g_type_check_instance_is_a (__inst, __t); \
__r; \
}))
In this last macro, the first thing that's checked is that the object
passed is not NULL. Thus, this is pointing to some piece of memory,
different than NULL, but on which it's not valid to access it's
->g_class member.
In my stack trace, the object is "optimized out", but in the one
provided in the Debian bug report, it says: object@entry=0x8469a38.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/867565
Title:
gnome-terminal crashed with SIGSEGV in g_object_notify()
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/867565/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 870514] Re: gnome-terminal crashed with SIGSEGV in g_object_notify()
*** This bug is a duplicate of bug 867565 *** https://bugs.launchpad.net/bugs/867565 ** This bug is no longer a duplicate of bug 860330 gnome-terminal crashed with SIGSEGV in g_object_notify() ** This bug has been marked a duplicate of bug 867565 gnome-terminal crashed with SIGSEGV in g_object_notify() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/870514 Title: gnome-terminal crashed with SIGSEGV in g_object_notify() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/870514/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1157863] Re: gnome-terminal crashed with SIGSEGV in g_object_notify()
*** This bug is a duplicate of bug 867565 *** https://bugs.launchpad.net/bugs/867565 ** This bug is no longer a duplicate of bug 860330 gnome-terminal crashed with SIGSEGV in g_object_notify() ** This bug has been marked a duplicate of bug 867565 gnome-terminal crashed with SIGSEGV in g_object_notify() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1157863 Title: gnome-terminal crashed with SIGSEGV in g_object_notify() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1157863/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 867565] Re: gnome-terminal crashed with SIGSEGV in g_object_notify()
** Bug watch added: Debian Bug tracker #677508 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677508 ** Also affects: gnome-terminal (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677508 Importance: Unknown Status: Unknown ** Bug watch added: GNOME Bug Tracker #678757 https://bugzilla.gnome.org/show_bug.cgi?id=678757 ** Also affects: gnome-terminal via https://bugzilla.gnome.org/show_bug.cgi?id=678757 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/867565 Title: gnome-terminal crashed with SIGSEGV in g_object_notify() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/867565/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 867565] Re: gnome-terminal crashed with SIGSEGV in g_object_notify()
Hi, This is a recent crash in gnome-terminal in g_object_notify. It happens reliably when moving a tab from one window to another. #0 0x7fb60eca80d6 in g_object_notify (object=, property_name=0x7fb60ff18d02 "accessible-value") at /tmp/buildd/glib2.0-2.32.4/./gobject/gobject.c:1154 #1 0x7fb60eca1ca2 in g_closure_invoke (closure=0x17042d0, return_value=0x0, n_param_values=1, param_values=0x7fffb087d3c0, invocation_hint=) at /tmp/buildd/glib2.0-2.32.4/./gobject/gclosure.c:777 #2 0x7fb60ecb2d71 in signal_emit_unlocked_R (node=, detail=0, instance=, emission_return=0x0, instance_and_params=0x7fffb087d3c0) at /tmp/buildd/glib2.0-2.32.4/./gobject/gsignal.c:3551 #3 0x7fb60ecbb069 in g_signal_emit_valist (instance=0x27378a0, signal_id=, detail=0, var_args=) at /tmp/buildd/glib2.0-2.32.4/./gobject/gsignal.c:3300 #4 0x7fb60ecbb212 in g_signal_emit (instance=, signal_id=, detail=) at /tmp/buildd/glib2.0-2.32.4/./gobject/gsignal.c:3356 #5 0x7fb60fbd40fa in gtk_adjustment_value_changed () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #6 0x7fb61082643e in ?? () from /usr/lib/libvte2_90.so.9 #7 0x7fb60e9e58db in g_timeout_dispatch (source=0x17fc330, callback=, user_data=) at /tmp/buildd/glib2.0-2.32.4/./glib/gmain.c:3882 #8 0x7fb60e9e4d13 in g_main_dispatch (context=0x1160e40) at /tmp/buildd/glib2.0-2.32.4/./glib/gmain.c:2539 #9 g_main_context_dispatch (context=0x1160e40) at /tmp/buildd/glib2.0-2.32.4/./glib/gmain.c:3075 #10 0x7fb60e9e5060 in g_main_context_iterate (dispatch=1, block=, context=0x1160e40, self=) at /tmp/buildd/glib2.0-2.32.4/./glib/gmain.c:3146 #11 g_main_context_iterate (context=0x1160e40, block=, dispatch=1, self=) at /tmp/buildd/glib2.0-2.32.4/./glib/gmain.c:3083 #12 0x7fb60e9e545a in g_main_loop_run (loop=0x114faf0) at /tmp/buildd/glib2.0-2.32.4/./glib/gmain.c:3340 #13 0x7fb60fcb342d in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #14 0x004135e1 in ?? () #15 0x7fb60dc8b76d in __libc_start_main (main=0x413320, argc=1, ubp_av=0x7fffb087d988, init=, fini=, rtld_fini=, stack_end=0x7fffb087d978) at libc-start.c:226 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/867565 Title: gnome-terminal crashed with SIGSEGV in g_object_notify() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/867565/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 998735] Re: Light blue screen on primary monitor when waking up from inactivity
The bug is in mutter and muffin (which is a fork of mutter). The upstream bug where it was finally fixed: https://bugzilla.gnome.org/show_bug.cgi?id=677116 I'm attaching here the patch that fixes the problem for mutter. ** Bug watch added: GNOME Bug Tracker #677116 https://bugzilla.gnome.org/show_bug.cgi?id=677116 ** Patch added: "Patch fixing blue screen bug for mutter" https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/998735/+attachment/3685806/+files/05_fix_blue_screen.patch ** Also affects: mutter via https://bugzilla.gnome.org/show_bug.cgi?id=677116 Importance: Unknown Status: Unknown ** Package changed: gnome-power-manager (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/998735 Title: Light blue screen on primary monitor when waking up from inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/998735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1154370] Re: [precise SRU] crash due to improper handling of "/" in GSettings
Hi, I can confirm that the proposed package fixes the issue. -- Cheers, Marga -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1154370 Title: [precise SRU] crash due to improper handling of "/" in GSettings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1154370/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1154370] Re: [precise SRU] crash due to improper handling of "/" in GSettings
There's currently an upload of glib2.0 in the unaccepted precise queue. Version is 2.32.4-0ubuntu1. This package includes the fix needed for this bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1154370 Title: [precise SRU] crash due to improper handling of "/" in GSettings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1154370/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1100587] Re: gnome-control-center does not remove system-wide proxy settings from /etc/environment when switch from manual to automatic mode.
Ok, my mistake, I found the -data package, although it was not in the build results. I guess there's something weird going on with those build results, since the package is actually there, and this is probably related with it being an _all package. I have re-verified and the uploaded package fixes the issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1100587 Title: gnome-control-center does not remove system-wide proxy settings from /etc/environment when switch from manual to automatic mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1100587/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1100587] Re: gnome-control-center does not remove system-wide proxy settings from /etc/environment when switch from manual to automatic mode.
Hi, I can verify that the provided package fixes the issue. HOWEVER, there seems to be no gnome-control-center-data package, which is a necessary dependency and causes problems when installing. I checked the build logs, but I couldn't find anything there. Also, the missing package WAS built for i386, but not for the other arches. I forced dpkg installation and the package seems to work, but the missing dependency is a serious issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1100587 Title: gnome-control-center does not remove system-wide proxy settings from /etc/environment when switch from manual to automatic mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1100587/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1154370] Re: [precise SRU] crash due to improper handling of "/" in GSettings
Hi, I was affected by this bug (cinnamon died when running dconf update), and after applying the above mentioned patch (e6f659a898595ba944bd02f0509b14694d1c26e7) the bug was solved. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1154370 Title: [precise SRU] crash due to improper handling of "/" in GSettings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1154370/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1100587] Re: gnome-control-center does not remove system-wide proxy settings from /etc/environment when switch from manual to automatic mode.
Yes, the package in quantal fixes the issue. Precise is still pending. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1100587 Title: gnome-control-center does not remove system-wide proxy settings from /etc/environment when switch from manual to automatic mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1100587/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1100587] Re: gnome-control-center does not remove system-wide proxy settings from /etc/environment when switch from manual to automatic mode.
Sorry. My previous message was about the precise package, which doesn't yet include the fix, but that was not what the automated message was asking. I suspect Alec made the same mistake. The quantal package includes the fix. I had wiped my quantal installation, so I'm re-installing it now to check if the fix verifies in quantal, I expect it will. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1100587 Title: gnome-control-center does not remove system-wide proxy settings from /etc/environment when switch from manual to automatic mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1100587/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1100587] Re: gnome-control-center does not remove system-wide proxy settings from /etc/environment when switch from manual to automatic mode.
Indeed, the uploaded version doesn't include my change. The uploaded version has the following changelog: gnome-control-center (1:3.4.2-0ubuntu0.9) precise; urgency=low * debian/UbuntuLogo.png: logo was saying 12.04.1 LTS, go back to just use "12.04 LTS" to avoid having to keep updating it (lp: #1116801) -- Sebastien Bacher Thu, 07 Feb 2013 17:57:58 +0100 Whereas my patch had the following changelog: gnome-control-center (1:3.4.2-0ubuntu0.9) precise; urgency=low * Added debian/patches/remove-manual-proxy-in-auto.patch to also remove the manual proxy setting when in AUTO mode. (LP: #1100587) -- Margarita Manterola Tue, 05 Feb 2013 11:55:06 +0100 I guess the other change was already in the pipeline, but the corresponding fix has not gone in. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1100587 Title: gnome-control-center does not remove system-wide proxy settings from /etc/environment when switch from manual to automatic mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1100587/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1122028] Re: gsettings does not respect dconf locks
On the other bug, Ryan Lortie explained that this is because the value needs to be casted to uint32. Changing: idle-delay=10 To: idle-delay=uint32 10 Makes this work correctly. I still think this is a bug though, since it's a conf file, not a programming language. But in any case it should be documented somewhere... Where? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1122028 Title: gsettings does not respect dconf locks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1122028/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1122028] Re: gsettings does not respect dconf locks
This bug was also reported in GNOME's bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=693149 Let me add that if the locks are removed from the /etc/dconf files, and then the user changes the value manually, for example to 3 minutes, then this is the result: $ dconf read /org/gnome/desktop/session/idle-delay uint32 180 $ gsettings get org.gnome.desktop.session idle-delay uint32 180 But if the locks are then restored (by editing the files and then running dconf update): $ dconf read /org/gnome/desktop/session/idle-delay 10 $ gsettings get org.gnome.desktop.session idle-delay uint32 600 ** Bug watch added: GNOME Bug Tracker #693149 https://bugzilla.gnome.org/show_bug.cgi?id=693149 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1122028 Title: gsettings does not respect dconf locks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1122028/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1100587] Re: gnome-control-center does not remove system-wide proxy settings from /etc/environment when switch from manual to automatic mode.
The code in raring is completely different, so even if I don't have a raring box to test it right now, I'm assuming it's unaffected by this bug. The code in quantal, however, is basically the same as in precise. I have prepared a patch based on the quantal version, debdiff attached. ** Patch added: "quantal debdiff that fixes the bug" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1100587/+attachment/3515612/+files/quantal-fix-for-1100587.diff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1100587 Title: gnome-control-center does not remove system-wide proxy settings from /etc/environment when switch from manual to automatic mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1100587/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1100587] Re: gnome-control-center does not remove system-wide proxy settings from /etc/environment when switch from manual to automatic mode.
Hi, The fix is simple, it just implies adding G_DESKTOP_PROXY_MODE_AUTO to the case block where the system proxy is reset. This leads to the same result than Manual->None->Auto leads. I'm attaching the debdiff for the precise version, will check the raring version next, and if the bug is still present and still the same, create a fix for that one as well. ** Patch added: "Debdiff containing the fix for the precise version of gnome-control-center" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1100587/+attachment/3515561/+files/precise-fix-for-1100587.diff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1100587 Title: gnome-control-center does not remove system-wide proxy settings from /etc/environment when switch from manual to automatic mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1100587/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 963125] Re: Some metacity shortcuts get changed into lists and stop working
Hi, I've retitled the bug to reflect more closely what happens. Not only Alt-Tab is lost, any shortcut managed through the metacity entries can be affected by this. Joel already explained what is happening and what the possible solutions are. It would be great to get some of the maintainers of these packages to chime in here. ** Summary changed: - Alt-Tab window switcher lost + Some metacity shortcuts get changed into lists and stop working -- 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/963125 Title: Some metacity shortcuts get changed into lists and stop working To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/963125/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 998735] Re: Light blue screen on primary monitor when waking up from inactivity
Hi, I'm affected by this bug, but only when using cinnamon, not unity. Something was done in compiz to prevent this problem but this was not done in muffin/mutter. I've found out that when using xscreensaver the issue happens as well, BUT when moving the mouse xscreensaver's password prompt shows up (with black background), and then goes away and blue comes back when the timeout expires, that sounds like some X buffer is turning blue, and xscreensaver is successful in overwriting it, while gnome-screensaver isn't. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/998735 Title: Light blue screen on primary monitor when waking up from inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/998735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1035219] Re: In System Settings preference tool/keyboard layouts page automaticaly wrong language selectedGNOME
** Description changed: + [Impact] + GNOME/Cinnamon users that use the "keyboard layout" preference pane, are presented with a list of languages in which none of them is selected. When moving to the next tab, the first in the list is selected, which causes the whole system to switch to Chinese/Bengali/Whichever language was alphabetically first. This is saved immediately, but only applied after logging out and in again. + + [Test case] + In a GNOME session of a machine with some alphabetically lower than English language pack installed (e.g. language-pack-aa), open "System Settings", select the "Keyboard Layout" pane, then move to the next tab and back. + + If the bug is present, the first language in the list will be selected. + If it's not, the current language will be selected. + + [Regression potential] + The fix consists of uncommenting a small piece of code that adds a new entry for the current language and marks it as selected. This means that the current language is duplicated, however, the current fix considers preferable to have a double entry for the current language than cause the user's session to be suddenly changed to Chinese. + + + [Original description] + Dear Developers, I using Ubuntu 12.04 with GNOME3 fallback session. I found a bug with System settings preference tooll the Keyboard Layouts preference pane: If launch System settings, choosing keyboard layouts preference pane, the first awailable page tab is the language page tab. When I moving the dialog with TAB and SHIFT+TAB key, the language tree table wrong language are default selected, not the current used language. Reproducation steps, I verified with Ubuntu 12.04 daily live CD in GNOME3 fallback session: 1. Boot Ubuntu 12.04 daily live CD. 2. In the language list select a non english language. 3. Click try Ubuntu button. 4. Enable the universe and multiverse repositoryes, and install gnome-session-fallback package. 5. Log out, and log in with Gnome Classic (no effects) session. 6. Launch System settings application. 7. Click keyboard layouts. 8. Press two TAB key, and you will be see the default selected language is not equals your prewious selected language. 9. For example jump the keyboard layouts page with CTRL+ALT+PAGEUP key combination without you correct the wrong selected language. 10. Click All settings button without you change the automated selected language. Log out, and log in again. Your system language will be changing. In Unity and Unity 2d this problem not happening, because in Keyboard Layout preference tool the language page tab are disabled. I sending six screenshot with showing this problem real happening. First screen shot shoving original language output (hungarian), other screen shots shoving the language changed with English the next login. Installed Ubuntu 12.04 system I reproduced this issue. Attila ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.2-0ubuntu0.4 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24 Uname: Linux 3.2.0-29-generic-pae i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Fri Aug 10 10:29:31 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120327) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: - activity-log-manager-control-center 0.9.4-0ubuntu3 - deja-dup22.0-0ubuntu2 - gnome-bluetooth 3.2.2-0ubuntu5 - indicator-datetime 0.3.94-0ubuntu2 + activity-log-manager-control-center 0.9.4-0ubuntu3 + deja-dup22.0-0ubuntu2 + gnome-bluetooth 3.2.2-0ubuntu5 + indicator-datetime 0.3.94-0ubuntu2 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1035219 Title: In System Settings preference tool/keyboard layouts page automaticaly wrong language selectedGNOME To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1035219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1035219] Re: In System Settings preference tool/keyboard layouts page automaticaly wrong language selectedGNOME
** Patch added: "Patch applied for precise proposed" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1035219/+attachment/3454070/+files/g-c-c-precise.diff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1035219 Title: In System Settings preference tool/keyboard layouts page automaticaly wrong language selectedGNOME To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1035219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1035219] Re: In System Settings preference tool/keyboard layouts page automaticaly wrong language selectedGNOME
Hi, The entry shown here by the launchpad editor is actually misleading. It's not patch 60, but patch 52 that fixes the issue, and actually a small change in patch 52. this patch included a section that commented out re-inserting the current language, because the language showed up twice. The fix is to leave this section as it was, so that even though the current language shows up twice, at least one of them is selected. This was applied in raring. I'm adding patches for precise and quantal that simply reapply the fix. I have tested these patches. They apply cleanly and fix the problem by making an extra selected entry for the current language. ** Patch added: "Patch applied for quantal-proposed" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1035219/+attachment/3454069/+files/g-c-c-quantal.diff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1035219 Title: In System Settings preference tool/keyboard layouts page automaticaly wrong language selectedGNOME To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1035219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1024057] Re: gnome control center crashed when attempting to open privacy dialogue
Hi, I have been able to reproduce and find the cause of this bug. The bug is triggered when the file ".config/user-dirs.dirs" is not present. Simply move that file away and you'll be able to reproduce this. Running xdg-user-dirs-update might or might not fix the problem, some variables might not get set in that case, and if there's one variable missing, the privacy pane fails. The bug is actually in the activity-log-manager package. The file src /files-widget.vala, lines 264-272, says: defined_dirs = new HashMap(str_hash, str_equal); defined_dirs.set(Environment.get_user_special_dir(UserDirectory.DESKTOP), UserDirectory.DESKTOP); defined_dirs.set(Environment.get_user_special_dir(UserDirectory.DOCUMENTS), UserDirectory.DOCUMENTS); defined_dirs.set(Environment.get_user_special_dir(UserDirectory.DOWNLOAD), UserDirectory.DOWNLOAD); defined_dirs.set(Environment.get_user_special_dir(UserDirectory.MUSIC), UserDirectory.MUSIC); defined_dirs.set(Environment.get_user_special_dir(UserDirectory.PICTURES), UserDirectory.PICTURES); defined_dirs.set(Environment.get_user_special_dir(UserDirectory.PUBLIC_SHARE), UserDirectory.PUBLIC_SHARE); defined_dirs.set(Environment.get_user_special_dir(UserDirectory.TEMPLATES), UserDirectory.TEMPLATES); defined_dirs.set(Environment.get_user_special_dir(UserDirectory.VIDEOS), UserDirectory.VIDEOS); which gets translated into calls like this one, for example: _tmp42_ = self->priv->defined_dirs; _tmp43_ = g_get_user_special_dir (G_USER_DIRECTORY_DOWNLOAD); gee_abstract_map_set ((GeeAbstractMap*) _tmp42_, _tmp43_, GINT_TO_POINTER (G_USER_DIRECTORY_DOWNLOAD)); If the userdir file is not present or the variable not defined in it, the call to g_get_user_special_dir will return null (documented behaviour), which will make gee_abstract_map_set fail. The code needs to be reworked to take into account that these dirs might not be set. ** Package changed: gnome-control-center (Ubuntu) => activity-log-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1024057 Title: gnome control center crashed when attempting to open privacy dialogue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1024057/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1024057] Re: gnome control center crashed when attempting to open privacy dialogue
** This bug is no longer a duplicate of bug 983934 gnome-control-center crashed with SIGSEGV in gtk_tree_model_get_valist() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1024057 Title: gnome control center crashed when attempting to open privacy dialogue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1024057/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1024057] Re: gnome control center crashed when attempting to open privacy dialogue
*** This bug is a duplicate of bug 983934 *** https://bugs.launchpad.net/bugs/983934 ** This bug has been marked a duplicate of bug 983934 gnome-control-center crashed with SIGSEGV in gtk_tree_model_get_valist() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1024057 Title: gnome control center crashed when attempting to open privacy dialogue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1024057/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
This problem is also present in KDE, so it's not a bug exclusive to gnome-screensaver. As was said before, this is a problem with the way X was designed, and the solutions imply either re-designing X (I doubt there are many people up to such a task) or working around it. For suspend/hibernate there's the inhibitor locks design doc from Freedesktop, that could allow adding some hooks and forcing pop-up windows to close just before suspending: http://www.freedesktop.org/wiki/Software/systemd/inhibit It's a different story when trying to manually lock (ctrl-alt-l), since the keyboard is grabbed by the pop-up, no application receives the lock combination and no application can then act appropriately. In any case it's quite a hard bug to fix, that requires a well thought solution, not a quick hack to fix it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
Thanks Sebastian, Steve, and everybody else involved in getting this fixed in precise! -- 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/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
I'm attaching a revised version, taking into account Ryan's comments. ** Patch added: "Updated patch" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+attachment/3418204/+files/fix-g-s-d-gconf-plugin.diff ** Patch removed: "Patch to the plugin" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+attachment/3418020/+files/fix-g-s-d-gconf-plugin.diff -- 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/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
Joel, regarding the Alt-Tab thing, it's reported in: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/963125 -- 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/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 509661] Re: Screen layout not remembered
Hi, This bug is still present and very easy to reproduce: * Plug in an external monitor to a laptop * Set it up different than the default. * Unplug the external monitor / Plug it in again * You'll need to go through the settings again. It'd be really nice if there was _some_ way to change the default. Either remembering the previous setting, or manually selecting a "use this setting as default". ** Changed in: gnome-settings-daemon (Ubuntu) Status: Expired => Confirmed -- 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/509661 Title: Screen layout not remembered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/509661/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
Hi, I have prepared and tested a small patch that fixes this issue. What the patch does is not update any keys when dconf emits the "everything changed" signal. To do this, it connects to the "event_change" signal and checks if the number of keys is 0, and returns TRUE in that case to prevent the "changed" signal from executing. I have tested that the dconf update call does not trigger the overwriting of keys, but that when using dconf-editor to edit keys, these values are copied over to gconf. ** Patch added: "Patch to the plugin" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+attachment/3418020/+files/fix-g-s-d-gconf-plugin.diff -- 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/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
This is my take on the issue from what I spoke with dsert earlier today: There's a signal that dconf update emits when there are changes, so that monitoring stuff can find out about it. This plugin is one of the monitoring stuff. The plugin is supposed to sync up settings from dconf to gconf for programs that are not aware of gconf. I think it's wrongly copying everything from dconf to gconf regardless of what the user had previously modified. What it _should_ do is only copy the stuff that comes from dconf but not what was modified directly in gconf. I suspect this is not possible. -- 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/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
Sample configuration that allows to reproduce the bug. ** Attachment added: "Sample /etc/dconf configuration to reproduce the bug." https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+attachment/3414956/+files/etc-dconf-files-reduced.tar.gz ** Attachment removed: "Sample /etc/dconf configuration to reproduce the bug." https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+attachment/3414955/+files/etc-dconf-files-reduced.tar.gz -- 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/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
I've reduced the amount of files needed in order to reproduce the bug. ** Attachment added: "Sample /etc/dconf configuration to reproduce the bug." https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+attachment/3414955/+files/etc-dconf-files-reduced.tar.gz ** Attachment removed: "Sample /etc/dconf configuration to reproduce the bug." https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+attachment/3414940/+files/etc-dconf-files.tar.gz -- 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/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] [NEW] gnome-settings-daemon dconf to gconf plugin causes settings to be lost
Public bug reported: This was tested in a fresh installed precise machine, with the addition of dconf and a particular dconf configuration. Settings set in gconf backend get overwritten when running 'dconf update'. This can be tested by changing any value in gconf to something different than the default: $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false $ gconftool --get /desktop/gnome/sound/event_sounds false $ gconftool --set /apps/metacity/general/focus_mode --type string sloppy $ gconftool --get /apps/metacity/general/focus_mode sloppy Then editing some file under /etc/dconf and running dconf update: $ sudo vi /etc/dconf/db/site.d/screensaver $ sudo dconf update $ gconftool --get /desktop/gnome/sound/event_sounds true $ gconftool --get /apps/metacity/general/focus_mode click After talking about this with Ryan Lortie, he suggested disabling the gnome-settings-daemon plugin: $ gsettings set org.gnome.settings-daemon.plugins.gconf active false $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false $ gconftool --set /apps/metacity/general/focus_mode --type string sloppy $ sudo vi /etc/dconf/db/site.d/screensaver $ sudo dconf update $ gconftool --get /desktop/gnome/sound/event_sounds false $ gconftool --get /apps/metacity/general/focus_mode sloppy It looks like the gconf plugin is overwriting all the settings with the defaults, thus losing anything the user had customized. It's quite likely that a number of other bugs "Compiz loses my settings" are actually caused by this plugin. Also, as instructed by Ryan, I tried removing /usr/share/GConf/gsettings /wm-schemas.convert and re-enabling the plugin, and then it doesn't override any values that are related to the window manager but it does override the one in the example: $ gsettings reset org.gnome.settings-daemon.plugins.gconf active $ gsettings get org.gnome.settings-daemon.plugins.gconf active true $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false $ gconftool --set /apps/metacity/general/focus_mode --type string sloppy $ sudo vi /etc/dconf/db/site.d/screensaver $ sudo dconf update $ gconftool --get /desktop/gnome/sound/event_sounds true $ gconftool --get /apps/metacity/general/focus_mode sloppy So, focus_mode didn't get overwritten while event_sounds did. One possible solution is to remove the wm-schemas so that compiz settings don't get lost. A better (but probably harder) solution would be to fix the plugin so that it doesn't overwrite what the user sets. Maybe just remove the schemas that are being modified and stored in gconf for Precise. I found out that to reproduce in a fresh installed precise machine, I had to set up some dconf files, then reboot, and then I could reproduce consistently as explained here. I'm attaching a bunch of dconf files. After unpacking, you need to run dconf update once to generate the db and then reboot. After that it should be reproducible. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Sample /etc/dconf configuration to reproduce the bug." https://bugs.launchpad.net/bugs/1071950/+attachment/3414940/+files/etc-dconf-files.tar.gz -- 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/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1035219] Re: In System Settings preference tool/keyboard layouts page automaticaly wrong language selectedGNOME
Hi, Ok, I've looked at it a bit more, and I guess you are right. Do you have any idea if/when this patch is going to get applied to precise? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1035219 Title: In System Settings preference tool/keyboard layouts page automaticaly wrong language selectedGNOME To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1035219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1035219] Re: In System Settings preference tool/keyboard layouts page automaticaly wrong language selectedGNOME
Hi, I tested the patch and it indeed "solves" the same issue for me. However, the solution is only to not display the Language window at all. What was wrong with the Language window that it didn't pre-select the current selected language? I think that fixing that behaviour would be better, since it doesn't remove functionality as the proposed patch does. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1035219 Title: In System Settings preference tool/keyboard layouts page automaticaly wrong language selectedGNOME To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1035219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 64538] Re: window resizing limited due to the new search bar
Hi! I'm using Debian Lenny and I really needed this bug fixed, so I spent quite a number of hours digging into Evolution until I found a way. I'm attaching the diff I made for the Debian package, I'm not sure if it'll be useful for ubuntu or for which versions of ubuntu it'd be useful, because evolution's files keep changing (more than the usual app), but I didn't want my work to be only for me, so I decided to attach it here, in case anyone else needs it. It's a patch for Debian Lenny's 2.22 version, that allows the search bar to shrink more (half of the current minimum size) and also allows it to expand to fill any empty space. Thus, evo looks good from 800x600 to 1280x1024. ** Attachment added: "Make the search-bar have a smaller minimum size and allow it to grow as much as needed. For Debian Lenny 2.22's version." http://launchpadlibrarian.net/33037291/evolution-2.22-debian-lenny-searchbar.patch -- window resizing limited due to the new search bar https://bugs.launchpad.net/bugs/64538 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
