[Dx-packages] [Bug 1407709] Re: Google Maps and Here Maps should handle custom intent:// URLs
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Tags removed: ww03 ** Tags added: ww05 -- 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/1407709 Title: Google Maps and Here Maps should handle custom intent:// URLs Status in the base for Ubuntu mobile products: New Status in The Webapps-core project: In Progress Status in Web Browser App: In Progress Status in url-dispatcher package in Ubuntu: In Progress Status in webbrowser-app package in Ubuntu: Confirmed Status in url-dispatcher package in Ubuntu RTM: In Progress Status in webbrowser-app package in Ubuntu RTM: Confirmed Bug description: ubuntu-rtm image 184 The maps apps in the system should register and respond to appropriate urls from the browser (not sure of the format, map:// or directions:// - need to check) Steps to reproduce: 1) open browser 2) type "Asai Belmont MA" in the url bar and press enter 3) this will do a google search for the resturant 4) click on the "Directions" button Expected result: - One of the maps apps should open displaying directions for the resturant Actual results: - no app is launched To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407709/+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 1386584] Re: SIGSEGV when notification contains |
This bug was fixed in the package indicator-messages - 13.10.1+15.04.20150112-0ubuntu1 --- indicator-messages (13.10.1+15.04.20150112-0ubuntu1) vivid; urgency=low [ Lars Uebernickel ] * desktop menu: don't warn when no default handler for a mime type is found (LP: #1389725) * Escape message and source ids when using them as action names (LP: #1386584) -- Ubuntu daily releaseMon, 12 Jan 2015 18:39:08 + ** Changed in: indicator-messages (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1386584 Title: SIGSEGV when notification contains | Status in The Messaging Menu: In Progress Status in indicator-messages package in Ubuntu: Fix Released Bug description: When a notification on the messages menu contains the | character (in my case a nickname in xchat), the process unity-panel-service crashes with: ngl@BEATRIX:~/Scrivania/database$ /usr/lib/unity/unity-panel-service (unity-panel-service:11336): Gtk-CRITICAL **: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_print_action_and_target: assertion 'strchr (action_name, '|') == NULL' failed Segmentation fault (core dumped) ngl@BEATRIX:~/Scrivania/database$ lsb_release -rd Description: Ubuntu 14.10 Release: 14.10 ngl@BEATRIX:~/Scrivania/database$ apt-cache policy unity-services unity-services: Installed: 7.3.1+14.10.20141016-0ubuntu1 Candidate: 7.3.1+14.10.20141016-0ubuntu1 Version table: *** 7.3.1+14.10.20141016-0ubuntu1 0 500 http://it.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1386584/+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 1389725] Re: g_app_info warning on start (utouch)
This bug was fixed in the package indicator-messages - 13.10.1+15.04.20150112-0ubuntu1 --- indicator-messages (13.10.1+15.04.20150112-0ubuntu1) vivid; urgency=low [ Lars Uebernickel ] * desktop menu: don't warn when no default handler for a mime type is found (LP: #1389725) * Escape message and source ids when using them as action names (LP: #1386584) -- Ubuntu daily releaseMon, 12 Jan 2015 18:39:08 + ** Changed in: indicator-messages (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1389725 Title: g_app_info warning on start (utouch) Status in indicator-messages package in Ubuntu: Fix Released Bug description: Using rtm 143, indicator-messages displays warnings on start backtrace of one of those #0 g_log (log_domain=0xb6f87914 "GLib-GIO", log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, format=0xb6e247d4 "%s: assertion '%s' failed") at /build/buildd/glib2.0-2.41.5/./glib/gmessages.c:1075 #1 0xb6dedd62 in g_return_if_fail_warning (log_domain=, pretty_function=, expression=) at /build/buildd/glib2.0-2.41.5/./glib/gmessages.c:1088 #2 0xb6ef610c in g_app_info_equal (appinfo1=0x4e088, appinfo2=0x0) at /build/buildd/glib2.0-2.41.5/./gio/gappinfo.c:132 #3 0x000170d2 in g_app_info_is_default_for_uri_scheme ( uri_scheme=0x1d63c "mailto", info=0x4e088) at im-desktop-menu.c:87 #4 im_desktop_menu_app_added (applist=, app_id=0x50b80 "telephony-service-call", app_info=0x4e088, user_data=0x3fe40) at im-desktop-menu.c:176 #5 0x000173ee in im_desktop_menu_constructed (object=0x3fe40) at im-desktop-menu.c:380 #6 0xb6e96fae in g_object_new_internal (class=class@entry=0x0, params=params@entry=0xbefff354, n_params=n_params@entry=1) at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1814 #7 0xb6e98650 in g_object_new_valist (object_type=object_type@entry=346680, first_property_name=first_property_name@entry=0x1d054 "application-list", var_args=..., var_args@entry=...) at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:2034 #8 0xb6e987ec in g_object_new (object_type=346680, first_property_name=0x1d054 "application-list") at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1617 #9 0x00017510 in im_desktop_menu_new (applist=) at im-desktop-menu.c:427 #10 0x00014d16 in main (argc=, argv=) at messages-service.c:277 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1389725/+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 1003950] Re: launcher does not show minimized update manager while clicked
I can confirm following: * The issue is definitely available in 14.10 Utopic (clean install, not upgrade), seen multiple times already. * I see this issue for years in different distributions and can surely state that it's appearance tightly connected to the way how update- manager is started. It could appear when it started automatically when updates available and user confirmation set to required, but never when update-manager start manually with any method (Unity launcher, command line, etc.). I suppose (but not sure though), the issue come out with _any_ automated startup of update-manager. Now trying to figure out where it started to get what's different... @3v1n0 , comment #24 "update-manager --no-focus-on-map" does not show the issue, window appears as it should. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1003950 Title: launcher does not show minimized update manager while clicked Status in Compiz: New Status in Accelerated Xorg driver for nVidia cards: New Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Fix Released Status in binary-driver-fglrx package in Ubuntu: New Status in intel-linux-graphics-installer package in Ubuntu: New Status in unity package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in binary-driver-fglrx source package in Precise: New Status in intel-linux-graphics-installer source package in Precise: New Status in unity source package in Precise: Fix Released Status in update-manager source package in Precise: Confirmed Status in xserver-xorg-video-nouveau source package in Precise: New Status in binary-driver-fglrx source package in Quantal: New Status in intel-linux-graphics-installer source package in Quantal: New Status in unity source package in Quantal: Fix Released Status in update-manager source package in Quantal: Won't Fix Status in xserver-xorg-video-nouveau source package in Quantal: New Bug description: Update manager is showing up in the dock but I can click on the icon all day and nothing happens. Similarly if I do Super-S or Super-W it doesn't show up anywhere. Even if I alt-tab to the application nothing shows up. This happens only when update manager runs on its own. If I kill it and then launch it myself it comes to the foreground just fine. I'm not 100% sure whether this is a unity, compiz, or update-manager bug but so far my bet is on unity. =Original Report= Bug #877444 is showing again in latest updates, please re-open it. This is the exact same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1003950/+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 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Changed in: canonical-devices-system-image Status: Confirmed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1389008 Title: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control) Status in the base for Ubuntu mobile products: Fix Released Status in indicator-sound package in Ubuntu: Invalid Status in ubuntu-touch-session package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Status in indicator-sound package in Ubuntu RTM: Invalid Status in ubuntu-touch-session package in Ubuntu RTM: Confirmed Status in unity8 package in Ubuntu RTM: Invalid Bug description: Often after boot indicator-sound fails to connect to Pulseaudio and to unity-notifications using libnotify. Therefore, volume notifications aren't shown and changes to the volume role go unnoticed, which then results in improper volume control. As already mentioned in the original bug description, running "restart indicator-sound" resolves the issue. Original description: Happens often after phone boot where changing volume by touch or by phone buttons. Volume correctly changes, but the org.freedesktop.Notifications popup isn't displayed. The problem seems fixes itself if you run "restart indicator-sound", so maybe there's an issue with i-sound and unity-notifications starting at the same time, with the former querying the latter's capabilities before it's ready for business? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1389008/+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 1387691] Re: Media Player should not be visible in the app scope and launcher
** No longer affects: mediaplayer-app -- 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/1387691 Title: Media Player should not be visible in the app scope and launcher Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in mediaplayer-app package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Status in url-dispatcher package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu RTM: In Progress Status in url-dispatcher package in Ubuntu RTM: In Progress Bug description: The mediaplayer is an 'auxiliary app' in the current design approach. That means that its purpouse it playback media launched by other apps (e.g Messaging) or scopes (e.g. Videos). It should not be launched from the App scopes. However, the 'Update' section System Settings should still display it when an update to mediaplayer is available. Current behaviour - Mediaplayer app displayed in App Scope, Launcher and Settings Desired behaviour - Mediaplayer app not displayed in App Scope or Launcher - Mediaplayer displayed in Settings > Update To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387691/+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 1387691] Re: Media Player should not be visible in the app scope and launcher
NOTE: The fixes for this bug are on hold pending the splash screen work for trusted prompt sessions that are discussed in bug 1352251 ** Changed in: url-dispatcher (Ubuntu) Status: Incomplete => In Progress ** Changed in: url-dispatcher (Ubuntu) Importance: Undecided => High ** Changed in: url-dispatcher (Ubuntu) Assignee: (unassigned) => Ted Gould (ted) ** Changed in: mediaplayer-app (Ubuntu RTM) Assignee: (unassigned) => Ted Gould (ted) ** Branch linked: lp:~ted/url-dispatcher/mediaplayer-app-helper ** Branch linked: lp:~ted/url-dispatcher/mediaplayer-app-helper-rtm ** Branch linked: lp:~ted/mediaplayer-app/trusted-session-helper ** Also affects: url-dispatcher (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: url-dispatcher (Ubuntu RTM) Status: New => In Progress ** Changed in: url-dispatcher (Ubuntu RTM) Importance: Undecided => High ** Changed in: url-dispatcher (Ubuntu RTM) Assignee: (unassigned) => Ted Gould (ted) -- 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/1387691 Title: Media Player should not be visible in the app scope and launcher Status in the base for Ubuntu mobile products: Confirmed Status in Media Player App: In Progress Status in Ubuntu UX bugs: Fix Committed Status in mediaplayer-app package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Status in url-dispatcher package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu RTM: In Progress Status in url-dispatcher package in Ubuntu RTM: In Progress Bug description: The mediaplayer is an 'auxiliary app' in the current design approach. That means that its purpouse it playback media launched by other apps (e.g Messaging) or scopes (e.g. Videos). It should not be launched from the App scopes. However, the 'Update' section System Settings should still display it when an update to mediaplayer is available. Current behaviour - Mediaplayer app displayed in App Scope, Launcher and Settings Desired behaviour - Mediaplayer app not displayed in App Scope or Launcher - Mediaplayer displayed in Settings > Update To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387691/+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 1090419] Re: messaging-menu doesn't allow one to set availability status if a chat program isn't open
** No longer affects: indicator-messages ** Changed in: indicator-messages (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1090419 Title: messaging-menu doesn't allow one to set availability status if a chat program isn't open Status in indicator-messages package in Ubuntu: Triaged Bug description: When I want to be available online, I would like to use the messaging indicator to become available (ie set my status to be "Available"). However, doing so has no effect if I haven't previously opened Empathy (or perhaps another properly registered chat program). Also, I am not told that the action I just performed had no effect. I have to guess or learn over time. Weirdly, if I open empathy and subsequently close the empathy window, the messaging indicator DOES work to the desired effect, that is, I can change my availability status and it will reflect in my online status in Empathy. Also, if I have successfully become available online, this status is not remembered across reboots. To regain availability after reboot I would, as described above, have to manually open the Empathy window, and then perhaps close it again if I don't want to look at it (I only opened it to achieve the side effect of becomning available for chat, so I don't want to actually look at it. How cumbersome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1090419/+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 796527] Re: Launcher - Count indicator should change size depending on the number of digits
Please update unity from trusty-proposed and verify the fix. ** Changed in: unity (Ubuntu Trusty) Status: New => Fix Committed ** Tags added: trusty verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/796527 Title: Launcher - Count indicator should change size depending on the number of digits Status in Ayatana Design: Fix Committed Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] The count indicator currently stays the same size irrespective of whether it is displaying one or two digits. Desired solution: If the count indicator only displays one digit it should be a circle e.g (7) If the count indicator displays two digits it should be a lozenge shape e.g. two half circles joined by two straight lines e.g. (27) If the count indicator displays three digits it should be a lozenge shape e.g. two half circles joined by two straight lines e.g (527) [ Test Case ] See above. [ Regression Potential ] Any code change to the Unity desktop shell has the potential to unleash a new crash or lockup in the desktop. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some months now without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/796527/+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 1387691] Re: Media Player should not be visible in the app scope and launcher
The plan is to treat the player as a trusted prompt session and not as an app. That means it will not appear in the app scope or the launcher, but as an overlay to the video scope or whatever starts it. ** Changed in: mediaplayer-app (Ubuntu) Assignee: (unassigned) => Ted Gould (ted) ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => ww05-2015 ** Changed in: mediaplayer-app (Ubuntu) Importance: Undecided => High ** Changed in: mediaplayer-app (Ubuntu RTM) Importance: Undecided => High -- 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/1387691 Title: Media Player should not be visible in the app scope and launcher Status in the base for Ubuntu mobile products: Confirmed Status in Media Player App: In Progress Status in Ubuntu UX bugs: Fix Committed Status in mediaplayer-app package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Status in url-dispatcher package in Ubuntu: Incomplete Status in mediaplayer-app package in Ubuntu RTM: In Progress Bug description: The mediaplayer is an 'auxiliary app' in the current design approach. That means that its purpouse it playback media launched by other apps (e.g Messaging) or scopes (e.g. Videos). It should not be launched from the App scopes. However, the 'Update' section System Settings should still display it when an update to mediaplayer is available. Current behaviour - Mediaplayer app displayed in App Scope, Launcher and Settings Desired behaviour - Mediaplayer app not displayed in App Scope or Launcher - Mediaplayer displayed in Settings > Update To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387691/+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 1387231] Re: [regression][clock] alarm still rings once it's been disabled or deleted
** Changed in: canonical-devices-system-image Status: Confirmed => Fix Released ** Changed in: canonical-devices-system-image Milestone: ww51-2014 => ww03-2015 -- 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/1387231 Title: [regression][clock] alarm still rings once it's been disabled or deleted Status in the base for Ubuntu mobile products: Fix Released Status in Clock application for Ubuntu devices: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Bug description: (r135) Steps to reproduce: 1. Create a single type alarm to ring in the next 5 minutes. 2. Wait for the alarm to ring. 3. After dismissing the alarm, delete it from the clock app. Actual behaviour: Once the alarm's been deleted, it still rings! Expected behaviour: Once you delete the alarm, this shouldn't ring anymore. Mako, Image #5 ubuntu rtm, Steps to reproduce: 1. Create an alarm to ring in the next 5 minutes. 2. Disable the alarm after it is created. Actual Behaviour: Alarm still rings! Expected Behaviour: Once you disable an alarm, it shouldn't ring anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387231/+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 1411792] [NEW] exported X displays confusing with unity launcher
Public bug reported: Distributor ID: Ubuntu Description:Ubuntu 14.04.1 LTS Release:14.04 Codename: trusty Sitting at machine A, I ssh -X to machine B and run "sudo synaptic". The window comes up (on A) and the unity launcher icon for synaptic gets a little mark by it. I can no longer bring up a local synaptic by clicking on the launcher icon. (<-- I expected this to work.) I can run a local synaptic via dash. Selecting quit on the launcher icon quits both. (I expected this to kill the local one.) I get similar results with nautilus (clicking the launcher icon will not open a local nautilus). Also, the launcher icon has right menu item "Open a new window" which opens a *local* (machine A) nautilus. Firefox is similar, but it's "new window" opens another machine B window. (Inconsistent with nautilus.) ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1411792 Title: exported X displays confusing with unity launcher Status in unity package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty Sitting at machine A, I ssh -X to machine B and run "sudo synaptic". The window comes up (on A) and the unity launcher icon for synaptic gets a little mark by it. I can no longer bring up a local synaptic by clicking on the launcher icon. (<-- I expected this to work.) I can run a local synaptic via dash. Selecting quit on the launcher icon quits both. (I expected this to kill the local one.) I get similar results with nautilus (clicking the launcher icon will not open a local nautilus). Also, the launcher icon has right menu item "Open a new window" which opens a *local* (machine A) nautilus. Firefox is similar, but it's "new window" opens another machine B window. (Inconsistent with nautilus.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1411792/+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 1411620] Re: Unity requires restart after enabling "always-show-menus" or LIM
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1411620 Title: Unity requires restart after enabling "always-show-menus" or LIM Status in unity package in Ubuntu: Confirmed Bug description: Unity requires restart after enabling "always-show-menus" or LIM. When I first tested the "always-show-menus" (about 3-4 weeks ago, by using Marco's branch), I don't remember it requiring a restart. Also, enabling LIM in Ubuntu 14.04 and 14.10 doesn't require restarting Unity but it does with the latest Unity in Ubuntu 15.04 Vivid Vervet. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150115-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Jan 16 13:23:00 2015 InstallationDate: Installed on 2015-01-16 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150116) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1411620/+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 1411620] Re: Unity requires restart after enabling "always-show-menus" or LIM
** Changed in: unity (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1411620 Title: Unity requires restart after enabling "always-show-menus" or LIM Status in unity package in Ubuntu: Confirmed Bug description: Unity requires restart after enabling "always-show-menus" or LIM. When I first tested the "always-show-menus" (about 3-4 weeks ago, by using Marco's branch), I don't remember it requiring a restart. Also, enabling LIM in Ubuntu 14.04 and 14.10 doesn't require restarting Unity but it does with the latest Unity in Ubuntu 15.04 Vivid Vervet. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150115-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Jan 16 13:23:00 2015 InstallationDate: Installed on 2015-01-16 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150116) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1411620/+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 1407192] Re: firefox icon frequently replaced by placeholder
** Changed in: unity Status: Confirmed => Invalid ** Changed in: unity (Ubuntu) Status: Confirmed => Invalid ** Changed in: bamf Status: Confirmed => In Progress ** Changed in: bamf (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1407192 Title: firefox icon frequently replaced by placeholder Status in BAMF Application Matching Framework: In Progress Status in Unity: Invalid Status in bamf package in Ubuntu: In Progress Status in unity package in Ubuntu: Invalid Bug description: Several times over the last week I have noticed that the when I start firefox, the default icon is replaced by a grey square with a question mark in the center as shown in the attached image. The only fix I've found is to unlock firefox from the launcher, quit the program, search for "firefox" in the dash, manually drag the icon onto the launcher, and then open it(i.e. if I start firefox directly from the dash, the grey icon appears on the launcher again). I haven't noticed this occurring with any other program. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20141216-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 2 21:38:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fb43] InstallationDate: Installed on 2014-12-11 (23 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141210) MachineType: TOSHIBA Satellite L875D ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PLCSC8 dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L875D dmi.product.version: PSKFQU-003034 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141119-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 1 20:07:44 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.2.901-1ubuntu3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1407192/+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 1407192] Re: firefox icon frequently replaced by placeholder
** Branch linked: lp:~andyrock/bamf/lp-1407192 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1407192 Title: firefox icon frequently replaced by placeholder Status in BAMF Application Matching Framework: In Progress Status in Unity: Invalid Status in bamf package in Ubuntu: In Progress Status in unity package in Ubuntu: Invalid Bug description: Several times over the last week I have noticed that the when I start firefox, the default icon is replaced by a grey square with a question mark in the center as shown in the attached image. The only fix I've found is to unlock firefox from the launcher, quit the program, search for "firefox" in the dash, manually drag the icon onto the launcher, and then open it(i.e. if I start firefox directly from the dash, the grey icon appears on the launcher again). I haven't noticed this occurring with any other program. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20141216-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 2 21:38:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fb43] InstallationDate: Installed on 2014-12-11 (23 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141210) MachineType: TOSHIBA Satellite L875D ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PLCSC8 dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L875D dmi.product.version: PSKFQU-003034 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141119-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 1 20:07:44 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.2.901-1ubuntu3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1407192/+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 1407192] Re: firefox icon frequently replaced by placeholder
** Changed in: unity Assignee: Marco Trevisan (Treviño) (3v1n0) => Andrea Azzarone (andyrock) ** Changed in: unity (Ubuntu) Assignee: Marco Trevisan (Treviño) (3v1n0) => Andrea Azzarone (andyrock) ** Changed in: bamf (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (andyrock) ** Changed in: bamf Assignee: (unassigned) => Andrea Azzarone (andyrock) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1407192 Title: firefox icon frequently replaced by placeholder Status in BAMF Application Matching Framework: In Progress Status in Unity: Invalid Status in bamf package in Ubuntu: In Progress Status in unity package in Ubuntu: Invalid Bug description: Several times over the last week I have noticed that the when I start firefox, the default icon is replaced by a grey square with a question mark in the center as shown in the attached image. The only fix I've found is to unlock firefox from the launcher, quit the program, search for "firefox" in the dash, manually drag the icon onto the launcher, and then open it(i.e. if I start firefox directly from the dash, the grey icon appears on the launcher again). I haven't noticed this occurring with any other program. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20141216-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 2 21:38:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fb43] InstallationDate: Installed on 2014-12-11 (23 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141210) MachineType: TOSHIBA Satellite L875D ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PLCSC8 dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L875D dmi.product.version: PSKFQU-003034 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141119-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 1 20:07:44 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.2.901-1ubuntu3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1407192/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once
Ok, so I'm leaving it on our issue list for Ubuntu until the situation gets cleared up - this way it will stay on our radar. Thanks! -- 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/1411171 Title: Repeating alarms appear disabled in clock app after it went off once Status in the base for Ubuntu mobile products: Fix Released Status in Clock application for Ubuntu devices: Fix Released Status in indicator-datetime package in Ubuntu: In Progress Status in indicator-datetime package in Ubuntu RTM: Fix Released Bug description: krillin #198 Repeating alarm is disabled after the first time it goes off. Test Case: 1. Setup a repeating alarm (everyday from Monday to Friday for example) and enable it 2. Close the clock app 3. Wait until it goes off 4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next occurrence) 5. Resume the device 6. Launch the clock app 7. Go the alarms and verify the status of the alarm Actual Result: The alarm is disabled but it shows in the indicator. The next and next-next occurrences of the alarm are scheduled correctly. Expected Result Alarm is still enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+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 1348538] Re: [power] Display should come on when started charging
** No longer affects: indicator-power (Ubuntu) ** No longer affects: unity-system-compositor ** No longer affects: unity-system-compositor (Ubuntu) ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Also affects: powerd (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1348538 Title: [power] Display should come on when started charging Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Triaged Status in powerd package in Ubuntu: New Status in powerd package in Ubuntu RTM: New Bug description: The display should be triggered to turn on for a $timeout when connected to a charger, so that users can see charging commenced. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-system-compositor (not installed) ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 25 09:45:42 2014 SourcePackage: unity-system-compositor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1348538/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once
** Changed in: canonical-devices-system-image Status: Confirmed => Fix Released -- 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/1411171 Title: Repeating alarms appear disabled in clock app after it went off once Status in the base for Ubuntu mobile products: Fix Released Status in Clock application for Ubuntu devices: Fix Released Status in indicator-datetime package in Ubuntu: In Progress Status in indicator-datetime package in Ubuntu RTM: Fix Released Bug description: krillin #198 Repeating alarm is disabled after the first time it goes off. Test Case: 1. Setup a repeating alarm (everyday from Monday to Friday for example) and enable it 2. Close the clock app 3. Wait until it goes off 4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next occurrence) 5. Resume the device 6. Launch the clock app 7. Go the alarms and verify the status of the alarm Actual Result: The alarm is disabled but it shows in the indicator. The next and next-next occurrences of the alarm are scheduled correctly. Expected Result Alarm is still enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+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 1411643] Re: Automatic brightness toggle switch missing on krillin/vivid
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-power (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1411643 Title: Automatic brightness toggle switch missing on krillin/vivid Status in indicator-power package in Ubuntu: Confirmed Bug description: I noticed that on my krillin device with devel-propsed (r70), the automatic display brightness toggle switch is missing in the battery indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1411643/+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 1411643] Re: Automatic brightness toggle switch missing on krillin/vivid
Confirmed on emulator 68 as well. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1411643 Title: Automatic brightness toggle switch missing on krillin/vivid Status in indicator-power package in Ubuntu: Confirmed Bug description: I noticed that on my krillin device with devel-propsed (r70), the automatic display brightness toggle switch is missing in the battery indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1411643/+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 1411643] [NEW] Automatic brightness toggle switch missing on krillin/vivid
Public bug reported: I noticed that on my krillin device with devel-propsed (r70), the automatic display brightness toggle switch is missing in the battery indicator. ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1411643 Title: Automatic brightness toggle switch missing on krillin/vivid Status in indicator-power package in Ubuntu: Confirmed Bug description: I noticed that on my krillin device with devel-propsed (r70), the automatic display brightness toggle switch is missing in the battery indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1411643/+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 1411620] [NEW] Unity requires restart after enabling "always-show-menus" or LIM
Public bug reported: Unity requires restart after enabling "always-show-menus" or LIM. When I first tested the "always-show-menus" (about 3-4 weeks ago, by using Marco's branch), I don't remember it requiring a restart. Also, enabling LIM in Ubuntu 14.04 and 14.10 doesn't require restarting Unity but it does with the latest Unity in Ubuntu 15.04 Vivid Vervet. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150115-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Jan 16 13:23:00 2015 InstallationDate: Installed on 2015-01-16 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150116) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1411620 Title: Unity requires restart after enabling "always-show-menus" or LIM Status in unity package in Ubuntu: New Bug description: Unity requires restart after enabling "always-show-menus" or LIM. When I first tested the "always-show-menus" (about 3-4 weeks ago, by using Marco's branch), I don't remember it requiring a restart. Also, enabling LIM in Ubuntu 14.04 and 14.10 doesn't require restarting Unity but it does with the latest Unity in Ubuntu 15.04 Vivid Vervet. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150115-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Jan 16 13:23:00 2015 InstallationDate: Installed on 2015-01-16 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150116) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1411620/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once
@lukasz, yeah this would also be affecting vivid. However at the moment the alarms feature in vivid is broken badly due to SDK Alarms API (alarms backend rewritten for performance and other benefits). Thereby it is difficult to identify if fixes like the above work or not. I would recommend waiting for the SDK Alarms API to settle down a bit in vivid before pushign this fix to vivid. ** Changed in: ubuntu-clock-app Status: Confirmed => Fix Released -- 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/1411171 Title: Repeating alarms appear disabled in clock app after it went off once Status in the base for Ubuntu mobile products: Confirmed Status in Clock application for Ubuntu devices: Fix Released Status in indicator-datetime package in Ubuntu: In Progress Status in indicator-datetime package in Ubuntu RTM: Fix Released Bug description: krillin #198 Repeating alarm is disabled after the first time it goes off. Test Case: 1. Setup a repeating alarm (everyday from Monday to Friday for example) and enable it 2. Close the clock app 3. Wait until it goes off 4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next occurrence) 5. Resume the device 6. Launch the clock app 7. Go the alarms and verify the status of the alarm Actual Result: The alarm is disabled but it shows in the indicator. The next and next-next occurrences of the alarm are scheduled correctly. Expected Result Alarm is still enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once
I was just wondering: is this also causing issues in vivid as well? We have an Ubuntu task for this bug here and this change didn't land in vivid, which is a requirement in case of reproducibility. -- 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/1411171 Title: Repeating alarms appear disabled in clock app after it went off once Status in the base for Ubuntu mobile products: Confirmed Status in Clock application for Ubuntu devices: Confirmed Status in indicator-datetime package in Ubuntu: In Progress Status in indicator-datetime package in Ubuntu RTM: Fix Released Bug description: krillin #198 Repeating alarm is disabled after the first time it goes off. Test Case: 1. Setup a repeating alarm (everyday from Monday to Friday for example) and enable it 2. Close the clock app 3. Wait until it goes off 4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next occurrence) 5. Resume the device 6. Launch the clock app 7. Go the alarms and verify the status of the alarm Actual Result: The alarm is disabled but it shows in the indicator. The next and next-next occurrences of the alarm are scheduled correctly. Expected Result Alarm is still enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+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
