[Dx-packages] [Bug 1629550] Re: url-dispatcher crashed with signal 5
*** This bug is a duplicate of bug 1608009 *** https://bugs.launchpad.net/bugs/1608009 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: url-dispatcher (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1629550 Title: url-dispatcher crashed with signal 5 Status in url-dispatcher package in Ubuntu: Confirmed Bug description: url-dispatcher crashed with signal 5 ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: url-dispatcher 0.1+16.10.20160816.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Sat Oct 1 16:20:43 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/url-dispatcher/url-dispatcher InstallationDate: Installed on 2016-06-05 (117 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: /usr/lib/x86_64-linux-gnu/url-dispatcher/url-dispatcher Signal: 5 SourcePackage: url-dispatcher StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: url-dispatcher crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.url-dispatcher-refresh.log: initctl: Event failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1629550/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7
@laney I tested per my original report, and the delays are gone when d-u-s is installed. Otherwise things I tried work with and without dbus- user-session. I am unclear on the symptoms in the rest of your description. I never recall seeing global menus for terminal app. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1644323 Title: Installing unity8-session-snap adversely effects unity7 Status in Canonical System Image: Fix Committed Status in dbus package in Ubuntu: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in dbus source package in Xenial: Fix Committed Status in unity-gtk-module source package in Xenial: In Progress Bug description: [ Description ] In Xenial, when dbus-user-session is installed, dbus' upstart job still starts a new bus. Things get confused about which bus to talk to. [ Fix ] Already fixed in Yakkety. Cherry-pick the upstart job. On top of Yakkety's version, call `dbus-update-activation-environment --verbose --systemd GTK_MODULES', because Xenial does not have the change in upstart to automatically publish to the systemd activation environment. /etc/X11/Xsession.d/95dbus_update-activation-env is called too early - before unity-gtk-module.conf is started - so dbus activated services miss the GTK_MODULES environment variable. Update unity-gtk- module.conf to set it in the dbus activation environment. [ QA ] Install dbus-user-session, press print screen. It should be delayed if you are experiencing this bug, and not delayed otherwise. Remove dbus-user-session, make sure the session still works properly - the global menu works, everything launches properly, etc. Test that gnome-terminal has global menus in both situations. [ Regression potential ] This change alters the way that the session bus is launched, even if you aren't using dbus-user-session. Even though this same change is deployed in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user-session by default, so the case where you don't have it isn't as well tested. I would suggest focusing some testing on the non dbus-user-session case. [ Original report ] After installing the deb (and then the snap), certain things in the unity7 session take a very long time (30 to 60 secs), such as launching chromium and ctrl-alt-t for a new terminal session. Removing both the deb and the snap followed by a reboot does not fix the symptoms. Xenial amd64 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7
I don't see how this can be v-done given the QA steps in the description, since unity-gtk-module isn't accepted yet. Were those steps followed? If so, maybe I was too hasty in linking u-g-m into the bug. If not, please could u-g-m be reviewed and ideally accepted into x-proposed so this can be re-verified? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1644323 Title: Installing unity8-session-snap adversely effects unity7 Status in Canonical System Image: Fix Committed Status in dbus package in Ubuntu: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in dbus source package in Xenial: Fix Committed Status in unity-gtk-module source package in Xenial: In Progress Bug description: [ Description ] In Xenial, when dbus-user-session is installed, dbus' upstart job still starts a new bus. Things get confused about which bus to talk to. [ Fix ] Already fixed in Yakkety. Cherry-pick the upstart job. On top of Yakkety's version, call `dbus-update-activation-environment --verbose --systemd GTK_MODULES', because Xenial does not have the change in upstart to automatically publish to the systemd activation environment. /etc/X11/Xsession.d/95dbus_update-activation-env is called too early - before unity-gtk-module.conf is started - so dbus activated services miss the GTK_MODULES environment variable. Update unity-gtk- module.conf to set it in the dbus activation environment. [ QA ] Install dbus-user-session, press print screen. It should be delayed if you are experiencing this bug, and not delayed otherwise. Remove dbus-user-session, make sure the session still works properly - the global menu works, everything launches properly, etc. Test that gnome-terminal has global menus in both situations. [ Regression potential ] This change alters the way that the session bus is launched, even if you aren't using dbus-user-session. Even though this same change is deployed in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user-session by default, so the case where you don't have it isn't as well tested. I would suggest focusing some testing on the non dbus-user-session case. [ Original report ] After installing the deb (and then the snap), certain things in the unity7 session take a very long time (30 to 60 secs), such as launching chromium and ctrl-alt-t for a new terminal session. Removing both the deb and the snap followed by a reboot does not fix the symptoms. Xenial amd64 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1651214] Re: Indicator Crash on CalDAV entry without time set
I excuse for the bad formatting in the end -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1651214 Title: Indicator Crash on CalDAV entry without time set Status in indicator-datetime package in Ubuntu: New Bug description: First of all, sorry; this explanation got a little long, but i fixed the bug myself for now. This is just a description for the developers, to fix the bug in the future. A brief explanation what "without time set" is supposed to mean: Let's say you synchronize your reminders from your phone over icloud (as i do - caldav.icloud.com) then there may be reminders that are not triggered by time, but for example by a location. I recently set a reminder to occure when i enter a specific street. As i went to that street these days the reminder came up on both devices, my phone and the ubuntu machine. Of course i did only set the location where the reminder should occure, no additional time. But as the reminder got triggered and was shown on the ubuntu machine, there simply was a notification in the top right corner saying "[Reminder info] (Invalid time: 0 seconds ago) Later i noticed, that the clock in the unity bar had frozen some time ago. I tried serval things and tried every known solution i could find - still nothing. Everything that happened was: when i restarted whole unity, the time was uptodate (for that moment) and the service was active for half a second, then it crashed, i could not access any menu entries from the clock menu, neither change the time settings. I started the indicator-datetime-service from command line, it simply crashed and now the clock also disappeared, only appearing for a second on launching the service again. The bug could be fixed by opening the synchronized calendar in Evolution and removing the concerning reminder. I could then launch the service again and my time is now uptodate. I guess this is something not occuring very often, but i think it should probably fixed so that a reminder without time set doesn't crash the whole service. Additional info: Package: indicator-datetime Version: 15.10+16.04.20160406-0ubuntu1 Ubuntu Version 16.04.1 LTS 64bit To reconstruct the bug: Use any calendar software (Evolution for example) to connect to a caldav calendar that supports different triggers than time (iOS reminders app for example - supports setting a place as trigger) Set the default calendar application to the ubuntu system internal one (gnome-calendar) and check if the calendar appears there as well Then on the other device / software, that supports the different trigger, simply add a reminder triggered not by time, but by that other event and fire it. The bug should now occure, the clock should freeze and the service should crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1651214/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1651214] [NEW] Indicator Crash on CalDAV entry without time set
Public bug reported: First of all, sorry; this explanation got a little long, but i fixed the bug myself for now. This is just a description for the developers, to fix the bug in the future. A brief explanation what "without time set" is supposed to mean: Let's say you synchronize your reminders from your phone over icloud (as i do - caldav.icloud.com) then there may be reminders that are not triggered by time, but for example by a location. I recently set a reminder to occure when i enter a specific street. As i went to that street these days the reminder came up on both devices, my phone and the ubuntu machine. Of course i did only set the location where the reminder should occure, no additional time. But as the reminder got triggered and was shown on the ubuntu machine, there simply was a notification in the top right corner saying "[Reminder info] (Invalid time: 0 seconds ago) Later i noticed, that the clock in the unity bar had frozen some time ago. I tried serval things and tried every known solution i could find - still nothing. Everything that happened was: when i restarted whole unity, the time was uptodate (for that moment) and the service was active for half a second, then it crashed, i could not access any menu entries from the clock menu, neither change the time settings. I started the indicator-datetime-service from command line, it simply crashed and now the clock also disappeared, only appearing for a second on launching the service again. The bug could be fixed by opening the synchronized calendar in Evolution and removing the concerning reminder. I could then launch the service again and my time is now uptodate. I guess this is something not occuring very often, but i think it should probably fixed so that a reminder without time set doesn't crash the whole service. Additional info: Package: indicator-datetime Version: 15.10+16.04.20160406-0ubuntu1 Ubuntu Version 16.04.1 LTS 64bit To reconstruct the bug: Use any calendar software (Evolution for example) to connect to a caldav calendar that supports different triggers than time (iOS reminders app for example - supports setting a place as trigger) Set the default calendar application to the ubuntu system internal one (gnome-calendar) and check if the calendar appears there as well Then on the other device / software, that supports the different trigger, simply add a reminder triggered not by time, but by that other event and fire it. The bug should now occure, the clock should freeze and the service should crash. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1651214 Title: Indicator Crash on CalDAV entry without time set Status in indicator-datetime package in Ubuntu: New Bug description: First of all, sorry; this explanation got a little long, but i fixed the bug myself for now. This is just a description for the developers, to fix the bug in the future. A brief explanation what "without time set" is supposed to mean: Let's say you synchronize your reminders from your phone over icloud (as i do - caldav.icloud.com) then there may be reminders that are not triggered by time, but for example by a location. I recently set a reminder to occure when i enter a specific street. As i went to that street these days the reminder came up on both devices, my phone and the ubuntu machine. Of course i did only set the location where the reminder should occure, no additional time. But as the reminder got triggered and was shown on the ubuntu machine, there simply was a notification in the top right corner saying "[Reminder info] (Invalid time: 0 seconds ago) Later i noticed, that the clock in the unity bar had frozen some time ago. I tried serval things and tried every known solution i could find - still nothing. Everything that happened was: when i restarted whole unity, the time was uptodate (for that moment) and the service was active for half a second, then it crashed, i could not access any menu entries from the clock menu, neither change the time settings. I started the indicator-datetime-service from command line, it simply crashed and now the clock also disappeared, only appearing for a second on launching the service again. The bug could be fixed by opening the synchronized calendar in Evolution and removing the concerning reminder. I could then launch the service again and my time is now uptodate. I guess this is something not occuring very often, but i think it shou
