[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 daemon: Failed to connect to socket /tmp/dbus-Zlu4hiB92O: Connection refused GConf Error: No D-BUS daemon running $ nautilus (nautilus:18870): libunity-CRITICAL **: unity-launcher.vala:154: Unable to connect to session bus: Could not connect: Connection refused (nautilus:18870): libunity-CRITICAL **: unity-launcher.vala:154: Unable to connect to session bus: Could not connect: Connection refused (nautilus:18870): libunity-CRITICAL **: unity-launcher.vala:154: Unable to connect to session bus: Could not connect: Connection refused (nautilus:18870): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: Could not connect: Connection refused (nautilus:18870): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: Could not connect: Connection refused (nautilus:18870): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: Could not connect: Connection refused ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: gtk-mir regression ** Also affects: dbus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1604704 Title: [regression] GTK apps hang for a very long time on start-up under Xmir and Mir failing to find dbus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1604704/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 because you are a member of Ubuntu Desktop Bugs, which is subscribed to libchamplain in Ubuntu. https://bugs.launchpad.net/bugs/1602035 Title: Maps app no longer works because MapQuest disabled access To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-maps/+bug/1602035/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1604446 Title: getcurrentPosition in oxide does not cause a wake up of the GPS To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1604446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 startUpdates() I’m getting a positionUpdated() signal almost instantly, with what seems to be the last known position, and its timestamp is 2016-03-24, i.e. 4 months ago. So it looks like it’s not even trying to get an updated position. Maybe it does, but prior to this it returns the last known position, and since we requested only one position (not regular updates), the source is shut down right away, thus not giving it time to get an actual update? ¹ https://doc.qt.io/qt-5/qgeopositioninfosource.html#startUpdates -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1604446 Title: getcurrentPosition in oxide does not cause a wake up of the GPS To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1604446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 carries an old timestamp I think that implementing #2 is a good thing regardless of #1, so I'd suggest that at least this part would be fixed in Oxide. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1604446 Title: getcurrentPosition in oxide does not cause a wake up of the GPS To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1604446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 like QtPositioning will instantly return the last known position even when an actual update has been requested. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1604446 Title: getcurrentPosition in oxide does not cause a wake up of the GPS To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1604446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Seahorse (and maybe even restart needed?). Had this experience multiple times when making news keys. Maybe change bug description to: takes a very long time before new gpg keys are visible in Seahorse (or by command). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1449795 Title: keys not showing up after creation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1449795/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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: https://github.com/qt/qtlocation/blob/dev/src/plugins/position/geoclue/qgeopositioninfosource_geocluemaster.cpp#L289 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1604446 Title: getcurrentPosition in oxide does not cause a wake up of the GPS To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1604446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 does not affect patch contents for distro but I should switch to 1.18 properly. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags added: gtk-mir ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed ** Changed in: xorg-server Status: New => Invalid ** Project changed: xorg-server => mir ** No longer affects: mir ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Fix Committed ** Summary changed: - keyboard autorepeat in libertine apps & gtk-mir does not work + keyboard autorepeat in Xmir apps & GTK-on-Mir does not work -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1591356 Title: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1591356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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. https://bugs.launchpad.net/bugs/571297 Title: Please support HKP over TLS (HKPS) and LDAP over TLS (LDAPS) using gnupg-curl To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/571297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 happening: QGeoPositionInfoSource has a lastKnownPosition() method¹ that allows clients to query the last know position explicitly, so I don’t think a call to startUpdates() should return that last known position first. Instead clients should be calling lastKnownPosition() themselves to get a first approximation, and then call startUpdates() to get an updated position (and thus expect that the first response will be with an accurate position). ¹ https://doc.qt.io/qt-5/qgeopositioninfosource.html#lastKnownPosition ** Changed in: location-service (Ubuntu) Assignee: (unassigned) => Thomas Voß (thomas-voss) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1604446 Title: getcurrentPosition in oxide does not cause a wake up of the GPS To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1604446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 found. It is a high accuracy position of where you have been at some point in the past, beyond a few minutes old it really is a very bad thing to store and return - it isn't an approximation of the current position. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1604446 Title: getcurrentPosition in oxide does not cause a wake up of the GPS To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1604446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1603501 Title: gimp: symbol lookup error: gimp: undefined symbol: gegl_param_multiline_get_type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1603501/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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? If my understanding is correct, please let me know if you'd welcome help to implement this. [1]: https://code.launchpad.net/~mardy/location-service/old- location-1551686/+merge/293075 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1604446 Title: getcurrentPosition in oxide does not cause a wake up of the GPS To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1604446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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. Position objects have attributes that convey the horizontal and vertical accuracy. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1604446 Title: getcurrentPosition in oxide does not cause a wake up of the GPS To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1604446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 things like http://pooperapp.com/ on Ubuntu Touch ;) As long as getCurrentPosition doesn't just return LKP and calls startupdates() and returns the first position from that (I am a little unconvinced it calls startupdates at all, because then repeated calls would presumably eventually work and they don't?) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1604446 Title: getcurrentPosition in oxide does not cause a wake up of the GPS To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1604446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 being woken up at all. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1604446 Title: getcurrentPosition in oxide does not cause a wake up of the GPS To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1604446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 that data to applications if they want to leverage it. Point being that it is up to them to filter/interpret the last known position in a sane way if they explicitly request it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1604446 Title: getcurrentPosition in oxide does not cause a wake up of the GPS To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1604446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 from default name with link file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1602737/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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" right click launcher entry doesn't work (on nautilus copy) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/887821/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1573206 Title: GNOME Software does not install third-party .deb packages To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1573206/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 issue? I'm wondering if there's some sort of "setting" which needs to applied to the pool. It's definitely a "rhythmbox integration" issue of some sort ... as playing through standard gnome-player works regardless of storage source. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1542471 Title: Playing mp3 files causes: Problem occurred without error being set. This is a bug in Rhythmbox or GStreamer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1542471/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 (Ubuntu Xenial) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libchamplain in Ubuntu. https://bugs.launchpad.net/bugs/1602035 Title: Maps app no longer works because MapQuest disabled access To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-maps/+bug/1602035/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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: https://bugs.launchpad.net/nautilus/+bug/1602863/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Title: Refresh hangs indefinitely, appstreamcli using 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1579712/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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. https://bugs.launchpad.net/bugs/1604998 Title: evolution-alarm-notify frequently hogs the system with 200% cpu usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1604998/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 DistroRelease: Ubuntu 16.04 Package: libevolution 3.18.5.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 20 23:25:06 2016 InstallationDate: Installed on 2012-01-12 (1651 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318) SourcePackage: evolution SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: UpgradeStatus: Upgraded to xenial on 2016-01-22 (180 days ago) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1604998 Title: evolution-alarm-notify frequently hogs the system with 200% cpu usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1604998/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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. https://bugs.launchpad.net/bugs/1602863 Title: nautilus crashes on non-X11 systems Wayland and Mir, with SIGSEGV trying to call XInternAtom() from gdk_x11_atom_to_xatom_for_display() To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1602863/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 gdk_x11_atom_to_xatom_for_display() -- 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 crashes on non-X11 systems Wayland and Mir, with SIGSEGV trying to call XInternAtom() from gdk_x11_atom_to_xatom_for_display() To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1602863/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 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/1603923 Title: nautilus crashes when run under Mir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1603923/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1602863 Title: nautilus crashes on non-X11 systems Wayland and Mir, with SIGSEGV trying to call XInternAtom() from gdk_x11_atom_to_xatom_for_display() To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1602863/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
