[Bug 1579712] Re: Refresh hangs indefinitely, appstreamcli using 100% CPU

For me issue was fixed by mixing comments #77 and #24. PS: can hardly imagine that such bugs live on stable channel :\ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1579712

[Bug 1602863] Re: nautilus crashed with SIGSEGV in XInternAtom()

Daniel, Wayland -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1602863 Title: nautilus crashed with SIGSEGV in XInternAtom() To manage notifications about this bug go to:

[Bug 1604998] Re: evolution-alarm-notify frequently hogs the system with 200% cpu usage

I have now uninstalled evolution, libevolution and killed run-away evolution-alarm-notify and the fans on my desktop have stopped spinning. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu.

[Bug 1604998] [NEW] evolution-alarm-notify frequently hogs the system with 200% cpu usage

Public bug reported: evolution-alarm-notify frequently hogs the system with 200% cpu usage it's hot in london as it is, without evolution thing adding heat to the problem. This is just a long running normal unity desktop. I don't even use evolution and have no events there. ProblemType:

[Bug 1602863] Re: nautilus crashed with SIGSEGV in XInternAtom()

Awesome, thanks. Then my Mir crash is the same bug as this. Nautilus on any non-X11 platform will hit it. ** Summary changed: - nautilus crashed with SIGSEGV in XInternAtom() + nautilus crashes on non-X11 systems Wayland and Mir, with SIGSEGV trying to call XInternAtom() from

[Bug 1602863] Re: nautilus crashes on non-X11 systems Wayland and Mir, with SIGSEGV trying to call XInternAtom() from gdk_x11_atom_to_xatom_for_display()

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu.

[Bug 1603923] Re: nautilus crashes when run under Mir

*** This bug is a duplicate of bug 1602863 *** https://bugs.launchpad.net/bugs/1602863 ** This bug has been marked a duplicate of bug 1602863 nautilus crashes on non-X11 systems Wayland and Mir, with SIGSEGV trying to call XInternAtom() from gdk_x11_atom_to_xatom_for_display() -- You

[Bug 1602863] Re: nautilus crashes on non-X11 systems Wayland and Mir, with SIGSEGV trying to call XInternAtom() from gdk_x11_atom_to_xatom_for_display()

I fixed a similar crash a while back in a different app. It might be the same issue... https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1444132/comments/1 ** Tags added: gtk-mir ** Changed in: nautilus (Ubuntu) Importance: Medium => High -- You received this bug notification because

[Bug 571297] Re: Please support HKP over TLS (HKPS) and LDAP over TLS (LDAPS) using gnupg-curl

See upstream: https://bugzilla.gnome.org/show_bug.cgi?id=617383 Too bad no change after more then six years. HKPS key server are becoming more and more popular. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu.

[Bug 1602035] Re: Maps app no longer works because MapQuest disabled access

** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: New => Invalid ** Changed in: livecd-rootfs (Ubuntu Xenial) Assignee: (unassigned) => Adam Conrad (adconrad) -- You received this bug notification

[Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

** Also affects: webapps-sprint Importance: Undecided Status: New ** Changed in: webapps-sprint Assignee: (unassigned) => Alberto Mardegan (mardy) ** Changed in: webapps-sprint Milestone: None => sprint-25 -- You received this bug notification because you are a member of

[Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

worth noting that the last known position isn't an estimate of where you are with low and decreasing accuracy (like a cell tower position is), where you have a rough position and an error radius, so you are in that circle with some kind of probability distribution on where you can expect to be

[Bug 1603501] Re: gimp: symbol lookup error: gimp: undefined symbol: gegl_param_multiline_get_type

For those who affected - you can downgrade gimp a bit: apt-cache policy gimp choose older version and install it (I showing example with exact versions, your available version may differ): sudo apt-get install gimp=2.8.16-1ubuntu1.1 -- You received this bug notification because you are a

[Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

The issue I’m seeing on my laptop seems to be specific to the geoclue location plugin: the last known position is serialized on disk, and it’s always emitted at startup, regardless of whether an update was requested:

[Bug 1591356] Re: keyboard autorepeat in libertine apps & gtk-mir does not work

Fixed in Xmir. Although I'm still confused as to why it always worked for Xmir on Mir's demo servers and not Unity8. https://git.launchpad.net/~xmir-team/xorg- server/+git/xmir/commit/?id=a64d38bae4f8a27126575299d15896d98e16d3f2 Another caveat: I've been working in the wrong branch lately. This

[Bug 1449795] Re: keys not showing up after creation

I also thought I had this bug (Ubuntu-Gnome 16.04), but apparently Seahorse (or gpg2) takes a quite some time to make the keys before they are visible in Seahorse (or by command: gpg2 --list-secret-keys). But after some time (do not know how exactly how long) keys are visible by command and in

[Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

I just had a chat with Thomas, and it appears that the GeoPositionInfoSource as implemented in qtubuntu-sensors always returns the last known position first on purpose, before starting to request updates. This is similar to what the geoclue plugin does. However it’s not clear that this should be

[Bug 1602737] Re: PCI RoCE Interface could not be renamed from default name with link file

** Also affects: ubuntu-z-systems Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1602737 Title: PCI RoCE Interface could not be renamed

[Bug 887821] Re: "Show copy dialog" right click launcher entry doesn't work (on nautilus copy)

Ctrl + Super + D brought the dialog back on Ubuntu 12.04.5 LTS x64. I hope this helps some of you. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/887821 Title: "Show copy dialog"

[Bug 1604704] [NEW] [regression] GTK apps hang for a very long time on start-up under Xmir and Mir failing to find dbus

Public bug reported: $ /usr/games/sol (sol:18808): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-7diijTV1R5: Connection refused GConf Error: No D-BUS daemon running (sol:18808): GConf-WARNING **: Client failed to connect to the D-BUS

[Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

Part of this is similar to bug 1551686. In addition the fix proposed in that bug (which won't help in this case, though) we have two options: 1) completely get rid of caching in location-service 2) When the client specifies maximumAge as 0, oxide should keep discarding any position update which

[Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

And to expand on this: even when requesting a single position with getCurrentPosition, oxide calls in to QGeoPositionInfoSource::startUpdates()¹. I wonder if there’s a bug in QtPositioning, or maybe incorrect documentation, as on my laptop (which doesn’t have a GPS chipset), when calling

[Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

@Alberto: the maximumAge parameter is not exposed in the chromium content API. See https://cs.chromium.org/chromium/src/content/public/browser/location_provider.h. Additionally, see my previous comment: I’m seeing the same issue on my laptop, which is not running the location service. It looks

[Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

Last known position is almost always going to be a full house level GPS lock on the place where you last turned off a map application, probably the last destination you navigated to. Might also be a full GPS lock on the last place you took a photograph. This could be a problem for implementing

[Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

Thomas, maybe we should drop my MP [1] and completely disable returning the LKP if it's more than a couple of minutes old, as Alan proposes, and instead add a LastKnownPosition property to the location service D-Bus interface, and query that in the qtubuntu-sensors's lastKnownPosition() method?

[Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

@Mardy: Any help is welcome :) I think we want to first drop providing the initial estimate altogether to get this bug fixed asap. We can then go ahead and investigate whether we want to expose the last known location to applications. @Alan: I think it's still an estimate and we should provide

[Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

Right, but as long as the location service doesn’t return the last known location when updates were requested, it’s okay. There’s a specific method for querying the last known location, and it does what it says on the tin. Note that the last known position isn’t necessarily very accurate either.

[Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

> I am a little unconvinced it calls startupdates at all, because then > repeated calls would presumably eventually work and they don't? startUpdates() is being called, but because oxide gets a position right away (the last known one), it calls stopUpdates(), which prevents the GPS from actually

[Bug 1573206] Re: GNOME Software does not install third-party .deb packages

*** This bug is a duplicate of bug 1573408 *** https://bugs.launchpad.net/bugs/1573408 Also affects me -- this is particular troublesome bug for new people (ubuntus target demographic) since Chrome, a popular browser with syncing abilities, can only be installed via a work around. -- You

[Bug 1602035] Re: Maps app no longer works because MapQuest disabled access

This bug was fixed in the package livecd-rootfs - 2.408.2 --- livecd-rootfs (2.408.2) xenial; urgency=medium * Switch ubuntu-gnome from using tasks to metapackages (LP: #1602035) -- Adam Conrad Wed, 20 Jul 2016 01:46:41 -0600 ** Changed in: livecd-rootfs

[Bug 1542471] Re: Playing mp3 files causes: Problem occurred without error being set. This is a bug in Rhythmbox or GStreamer.

Same issue here on Fedora22. The "touch trick" did not work for me. can't play MP3 files via Rhythmbox when the file source is a ZFS pool :( -- it works fine from a non-ZFS storage device. (Fedora 22, 4.4.13-200.fc22.x86_64, zfs = 0.6.5.7-1.fc22, rhythmbox = 3.2.1-1.fc22) -- anyone know of this