[Dx-packages] [Bug 1491542] Re: libunity ftbfs in wily
** Changed in: libunity (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1491542
Title:
libunity ftbfs in wily
Status in libunity:
New
Status in libunity package in Ubuntu:
New
Bug description:
libunity seems to no longer be buildable in wily. This is a problem
because it must be rebuilt for Python 3.5, but it is failing for
unrelated reasons. Here's an excerpt of the build log from a local
build using the current wily source package:
/usr/bin/glib-compile-resources --sourcedir . --target=unity-tool-res.c
--generate-source unity-tool-res.gresource.xml
/usr/bin/valac -C --vapidir ../vapi --vapidir=../protocol --vapidir=../src
--pkg config --pkg gtk+-3.0 --pkg gmodule-2.0 --pkg unity-internal --pkg
unity-protocol --pkg glib-2.0 --pkg gmodule-2.0 --pkg gobject-2.0 --pkg gio-2.0
--pkg gio-unix-2.0 --pkg dee-1.0 --pkg Dbusmenu-0.4 unity-tool.vala
unity-tool-dbus-util.vala unity-tool-ui.vala preview-renderer.vala
music-track-model-renderer.vala
unity-tool-ui.vala:846.13-846.21: error: `ListStore' is an ambiguous
reference between `GLib.ListStore' and `Gtk.ListStore'
private ListStore uimodel = null;
^
unity-tool-ui.vala:847.13-847.21: error: `ListStore' is an ambiguous
reference between `GLib.ListStore' and `Gtk.ListStore'
private ListStore ui_filter_model = null;
^
unity-tool-ui.vala:848.13-848.21: error: `ListStore' is an ambiguous
reference between `GLib.ListStore' and `Gtk.ListStore'
private ListStore scope_list_model = null;
^
unity-tool-ui.vala:849.13-849.21: error: `ListStore' is an ambiguous
reference between `GLib.ListStore' and `Gtk.ListStore'
private ListStore ui_cat_model = null;
^
unity-tool-ui.vala:43.62-43.70: error: `ListStore' is an ambiguous reference
between `GLib.ListStore' and `Gtk.ListStore'
uimodel = builder.get_object("results_model") as ListStore;
^
unity-tool-ui.vala:44.70-44.78: error: `ListStore' is an ambiguous reference
between `GLib.ListStore' and `Gtk.ListStore'
ui_filter_model = builder.get_object("filters_model") as
ListStore;
^
unity-tool-ui.vala:45.70-45.78: error: `ListStore' is an ambiguous reference
between `GLib.ListStore' and `Gtk.ListStore'
ui_cat_model = builder.get_object("categories_model") as
ListStore;
^
unity-tool-ui.vala:158.74-158.82: error: `ListStore' is an ambiguous
reference between `GLib.ListStore' and `Gtk.ListStore'
scope_list_model = builder.get_object("scope_list_model") as
ListStore;
^
music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
public ListStore track_view_model { get; construct; }
^
music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
public ListStore track_view_model { get; construct; }
^
music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
public ListStore track_view_model { get; construct; }
^
music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
public ListStore track_view_model { get; construct; }
^
Compilation failed: 12 error(s), 0 warning(s)
Seems like the same problem in all cases, and I'm not sure which
ListStore is intended. Full buildlog is available in the Python 3.5
-as-default PPA:
https://launchpadlibrarian.net/216183170/buildlog_ubuntu-wily-
amd64.libunity_7.1.4%2B14.10.20140808-0ubuntu1_BUILDING.txt.gz
This is blocking several other critical packages which need updating
for Python 3.5.
To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1491542/+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 1185784] Re: Multi-monitor configuration with different vertical resolution
Maybe this can split into several bug reports, since there could be several causes for the single points. Personally I can confirm point 3). I will further explain the problem. My setup is a one portrait monitor (1920x1080) and one landscape (1080x1920). My desktop background is 1920x1920 so in zoom & center setting both monitors are filled without the background being zoomed. However after relogin or reboot the secondary landscape monitor's background is either zoomed by 1.7x (1920/1080) or cropped to 1080x1080 leaving black bars left and right, whether the setting was zoom or center. Switching between zoom and center in the setting then returns the original mode. Steps to reproduce: 1. Have two fullhd monitors, primary in portrait, other in landscape mode. 2. Set a 1920x1920 image as desktop background 3. Set center or zoom mode 4. Log out and log in again ** Attachment added: "Screenshots of the two error modes and how it should be" https://bugs.launchpad.net/unity/+bug/1185784/+attachment/4461221/+files/screenshots.tgz -- 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/1185784 Title: Multi-monitor configuration with different vertical resolution Status in Unity: New Status in unity package in Ubuntu: New Bug description: I observe this bug for a long time in all versions of Ubuntu. Bug is simple: ubuntu doesn't work correctly with 2 or more monitors that have different vertical resolution. This bug starts at login screen, where monitors works as mirrors, and ends in Unity with different bugs with background, windows position and so on. Now I'm using Ubuntu 13.04 and radeon driver. I have 2 monitors with resolution 2560x1440, they are connected to 2 video cards (tried HD5450+HD5450 and HD6570+HD5450). In this case configuration with two horizontal monitors works good enough, but when I rotate monitors - several bugs occurred at the same place: 1) It is not possible to rotate any monitor, that is connected to not primary video card (primary means installed in the first PCI-E slot), because xserver crashes, and I see login screen 2) If I rotate primary screen - I see large degradation in performance (comparing to horizontal position) 3) After reboot primary (rotated) monitor is cropped to height of horizontal monitor (and performance is the same as in horizontal position of both monitors), and only opening monitors settings window and applying current settings without any changes (after this desktop background is not displayed correctly [scale mode], but returns if choose any other displaying mode, and then switch to scale) 4) At login screen only primary monitor works and in default (unrotated) position This all was tested on Ubuntu 13.04 and 13.10 with stock and compiled by myself kernels 3.8-3.10-rc3 and with different stock and testing versions of radeon driver, mesa, and other stuff from xorg-edgers. Sorry if something is not understandable, I'm pretty sure all this is simply reproducible and can repeat any steps again with any necessary logs to solve this problem as fast as it is possible. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1185784/+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 1446081] Re: Incorrect scaling of launcher icons
Sample problem here. -- 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/1446081 Title: Incorrect scaling of launcher icons Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Launcher icons shown w/o issues only on this sizes of launcher: 16, 24, 32, 48, 64. Screenshot attached. Look at Sublime, Chrome and Skype icons. There was no such issue before vivid. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 20 00:26:44 2015 JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-27 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1446081/+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 1494620] Re: Allow turning alarm off directly in the indicator
** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-clock-app -- 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/1494620 Title: Allow turning alarm off directly in the indicator Status in indicator-datetime package in Ubuntu: New Bug description: Hello, since I switched from Android to Ubuntu full-time I've been among other things using my Ubuntu phone as my alarm. However, I mostly wake up a few minutes before the alarm actually starts and in that case I no longer want it to make any noises once I am already up. On Android I could kill the alarm directly from the "indicator" but here I have to go to the indicator, hit the alarm listed there, an app opens, I have to slide from the bottom to reveal all alarms and then I can kill it. It is too much complicated to do such an easy task. I know this is not really a bug, just an idea, and I would very much appreciate it to be implemented :), would save me some tome each morning :). I suggest to implement slide left/right to kill it or maybe better just a simple "delete" button :). Thank you very much for considering this and supplying some more thoughts on this topic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1494620/+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 1484126] Re: [Indicators] Volume notification unnecessary when adjusting volume slider
** Changed in: unity8 (Ubuntu) Status: In Progress => Fix Committed ** No longer affects: indicator-sound (Ubuntu) -- 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/1484126 Title: [Indicators] Volume notification unnecessary when adjusting volume slider Status in Ubuntu UX: Fix Committed Status in unity8 package in Ubuntu: Fix Committed Bug description: Current situation: Go to Sound section of indicators, drag volume slider. The volume notification pops up, essentially replicating the slider below Desired solution: Let's remove the volume notification when sliding the the volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1484126/+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 1450741] Re: package humanity-icon-theme 0.6.8 failed to install/upgrade: package humanity-icon-theme is already installed and configured
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of DX Packages, which is subscribed to humanity-icon-theme in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1450741 Title: package humanity-icon-theme 0.6.8 failed to install/upgrade: package humanity-icon-theme is already installed and configured Status in humanity-icon-theme package in Ubuntu: New Bug description: erreur systeme. paquets cassés à la mise à jour.. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: humanity-icon-theme ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 ApportVersion: 2.17.2-0ubuntu1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu3 Architecture: i386 Date: Thu Apr 30 13:25:19 2015 DuplicateSignature: package:humanity-icon-theme:0.6.8:package humanity-icon-theme is already installed and configured ErrorMessage: package humanity-icon-theme is already installed and configured InstallationDate: Installed on 2015-04-20 (10 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: humanity-icon-theme Title: package humanity-icon-theme 0.6.8 failed to install/upgrade: package humanity-icon-theme is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1450741/+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 1158200] No launchpad retracing
Unsetting the need retracing tag, there is no retracer left running on that version of Ubuntu, the crash will need to be manually retraced ** Tags removed: need-amd64-retrace -- 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/1158200 Title: unity-panel-service crashed with SIGSEGV in g_data_set_internal() Status in Unity: Triaged Status in unity package in Ubuntu: Confirmed Bug description: when restarting session after adding experimental ppa ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: unity-services 6.12.0daily13.03.21ubuntu.unity.experimental.certified-0ubuntu1 [origin: LP-PPA-ubuntu-unity-experimental-prevalidation] ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CrashDB: unity Date: Thu Mar 21 10:26:13 2013 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationDate: Installed on 2012-08-22 (210 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: SHELL=/bin/zsh XDG_RUNTIME_DIR= PATH=(custom, user) LANG=de_DE.UTF-8 SegvAnalysis: Segfault happened at: 0x7facdf1a0d43 : mov(%rcx),%edi PC (0x7facdf1a0d43) ok source "(%rcx)" (0xaaa8) not located in a known VMA region (needed readable region)! destination "%edi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: g_data_set_internal (dataset=0x0, new_destroy_func=0x0, new_data=0x0, key_id=53, datalist=0x22d5290) at /build/buildd/glib2.0-2.35.8/./glib/gdataset.c:367 g_datalist_id_set_data_full (datalist=datalist@entry=0x22d5290, key_id=53, data=data@entry=0x0, destroy_func=destroy_func@entry=0x0) at /build/buildd/glib2.0-2.35.8/./glib/gdataset.c:674 g_object_unref (_object=0x22d5280) at /build/buildd/glib2.0-2.35.8/./gobject/gobject.c:3011 ?? () ?? () Title: unity-panel-service crashed with SIGSEGV in g_data_set_internal() UpgradeStatus: Upgraded to raring on 2012-12-06 (104 days ago) UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo XsessionErrors: gnome-session[11979]: WARNING: Application 'compiz.desktop' killed by signal 9 gnome-session[11979]: WARNING: App 'compiz.desktop' respawning too quickly gnome-session[11979]: CRITICAL: We failed, but the fail whale is dead. Sorry gnome-session[11979]: WARNING: App 'compiz.desktop' respawning too quickly To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1158200/+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 1411187] Re: [datetime] Add option to not have snooze
** Changed in: ubuntu-clock-app Milestone: 3.6 => 3.x.backlog -- 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/1411187 Title: [datetime] Add option to not have snooze Status in Ubuntu Clock App: Triaged Status in Ubuntu UX: Fix Committed Status in unity-notifications: New Status in indicator-datetime package in Ubuntu: Triaged Status in unity-notifications package in Ubuntu: New Bug description: Snooze is evil. I suggest to add to snooze dropdown menu in the option the voice "No snooze" or something like this Documentation: https://docs.google.com/a/canonical.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g34303b1ce_2_11 https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g36c1a0cdd_010 https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit https://developer.gnome.org/notification-spec/ [UX Comment] As it seems unlikely that we will be able to implement snooze on/off & snooze duration for individual alarms, but do have an application-wide setting that allows snooze duration to be set (but not disabled), I'd recommend the options relating to snooze in application settings be changed to the following: - No snooze - 5 minutes - 10 minutes - 15 minutes This way the list is still short (four options, as it is currently) but the options provided are likely to be more useful (current 2 minute snooze doesn't seem very useful, nor does the difference between 4 mins and 5 min snooze periods). [UX Comment 2] Additionally, notifications for snoozing alarms should come in two forms: 1. With the options 'OK' (ceases alarm) and 'Snooze' (sets the alarm to the snooze period elected by the user) 2. With the option 'OK' (ceases the alarm) when snooze is not enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1411187/+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 1494711] [NEW] Non-existent untitled events appearing in indicator
You have been subscribed to a public bug: Long press somewhere in week view. This used to create a new event, but now *appears* to do absolutely nothing. Nowhere in the Calendar app will you find any evidence of a event existing at that time, even if you close/reopen the app. But, in the indicator suddenly an "Untitled" event appears for that time. Given that this is not in the Calendar app, there is also no way to remove this event from the indicator. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-calendar-app Importance: Undecided Status: New -- Non-existent untitled events appearing in indicator https://bugs.launchpad.net/bugs/1494711 You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. -- 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 1494711] Re: Non-existent untitled events appearing in indicator
Seems that I can change the target. But how do I set it correctly in the firstplace? -- 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/1494711 Title: Non-existent untitled events appearing in indicator Status in Ubuntu Calendar App: New Status in indicator-datetime package in Ubuntu: New Bug description: Long press somewhere in week view. This used to create a new event, but now *appears* to do absolutely nothing. Nowhere in the Calendar app will you find any evidence of a event existing at that time, even if you close/reopen the app. But, in the indicator suddenly an "Untitled" event appears for that time. Given that this is not in the Calendar app, there is also no way to remove this event from the indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1494711/+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 1494711] Re: Non-existent untitled events appearing in indicator
How do you add indicator-datetime as an affected project correctly? The project doesn't track bugs directly, but through ubuntu/+source /indicator-datetime. How do you add this? ** Project changed: indicator-datetime => indicator-datetime (Ubuntu) -- 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/1494711 Title: Non-existent untitled events appearing in indicator Status in Ubuntu Calendar App: New Status in indicator-datetime package in Ubuntu: New Bug description: Long press somewhere in week view. This used to create a new event, but now *appears* to do absolutely nothing. Nowhere in the Calendar app will you find any evidence of a event existing at that time, even if you close/reopen the app. But, in the indicator suddenly an "Untitled" event appears for that time. Given that this is not in the Calendar app, there is also no way to remove this event from the indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1494711/+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 1488569] Re: MPRIS controls don't reflect the current player state
** Changed in: indicator-sound (Ubuntu) Importance: Undecided => Critical -- 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/1488569 Title: MPRIS controls don't reflect the current player state Status in Canonical System Image: New Status in indicator-sound package in Ubuntu: New Bug description: The MPRIS controls (play/pause, next, previous) should reflect the current state of the current media player in media-hub. The following are what I would expect: 1. When media-hub reports that CanGoNext/Previous are false, the next and previous buttons in the indicator are disabled and visually greyed out or something to this effect. 2. The play button should show when media-hub reports that the current player is stopped or pause. 3. The pause button should show instead of the play button when media- hub reports that the current player is playing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488569/+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 1488569] Re: MPRIS controls don't reflect the current player state
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Alejandro J. Cura (alecu) ** Changed in: canonical-devices-system-image Milestone: None => ww40-2015 ** Changed in: canonical-devices-system-image Importance: Undecided => Critical -- 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/1488569 Title: MPRIS controls don't reflect the current player state Status in Canonical System Image: New Status in indicator-sound package in Ubuntu: New Bug description: The MPRIS controls (play/pause, next, previous) should reflect the current state of the current media player in media-hub. The following are what I would expect: 1. When media-hub reports that CanGoNext/Previous are false, the next and previous buttons in the indicator are disabled and visually greyed out or something to this effect. 2. The play button should show when media-hub reports that the current player is stopped or pause. 3. The pause button should show instead of the play button when media- hub reports that the current player is playing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488569/+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 1488569] Re: MPRIS controls don't reflect the current player state
I understand the fixes for this bug belong in silo 55 for testing with the media-hub changes -- 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/1488569 Title: MPRIS controls don't reflect the current player state Status in Canonical System Image: New Status in Ubuntu UX: New Status in indicator-sound package in Ubuntu: New Bug description: The MPRIS controls (play/pause, next, previous) should reflect the current state of the current media player in media-hub. The following are what I would expect: 1. When media-hub reports that CanGoNext/Previous are false, the next and previous buttons in the indicator are disabled and visually greyed out or something to this effect. 2. The play button should show when media-hub reports that the current player is stopped or pause. 3. The pause button should show instead of the play button when media- hub reports that the current player is playing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488569/+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 1373313] Re: Media Hub not exporting MPRIS controls
OK, so we've broken out the indicator work into bug #1488569. Landing the MPRIS controls is stalled until that bug is fixed. -- 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/1373313 Title: Media Hub not exporting MPRIS controls Status in Canonical System Image: In Progress Status in Ubuntu Music App: Invalid Status in indicator-sound package in Ubuntu: In Progress Status in media-hub package in Ubuntu: Fix Committed Bug description: Pressing the previous or next button in the indicator sound menu does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373313/+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 1491542] Re: libunity ftbfs in wily
** Changed in: libunity
Status: New => In Progress
** Changed in: libunity (Ubuntu)
Status: New => In Progress
** Changed in: libunity
Importance: Undecided => Critical
** Changed in: libunity
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: libunity
Milestone: None => 7.1.0
** Branch linked: lp:~3v1n0/libunity/fix-ftb-wily
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1491542
Title:
libunity ftbfs in wily
Status in libunity:
In Progress
Status in libunity package in Ubuntu:
In Progress
Bug description:
libunity seems to no longer be buildable in wily. This is a problem
because it must be rebuilt for Python 3.5, but it is failing for
unrelated reasons. Here's an excerpt of the build log from a local
build using the current wily source package:
/usr/bin/glib-compile-resources --sourcedir . --target=unity-tool-res.c
--generate-source unity-tool-res.gresource.xml
/usr/bin/valac -C --vapidir ../vapi --vapidir=../protocol --vapidir=../src
--pkg config --pkg gtk+-3.0 --pkg gmodule-2.0 --pkg unity-internal --pkg
unity-protocol --pkg glib-2.0 --pkg gmodule-2.0 --pkg gobject-2.0 --pkg gio-2.0
--pkg gio-unix-2.0 --pkg dee-1.0 --pkg Dbusmenu-0.4 unity-tool.vala
unity-tool-dbus-util.vala unity-tool-ui.vala preview-renderer.vala
music-track-model-renderer.vala
unity-tool-ui.vala:846.13-846.21: error: `ListStore' is an ambiguous
reference between `GLib.ListStore' and `Gtk.ListStore'
private ListStore uimodel = null;
^
unity-tool-ui.vala:847.13-847.21: error: `ListStore' is an ambiguous
reference between `GLib.ListStore' and `Gtk.ListStore'
private ListStore ui_filter_model = null;
^
unity-tool-ui.vala:848.13-848.21: error: `ListStore' is an ambiguous
reference between `GLib.ListStore' and `Gtk.ListStore'
private ListStore scope_list_model = null;
^
unity-tool-ui.vala:849.13-849.21: error: `ListStore' is an ambiguous
reference between `GLib.ListStore' and `Gtk.ListStore'
private ListStore ui_cat_model = null;
^
unity-tool-ui.vala:43.62-43.70: error: `ListStore' is an ambiguous reference
between `GLib.ListStore' and `Gtk.ListStore'
uimodel = builder.get_object("results_model") as ListStore;
^
unity-tool-ui.vala:44.70-44.78: error: `ListStore' is an ambiguous reference
between `GLib.ListStore' and `Gtk.ListStore'
ui_filter_model = builder.get_object("filters_model") as
ListStore;
^
unity-tool-ui.vala:45.70-45.78: error: `ListStore' is an ambiguous reference
between `GLib.ListStore' and `Gtk.ListStore'
ui_cat_model = builder.get_object("categories_model") as
ListStore;
^
unity-tool-ui.vala:158.74-158.82: error: `ListStore' is an ambiguous
reference between `GLib.ListStore' and `Gtk.ListStore'
scope_list_model = builder.get_object("scope_list_model") as
ListStore;
^
music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
public ListStore track_view_model { get; construct; }
^
music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
public ListStore track_view_model { get; construct; }
^
music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
public ListStore track_view_model { get; construct; }
^
music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
public ListStore track_view_model { get; construct; }
^
Compilation failed: 12 error(s), 0 warning(s)
Seems like the same problem in all cases, and I'm not sure which
ListStore is intended. Full buildlog is available in the Python 3.5
-as-default PPA:
https://launchpadlibrarian.net/216183170/buildlog_ubuntu-wily-
amd64.libunity_7.1.4%2B14.10.20140808-0ubuntu1_BUILDING.txt.gz
This is blocking several other critical packages which need updating
for Python 3.5.
To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1491542/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-
[Dx-packages] [Bug 1488569] Re: MPRIS controls don't reflect the current player state
This bug blocks bug #1373313 from landing. ** Also affects: ubuntu-ux Importance: Undecided Status: New -- 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/1488569 Title: MPRIS controls don't reflect the current player state Status in Canonical System Image: New Status in Ubuntu UX: New Status in indicator-sound package in Ubuntu: New Bug description: The MPRIS controls (play/pause, next, previous) should reflect the current state of the current media player in media-hub. The following are what I would expect: 1. When media-hub reports that CanGoNext/Previous are false, the next and previous buttons in the indicator are disabled and visually greyed out or something to this effect. 2. The play button should show when media-hub reports that the current player is stopped or pause. 3. The pause button should show instead of the play button when media- hub reports that the current player is playing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488569/+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 1438870] Re: Lock screen doesn't emit ActiveChanged signal
** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: unity-settings-daemon (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: unity (Ubuntu Trusty) Status: New => Fix Released ** Changed in: unity-settings-daemon (Ubuntu Trusty) Status: New => Confirmed ** Changed in: unity-settings-daemon (Ubuntu Trusty) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- 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/1438870 Title: Lock screen doesn't emit ActiveChanged signal Status in Unity: Won't Fix Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Status in unity-settings-daemon source package in Trusty: Confirmed Bug description: tl;dr; Unity doesn't emit the ActiveChanged signal when the screen is locked/unlocked Long version: unity-settings-daemon's automount plugin has code to detect whether the screen is locked or not before automatically mounting a volume. This prevents someone from inserting a USB thumb drive when the screen is locked and exploiting a possible nautilus thumbnailer vulnerability. (See bug #714958 for original implementation details.) In Ubuntu 14.04, this code no longer works. Inserting a USB thumb drive while the screen is locked results in a Nautilus window opening underneath the lock screen, and the contents of the USB thumb drive being read. Since the screen lock got switched to Unity in Ubuntu 14.04, Unity no longer emits the org.gnome.ScreenSaver ActiveChanged signal when the screen gets locked or unlocked. To test: 1- in terminal, type: dbus-monitor "type='signal',sender='org.gnome.ScreenSaver',interface='org.gnome.ScreenSaver'" 2- Lock the screen 3- Unlock the screen 4- Notice that no signal was received ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 31 15:15:48 2015 InstallationDate: Installed on 2013-11-26 (489 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-07 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1438870/+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 1494620] Re: Allow turning alarm off directly in the indicator
For repeated alarms, it would be nice to have a "skip this time" option. (Exactly for the case that I'm actually awake. But if it's periodic alarm, I might not want to turn the alarm off as I might want it next time.) But getting this right in the UI sounds non-trivial. -- 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/1494620 Title: Allow turning alarm off directly in the indicator Status in indicator-datetime package in Ubuntu: New Bug description: Hello, since I switched from Android to Ubuntu full-time I've been among other things using my Ubuntu phone as my alarm. However, I mostly wake up a few minutes before the alarm actually starts and in that case I no longer want it to make any noises once I am already up. On Android I could kill the alarm directly from the "indicator" but here I have to go to the indicator, hit the alarm listed there, an app opens, I have to slide from the bottom to reveal all alarms and then I can kill it. It is too much complicated to do such an easy task. I know this is not really a bug, just an idea, and I would very much appreciate it to be implemented :), would save me some tome each morning :). I suggest to implement slide left/right to kill it or maybe better just a simple "delete" button :). Thank you very much for considering this and supplying some more thoughts on this topic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1494620/+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 1491555] Re: Unity unnecessarily goes to low graphics mode
This bug was fixed in the package unity - 7.3.2+15.10.20150910.1-0ubuntu1 --- unity (7.3.2+15.10.20150910.1-0ubuntu1) wily; urgency=medium [ Andrea Azzarone andrea.azzar...@canonical.com ] * Add unit tests for unity::lockscreen::DBusManager. * Add/Update tests for gnome session manager. * Do not allow shutdown when screen is locked. (LP: #1460626) * Make sure we update the maximized window when "show desktop"/"restore desktop". (LP: #1485559) * Merge patch from https://launchpadlibrarian.net/216192448/llvm- fix.patch (LP: #1491555) * Merge patch from https://launchpadlibrarian.net/216276242/low-gfx- override.patch (LP: #1491913) [ Andrea Azzarone azzaro...@gmail.com ] * Properly hide decorations when on "Show Desktop" mode. (LP: #1485073) [ Marco Trevisan (Treviño) ] * UnityScreen: force shell to be on top when there's a window fullscreen and we've a menu open. (LP: #591189) -- Marco Trevisan (Treviño) Thu, 10 Sep 2015 15:37:46 + ** Changed in: unity (Ubuntu) Status: In Progress => Fix Released -- 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/1491555 Title: Unity unnecessarily goes to low graphics mode Status in Unity: In Progress Status in unity package in Ubuntu: Fix Released Bug description: Unity goes into low graphics mode when it detects "LLVM" in the renderer string. "LLVM" is not the right pattern to match because there are now accelerated Gallium drivers those also report "LLVM" in the render string, e.g. VMWare and Radeon. For example, this bug that showed up recently: https://bugs.freedesktop.org/show_bug.cgi?id=91747#c3 Gallium drivers may fall back to the Gallium Draw module for certain operations, and the Draw module can go down an LLVM path if necessarily and enabled. I think the original intention of this check is to catch "llvmpipe" driver, so I've attached a patch to do just that. Also, instead of matching "on softpipe", it seems that "softpipe" is sufficient. FYI, this fix can hopefully end up in Ubuntu 14.04 onwards. Unfortunately, I can't get through my company's proxy to push my branch, so instead of a merge request, please see the patch attached. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1491555/+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 1491913] Re: Force high gfx mode with UNITY_LOW_GFX_MODE == 0
This bug was fixed in the package unity - 7.3.2+15.10.20150910.1-0ubuntu1 --- unity (7.3.2+15.10.20150910.1-0ubuntu1) wily; urgency=medium [ Andrea Azzarone andrea.azzar...@canonical.com ] * Add unit tests for unity::lockscreen::DBusManager. * Add/Update tests for gnome session manager. * Do not allow shutdown when screen is locked. (LP: #1460626) * Make sure we update the maximized window when "show desktop"/"restore desktop". (LP: #1485559) * Merge patch from https://launchpadlibrarian.net/216192448/llvm- fix.patch (LP: #1491555) * Merge patch from https://launchpadlibrarian.net/216276242/low-gfx- override.patch (LP: #1491913) [ Andrea Azzarone azzaro...@gmail.com ] * Properly hide decorations when on "Show Desktop" mode. (LP: #1485073) [ Marco Trevisan (Treviño) ] * UnityScreen: force shell to be on top when there's a window fullscreen and we've a menu open. (LP: #591189) -- Marco Trevisan (Treviño) Thu, 10 Sep 2015 15:37:46 + ** Changed in: unity (Ubuntu) Status: In Progress => Fix Released -- 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/1491913 Title: Force high gfx mode with UNITY_LOW_GFX_MODE == 0 Status in Unity: In Progress Status in unity package in Ubuntu: Fix Released Bug description: While discussing bug #1491555, my colleague Brian Paul suggested that in addition to forcing low gfx mode with UNITY_LOW_GFX_MODE = 1, it would also be helpful to force it out of low gfx mode with UNITY_LOW_GFX_MODE = 0. This way if Unity ends up in low gfx mode unnecessarily due to a wrong renderer string match, e.g. LLVM in the current case, there is a quick workaround to get out of it while a fix works its way through the release process. The patch (signed-off-by: Sinclair Yeh ) attached adds this capability. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1491913/+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 1485559] Re: Using integrated menus "Show Desktop" still shows title/menus from the previous maximized window
This bug was fixed in the package unity - 7.3.2+15.10.20150910.1-0ubuntu1 --- unity (7.3.2+15.10.20150910.1-0ubuntu1) wily; urgency=medium [ Andrea Azzarone andrea.azzar...@canonical.com ] * Add unit tests for unity::lockscreen::DBusManager. * Add/Update tests for gnome session manager. * Do not allow shutdown when screen is locked. (LP: #1460626) * Make sure we update the maximized window when "show desktop"/"restore desktop". (LP: #1485559) * Merge patch from https://launchpadlibrarian.net/216192448/llvm- fix.patch (LP: #1491555) * Merge patch from https://launchpadlibrarian.net/216276242/low-gfx- override.patch (LP: #1491913) [ Andrea Azzarone azzaro...@gmail.com ] * Properly hide decorations when on "Show Desktop" mode. (LP: #1485073) [ Marco Trevisan (Treviño) ] * UnityScreen: force shell to be on top when there's a window fullscreen and we've a menu open. (LP: #591189) -- Marco Trevisan (Treviño) Thu, 10 Sep 2015 15:37:46 + ** Changed in: unity (Ubuntu) Status: In Progress => Fix Released -- 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/1485559 Title: Using integrated menus "Show Desktop" still shows title/menus from the previous maximized window Status in Unity: In Progress Status in unity package in Ubuntu: Fix Released Bug description: 1. Activate integrated menus 2. Open and maximize a window 3. Click on "Show Desktop" Expected result: Panels shows "Ubuntu Desktop" Actual results: Panel still shows the menu/title of the maximized window. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1485559/+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 1460626] Re: Unity Lockscreen still shows unlocked desktop while shutting down
This bug was fixed in the package unity - 7.3.2+15.10.20150910.1-0ubuntu1 --- unity (7.3.2+15.10.20150910.1-0ubuntu1) wily; urgency=medium [ Andrea Azzarone andrea.azzar...@canonical.com ] * Add unit tests for unity::lockscreen::DBusManager. * Add/Update tests for gnome session manager. * Do not allow shutdown when screen is locked. (LP: #1460626) * Make sure we update the maximized window when "show desktop"/"restore desktop". (LP: #1485559) * Merge patch from https://launchpadlibrarian.net/216192448/llvm- fix.patch (LP: #1491555) * Merge patch from https://launchpadlibrarian.net/216276242/low-gfx- override.patch (LP: #1491913) [ Andrea Azzarone azzaro...@gmail.com ] * Properly hide decorations when on "Show Desktop" mode. (LP: #1485073) [ Marco Trevisan (Treviño) ] * UnityScreen: force shell to be on top when there's a window fullscreen and we've a menu open. (LP: #591189) -- Marco Trevisan (Treviño) Thu, 10 Sep 2015 15:37:46 + ** Changed in: unity (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1460626 Title: Unity Lockscreen still shows unlocked desktop while shutting down Status in Unity: In Progress Status in indicator-session package in Ubuntu: In Progress Status in unity package in Ubuntu: Fix Released Bug description: This was reported and supposedly fixed in https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1370017, but the bug is still present in the current Unity version in Trusty. I've reported it in that bug already, but got ignored, so I'm opening a new bug about it. [Impact and Test Case] Steps to reproduce: 1 - Log into Unity 2 - Open a terminal. 3 - Lock the screen 4 - From the lockscreen, tell the computer to shut down / restart Expected behavior: * Session programs are closed while the screen is still locked * During shutdown, no user interaction is possible Observed behavior: * The lockscreen is gone immediately, with the rest of compiz (e.g. window decorations are not present) * But it's possible to interact with programs that are still running in the session for about 3 seconds Observed on an updated Trusty machine, running unity version 7.2.5+14.04.20150521.1-0ubuntu1 This bug is a security vulnerability because during those 3 seconds it could be possible to access and interact with sensitive information. Yes, it's short, but you could take a picture or even rm -rf / if there happened to be a root console available. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1460626/+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 591189] Re: Manage the fullscreen application case
This bug was fixed in the package unity - 7.3.2+15.10.20150910.1-0ubuntu1 --- unity (7.3.2+15.10.20150910.1-0ubuntu1) wily; urgency=medium [ Andrea Azzarone andrea.azzar...@canonical.com ] * Add unit tests for unity::lockscreen::DBusManager. * Add/Update tests for gnome session manager. * Do not allow shutdown when screen is locked. (LP: #1460626) * Make sure we update the maximized window when "show desktop"/"restore desktop". (LP: #1485559) * Merge patch from https://launchpadlibrarian.net/216192448/llvm- fix.patch (LP: #1491555) * Merge patch from https://launchpadlibrarian.net/216276242/low-gfx- override.patch (LP: #1491913) [ Andrea Azzarone azzaro...@gmail.com ] * Properly hide decorations when on "Show Desktop" mode. (LP: #1485073) [ Marco Trevisan (Treviño) ] * UnityScreen: force shell to be on top when there's a window fullscreen and we've a menu open. (LP: #591189) -- Marco Trevisan (Treviño) Thu, 10 Sep 2015 15:37:46 + ** Changed in: unity (Ubuntu) Status: In Progress => Fix Released -- 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/591189 Title: Manage the fullscreen application case Status in Application Menu Indicator: Invalid Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: See https://wiki.ubuntu.com/MenuBar#Full-screen%20windows To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/591189/+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 1485073] Re: Windows in "Show Desktop" mode lose decorations
This bug was fixed in the package unity - 7.3.2+15.10.20150910.1-0ubuntu1 --- unity (7.3.2+15.10.20150910.1-0ubuntu1) wily; urgency=medium [ Andrea Azzarone andrea.azzar...@canonical.com ] * Add unit tests for unity::lockscreen::DBusManager. * Add/Update tests for gnome session manager. * Do not allow shutdown when screen is locked. (LP: #1460626) * Make sure we update the maximized window when "show desktop"/"restore desktop". (LP: #1485559) * Merge patch from https://launchpadlibrarian.net/216192448/llvm- fix.patch (LP: #1491555) * Merge patch from https://launchpadlibrarian.net/216276242/low-gfx- override.patch (LP: #1491913) [ Andrea Azzarone azzaro...@gmail.com ] * Properly hide decorations when on "Show Desktop" mode. (LP: #1485073) [ Marco Trevisan (Treviño) ] * UnityScreen: force shell to be on top when there's a window fullscreen and we've a menu open. (LP: #591189) -- Marco Trevisan (Treviño) Thu, 10 Sep 2015 15:37:46 + ** Changed in: unity (Ubuntu) Status: In Progress => Fix Released -- 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/1485073 Title: Windows in "Show Desktop" mode lose decorations Status in Unity: In Progress Status in unity package in Ubuntu: Fix Released Bug description: 1. Open two windows of a same application 2. Click on "show desktop" 3. Click on the application icon 4. Click again on the application icon One windows has no decorations. This is also causes a glitch during the fade out effect. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1485073/+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 1488051] Re: compiz crashed with SIGSEGV in g_bit_lock()
*** This bug is a duplicate of bug 1492437 *** https://bugs.launchpad.net/bugs/1492437 ** This bug has been marked a duplicate of bug 1492437 Unity crash when trying to "unlock from launcher" a disk drive icon -- 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/1488051 Title: compiz crashed with SIGSEGV in g_bit_lock() Status in Unity: New Status in unity package in Ubuntu: New Bug description: Test Case: Try to unlock an internal volume from unity launcher. If fails to be removed, compiz crashes (- manually blacklisting in dconf works ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20150819-0ubuntu1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 24 06:55:06 2015 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2015-08-21 (3 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150820) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=en_US.UTF-8 LANGUAGE=en_US XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f9b386e8328 :lock bts %r12d,(%rbx) PC (0x7f9b386e8328) ok source "%r12d" ok destination "(%rbx)" (0x0020) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: g_bit_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_serialiser_needed_size () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: compiz crashed with SIGSEGV in g_bit_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1488051/+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
