[Bug 1625235] [NEW] lxc doesn't follow xdg basedir spec if XDG_DATA_HOME is set
Public bug reported: Pretty simple bug: lxc-create: utils.c: mkdir_p: 253 Permission denied - failed to create directory '/home/desrt/.local/share/lxc' desrt@humber:~$ echo $XDG_DATA_HOME /home/desrt/.var/lib lxc has no business putting files in ~/.local/share if XDG_DATA_HOME is set elsewhere. Please see https://standards.freedesktop.org/basedir- spec/basedir-spec-latest.html ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Description changed: Pretty simple bug: lxc-create: utils.c: mkdir_p: 253 Permission denied - failed to create directory '/home/desrt/.local/share/lxc' - desrt@humber:~/code/dconf$ echo $XDG_DATA_HOME + desrt@humber:~$ echo $XDG_DATA_HOME /home/desrt/.var/lib - - lxc has no business putting files in ~/.local/share if XDG_DATA_HOME is set elsewhere. Please see https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html + lxc has no business putting files in ~/.local/share if XDG_DATA_HOME is + set elsewhere. Please see https://standards.freedesktop.org/basedir- + spec/basedir-spec-latest.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625235 Title: lxc doesn't follow xdg basedir spec if XDG_DATA_HOME is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1625235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506744] Re: Newly installed applications do not show in the dash
To elaborate on the previous remark: why didn't we just replace: menu_monitor_queue_event (event_info); with: g_timeout_add_seconds (2, menu_monitor_queue_event, event_info); (and make sure menu_monitor_queue_event() returns FALSE)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506744] Re: Newly installed applications do not show in the dash
The latest patch looks good to me, but with a couple of notes (no need to fix these): - using the _full() version of the timeout call is not necessary here - now that this patch is simplified it becomes easy to see how all of this is just putting values into one structure and then later moving them into another structure. It seems like we could have just used the first structure type, or even just fixed the other queue mechanism to add the delay. Oh well. No real gain from making that change at this point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506744] Re: Newly installed applications do not show in the dash
The patch in comment 42 is not acceptable, for two big reasons. First: you need to hold a ref on the GFile object when you put it into the info struct. This means that you cannot simply use g_free for the struct: you need to write a custom free func that handles the unref as well. Also: you can't cast g_source_remove() to a GDestroyNotify and expect that to work... one takes a pointer, and the other an int. This may randomly work on some architectures, sometimes, but you cannot rely on this. The entire act of keeping the list is slightly suspect. At the sprint I think I mentioned that it would be better to have one global timeout that is set (and reset) when any activity happens. The timeout would run after the activity died down, and it would handle all things together in one go. In that case, you'd still need a list, except for the info objects themselves. It's also fine to keep the list of the timeout IDs, but you can't free it in the way that you're doing in the current patch. Another nice approach, if you want to avoid running the callbacks after teardown: store a weak pointer to the main object in each of the info structs (g_object_add_weak_pointer). The info structs are then used as the user_data to the timeout (this assumes you keep the multiple timeouts). If you find the weak pointer to be empty, then just return without doing anything. That also means that you don't need to handle the "cleanup" -- it will happen automatically. It also means that you can avoid the custom free function if you are clever: the timeout will always run once, and you can do the cleanup from the normal handler (taking care regarding the early exit discussed above). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576066] [NEW] 32bit glibc calls old socketcall() syscall, causing seccomp problems
Public bug reported: Back in the day when Linux was created for i386, for who knows what reason, all socket calls were multiplexed through a single syscall API, socketcall(). This was a strange thing to do, but it probably made sense from the standpoint of the same part of the kernel handling all of those calls. It was realised a long time ago that this was a strange and suboptimal arrangement. By the time they got around to doing amd64 and other architectures, they fixed this arrangement and gave each socket call a separate syscall entry point. 32bit systems continued to do it this old way, however, multiplexing all calls through socketcall(). This is a problem for seccomp. If we want to allow a program to make casual use of the network, but not bind a listener socket, we cannot currently do that. On 64bits we just filter out the bind() and listen() calls, but on 32bit, it's all the same syscall. The kernel people fixed this problem up last summer by introducing new, separate, syscall entries for each separate call. http://patchwork.sourceware.org/patch/7679/ The problem is that glibc in Y is still using the old socketcall() interface on i386. It needs to be updated to use the new calls. A possible caveat is that this might create problems for running newer binaries on older kernels on i386 (as we sometimes do with builders) because they won't have the new syscalls. A solution could involve checking for ENOSYS and trying again via the old route. ** Affects: glibc (Ubuntu) Importance: High Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576066 Title: 32bit glibc calls old socketcall() syscall, causing seccomp problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1576066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512002] Re: Annoying dialog "Authentication is required to change your own user data"
Although I agree that it makes sense to allow the user to modify their own data even if not "actively logged in", I think it would also be interesting to track down the program that is the real source of this problem. ie: let's figure out which part of the session is writing to accountsservice at random times... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512002 Title: Annoying dialog "Authentication is required to change your own user data" To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1512002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279021] Re: CacheDir setting ignored
Same bug here and, indeed: zz_debconf.conf:CacheDir: /var/cache/apt-cacher-ng # default or overridden since '/var/cache/apt-cacher-ng' directory didn't exist I spent more time than I care to admit tracking this problem down and this situation is pretty frustrating. I particularly love this part: # To override this values permanently, put the assignments into a file # like /etc/apt-cacher-ng/zzz_override.conf . Of course. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279021 Title: CacheDir setting ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1279021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1485659] Re: Date/time indicator doesn't update after changing time zone
A couple of notes: - this is fixed upstream in GLib already - watching dbus for the signal is fine, but you should not use dbus to read the property in the first place. This will result in activation of the datetime service, which is expensive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1485659 Title: Date/time indicator doesn't update after changing time zone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1485659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged
Just to play devil's advocate a bit here: The logic taken in this bug (that we should show the device that will run out of power first) seems perfectly sound, but it makes a very large assumption, which I suspect will often be untrue: that reporting of time remaining on mice will always be completely accurate. I think there are two problems with the assumption. The first is that there have been reports (one just now on IRC from jcastro) about faulty hardware/driver combos that report things like 1 minute remaining all the time. Users with this hardware would probably like that fixed, but for lack of a fix, would probably prefer to be able to go on with their lives with the minimum amount of disruption. Second issue is that I wonder if estimated time left reporting on a device which has a battery that lasts up to a year is _ever_ accurate to the hours or minutes that we would need it to be in order to meaningfully compare it against laptop battery life. Those two point combined cause me to believe that the only case in which this feature would be engaged would be in the wrong case. Maybe it makes sense to just remove it entirely after all? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315434 Title: Mouse with no time remaining estimate showing in preference to battery being charged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430542] [NEW] Indicator doesn't use weighted average with different-sized batteries
Public bug reported: The indicator implements the spec: https://wiki.ubuntu.com/Power#Handling_multiple_batteries which states: Their percentages should be averaged. Apparently this was taken to mean the simple arithmetic mean, and not the weighted average (by the capacity of each battery). http://bazaar.launchpad.net/~indicator-applet-developers/indicator- power/trunk.15.04/view/head:/src/service.c#L1316 shows: const double percent = sum_percent / n_batteries; This means that if one battery is twice as large as another, then after that battery is discharged, 50% would be reported. I'd expect 33%. The spec needs to be updated to be less ambiguous about the intended meaning of the word average and the code needs to be fixed. ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430542 Title: Indicator doesn't use weighted average with different-sized batteries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1430542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 867424]
There is really no good reason for this code to exist anymore. I ended up with libgnome installed as a dependency for another old program and my Firefox install started misbehaving as a (nearly untracable) sideeffect of that. It took me quite a while to figure out that a Firefox bug could be triggered as a result of installing an unrelated program. The fact that I didn't have libgnome installed before, and everything was working just fine, is as much of an indication as any that this code needs to die. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/867424 Title: Oneric: On boot up Firefox always displays the “Well, This Is Embarrassing” screen. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284017] Re: gnome-shell crashed with SIGABRT in g_thread_abort()
In fact, I think this was fixed a year ago already: https://bugzilla.gnome.org/show_bug.cgi?id=724929 Did anyone see this in newer Ubuntu releases (ie: the released version of trusty or later)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284017 Title: gnome-shell crashed with SIGABRT in g_thread_abort() To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1284017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284017] Re: gnome-shell crashed with SIGABRT in g_thread_abort()
It's worth noting that this bug can no longer occur as it is described here -- g_mutex_lock() has been rewritten and the new version doesn't abort. That said, the underlying issue that was causing the misuse of a mutex could very well still exist... Unfortunately, it's very difficult to guess what that may be, at this point. ** Bug watch added: GNOME Bug Tracker #724929 https://bugzilla.gnome.org/show_bug.cgi?id=724929 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284017 Title: gnome-shell crashed with SIGABRT in g_thread_abort() To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1284017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364070] Re: vivid, utopic and trusty unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up
Yup. This is a GIO issue. We register a file monitor and don't bother checking if desktop files changed until we see the file monitor has fired. Due to inotify implementation issues, this usually happens about ~1s later. We will need to add a mechanism to force a reload and/or do it automatically in case we see a lookup failure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364070 Title: vivid, utopic and trusty unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1364070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1404599] [NEW] libpam-mount installs pkgconfig in /lib
Public bug reported: In vivid (and maybe other releases) libpam-mount installs the file /lib/pkgconfig/libcryptmount.pc That's strange for two reasons: 1) pkg-config files should not be installed by non-'-dev' packages 2) pkg-config files won't be found in /lib/pkgconfig Note for example: (vivid-amd64)desrt@spadina:~$ pkg-config --libs libcryptmount Package libcryptmount was not found in the pkg-config search path. Perhaps you should add the directory containing `libcryptmount.pc' to the PKG_CONFIG_PATH environment variable No package 'libcryptmount' found but forcing it will demonstrate that the package is installed: (vivid-amd64)desrt@spadina:~$ PKG_CONFIG_PATH=/lib/pkgconfig pkg-config --libs libcryptmount -lcryptmount ** Affects: libpam-mount (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libpam-mount in Ubuntu. https://bugs.launchpad.net/bugs/1404599 Title: libpam-mount installs pkgconfig in /lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpam-mount/+bug/1404599/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1404599] [NEW] libpam-mount installs pkgconfig in /lib
Public bug reported: In vivid (and maybe other releases) libpam-mount installs the file /lib/pkgconfig/libcryptmount.pc That's strange for two reasons: 1) pkg-config files should not be installed by non-'-dev' packages 2) pkg-config files won't be found in /lib/pkgconfig Note for example: (vivid-amd64)desrt@spadina:~$ pkg-config --libs libcryptmount Package libcryptmount was not found in the pkg-config search path. Perhaps you should add the directory containing `libcryptmount.pc' to the PKG_CONFIG_PATH environment variable No package 'libcryptmount' found but forcing it will demonstrate that the package is installed: (vivid-amd64)desrt@spadina:~$ PKG_CONFIG_PATH=/lib/pkgconfig pkg-config --libs libcryptmount -lcryptmount ** Affects: libpam-mount (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404599 Title: libpam-mount installs pkgconfig in /lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpam-mount/+bug/1404599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384776] Re: Occasional hang in unity 8 dash on the phone
I'm not sure it would be very helpful for me to review this either -- I'm very unfamiliar with the codebase and even with how locking works in libdbus-1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384776 Title: Occasional hang in unity 8 dash on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1384776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383486] Re: menu to select zoom doesn't drop down
This was fixed upstream here: https://git.gnome.org/browse/gtk+/commit/?id=a1af365566161067c4eb246a1c66e7914f119537 Unfortunately this doesn't backport cleanly. I'll try to rebase the patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383486 Title: menu to select zoom doesn't drop down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1383486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383486] Re: menu to select zoom doesn't drop down
It will work if we also take 0dcffe3cd421555926e74002d5297d6dac0886e7, which is another bugfix that may be worth having. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383486 Title: menu to select zoom doesn't drop down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1383486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383486] Re: menu to select zoom doesn't drop down
Both have been pushed upstream on gtk-3-12 branch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383486 Title: menu to select zoom doesn't drop down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1383486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384776] [NEW] Occasional hang in unity 8 dash on the phone
Public bug reported: The dash is sometimes hanging on the phone. See the attached backtrace. The issue is as follows: we are maintaining a client-side tree of all NetworkManager devices. When we see that a new device has been added, we query its properties in order to build our local proxy. Doing this means that we are making QtDBus calls from a signal handler. Due to a bug in QtDBus this is not safe. libdbus-1 has a recursive lock on its DBusConnection. When the signal arrives, the lock is acquired and the sginal handler is run. The signal handler can make DBus calls (which also require the lock) because the lock is recursive. QtDBus also has a lock that is always acquired before the libdbus-1 connection lock is acquired. Unfortuntaely, the QtDBus lock is not acquired in the case of the incoming call from DBus -- only the DBus lock is. If another thread tries to do an unrelated DBus call meanwhile, it will acquire the QtDBus lock first and then the DBus lock (which is held because of the signal that arrived). Once the signal handler gets to the point of wanting to make a DBus call (in order to query the properties of the just-added network device) it will attempt to acquire the QtDBus lock. This is a lock-inversion deadlock. There are at least three bugs here: 1) QtDBus should be fixed in order to avoid this sort of lock inversion problem. Even if we fix this one situation, it seems quite likely that issues like this will arise again. 2) QNetworkManager should avoid the issue in QtDBus until such a time as it is fixed. This could be done by dispatching to a worker thread on receipt of signals so that the queries are done in a fresh call stack (without the libdbus-1 lock held). 3) Apparently the only reason we are using NetworkManager at all is in order to know if we are on a 3G connection or not (in order to avoid too much data charges). This would be much easier to do if NetworkManager provided a property that we could watch directly instead of bringing up an entire tree of objects in order to answer a very simple question. To that end I've filed https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can hopefully get addressed relatively quickly. I consider 3) to be the real fix as far as we are concerned, but we should probably ensure that the Qt people know about 1) and 2). Either of those could function as a workaround for us in the meantime, but the idea that we are creating this complex object tree to answer a simple question is ridiculous, so we should really fix that directly. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384776 Title: Occasional hang in unity 8 dash on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1384776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384776] Re: Occasional hang in unity 8 dash on the phone
** Attachment added: backtrace https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1384776/+attachment/4242439/+files/backtrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384776 Title: Occasional hang in unity 8 dash on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1384776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384776] Re: Occasional hang in unity 8 dash on the phone
The patch already went upstream in NetworkManager and now we have an Ubuntu package landing soon. The upshot is that we now have a simple DBus property: system org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.PrimaryConnectionType which is a string like '802-11-wireless' or 'bluetooth'. If there is no connection then it is an empty string. We don't have normal D-Bus property change notification here but rather a custom-rolled signal from NetworkManager itself (PropertiesChanged). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384776 Title: Occasional hang in unity 8 dash on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1384776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1344386] Re: Do.exe crashed with SIGABRT in __GI_raise()
GLib completely changed the implementation of GMutex from being based on POSIX primatives to being based on a home-grown solution that is substantially faster (and with room for further improvements). This caused deadlocks/crashes in some Vala programs, and I wonder if the same thing is going on with Mono. See this bug: https://bugzilla.gnome.org/show_bug.cgi?id=733500 ** Bug watch added: GNOME Bug Tracker #733500 https://bugzilla.gnome.org/show_bug.cgi?id=733500 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1344386 Title: Do.exe crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1344386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1344386] Re: Do.exe crashed with SIGABRT in __GI_raise()
Invalid for glib since the bug is confirmed as being in gnome-do (not acquiring the lock before gtk_main). ** Changed in: glib2.0 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1344386 Title: Do.exe crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1344386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1344386] Re: Do.exe crashed with SIGABRT in __GI_raise()
The new mutex implementation detects the (error) case when you try to unlock a mutex that is not locked. Callers are supposed to acquire the Gtk lock before calling gtk_main() and I guess gnome-do isn't doing that... POSIX silently ignores this... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1344386 Title: Do.exe crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1344386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1344386] Re: Do.exe crashed with SIGABRT in __GI_raise()
** Also affects: do Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1344386 Title: Do.exe crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/do/+bug/1344386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333632] Re: D-Bus interface is hard to use
On a somewhat higher level, the separate concepts of state requests and state change acknowledgement, and their interaction, are very underspecified. For example, what happens when a client fails to acknowledge a state change? What if a client is only interested in some types of changes? How are the clients identified (ie: why no cookies on this part of the API)? It might be useful to look at what logind has done in the same problem space -- it has a far more fleshed-out API. It decided to merge these two concepts and allow establishing two types of locks on each type of event -- one for demanding a particular state and one for notification about that state: http://www.freedesktop.org/wiki/Software/systemd/inhibit/ Note that the details of what happens when clients misbehave are well spelled-out. It also has a very nice mechanism of avoiding cookies and the need to unregister them: it uses file descriptors. When you close the fd (which automatically happens on program crashes, for example) then the request is cancelled. The additional things that exist on the powerd API could be introduced as additional 'what' type (proximity sensor, etc). About those things: the interaction between different requests from clients should be better documented. What if one client asks for the display to be on and another asks for the proximity detector to turn the display off? Does it matter which app is in the foreground or does one request always override the other? One more high level 'flavour' comment: the comment in the API doc about If this is the last request to keep the screen on, it will turn off. is not what you want. Presumably you have some sort of hooks into the display server to monitor for user inactivity -- what you want to do is to restart the inactivity timer at the point that the last request is dropped. Consider that I am playing a video and the video comes to an end. The video player releases its keep the screen on lock. I don't want the screen to turn off immediately in this case, but rather I'd like if the usual idle rules came into play. We can't do this just by having idle being considered as a separate thing ,either, because if the video was long enough, the user input has probably already been idle for a long time. We actually need to restart the counter from 0 when the last request drops. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333632 Title: D-Bus interface is hard to use To manage notifications about this bug go to: https://bugs.launchpad.net/powerd/+bug/1333632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296233] Re: increase in number of wakeups in recent release in indicator-datetime
This is my fault indeed. I introduced the code that added this watch without remembering that it does the wrong thing in the case of missing directories. I think the correct fix here is to reevaluate our approach to dealing with missing files in the inotify monitor... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296233 Title: increase in number of wakeups in recent release in indicator-datetime To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1296233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284647] Re: gsettings crashed with SIGSEGV in g_settings_backend_dispatch_signal()
Confirmed GLib bug: https://bugzilla.gnome.org/show_bug.cgi?id=710367 ** Bug watch added: GNOME Bug Tracker #710367 https://bugzilla.gnome.org/show_bug.cgi?id=710367 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284647 Title: gsettings crashed with SIGSEGV in g_settings_backend_dispatch_signal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1284647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 956046] Re: intel driver fails to use dual-link LVDS if lid is down at boot
As noted on the upstream bug, this has been fixed for quite some time already. I'm guessing (through no special effort) this fix has made its way into Ubuntu at some point and is therefore fixed there as well. ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/956046 Title: intel driver fails to use dual-link LVDS if lid is down at boot To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/956046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 967879] Re: hud-service has a memory leak (I think)
** Changed in: indicator-appmenu (Ubuntu) Assignee: Ryan Lortie (desrt) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/967879 Title: hud-service has a memory leak (I think) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/967879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1235797] Re: Will not let me download an ISO directly from Gnome-Boxes
Pretty sure that this feature doesn't do in-app downloads, but rather is just showing images that are already in your Downloads folder. Even the text below says ...software products you have already obtained ** Changed in: gnome-boxes (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235797 Title: Will not let me download an ISO directly from Gnome-Boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1235797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171587] Re: update to GTK 3.9 and the issues to resolve for it
https://bugzilla.gnome.org/show_bug.cgi?id=712302 is now resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171587 Title: update to GTK 3.9 and the issues to resolve for it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1171587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246516] Re: Memory from slice allocator passed to PyObject_Free
This is not the same as the error we were seeing before: that error was an invalid read on memory that was just before a piece of memory that was allocated through the slice allocator. There is no gslice in this trace... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1246516 Title: Memory from slice allocator passed to PyObject_Free To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1246516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222053] Re: per-session gsettings overrides
Worth noting that it's already possible to add new directories to the schema search path via GSETTINGS_SCHEMA_DIR. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222053 Title: per-session gsettings overrides To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1222053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196752] Re: Suspend only works once when using upower with logind -- s-shim needs to call /lib/systemd/system-sleep/*
No. I talked about this with Martin today and we both agree that it's not really worth it for supporting a deprecated API that we will remove soon anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196752 Title: Suspend only works once when using upower with logind -- s-shim needs to call /lib/systemd/system-sleep/* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1196752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206314] Re: install-default-webapps-in-launcher.py crashed with signal 5 in g_settings_get_mapped()
Line 1520 in that file looks like so: g_error (The mapping function given to g_settings_get_mapped() for key '%s' in schema '%s' returned FALSE when given a NULL value., key, g_settings_schema_get_id (settings-priv-schema)); which is a pretty good indicator of what's probably happening here. Quoth the docs: If the mapping function fails for all possible values, one additional attempt is made: the mapping function is called with a NULL value. If the mapping function still indicates failure at this point then the application will be aborted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206314 Title: install-default-webapps-in-launcher.py crashed with signal 5 in g_settings_get_mapped() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1206314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206314] Re: install-default-webapps-in-launcher.py crashed with signal 5 in g_settings_get_mapped()
So indeed, the script contains this code:
first_mapping = [True]
def mapping_callback(value, first_mapping):
if not value:
return (True, [])
if first_mapping[0]:
first_mapping[0] = False
return (False, value)
return (True, value)
def get_default_value_for(settings, key):
return settings.get_mapped(UNITY_LAUNCHER_FAVORITE_KEY, mapping_callback,
first_mapping)
Which looks like it's fine because of:
if not value:
return (True, [])
but for some reason, the python bindings are unable to deal with this.
Running the script gives warnings like so:
** (process:21913): WARNING **: (pygi-
argument.c:903):_pygi_argument_from_object: runtime check failed:
(transfer == GI_TRANSFER_NOTHING)
before crashing with the error from the previous comment.
An easier way of getting the default value of a key (and the one most commonly
used by other developers) is this pattern:
1) create a GSettings object
2) .delay()
3) .reset('key')
4) .get('key')
5) free the object without calling .apply()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1206314
Title:
install-default-webapps-in-launcher.py crashed with signal 5 in
g_settings_get_mapped()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1206314/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1207408] Re: gnome-contacts fails to build: memory-icon.vala:29.1-29.63: error: `Contacts.MemoryIcon' does not implement interface method `GLib.Icon.serialize
This needs to be fixed upstream by deleting MemoryIcon and replacing it with BytesIcon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1207408 Title: gnome-contacts fails to build: memory-icon.vala:29.1-29.63: error: `Contacts.MemoryIcon' does not implement interface method `GLib.Icon.serialize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vala-0.20/+bug/1207408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205562] Re: [background] wallpapers in grid are too small, take long time to load
Patch here. Please test. https://bugzilla.gnome.org/show_bug.cgi?id=705320 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205562 Title: [background] wallpapers in grid are too small, take long time to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1205562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205562] Re: [background] wallpapers in grid are too small, take long time to load
Gtk bug. Gtk puts loadable icons ahead of pixbufs in its icon loading code, and now that GdkPixbuf is a gloadable icon, it'll take the slow path. The order of the cases in gtkicontheme.c:gtk_icon_theme_lookup_by_gicon_for_scale() needs to be changed. ** Bug watch added: GNOME Bug Tracker #705320 https://bugzilla.gnome.org/show_bug.cgi?id=705320 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205562 Title: [background] wallpapers in grid are too small, take long time to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1205562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager
This is an issue between logind and gnome-session. Once systemd-shim gets the instruction to shutdown, it shuts down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 922968] Re: shouldn't queue a second suspend if the machine is already suspending
hi James, Unfortunately we handle suspend in a much more ad-hoc way on precise. There is no logind or systemd-shim through which all suspend requests are handled. These changes are therefore not really possible to backport. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922968 Title: shouldn't queue a second suspend if the machine is already suspending To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/922968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 922968] Re: shouldn't queue a second suspend if the machine is already suspending
We fixed this issue in saucy by moving responsibility for handling suspend into systemd-shim and adding a check there to ignore suspend requests that come in during a very small window after waking up. From personal reports, this has solved the issue for everyone who has tried it. I'm not totally happy with the solution -- I would prefer if we had one based on the timestamps of the source of the suspend (ie: clicking a menu item with the mouse, lid-close events, etc) and were able to compare that with the time of the suspend itself. This requires some changes to logind, though. This has been discussed with upstream and we're waiting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922968 Title: shouldn't queue a second suspend if the machine is already suspending To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/922968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1159036] Re: gedit 3.7 doesn't display application menu
*** This bug is a duplicate of bug 999827 *** https://bugs.launchpad.net/bugs/999827 This is an old bug in the appmenu indicator. gedit gives an appmenu via GMenu but also has oldschool GtkMenu menus for the menubar. Unity can't deal with both of these at the same time. ** This bug has been marked a duplicate of bug 999827 App menus aren't shown in the panel if the app is also exporting menus via dbusmenu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1159036 Title: gedit 3.7 doesn't display application menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1159036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999827] Re: App menus aren't shown in the panel if the app is also exporting menus via dbusmenu
fwiw: this will be fixed when unity-gtk-module lands. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/999827 Title: App menus aren't shown in the panel if the app is also exporting menus via dbusmenu To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/999827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999827] Re: App menus aren't shown in the panel if the app is also exporting menus via dbusmenu
note also: unity-gtk-module is pretty much ready to land but it didn't make feature freeze, so I guess it will be landing early in 'S'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/999827 Title: App menus aren't shown in the panel if the app is also exporting menus via dbusmenu To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/999827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152187] Re: [MIR] systemd
I've reviewed the review in comment #14 and looked over the code myself as well as talking to Lennart. Point-by-point: - I don't understand why having /etc/localtime as a symlink is anything but desirable other than that Debian didn't do it this way before. I do notice that the symlink is not replaced atomically (using the rename- temp trick), however, meaning that the system is (de facto) on UTC for a short period during changes. I've raised this point with upstream. - The race condition between checking timezone validity and changing the timezone is a total non-issue; mostly for the reason that you mention, but also because even if the timezone was erased _after_ the link was established, the result would be the same: dangling symlink. This is really not a race... - the story with hwclock_set_timezone() and hwclock_reset_timezone() is stupidly complicated because of Linux being ridiculous on this point. The kernel wants to know the timezone for two reasons: in case the RTC is in localtime, it wants to jog the system time (that it assumed was in UTC) to proper UTC. This is done only on the first call to settimeofday(). The kernel also wants to know the timezone for other reasons though (like setting proper timestamps on FAT filesystems). The way to set the timezone for these other reasons without doing the 'first time warp' is to first set a NULL timezone (no warp on the first time) and then make a second call to actually set the timezone. I agree that it's stupid that the kernel should want to know what timezone userspace thinks that it's in, but that's how it is... - the write_data_local_rtc() point you raise is valid code, but utterly ugly. I asked Lennart to rewrite it. - the wraparound issue: I assume you mean that relative time changes are not checked for wrapping the clock. I don't think this is a big problem since it's a privileged operation and you could simply say that this is the semantics of the interface (and honestly, I can't imagine what else you would want to happen in this situation -- we could end up with a clock set to a ridiculous time, but we could end up with that anyway). - localised strings: true. - Lennart claims that realloc() is smart enough not to reallocate every time so we'd be wasting our time by trying to duplicate its efforts. That claim seems a bit suspect from the standpoint of my doubt that it would waste as much as double the amount of requested memory, but I didn't investigate further. I don't believe this to be a substantial problem in any case. - The examples you give for hostnames accepted by hostname_is_valid() are obviously pretty bogus. This will be fixed upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152187 Title: [MIR] systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1152187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1153633] Re: [MIR] systemd-shim
Reply to some of the points raised: - Doesn't daemonize as usual -- is this intentional to ease upstart tracking the service? It's not required becaues the service is only ever started as a result of D-Bus activation. D-Bus is okay with that. - running_in_chroot() is liable to not function reliably in new namespaces; expect this to work only for traditional chroot environments - detect_container() may give silly results if kernel command line includes container=... string or if the userns namespace started init with funny environment variables This code is copied straight out of upstream systemd sources -- I'm trying to emulate what they do here. - _set_using_ntpdate() uses '/bin/mv -f' rather than rename(2) - _set_using_ntpdate() does not stop ntpd before starting ntpdate - _set_using_ntpdate() returns TRUE if ntpdate is not available - _set_using_ntpd() returns TRUE if ntpd is not available - _set_using_ntp_debian() returns TRUE if: (a) ntpd doesn't exist and ntpdate doesn't exist (b) ntpd doesn't exist and ntpdate started once (c) ntpd doesn't exist and if-up.d/ntpdate and if-up.d/ntpdate.disabled don't exist (d) ntpd was (re)started or stopped and ntpdate doesn't exist (e) ntpd was (re)started or stopped and ntpdate started once (f) ntpd was (re)started or stopped and if-up.d/ntpdate and if-up.d/ntpdate.disabled don't exist returns FALSE if errors returned while executing: (a) g_strconcat (/usr/sbin/update-rc.d ntp , using_ntp ? enable : disable, NULL); (b) g_strconcat (/usr/sbin/service ntp , using_ntp ? restart : stop, NULL);; (c) /bin/mv -f NTPDATE_DISABLED NTPDATE_ENABLED; (d) /bin/mv -f NTPDATE_ENABLED NTPDATE_DISABLED; (e) /etc/network/if-up.d/ntpdate The NTP code is gross but we already have it in Ubuntu as part of the gnome-settings-daemon datetime mechanism. It's true that this could use some cleaning up, but I wanted to go with 'tried and tested' rather than rewriting it too much. - return value of detect_virtualization() is ignored This is a good catch. I ignored the return value because in the case of failure I was just going to return the empty string, but on closer reading of the code I now see that detect_virtualization() doesn't actually set the return value in the failure case. I'll fix this by initialising to . - shim_get_property allocates memory with g_variant_new(), appears leaked. Is this the intentional way to use DBus? From the GDBus documentation for the callback type of this function: Returns : A GVariant with the value for property_name or NULL if error is set. If the returned GVariant is floating, it is consumed - otherwise its reference count is decreased by one. I'll fix up the virtualisation thing, but I think we should avoid refactoring the NTP code for now and clean it up after raring. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1153633 Title: [MIR] systemd-shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1153633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1154370] [NEW] [precise SRU] crash due to improper handling of / in GSettings
Public bug reported:
GSettings in GLib 2.32.3 has a bug where the changed signal is emitted
for child settings objects as if they were keys ending with /.
That was fixed upstream and merged into the glib-2-32 stable branch
here:
https://git.gnome.org/browse/glib/commit/?h=glib-2-32id=e6f659a898595ba944bd02f0509b14694d1c26e7
GLib 2.32.4 was since released and contains the fix.
This fix is needed because there exists software (muffin) that contains
code along these lines:
void
change_event_handler (GSettings *settings, const gchar *key, gpointer user_data)
{
...
g_settings_get_value (settings, key);
...
}
and it's invalid to pass a key containing / to g_settings_get_value()
(causing crashes).
This only happens when entire paths are reset (such as when running
'dconf update'). That makes the issue relatively rare but it's
affecting corporate deployments (Google, specifically).
We should either do an SRU with just the patch linked to above to
(ideally) QA and SRU the entire GLib 2.32.4 release to precise.
** Affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Package changed: ubuntu = glib2.0 (Ubuntu)
** Changed in: glib2.0 (Ubuntu)
Milestone: None = precise-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1153633] [NEW] [MIR] systemd-shim
Public bug reported: * The package is in universe and built on all archs: https://launchpad.net/ubuntu/+source/systemd-shim/0.0-0ubuntu1 * Rationale: This is a necessary part of the work to have systemd-services replacing ubuntu-system-services. The service emuates a few select systemd interface on an ad hoc basis in order to allow various things depending on systemd to work. For now this is the Virtualization property to detect if the system is a VM (with code to do this copied from systemd itself) and the unit control APIs for a faked ntpd.service unit. This allows timedated to think that it is requesting systemd to start and stop ntpd when really it is executing the logic that used to be in the Debian-specific gnome- settings-daemon patch we carried to setup and call ntpdate (but ntpd support is also included). Without this or the real systemd running, timedated won't even start. We could patch that away, but I don't want to get into the business of carrying large/ugly distro-specific patches to timedated when we can just as easily do the compatibility along a documented and stable interface (http://www.freedesktop.org/wiki/Software/systemd/dbus). It is expected that a few more odds and ends will be discovered over time that belong here. logind work is somewhat likely to kick up a thing or two. * Security: The code is small but it needs a full security review. The parts that enable/disable NTP were already running as root via the g-s-d DateTimeMechanism (although the code has been refactored a bit). The virtualisation detection code is copied straight out of systemd, which is being reviewed as part of the systemd MIR. The rest of the code (ie: mostly D-Bus logic) is newly-written. This is a system service running as root (so that it can start/stop NTP). The primary mechanism for security control is the D-Bus policy file. Root-owned processes are allowed to call all methods (no help there if they already have root). Other processes are only allowed access only to the standard D-Bus interfaces (Introspection, Peer) and property getters. The code dealing with property gets (there is only one property) is extremely small and unlikely to contain exploitable flaws. The D-Bus interfaces (Introspection, Peer) are implemented by GDBus and although it is complicated it is already running inside of several other system services. * Quality: - not a user-visible component in any way - no configuration settings - no exotic hardware interaction (although it does attempt to use some nice tricks to detect virtualization, but those are copied straight from systemd) - new code, no known bugs yet, but - when the bugs are found, I am the developer, so I'll fix them :) The desktop bugs team is subscribed to the package in launchpad, foundations/desktop will maintain the package and look to the bug reports regularly. ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: New ** Package changed: systemd (Ubuntu) = systemd-shim (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1153633 Title: [MIR] systemd-shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1153633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1153567] Re: [FFE] Use systemd-services rather than ubuntu-system-service systemdcompatibility code
Note also that this depends on the systemd-shim MIR being approved: bug 1153633 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1153567 Title: [FFE] Use systemd-services rather than ubuntu-system-service systemdcompatibility code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1153567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1153633] Re: [MIR] systemd-shim
See bug 1153567 for the blanket FFe (which was ACKed already). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1153633 Title: [MIR] systemd-shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1153633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1153567] Re: [FFE] Use systemd-services rather than ubuntu-system-service systemdcompatibility code
You need to ensure that you manually install the PPA versions of all 5 components listed above (since at least one of them is out of date in the PPA at the time of writing). Also need to install systemd-shim (which will eventually make it into at least a recommends of ubuntu- desktop at some point, I assume). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1153567 Title: [FFE] Use systemd-services rather than ubuntu-system-service systemdcompatibility code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1153567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 729056] Re: Date setting in the preferences should be not be shown in ISO format
This broke the preferences panel. The code to parse the text back into a unix timestamp can only deal with -mm-dd formatted strings so this either means that the user cannot change the date (by typing) or that the date is changed to something unexpected (for example, in the case that %x produces a 2-digit year, you may find yourself in the year 0013). ** Changed in: indicator-datetime Status: Fix Released = New ** Changed in: indicator-datetime Milestone: 0.2.93 = None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/729056 Title: Date setting in the preferences should be not be shown in ISO format To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/729056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037588] Re: Provide pkg-config pc files
Rebuilding the quantal package with the patch in this bug fixes the problem. I appreciate the reasons for not uploading this as an SRU but I think the least we can do is to offer a quantal package in the desktop-team PPA. Meanwhile, upstream jhbuild tries very hard not to introduce depdencies that would prevent it from building in stable releases of Ubuntu (being one of its primary target platforms). For example, our version of libicu is totally fine (except for this bug) and the webkit and js185 dependencies you mention are listed in the Optional section above (and indeed, jhbuild is happy to build those) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037588 Title: Provide pkg-config pc files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1037588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1104883] Re: dconf-service crashed with SIGSEGV in g_variant_is_trusted()
Fixed here: http://git.gnome.org/browse/glib/commit/?id=998c6e65cf18aee626b9982347c29b4b09f2c097 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1104883 Title: dconf-service crashed with SIGSEGV in g_variant_is_trusted() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1104883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1086868] Re: No global menu in Plasma (KDE) session in Raring
The D-Bus protocol used to communicate the menus to the shell has changed. Some gtk3 applications (not GIMP) were the first to be affected by this change, followed by Libreoffice. The rest of the Gtk applications will follow either this cycle or next. The plan is to completely eliminate the old protocol. The proper fix for this is to update the menu widget in the plasma desktop to speak the new protocol (GMenuModel). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1086868 Title: No global menu in Plasma (KDE) session in Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1086868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 845901] Re: libneon can't find SSLv2_server_method
This seems to be working on quantal now, but a SRU in precise would be nice. This got fixed in debian with this patch (which we also now have in quantal). http://patch- tracker.debian.org/patch/series/view/neon27/0.29.6-3/disabled_SSLv2_support.patch A good testcase: try to compile libmusicbrainz 5.0.1 with the non-gnutls version of the library (libneon27-dev) installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/845901 Title: libneon can't find SSLv2_server_method To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/845901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 845901] Re: libneon can't find SSLv2_server_method
** Description changed: - I just upgraded to Oneiric Beta 1, and in attempting to build Subversion - 1.7 from source, I get the following error: + [ Impact ] - /usr/lib/gcc/x86_64-linux-gnu/4.6.1/../../../../lib/libneon.so: undefined reference to `SSLv2_server_method' - collect2: ld returned 1 exit status - make: *** [subversion/svn/svn] Error 1 + Trying to build programs against libneon27-dev (non-gnutls version) is + broken in precise and lower. - I also get the above as a runtime error when running pre-built binaries. + [ Test Case ] - It appears that libneon27 is not linking to the correct libraries to - resolve the above function. I don't know if neon is or should be using - gnutls or openssl. - + (from original reporter) To reproduce: $ svn co https://svn.apache.org/repos/asf/subversion/branches/1.7.x wc $ cd wc $ ./autogen.sh $ ./configure $ make + + (from me) + Download and compile libmusicbrainz 5.0.1. + + Probably many other packages are impacted. + + [ Regression Potential ] + + Pretty slim -- it doesn't work at all right now due to missing symbols. + I'm not sure how it's possible that so few people have noticed this + other than the perhaps that the rdepend list for libneon27 is empty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/845901 Title: libneon can't find SSLv2_server_method To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/845901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1081328] [NEW] intermediate files incorrectly pruned in parallel builds
Public bug reported: There is a closed bug upstream that breaks parallel builds of webkit: http://savannah.gnu.org/bugs/?30653 Unfortunately 'make' hasn't had a release in years... The patch is pretty simple: http://cvs.savannah.gnu.org/viewvc/make/remake.c?root=maker1=1.153r2=1.154 We should consider introducing the one-liner fix as a distro patch (ideally with SRUs to precise and quantal). ** Affects: make-dfsg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1081328 Title: intermediate files incorrectly pruned in parallel builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1081328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1081328] Re: intermediate files incorrectly pruned in parallel builds
Interesting. I never considered the obvious possibility that this issue was first introduced in 3.82 and to be honest, I've never actually encountered it on my Ubuntu box. This may be a total non-issue... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1081328 Title: intermediate files incorrectly pruned in parallel builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1081328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1076426] Re: Argument length limitations prevent building some packages
I installed the package from precise-proposed yesterday (3.81-8.1ubuntu1.1) and built WebKit overnight. It worked (whereas before, it didn't). ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1076426 Title: Argument length limitations prevent building some packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1076426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
Ready to go, imho. Marga: one tiny point that I missed the first time around. GObject signals are nominally written like signal-name rather than signal_name. Your patch is fine as-is -- it's mostly a matter of style in this case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1042070] Re: soffice.bin crashed with SIGSEGV in g_menu_exporter_menu_prepare()
This is at least partially caused by an upstream bug in GLib. ** Bug watch added: GNOME Bug Tracker #685995 https://bugzilla.gnome.org/show_bug.cgi?id=685995 ** Also affects: df-libreoffice via https://bugzilla.gnome.org/show_bug.cgi?id=685995 Importance: Unknown Status: Unknown ** Project changed: df-libreoffice = glib ** Bug watch added: GNOME Bug Tracker #687089 https://bugzilla.gnome.org/show_bug.cgi?id=687089 ** Changed in: glib Remote watch: GNOME Bug Tracker #685995 = GNOME Bug Tracker #687089 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1042070 Title: soffice.bin crashed with SIGSEGV in g_menu_exporter_menu_prepare() To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1042070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
Functionally, the patch looks pretty good to me. Thanks for the attention to detail with respect to the signal disconnection. One small detail is that the function you introduce should be marked 'static' (since it is not used outside of the current file). Otherwise, everything else looks fine. A comment about why this function exists is probably also reasonable since it's non-obvious from just looking at it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
The issue specifically: 'dconf update' emits a signal that says everything has changed Meanwhile, we have the configuration migration stuff watching for changes and assuming that if there was a change in dconf it means that we should sync it up to gconf. The trouble comes that everything has changed actually only means everything has *potentially* changed. One way we can work around this is the change-event signal on GSettings. It allows two things: 1) We can find out the difference between everything changed and one thing changed. 2) We can return TRUE here to stop the signal from going further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045372] Re: libreoffice unity menu bars greyed out after opening any dialog or switching window
No worries. I've done the same. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045372 Title: libreoffice unity menu bars greyed out after opening any dialog or switching window To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-applet/+bug/1045372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045372] Re: libreoffice unity menu bars greyed out after opening any dialog or switching window
This bug is fixed says who. who is the person who found the source of the problem (me) and the person who fixed it (currently sitting across the table from me). But sure, if you insist, I'll open a new one. It's possible that the issue that you are describing is bug 1064962. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045372 Title: libreoffice unity menu bars greyed out after opening any dialog or switching window To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-applet/+bug/1045372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070905] [NEW] a11y panel calls g_settings_new() on (uninstalled) overlay scrollbar schema
Public bug reported: We have a patch in the control-centre that depends on a schema that may not be installed (if overlay scrollbars have been removed). This causes the entire control centre to crash when trying to open the a11y panel if overlay scrollbars have been uninstalled (which is something particularly likely to be done by a user requiring a11y features, since overlay scrollbars are known to cause issues for these users). ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070905 Title: a11y panel calls g_settings_new() on (uninstalled) overlay scrollbar schema To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1070905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070905] Re: a11y panel calls g_settings_new() on (uninstalled) overlay scrollbar schema
hi Will, Two notes: 1) you don't need to set this variable to NULL -- it will already be NULL by virtue of being in a GObject priv structure. 2) the code further down calls g_settings_set() on the object without first checking if it will be NULL, so in the case that you don't do g_settings_new() there will be a crash (or probably at least critical) there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070905 Title: a11y panel calls g_settings_new() on (uninstalled) overlay scrollbar schema To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1070905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064962] Re: Global menubar items do not work when opening a document directly from nautilus with no LibreOffice instance running
I can confirm this bug locally. Looking at the D-Bus log, I see: method call sender=:1.41 - dest=org.ayatana.bamf serial=480 path=/org/ayatana/bamf/window60817505; interface=org.ayatana.bamf.window; member=Xprop string _GTK_UNIQUE_BUS_NAME method return sender=:1.30 - dest=:1.41 reply_serial=480 string ... method call sender=:1.41 - dest=org.ayatana.bamf serial=461 path=/org/ayatana/bamf/window60817505; interface=org.ayatana.bamf.window; member=Xprop string _GTK_UNIQUE_BUS_NAME method return sender=:1.30 - dest=:1.41 reply_serial=461 string ... method call sender=:1.38 - dest=org.ayatana.bamf serial=524 path=/org/ayatana/bamf/window60817505; interface=org.ayatana.bamf.window; member=Xprop string _GTK_UNIQUE_BUS_NAME method return sender=:1.30 - dest=:1.38 reply_serial=524 string in essence: bamf is reporting that the _GTK_UNIQUE_BUS_NAME property is not set on the window when it is first presented. This means that either a) libreoffice is not setting the property before mapping the window (libreoffice bug) b) bamf is telling lies (bamf bug) Pretty sure we can rule out the chances of this being in any other component... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064962 Title: Global menubar items do not work when opening a document directly from nautilus with no LibreOffice instance running To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1064962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064962] Re: Global menubar items do not work when opening a document directly from nautilus with no LibreOffice instance running
The bamf code is a bit hairy, but basically it is synchronously calling XGetWindowProperty here, so I doubt that it's getting it wrong. Looks like a libreoffice issue... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064962 Title: Global menubar items do not work when opening a document directly from nautilus with no LibreOffice instance running To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1064962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045372] Re: libreoffice unity menu bars greyed out after opening any dialog or switching window
@#21: that is a different bug. This bug is fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045372 Title: libreoffice unity menu bars greyed out after opening any dialog or switching window To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-applet/+bug/1045372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1044322] Re: indicator-messages-service crashed with assert in g_menu_exporter_name_vanished()
Fixed upstream here: http://git.gnome.org/browse/glib/commit/?id=3766b7b5cd0f22d2773c7efc8b52fc2f214d0372 Distro backport coming soon... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1044322 Title: indicator-messages-service crashed with assert in g_menu_exporter_name_vanished() To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1044322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058250] Re: conditionalise empathy u-o-a dependency
This is empathy 3.5.92-0ubuntu2 in Q. ** Changed in: empathy (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058250 Title: conditionalise empathy u-o-a dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1058250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058250] [NEW] conditionalise empathy u-o-a dependency
Public bug reported: Empathy currently has a hard dependency on ubuntu-online-accounts. ubuntu-online-accounts is currently not working. A workaround is to directly run empathy-accounts from the commandline, but this is hardly discoverable. Ideally, we should only have this patch butchery enabled when running under Unity and disabled otherwise (ie: you get the normal Empathy accounts dialog). Also: Empathy (via ubuntu-online-accounts) currently hard-depends on libqt, which is just a little bit odd... ** Affects: empathy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058250 Title: conditionalise empathy u-o-a dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1058250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045372] Re: libreoffice unity menu bars greyed out after opening any dialog or switching window
A bit more info on this: the bug is caused by the gtk_menu_detach() call in the cloaking code in libindicator. The menu gets detached from its GtkMenuItem, which breaks the GtkModelMenu logic (specifically: it separates it from the action group so all actions disappear, disabling the items). The decloak code doesn't reverse this. We could workaround it in indicator-appmenu by associating the actions directly with each submenu but I think we should probably fix this in libindicator instead. The cloak logic is pretty suspicious ** Package changed: libreoffice (Ubuntu) = libindicator (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045372 Title: libreoffice unity menu bars greyed out after opening any dialog or switching window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1045372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045372] Re: Menu bar in Unity is disabled
I think this is more likely to be a bug in libreoffice since we have quite a lot of apps that are working properly with Unity/Gtk in Q and the libreoffice code is new. I welcome a small testcase that demonstrates the issue. Otherwise we're going to have to go digging through some rather large D-Bus logs to find the truth -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045372 Title: Menu bar in Unity is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1045372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045361] Re: Accelerators are not displayed
Confirmed known issue. Working on it... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045361 Title: Accelerators are not displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1045361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045372] Re: Menu bar in Unity is disabled
I've tried to reproduce this bug and for me it's not happening as described. What does happen, however, with 100% reliability, is that the actions are disabled when switching away from the window and back to it again. In the case of triggering actions like Open or About this would indeed cause the foreground window to be changed (to the open or about dialog). This is probably a unity-panel-service bug (probably in the appmenu indicator). For me, the bug does not happen with other actions like copy/paste that do not display new windows -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045372 Title: Menu bar in Unity is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1045372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1042293] [NEW] assert in intel_resolve_map_set
Public bug reported: This can be seen on my Thinkpad 420 (i7) machine with Intel graphics, by resizing a totem window. The bug is extremely visible because totem is essentially unusable on a rather common hardware configuration. The bug can be made to go away by running totem with LIBGL_ALWAYS_SOFTWARE=y libgl1-mesa-dri: Installed: 9.0~git20120821.c1114c61-0ubuntu1 #0 0x76070405 in __GI_raise (sig=optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x76073b6b in __GI_abort () at abort.c:91 #2 0x760690ce in __assert_fail_base (fmt=optimized out, assertion=0x7fffdf7b16c6 (*tail)-need == need, file=0x7fffdf7b16b2 intel_resolve_map.c, line=optimized out, function=optimized out) at assert.c:94 #3 0x76069172 in __GI___assert_fail (assertion=0x7fffdf7b16c6 (*tail)-need == need, file=0x7fffdf7b16b2 intel_resolve_map.c, line=46, function=0x7fffdf7b16e0 intel_resolve_map_set) at assert.c:103 #4 0x7fffdf73575b in intel_resolve_map_set () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7fffdf746e81 in brw_draw_prims () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #6 0x7fffdf2ad7f4 in ?? () from /usr/lib/x86_64-linux-gnu/libdricore8.1.0.so.1 #7 0x73ae785b in _cogl_journal_flush_modelview_and_entries (data=0x7fffdbd0, batch_len=optimized out, batch_start=optimized out) at ./cogl-journal.c:315 #8 _cogl_journal_flush_pipeline_and_entries (batch_start=optimized out, batch_len=optimized out, data=0x7fffdbd0) at ./cogl-journal.c:467 #9 0x73ae7533 in _cogl_journal_flush_vbo_offsets_and_entries (batch_start=0x1b99dd0, batch_len=optimized out, data=0x7fffdbd0) at ./cogl-journal.c:667 #10 0x73ae73c6 in _cogl_journal_flush_clip_stacks_and_entries (batch_start=0x1b99dd0, batch_len=1, data=0x7fffdbd0) at ./cogl-journal.c:746 #11 0x73ae85ac in _cogl_journal_flush (journal=optimized out) at ./cogl-journal.c:1452 #12 0x73ae977c in _cogl_framebuffer_flush_journal (framebuffer=framebuffer@entry=0x1a6ac30) at ./cogl-framebuffer.c:639 #13 0x73aead84 in cogl_framebuffer_clear4f (framebuffer=0x1a6ac30, buffers=buffers@entry=3, red=0, green=0, blue=0, alpha=1) at ./cogl-framebuffer.c:425 #14 0x73aeaf7c in cogl_framebuffer_clear (framebuffer=optimized out, buffers=buffers@entry=3, color=color@entry=0x7fffdcc0) at ./cogl-framebuffer.c:491 #15 0x73ab2cb5 in cogl_clear (color=color@entry=0x7fffdcc0, buffers=buffers@entry=3) at ./cogl.c:137 #16 0x73dc494e in clutter_stage_paint (self=0x19f25d0) at ./clutter-stage.c:713 #17 0x7691b307 in _g_closure_invoke_va (closure=0x19f1730, return_value=0x0, instance=0x19f25d0, args=0x7fffdfe8, n_params=0, param_types=0x0) at /build/buildd/glib2.0-2.33.10/./gobject/gclosure.c:840 #18 0x76934ab8 in g_signal_emit_valist (instance=0x19f25d0, signal_id=optimized out, detail=0, var_args=var_args@entry=0x7fffdfe8) at /build/buildd/glib2.0-2.33.10/./gobject/gsignal.c:3211 #19 0x769351f2 in g_signal_emit (instance=instance@entry=0x19f25d0, signal_id=optimized out, detail=detail@entry=0) at /build/buildd/glib2.0-2.33.10/./gobject/gsignal.c:3356 #20 0x73d6259d in clutter_actor_continue_paint (self=self@entry=0x19f25d0) at ./clutter-actor.c:3869 #21 0x73d6fa43 in clutter_actor_paint (self=0x19f25d0) at ./clutter-actor.c:3794 #22 0x73d6ff99 in clutter_actor_paint (self=optimized out) at ./clutter-actor.c:3816 #23 0x73dc8aed in _clutter_stage_do_paint (stage=0x19f25d0, clip=clip@entry=0x0) at ./clutter-stage.c:671 #24 0x73d57e3a in clutter_stage_cogl_redraw (stage_window=optimized out) at ./cogl/clutter-stage-cogl.c:404 #25 0x73dc73ee in clutter_stage_do_redraw (stage=0x19f25d0) at ./clutter-stage.c:1172 #26 _clutter_stage_do_update (stage=0x19f25d0) at ./clutter-stage.c:1230 #27 0x73dac51d in master_clock_update_stages (stages=0x18c2a10, master_clock=0x19f4cf0) at ./clutter-master-clock.c:386 #28 clutter_clock_dispatch (source=source@entry=0x198b670, callback=optimized out, user_data=optimized out) at ./clutter-master-clock.c:520 #29 0x7665bdb5 in g_main_dispatch (context=0x643e00) at /build/buildd/glib2.0-2.33.10/./glib/gmain.c:2707 #30 g_main_context_dispatch (context=context@entry=0x643e00) at /build/buildd/glib2.0-2.33.10/./glib/gmain.c:3211 #31 0x7665c0e8 in g_main_context_iterate (context=context@entry=0x643e00, block=block@entry=1, ---Type return to continue, or q return to quit--- dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.33.10/./glib/gmain.c:3282 #32 0x7665c1a4 in g_main_context_iteration (context=0x643e00, context@entry=0x0, may_block=may_block@entry=1) at /build/buildd/glib2.0-2.33.10/./glib/gmain.c:3343 #33 0x76bfcefc in g_application_run (application=0x6871a0,
[Bug 1041354] Re: unity-panel-service since yesterday uses ~100% CPU, may be related to LibreOffice
The new libreoffice upload is causing this. It updates its menubar once per second, which it does by completely removing and readding all menu items and actions. The resulting thrash is what causes the panel to use 100%. They're working on it... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041354 Title: unity-panel-service since yesterday uses ~100% CPU, may be related to LibreOffice To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1041354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 956046]
Will this go in for 3.4 or wait until 3.5? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/956046 Title: intel driver fails to use dual-link LVDS if lid is down at boot To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/956046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 968268] Re: Cannot permanently add wallpaper to 'Pictures Folder'
Seb: we discussed this on IRC a few weeks ago and I mentioned that this is a known and intended side effect. Also note that the wallpaper is never really added to the pictures folder -- just to a cache directory that appears under Pictures Folder in the UI (which is a bit of a lie, imho). It is my understanding that the existing behaviour (after the patch) is the correct behaviour and that if you set an image as your wallpaper then you should not delete it after. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/968268 Title: Cannot permanently add wallpaper to 'Pictures Folder' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/968268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932435] Re: HUD - HUD offers search results from app indicators more often than from currently focused application
I'm not sure we can call this a bug or fix it. This is in direct conflict with bug 947283 which complains about getting hits on Save as before Save. In order to resolve that bug we prefer shorter terms with fewer words, so that's exactly what you're seeing here. imho, sh is a far better match for Shutdown than for Show only glyphs... and the situation is very easily resolved by you pressing one more extra letter. In the other situation, what would you do to indicate that you really wanted Save rather than Save as? I think the only way that we could fix this without breaking the other case is to penalise indicator results much more heavily than we do now, but then we could get into a worse situation: it being impossible for indicators to get the first spot because they are drowned out by only- vaguely-matching items from the application. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932435 Title: HUD - HUD offers search results from app indicators more often than from currently focused application To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/932435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858390] Re: nautilus crashed on startup in dconf_engine_refresh_user()
Any chance this is on a system with NFS home directories? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/858390 Title: nautilus crashed on startup in dconf_engine_refresh_user() To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/858390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858390] Re: nautilus crashed on startup in dconf_engine_refresh_user()
...or encrypted home directories for that matter. Also: can anyone send a core file? The extra information would be useful in this case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/858390 Title: nautilus crashed on startup in dconf_engine_refresh_user() To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/858390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858390] Re: nautilus crashed on startup in dconf_engine_refresh_user()
Just to clarify: you're using ecryptfs (ie: the one that you get when you check the use encrypted home directory option during the install)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/858390 Title: nautilus crashed on startup in dconf_engine_refresh_user() To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/858390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 981053] Re: Creating system dconf configuration crashes Unity greeter
This really is a case of user error. Why are you creating empty files in the place where dconf databases are supposed to be? Of course dconf would consider those to be corrupt. I agree that we should deal more gracefully with that case, but it is your mistake... Please follow the instructions here for creating those files: https://live.gnome.org/dconf/SystemAdministrators -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/981053 Title: Creating system dconf configuration crashes Unity greeter To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/981053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974938] Re: Process gsettings prevents logging in
Looking at these traces I have a hard time beleiving this is a glib/gsettings problem. It rather looks like some deadlock between fork() and the ldap nss module... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974938 Title: Process gsettings prevents logging in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/974938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 962984] Re: HUD: The selection always returns to the first item whenever menus are updated
two possible fixes, both in unity: 1) keep the cursor in the same physical position when the list updates 2) look at the item key (which is just a 64bit integer these days) of the item that was selected before refreshing the list and search for that item in the new list, causing it to be the new highlighted item one more possible fix in the backend (but will only help with some cases): scan the old list and the new list for being equal and don't send updates in that case -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/962984 Title: HUD: The selection always returns to the first item whenever menus are updated To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/962984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974938] Re: Process gsettings prevents logging in
Can you get a backtrace of the stuck gsettings process? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974938 Title: Process gsettings prevents logging in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/974938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 957022] Re: hud-service sends insane number of dbus messages
It's my opinion that this issue is substantially improved, but not yet fixed. Items 'a', 'c', 'd' have all been fixed, but item 'b' is still outstanding. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/957022 Title: hud-service sends insane number of dbus messages To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/957022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965493] Re: cpu race between nautilus, hud- and unity-service
Fix is committed upstream now too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965493 Title: cpu race between nautilus, hud- and unity-service To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/965493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973203] Re: hud-service crashed with SIGSEGV
** Changed in: indicator-appmenu (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973203 Title: hud-service crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/973203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 972354] Re: HUD: Small memory leak when switching windows
** Changed in: indicator-appmenu Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972354 Title: HUD: Small memory leak when switching windows To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/972354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 937020] Re: hud searches should strip() the search string
** Changed in: indicator-appmenu Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/937020 Title: hud searches should strip() the search string To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/937020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965493] Re: cpu race between nautilus, hud- and unity-service
So the involvement of menus is secondary to the main problem -- nautilus gets itself stuck in a silly loop reading and re-reading the free space on the drive. If a bookmarked directory is also involved then this results in the bookmarks menu also being updated, thus causing the issue we see here. ** Changed in: indicator-appmenu Status: Triaged = Invalid ** Changed in: unity Status: Triaged = Invalid ** Changed in: indicator-appmenu (Ubuntu) Status: Triaged = Invalid ** Changed in: unity (Ubuntu) Status: Triaged = Invalid ** Bug watch added: GNOME Bug Tracker #673550 https://bugzilla.gnome.org/show_bug.cgi?id=673550 ** Also affects: nautilus via https://bugzilla.gnome.org/show_bug.cgi?id=673550 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965493 Title: cpu race between nautilus, hud- and unity-service To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/965493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
