[Dx-packages] [Bug 1228765] Re: Need to implement DisplayConfig dbus interface within Unity
** Patch added: gnome-desktop 3.10 update https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1228765/+attachment/4006361/+files/gd310.debdiff -- 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/1228765 Title: Need to implement DisplayConfig dbus interface within Unity Status in Ubuntu GNOME: Triaged Status in Unity: Triaged Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such it seems the cleanest solution would be to copy the display config interface from Mutter into Unity. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
** Summary changed: - Need to implement DisplayConfig dbus interface within Unity + [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10 -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Triaged Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such it seems the cleanest solution would be to copy the display config interface from Mutter into Unity. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1281640] Re: Obscene content in music search results
I confirm that. The Soundcloud API doesn't provide a way to filter these, but the Amazon scope has a way to filter offensive content (blacklisted words per locale). While this isn't an optimal solution, I'm going to see asap if it's possible for that method (provided by the smartscopes server) to be shared with the Soundcloud scope. Thanks for the report, I would hate having to get that scope taken down. ** Changed in: unity-scope-soundcloud Assignee: (unassigned) = David Callé (davidc3) ** Changed in: unity-scope-soundcloud Importance: Undecided = High -- 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/1281640 Title: Obscene content in music search results Status in Unity Music Lens: New Status in Unity SoundCloud Scope: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: Some search terms return obscene content in the dash To reproduce: 1) Search for 'rhy' in the dash Expected results: Rhythmbox and other search results are returned, all of which I could show to a customer Actual results: The music scope returns offensive/obscene results, such as WORDS MOTHERF*CKER or Absolute Bullsh*t (see attached screenshot) I am not aware of any way to filter search results (similar to Google's Safe Search). If there is a way, it should be turned on by default. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu3 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Tue Feb 18 10:50:44 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (77 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-music-lens/+bug/1281640/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
** Tags added: patch -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Triaged Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such it seems the cleanest solution would be to copy the display config interface from Mutter into Unity. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
** Description changed: - For GNOME 3.10, all the display configuration/xrandr code has been moved - into Mutter as dbus interface. The Main reason for this move was to - abstract away the display server (x11/wayland). + Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- + control-center 3.10. This however requires a transition to gnome-desktop + 3-10. I have been working on this for quite some time however this work + was essentially blocked waiting on the unity- forks for settings daemon + and control center. These were only finalised the day before feature + freeze. + + Right now there are quite a few features that are not available for + configuration in g-c-c given it is so old. We are also hitting some odd + bugs with mutter using its own display config separate to what gnome- + settings-daemon is doing with xrandr. + + + For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to - revert these changes for Unity only. As such it seems the cleanest - solution would be to copy the display config interface from Mutter into - Unity. The code itself is fairly self contained, so apart from the - resulting duplication of code, it shouldnt really be much of an issue. + revert these changes for Unity only. As such have forked the display + config code from mutter and ported *-settings-daemon and *-control- + center to the new api. The code itself is fairly self contained, so + apart from the resulting duplication of code, it shouldnt really be much + of an issue. + + ultimately it was We did do some testing via a ppa, however it was hard + to get extensive testing, due to the amount of archive churn in the + affected packages. I am pretty confident there are no much regressions + and I will commit to fixing any issues to do appear. + + Essentially this transition will involve: + new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) + + gnome/unity-settings-daemon, have backported patches to adapt to the new API. + Likewise for gnome/unity-control-center. + All other rdepends just require a no-change rebuild to adapt to the new soname. ** Description changed: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome-desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome- settings-daemon is doing with xrandr. - - For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. + For GNOME 3.10, all the display configuration/xrandr code has been moved + into Mutter as dbus interface. The Main reason for this move was to + abstract away the display server (x11/wayland). Apart from these changes + there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control- center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. - ultimately it was We did do some testing via a ppa, however it was hard - to get extensive testing, due to the amount of archive churn in the - affected packages. I am pretty confident there are no much regressions - and I will commit to fixing any issues to do appear. + We have tested this via a ppa, however it was hard to get extensive + testing, due to the amount of archive churn in the affected packages. I + am pretty confident there are no much regressions and I will commit to + fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11
[Dx-packages] [Bug 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
gnome-desktop buildlog https://launchpadlibrarian.net/168292752/buildlog_ubuntu-trusty-amd64.gnome-desktop3_3.10.1-0ubuntu1~trusty2_UPLOADING.txt.gz displayconfig buildlog https://launchpadlibrarian.net/168120073/buildlog_ubuntu-trusty-amd64.displayconfig_3.10.4-0ubuntu1~trusty1_UPLOADING.txt.gz logs for the other packages should be at https://launchpad.net/~noskcaj/+archive/build ** Changed in: gnome-desktop3 (Ubuntu) Status: Triaged = 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Triaged Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
Thanks for the work you guys put on this. I'm not part of the release team but from an Ubuntu Desktop/Unity perspective that transition seems risky just before the LTS. The new version does change quite some APIs, when I looked at it those API were used e.g in gnome-screensaver. Could you include on the FFe the list of API changes in the next version and the reverse depends of those APIs? We need to make sure everything in the archive get ported if we transition. During the call for testing on the ubuntu-desktop list there was some feedback about existing configurations not being respected on upgrade and unity barrier not working, have those issues been resolved? -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Triaged Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
The ffe also lists unity, should those lines be set to invalid since the current solution feature a new component rather than unity changes? -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Triaged Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
(oh, another note, g-c-c 3.10 depends on a new gnome-bluetooth apparently, might might depends on bluez5, I just crossed bug #1267909 which is about that) -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Triaged Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1223739] Re: Launcher - unable to reveal Launcher under autohide after using the touch screen
I can not reproduce this in trusty daily build today. I think it already fixed in trusty. -- 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/1223739 Title: Launcher - unable to reveal Launcher under autohide after using the touch screen Status in OEM Priority Project: Confirmed Status in Unity 5.0 series: Confirmed Status in “unity” package in Ubuntu: Triaged Status in “unity” source package in Precise: Confirmed Bug description: To Reproduce (in a system with a touch screen) 1. Boot the system and don't touch the screen 2. Set the Launcher to autohide 3. Move the cursor to the left (using the touchpad or an external mouse) 4. The Launcher is revealed successfully 5. Wait until the launcher hides again 6. Now, touch the screen for the first time (no matter where you touch the screen) 7. Now, use again the touchpad or external mouse to move the cursor to the left to reveal the Launcher Expected result: Launcher is revealed Actual result: Launcher cannot be revealed. Additional information: 1. When the issue happens, can press window key to show dash and launcher (or alt-f1 to reveal the launcher), but moving cursor to the left side still can't show launcher 2. There is no crash is observed so far on X or Compiz 3. Switch to ttyl1 and restart lightdm can recover To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1223739/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
** Changed in: unity Status: Triaged = Invalid -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Invalid Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1287663] [NEW] unlock from lancher not working
Public bug reported: After updating to 14.04 I recently found that the right click on any icon on launcher shows the unlock from launcher button but when i try to do that it does not unlock the icon from launcher ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,resize,snap,imgpng,grid,gnomecompat,unitymtgrabhandles,mousepoll,vpswitch,regex,move,place,compiztoolbox,session,animation,wall,workarounds,expo,fade,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 4 15:37:19 2014 DistUpgraded: 2014-01-30 09:50:42,576 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-13-generic, i686: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-14-generic, i686: installed GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1423] InstallationDate: Installed on 2012-03-24 (709 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120324) MachineType: Hewlett-Packard HP ProBook 4420s ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=8a691df1-94b5-42e2-9bc9-58195c3ca7ac ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-30 (33 days ago) dmi.bios.date: 06/29/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68AHH Ver. F.09 dmi.board.name: 1423 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 53.1D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68AHHVer.F.09:bd06/29/2010:svnHewlett-Packard:pnHPProBook4420s:pvr:rvnHewlett-Packard:rn1423:rvrKBCVersion53.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4420s dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140303-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Mar 4 19:09:52 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 593 vendor LGD xserver.version: 2:1.15.0-1ubuntu6 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- 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/1287663 Title: unlock from lancher not working Status in “unity” package in Ubuntu: New Bug description: After updating to 14.04 I recently found that the right click on any icon on launcher shows the unlock from launcher button but when i try to do that it does not unlock the icon from launcher ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,resize,snap,imgpng,grid,gnomecompat,unitymtgrabhandles,mousepoll,vpswitch,regex,move,place,compiztoolbox,session,animation,wall,workarounds,expo,fade,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 4 15:37:19 2014 DistUpgraded: 2014-01-30 09:50:42,576 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-13-generic, i686: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-14-generic, i686: installed GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1423]
[Dx-packages] [Bug 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
- I fixed the issue with configurations not being read from the gnome-settings-daemon monitors.xml config file, I',m not entirely sure what wrote this file, but Laney suggested it was maybe copied across by one of the indicators? - I couldn't reproduce the pointer barrier issue here on my dual monitor setup. I actually don't believe there is any code dealing with pointer barriers involved here either. - Right, Unity no longer requires changes with this solution. marked invalid. - Our build of g-c-c 3.10 has the bluetooth changes reverted, so no need for BlueZ 5 this cycle (will definitely need that for next cycle however). - I will add a list of the changed API tomorrow, however I don't believe gnome-screensaver is affected by this and certainly built fine when I tested it. Most of the API changes are pretty internal (i.e. limited to g-s-d and g-c-c). The api's that most apps are using (background, thumbnailer, etc) are unaffected. As a side note, I have spoken with upstream about splitting out all app dependencies from gnome-desktop, at which point it would become feasible to fork gnome-desktop, however this won't happen until atleast 3.14 anyway. -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Invalid Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 784055] Re: compiz CPU usage increases dramatically when running indicator-multiload
** Branch linked: lp:ubuntu/trusty-proposed/libindicator -- 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/784055 Title: compiz CPU usage increases dramatically when running indicator- multiload Status in System Load Indicator: Confirmed Status in Libindicator: In Progress Status in The Ubuntu Power Consumption Project: New Status in Unity: Won't Fix Status in “indicator-multiload” package in Ubuntu: Confirmed Status in “libindicator” package in Ubuntu: New Status in “unity” package in Ubuntu: Triaged Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying 300% (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-multiload/+bug/784055/+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 1281640] Re: Obscene content in music search results
** Changed in: unity-music-lens Status: New = Invalid -- 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/1281640 Title: Obscene content in music search results Status in Unity Music Lens: Invalid Status in Unity SoundCloud Scope: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: Some search terms return obscene content in the dash To reproduce: 1) Search for 'rhy' in the dash Expected results: Rhythmbox and other search results are returned, all of which I could show to a customer Actual results: The music scope returns offensive/obscene results, such as WORDS MOTHERF*CKER or Absolute Bullsh*t (see attached screenshot) I am not aware of any way to filter search results (similar to Google's Safe Search). If there is a way, it should be turned on by default. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu3 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Tue Feb 18 10:50:44 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (77 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-music-lens/+bug/1281640/+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 1040259] Re: FFE: libmessaging-menu transitions for quantal
Invaliding since quantal reaches EOL. ** Changed in: liferea (Ubuntu Quantal) Status: Triaged = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1040259 Title: FFE: libmessaging-menu transitions for quantal Status in Gmail Watcher: Triaged Status in Lightread: Triaged Status in Quassel Irc Client: New Status in Skype-wrapper: In Progress Status in “evolution-indicator” package in Ubuntu: Fix Released Status in “gm-notify” package in Ubuntu: Triaged Status in “guayadeque” package in Ubuntu: Fix Released Status in “gwibber” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: Fix Released Status in “kdenetwork” package in Ubuntu: New Status in “kdepim” package in Ubuntu: New Status in “libdbusmenu-qt” package in Ubuntu: New Status in “libunity-webapps” package in Ubuntu: Fix Released Status in “liferea” package in Ubuntu: Fix Released Status in “openfetion” package in Ubuntu: New Status in “pidgin” package in Ubuntu: Fix Released Status in “pidgin-libnotify” package in Ubuntu: Fix Released Status in “quassel” package in Ubuntu: New Status in “smuxi” package in Ubuntu: Fix Released Status in “telepathy-indicator” package in Ubuntu: Fix Released Status in “thunderbird” package in Ubuntu: Fix Released Status in “unity-mail” package in Ubuntu: Fix Released Status in “xchat-indicator” package in Ubuntu: Fix Released Status in “gm-notify” source package in Quantal: Triaged Status in “guayadeque” source package in Quantal: New Status in “gwibber” source package in Quantal: Fix Released Status in “indicator-messages” source package in Quantal: Fix Released Status in “kdenetwork” source package in Quantal: New Status in “kdepim” source package in Quantal: New Status in “libdbusmenu-qt” source package in Quantal: New Status in “libunity-webapps” source package in Quantal: Fix Released Status in “liferea” source package in Quantal: Invalid Status in “openfetion” source package in Quantal: New Status in “pidgin” source package in Quantal: Confirmed Status in “pidgin-libnotify” source package in Quantal: In Progress Status in “quassel” source package in Quantal: New Status in “smuxi” source package in Quantal: Fix Released Status in “telepathy-indicator” source package in Quantal: Fix Released Status in “thunderbird” source package in Quantal: Fix Released Status in “unity-mail” source package in Quantal: Fix Released Status in “xchat-indicator” source package in Quantal: Fix Released Bug description: indicator-messages got updated, introducing a new libmessaging-menu api (deprecating the old libindicate library) which should make application developper's life easier. The indicator work is done and the library is ready and we started porting applications The current stack is being tested in https://launchpad.net/~ubuntu- desktop/+archive/ppa/ It includes - indicator-messages - gwibber - indicator-telepathy - thunderbird (soon, work is being finished) which is what we consider the minimal set for landing the feature for quantal we will add those soon: - pidgin - xchat-indicator - evolution-indicator To manage notifications about this bug go to: https://bugs.launchpad.net/gmailwatcher/+bug/1040259/+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 784055] Re: compiz CPU usage increases dramatically when running indicator-multiload
This bug was fixed in the package libindicator - 12.10.2+14.04.20140304-0ubuntu1 --- libindicator (12.10.2+14.04.20140304-0ubuntu1) trusty; urgency=low [ Marco Trevisan (Treviño) ] * IndicatorImageHelper: always try to use a GIcon or the filename as source of the GdkImage We don't need to fallback to pure pixbuf, unless an indicator provided a custom icon that is not in the current theme path. This helps a lot in reducing the Unity7 workload as this decreases the cases where we need to encode the pixbuf contents, send them via dbus to unity, encode them back, reload to a new pixbuf... Also thanks to this, the library clients can load the actual icon, scaled at the value they want. (LP: #784055) -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 04 Mar 2014 10:58:35 + ** Changed in: libindicator (Ubuntu) Status: New = 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/784055 Title: compiz CPU usage increases dramatically when running indicator- multiload Status in System Load Indicator: Confirmed Status in Libindicator: In Progress Status in The Ubuntu Power Consumption Project: New Status in Unity: Won't Fix Status in “indicator-multiload” package in Ubuntu: Confirmed Status in “libindicator” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Triaged Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying 300% (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-multiload/+bug/784055/+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 1285758] Re: Some Spread Autopilot tests fail randomly
** Changed in: unity Status: In Progress = Fix Committed ** Changed in: unity Milestone: None = 7.2.0 -- 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/1285758 Title: Some Spread Autopilot tests fail randomly Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: A few Spread Autopilot tests randomly fail. Any test that uses the assertWindowIsScaledEquals() method such as * test_scaled_window_closes_on_middle_click * test_scaled_window_closes_on_close_button_click Also, test_scaled_window_closes_on_close_button_click will fail sometimes if there is another window open and the mouse is not over the window in test. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1285758/+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 1285361] Re: Launcher keynav highlighting is broken on a second monitor
** Changed in: unity Status: In Progress = Fix Committed -- 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/1285361 Title: Launcher keynav highlighting is broken on a second monitor Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: An AP test revealed that Launcher keynav highlighting is broken on a second monitor when the primary Launcher is on the second monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1285361/+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 1283159] Re: Dash: no filters
** Changed in: unity Status: In Progress = Fix Committed -- 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/1283159 Title: Dash: no filters Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: Last seen with unity_7.1.2+14.04.20140217 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Feb 21 12:50:59 2014 InstallationDate: Installed on 2014-02-21 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283159/+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 1285349] Re: While hovering indicator menus and crossing to a different monitor, the hover does does not continue on the second monitor
Based on Marco's comments, this bug is invalid. However, the Autopilot test that fails needs to be fixed to account for the new behavior. That will be handled in a separate bug. ** Changed in: unity Status: Triaged = Invalid ** Changed in: unity (Ubuntu) Status: Triaged = Invalid ** Changed in: unity Assignee: Christopher Townsend (townsend) = (unassigned) ** Changed in: unity (Ubuntu) Assignee: Christopher Townsend (townsend) = (unassigned) -- 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/1285349 Title: While hovering indicator menus and crossing to a different monitor, the hover does does not continue on the second monitor Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: When hovering over indicator entries to reveal the menu and switching to different indicators and then crossing into a second monitor, the last indicator that was hovered on the first monitor stays open and the hovering will not continue on the second monitor. This is a regression found in the unity.tests.test_panel.PanelCrossMonitorsTests.test_hovering_indicators_on_multiple_monitors Autopilot test. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1285349/+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 1287747] [NEW] Trying to open an indicator on a second monitor when an indicator is open on the first monitor does not work correctly
Public bug reported: When you have an indicator opened on the first monitor and then cross over to the second monitor and then try to open an indicator on that monitor, the indicator opens in the wrong position on the second monitor and hovering does not work. ** Affects: unity Importance: Medium Status: Triaged ** Affects: unity (Ubuntu) Importance: Medium Status: Triaged ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity Status: New = Triaged ** Changed in: unity (Ubuntu) Status: New = Triaged -- 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/1287747 Title: Trying to open an indicator on a second monitor when an indicator is open on the first monitor does not work correctly Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: When you have an indicator opened on the first monitor and then cross over to the second monitor and then try to open an indicator on that monitor, the indicator opens in the wrong position on the second monitor and hovering does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1287747/+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 1287745] [NEW] Some more Autopilot Panel tests need fixing
Public bug reported: In drilling down on some more Autopilot test failures, some Panel tests will fail, either 100% of the time or occasionally. 1. Some Panel tests will fail if the previous test leaves the system with only the Launcher on the primary monitor. 2. test_window_buttons_show_when_holding_show_menu_key can fail due to a race when pressing and releasing the Alt key. This sometimes opens the Hud during the test which is not expected. 3. test_hovering_indicators_on_multiple_monitors fails due to a change in how multi-monitor Panels are handled. The test needs fixed to account for the new behavior. ** Affects: unity Importance: Medium Assignee: Christopher Townsend (townsend) Status: In Progress ** Affects: unity (Ubuntu) Importance: Medium Assignee: Christopher Townsend (townsend) Status: In Progress ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity Status: New = In Progress ** Changed in: unity (Ubuntu) Status: New = In Progress ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity Milestone: None = 7.2.0 -- 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/1287745 Title: Some more Autopilot Panel tests need fixing Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: In drilling down on some more Autopilot test failures, some Panel tests will fail, either 100% of the time or occasionally. 1. Some Panel tests will fail if the previous test leaves the system with only the Launcher on the primary monitor. 2. test_window_buttons_show_when_holding_show_menu_key can fail due to a race when pressing and releasing the Alt key. This sometimes opens the Hud during the test which is not expected. 3. test_hovering_indicators_on_multiple_monitors fails due to a change in how multi-monitor Panels are handled. The test needs fixed to account for the new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1287745/+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 1274181] Re: notification-daemon crashed with signal 5 in g_source_remove()
same here, using kernel 3.13.0-11-lowlatency -- You received this bug notification because you are a member of DX Packages, which is subscribed to notification-daemon in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1274181 Title: notification-daemon crashed with signal 5 in g_source_remove() Status in “notification-daemon” package in Ubuntu: Confirmed Bug description: Just rebooted and logged into Gnome Flashback with Compiz and immediately got this error notification. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: notification-daemon 0.7.6-1 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Jan 29 11:37:58 2014 ExecutablePath: /usr/lib/notification-daemon/notification-daemon InstallationDate: Installed on 2014-01-08 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140108) ProcCmdline: /usr/lib/notification-daemon/notification-daemon ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: notification-daemon StacktraceTop: g_source_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: notification-daemon crashed with signal 5 in g_source_remove() 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/ubuntu/+source/notification-daemon/+bug/1274181/+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 1266464] Re: HUD Super and Alt shortcuts works through locked screen
** Changed in: unity Milestone: None = 7.2.0 ** Changed in: unity Assignee: (unassigned) = Andrea Azzarone (andyrock) ** Changed in: unity Importance: Undecided = High ** Changed in: unity Status: Confirmed = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1266464 Title: HUD Super and Alt shortcuts works through locked screen Status in Unity: In Progress Status in “hud” package in Ubuntu: Invalid Bug description: To reproduce: 1. Lock screen (e.g. using Ctrl+Alt+L or corresponding option in menu). 2. Press Super (or Alt) key. 3. Enter password to unlock desktop. Expected behaviour: nothing on desktop should be changed. Observed behaviour: HUD menu pupped up, as if Alt or Super were pressed on desktop. I mark this bug report as security issue, because not sure is Super and Alt keys are only shortcuts that being passed to desktop, if other keys can be passed to desktop in any way it would be possible to run some command through HUD. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20131031-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CheckboxSubmission: 3d16077c4fdd6a017d47f6e3dc4f3c54 CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3 Date: Mon Jan 6 17:18:05 2014 InstallationDate: Installed on 2014-01-01 (4 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1266464/+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 1287745] Re: Some more Autopilot Panel tests need fixing
** Branch linked: lp:~townsend/unity/fix-lp1287745 -- 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/1287745 Title: Some more Autopilot Panel tests need fixing Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: In drilling down on some more Autopilot test failures, some Panel tests will fail, either 100% of the time or occasionally. 1. Some Panel tests will fail if the previous test leaves the system with only the Launcher on the primary monitor. 2. test_window_buttons_show_when_holding_show_menu_key can fail due to a race when pressing and releasing the Alt key. This sometimes opens the Hud during the test which is not expected. 3. test_hovering_indicators_on_multiple_monitors fails due to a change in how multi-monitor Panels are handled. The test needs fixed to account for the new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1287745/+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 1287747] Re: Trying to open an indicator on a second monitor when an indicator is open on the first monitor does not work correctly
** Changed in: unity Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity Milestone: None = 7.2.0 ** Changed in: unity Status: Triaged = In Progress ** Changed in: unity (Ubuntu) Status: Triaged = In Progress ** Changed in: unity (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 unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1287747 Title: Trying to open an indicator on a second monitor when an indicator is open on the first monitor does not work correctly Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: When you have an indicator opened on the first monitor and then cross over to the second monitor and then try to open an indicator on that monitor, the indicator opens in the wrong position on the second monitor and hovering does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1287747/+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 1282798] Re: [FFe] Provide a lock screen and unlock dialogs in Unity
Is this ready to be uploaded right now? If not, when will it be? @Seb, how is it configured? -- 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/1282798 Title: [FFe] Provide a lock screen and unlock dialogs in Unity Status in Unity: In Progress Status in “unity” package in Ubuntu: Incomplete Bug description: [FFe] The merge proposal for this work missed the feature freeze dealine by a few hours and requires a freeze exception. This bug replaces the original FFe file under bug #878836. --- original description --- We need to provide a thematically compatible lock screen and unlock dialogs in Unity, consistent with the unity-greeter authentication dialog used in LightDM. This will replace gnome-screenlocker. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1282798/+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 829648] Re: [ffe] No easy way to turn the sound menu on/off
Ok, this seems small and not likely to cause problems - please get it uploaded asap. -- 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/829648 Title: [ffe] No easy way to turn the sound menu on/off Status in Sound Menu: In Progress Status in “indicator-sound” package in Ubuntu: In Progress Status in “unity-control-center” package in Ubuntu: In Progress Bug description: indicator-sound 0.7.6-0ubuntu1, Ubuntu Ocelot 1. Try to work out how to hide the sound menu. What happens: There's no obvious way to do it (short of uninstalling the package). What should happen: At the bottom left corner of the System Settings “Sound” panel should be a checkbox, “Show sound volume in the menu bar”. It should be checked by default for a new user account. Whenever it is checked, the sound menu should be present in the menu bar. https://wiki.ubuntu.com/SoundMenu#presence [Reported by Eustace in http://www.omgubuntu.co.uk/2011/08/power- cog-icon-oneiric/#comment-291049247.] To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/829648/+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 1287343] Re: Application menu hijacks Alt+F, E, V, S, T, H keybindings in gnome-terminal
*** This bug is a duplicate of bug 1282782 *** https://bugs.launchpad.net/bugs/1282782 ** This bug has been marked a duplicate of bug 1282782 Newest compiz/unity has decided that it owns my Alt key -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1287343 Title: Application menu hijacks Alt+F,E,V,S,T,H keybindings in gnome-terminal Status in “unity-gtk-module” package in Ubuntu: New Bug description: 1. Enable the menubar in gnome-terminal 2. Go to Edit-Keyboard Shortcuts and uncheck Enable menu access keys (such as Alt+F to open the File menu) 3. Type something in the shell, then go to the beginning of the line, and attempt to use Alt+F to navigate forward by word 4. Observe that the File menu triggers instead, even though it should have been disabled as per step 2. Repeat the above steps running gnome-terminal like: UBUNTU_MENUPROXY=0 gnome-terminal, and notice that the menu doesn't activate, and Alt+F gets successfully handled by the shell. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-gtk3-module 0.0.0+14.04.20140213.2-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 4 03:53:14 2014 SourcePackage: unity-gtk-module UpgradeStatus: Upgraded to trusty on 2014-03-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1287343/+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 1283786] Re: The title of unfocused maximized window remains in panel when it's closed with LIM enabled
** Changed in: unity Status: Triaged = In Progress ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity (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/1283786 Title: The title of unfocused maximized window remains in panel when it's closed with LIM enabled Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Steps to reproduce: 0. Have menus to be in window title bars. 1. Open a window that's maximized. 2. Open and focus a window that's unmaximized. 3. Use the controls in panel to close or minimize the maximized window. What happens: The title of the maximized window is still in the top bar. What should happen: The title should disappear. See the attached screenshot for a bogus 'Untitled 1 - LibreOffice Writer' in the panel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CasperVersion: 1.337 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: Sun Feb 23 20:09:04 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1587] NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1587] LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140223) MachineType: ASUSTeK COMPUTER INC. K56CM ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash -- SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K56CM.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K56CM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK56CM.209:bd11/19/2012:svnASUSTeKCOMPUTERINC.:pnK56CM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK56CM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K56CM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Feb 23 20:00:05 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.15.0-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283786/+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 1283156] Re: menus switch to window title when window is unmaximized
** Changed in: unity Status: New = Triaged -- 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/1283156 Title: menus switch to window title when window is unmaximized Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: When running with Application Menu set to In top bar, applications menus switch to the window title bar when a window is unmaximized, until a different window gets focus. Steps to reproduce: 1- Launch gnome-terminal 2- hover mouse on window title bar to make sure there is no menu 3- maximize gnome-terminal 4- unmaximize gnome-terminal 5- hover mouse on window title...notice that the application menus appear in window title bar 6- Click on another window to take focus away from gnome-terminal 7-Click on gnome-terminal again 8- Hover mouse on window title, menu is now gone ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Feb 21 12:38:20 2014 InstallationDate: Installed on 2013-11-26 (86 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-17 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283156/+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 1274181] Re: notification-daemon crashed with signal 5 in g_source_remove()
...and same now with 3.13.0-14-lowlatency -- You received this bug notification because you are a member of DX Packages, which is subscribed to notification-daemon in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1274181 Title: notification-daemon crashed with signal 5 in g_source_remove() Status in “notification-daemon” package in Ubuntu: Confirmed Bug description: Just rebooted and logged into Gnome Flashback with Compiz and immediately got this error notification. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: notification-daemon 0.7.6-1 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Jan 29 11:37:58 2014 ExecutablePath: /usr/lib/notification-daemon/notification-daemon InstallationDate: Installed on 2014-01-08 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140108) ProcCmdline: /usr/lib/notification-daemon/notification-daemon ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: notification-daemon StacktraceTop: g_source_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: notification-daemon crashed with signal 5 in g_source_remove() 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/ubuntu/+source/notification-daemon/+bug/1274181/+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 1274181] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1274181/+attachment/4006833/+files/ProcEnviron.txt -- You received this bug notification because you are a member of DX Packages, which is subscribed to notification-daemon in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1274181 Title: notification-daemon crashed with signal 5 in g_source_remove() Status in “notification-daemon” package in Ubuntu: Confirmed Bug description: Just rebooted and logged into Gnome Flashback with Compiz and immediately got this error notification. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: notification-daemon 0.7.6-1 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Jan 29 11:37:58 2014 ExecutablePath: /usr/lib/notification-daemon/notification-daemon InstallationDate: Installed on 2014-01-08 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140108) ProcCmdline: /usr/lib/notification-daemon/notification-daemon ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: notification-daemon StacktraceTop: g_source_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: notification-daemon crashed with signal 5 in g_source_remove() 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/ubuntu/+source/notification-daemon/+bug/1274181/+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 1274181] Re: notification-daemon crashed with signal 5 in g_source_remove()
ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2012-02-27 (735 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) Package: notification-daemon 0.7.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-14.34-lowlatency 3.13.5 Tags: trusty Uname: Linux 3.13.0-14-lowlatency x86_64 UpgradeStatus: Upgraded to trusty on 2013-12-03 (90 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers wireshark _MarkForUpload: True ** Tags added: apport-collected -- You received this bug notification because you are a member of DX Packages, which is subscribed to notification-daemon in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1274181 Title: notification-daemon crashed with signal 5 in g_source_remove() Status in “notification-daemon” package in Ubuntu: Confirmed Bug description: Just rebooted and logged into Gnome Flashback with Compiz and immediately got this error notification. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: notification-daemon 0.7.6-1 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Jan 29 11:37:58 2014 ExecutablePath: /usr/lib/notification-daemon/notification-daemon InstallationDate: Installed on 2014-01-08 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140108) ProcCmdline: /usr/lib/notification-daemon/notification-daemon ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: notification-daemon StacktraceTop: g_source_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: notification-daemon crashed with signal 5 in g_source_remove() 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/ubuntu/+source/notification-daemon/+bug/1274181/+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 1274181] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1274181/+attachment/4006832/+files/Dependencies.txt -- You received this bug notification because you are a member of DX Packages, which is subscribed to notification-daemon in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1274181 Title: notification-daemon crashed with signal 5 in g_source_remove() Status in “notification-daemon” package in Ubuntu: Confirmed Bug description: Just rebooted and logged into Gnome Flashback with Compiz and immediately got this error notification. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: notification-daemon 0.7.6-1 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Jan 29 11:37:58 2014 ExecutablePath: /usr/lib/notification-daemon/notification-daemon InstallationDate: Installed on 2014-01-08 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140108) ProcCmdline: /usr/lib/notification-daemon/notification-daemon ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: notification-daemon StacktraceTop: g_source_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: notification-daemon crashed with signal 5 in g_source_remove() 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/ubuntu/+source/notification-daemon/+bug/1274181/+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 1282798] Re: [FFe] Provide a lock screen and unlock dialogs in Unity
** Changed in: unity Milestone: None = 7.2.0 -- 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/1282798 Title: [FFe] Provide a lock screen and unlock dialogs in Unity Status in Unity: In Progress Status in “unity” package in Ubuntu: Incomplete Bug description: [FFe] The merge proposal for this work missed the feature freeze dealine by a few hours and requires a freeze exception. This bug replaces the original FFe file under bug #878836. --- original description --- We need to provide a thematically compatible lock screen and unlock dialogs in Unity, consistent with the unity-greeter authentication dialog used in LightDM. This will replace gnome-screenlocker. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1282798/+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 1283238] Re: After using an app's menu item in unity panel the menu stays exposed
** Tags added: lim ** Changed in: unity Status: Triaged = 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/1283238 Title: After using an app's menu item in unity panel the menu stays exposed Status in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Bug description: Maybe intended?, though if so don't know why. Test case: With the default appearance setting of In top bar Open a document in gedit Wait for panel menu to disappear. Expose the panel menu either thru cursor or hold alt button Choose a menu item, About will be fine Close the 'about' winow, the gedit panel menu remains as long as focus is on gedit Move focus off gedit, then back on to geit, panel menu returns doesn't disappear A click or d. click in empty space on panel will cause the menu to finally disappear ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Feb 21 15:52:29 2014 InstallationDate: Installed on 2014-02-21 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283238/+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 1283238] Re: After using an app's menu item in unity panel the menu stays exposed
** Changed in: unity (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/1283238 Title: After using an app's menu item in unity panel the menu stays exposed Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Maybe intended?, though if so don't know why. Test case: With the default appearance setting of In top bar Open a document in gedit Wait for panel menu to disappear. Expose the panel menu either thru cursor or hold alt button Choose a menu item, About will be fine Close the 'about' winow, the gedit panel menu remains as long as focus is on gedit Move focus off gedit, then back on to geit, panel menu returns doesn't disappear A click or d. click in empty space on panel will cause the menu to finally disappear ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Feb 21 15:52:29 2014 InstallationDate: Installed on 2014-02-21 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283238/+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 1287798] [NEW] HUD erroneously pops up when not wanted
Public bug reported: In the last few weeks or so I've noticed the HUD on my 14.04 laptop pops up way more than it ever used to, when not wanted. I am always in an app (irssi in screen in terminator) where I press ALT+w sometimes, many times a day. Often I get the HUD popup and frantically stab escape or alt to get rid of it. I've always had it pop up in the past now and then but now it's many times a day. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,imgpng,gnomecompat,scale,workarounds,mousepoll,regex,wall,move,place,vpswitch,resize,unitymtgrabhandles,snap,session,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Tue Mar 4 16:44:03 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-06-29 (612 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-20 (43 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1287798 Title: HUD erroneously pops up when not wanted Status in “unity” package in Ubuntu: New Bug description: In the last few weeks or so I've noticed the HUD on my 14.04 laptop pops up way more than it ever used to, when not wanted. I am always in an app (irssi in screen in terminator) where I press ALT+w sometimes, many times a day. Often I get the HUD popup and frantically stab escape or alt to get rid of it. I've always had it pop up in the past now and then but now it's many times a day. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,imgpng,gnomecompat,scale,workarounds,mousepoll,regex,wall,move,place,vpswitch,resize,unitymtgrabhandles,snap,session,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Tue Mar 4 16:44:03 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-06-29 (612 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-20 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1287798/+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 900412] Re: Spread - The app title in the top left of the top bar should change as the mouse focus changes
** Changed in: unity Status: Triaged = Won't Fix ** Changed in: unity (Ubuntu) Status: Triaged = Invalid ** Changed in: ayatana-design Status: Fix Committed = Invalid -- 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/900412 Title: Spread - The app title in the top left of the top bar should change as the mouse focus changes Status in Ayatana Design: Invalid Status in Unity: Won't Fix Status in “unity” package in Ubuntu: Invalid Bug description: Spread - The app title in the top left of the top bar should change inline with mouse pointer focus changes of the spread. While on Application Spread (i.e. clicking over a launcher icon with multiple associated windows), as a user mouse-over a window, the top- bar title should reflect the window title. When the mouse is outside a window area, the title should fall-back to the application title. While on Windows Spread (i.e. pressing Super+w), should happen the same, but when the mouse is not over any window, the top-panel title should show nothing (or something like Unity desktop?). Somewhat related to bug #879888 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/900412/+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 1276352] Re: Repeatedly maximizing und restoring windows by dragging resizes them
** Changed in: unity Status: In Progress = Fix Committed -- 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/1276352 Title: Repeatedly maximizing und restoring windows by dragging resizes them Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: I'm running Ubuntu 14.04 with the new decorators from the Unity daily build PPA. The new decorator causes windows to resize when maximizing and restoring windows by dragging them to/from the panel. That doesn't happen when maximizing/restoring with keyboard shortcuts or the window controls. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140204.2-0ubuntu1 [origin: LP-PPA-ubuntu-unity-daily-build] ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Tue Feb 4 22:54:24 2014 InstallationDate: Installed on 2014-02-03 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140202) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1276352/+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 1283451] Re: window spread searchbox misplaced when using auto-hide launcher
** Summary changed: - window spread searchbox misplaced on high-dpi screen + window spread searchbox misplaced when using auto-hide launcher ** Description changed: - When the global scaling factor is set to 2, the window spread searchbox overlays the launcher (and text is small). + When using the launcher in auto-hide mode, the window spread searchbox overlays the launcher (and text is small). Expected would be that it is positioned analogue to the dash search box. - org.gnome.desktop.interface.scaling-factor = 2 - org.gnome.desktop.interface.text-scaling-factor = 1.0 - - ProblemType: Bug - DistroRelease: Ubuntu 14.04 + ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Feb 22 15:00:14 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (19 days ago) - InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) - SourcePackage: unity + InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201)SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Tags removed: hidpi -- 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/1283451 Title: window spread searchbox misplaced when using auto-hide launcher Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: When using the launcher in auto-hide mode, the window spread searchbox overlays the launcher (and text is small). Expected would be that it is positioned analogue to the dash search box. ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Feb 22 15:00:14 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (19 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201)SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283451/+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 994892] Re: Launcher - tooltips don't deal correctly with text size change
Seb, is this still wrong with recent changes? -- 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/994892 Title: Launcher - tooltips don't deal correctly with text size change Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Using unity 5.12: - open system settings - go to a11y panel, change the text size - go over the launcher, notice how the tooltip padding is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/994892/+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 918084] Re: help-overlay of unity lacks bottom decoration edge
** Changed in: unity Status: Triaged = Fix Released ** Changed in: unity (Ubuntu) Status: Triaged = 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/918084 Title: help-overlay of unity lacks bottom decoration edge Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: See the bottom edge of the help-overlay in this screenshot... http://people.canonical.com/~mmueller/help-overlay-bottom-edge-bug.png ... it's missing the decorations. Unleash the italians! :) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/918084/+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 681938] Re: Workspaces - It is possible to click on panel AppMenu menus when in workspace switcher, but they don't show
** Changed in: unity Status: Triaged = Fix Committed ** Changed in: unity Milestone: backlog = 7.2.0 ** Changed in: unity (Ubuntu) Status: Triaged = Fix Released ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Branch linked: lp:~3v1n0/unity/spreadish-scale -- 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/681938 Title: Workspaces - It is possible to click on panel AppMenu menus when in workspace switcher, but they don't show Status in Ayatana Design: Fix Committed Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: Binary package hint: unity When you are in the workspace switcher mode of Unity (on Natty) it is possible to click on the menus shown in the top panel by AppMenu. When you click on such a menu, on the panel the texture is changed to make it look like the menu is open. However, any possibly open menu that should be located underneath the menu's name is not shown; it seems to be hidden underneath the black of the workspace switcher. One possible solution could be to make Unity's launcher and panel non- interactive when the user is in the work-space switcher. However, personally I would prefer to keep the interface sensitive—as to prevent user confusion because of a seemingly frozen interface that is still there—but instead make everything work, despite the workspace switcher being displayed instead of the desktop, or open windows. --- Desired resolution: - For 12.04, when the workspace switcher is open, the word Workspace switcher should be displayed in the top bar, and there should be no associated menu items - Post 12.04 when the new spread is implemented, the title of the currently selected window should be displayed in the top bar. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/681938/+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 732653] Re: Menus are hidden by default
** No longer affects: unity-2d -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/732653 Title: Menus are hidden by default Status in Ayatana Design: Confirmed Status in Unity: Confirmed Status in “unity” package in Ubuntu: Triaged Status in “unity-2d” package in Ubuntu: Triaged Bug description: Ubuntu 11.04, Ubuntu 11.10, Ubuntu 12.04 1. Log in to Unity, and try to connect to a server: File Connect to Server. 2. Launch Firefox, and try to select an item from the Bookmarks menu. What happens: 1. The File menu, and the rest of Nautilus's menus, are hidden by default. - Unless you mouse over it, the menu bar is blank. - When you mouse over it, the menus appear. 2. The Bookmarks menu, and the rest of Firefox's menus, are hidden by default. - Unless you mouse over it, the menu bar contains only the text Firefox Web Browser, which isn't useful at all (especially, but not only, since the real name of the application -- Mozilla Firefox -- is already present in the window title bar). - When you mouse over it, the menus appear, partly but not completely replacing the previous text: Firefox W File Edit View…. What should happen: Menus should be visible by default, so that you can know that they exist without scrubbing the screen, and so that you can see where a menu is each time you aim for it. The current behavior has led some people (including, this week, one of my design colleagues) to conclude that Ubuntu applications don't have menus when they do. For example http://www.techrepublic.com/blog/opensource/gnome-shell-vs-ubuntu- unity-which-desktop-wins/2291: One of the most handy menu entries in GNOME (for me at least) is the Connect to Server entry in the Places menu. This allows the user to connect to nearly any type of server quickly and easily. The user can even connect to a Windows Share from here. In Unity - you won’t find that. In fact, you will be hard pressed to find any means to connect to a server in Ubuntu Unity. In bug 720424, Jono Bacon reported that when we did some developer tools usability testing last week and on some other occasions when I have had someone use Unity, I have noticed that some folks don't realize there is a menu there as it is not visible. This was confirmed by usability testing of Ubuntu 11.04, where 2 out of the 10 people who needed to use a menu item could not find the menus at all -- and of the 8 who did find them, 7 did so only when the window was maximized. https://lists.ubuntu.com/archives/ubuntu- desktop/2011-April/002970.html (Usability testing results of Ubuntu 11.10 or 12.04 have never been published, but this part of the design did not change.) Do not confuse this bug with bug 682788, which is about adding an option for visibility. Adding any options would not fix this bug, which is about menus being hidden *by default*. - Desired change: Implement the 'Enhanced Menu' project for 12.10. This project will address the issues described in this bug and also issues described in the duplicates of this bus. Note the 'official' bug that tracks the implementation of this project is bug #682788 The following options will be added to 'System Settings/Appearance': --- Menus Location: Global/Local Visibility: Hidden/Always displayed --- More details to follow during the 12.10 cycle... ;-) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/732653/+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 1281368] Re: Decorations: windows should have 0px (bottom and side) borders
** Changed in: unity Status: Incomplete = Triaged ** Changed in: unity (Ubuntu) Status: Incomplete = Confirmed ** Changed in: unity Milestone: None = 7.2.0 ** Changed in: unity Importance: Undecided = Medium ** Also affects: ubuntu-themes Importance: Undecided Status: New ** Changed in: ubuntu-themes Status: New = Triaged ** Changed in: ubuntu-themes Importance: Undecided = Medium ** Changed in: ubuntu-themes Assignee: (unassigned) = Jouni Helminen (jounihelminen) -- 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/1281368 Title: Decorations: windows should have 0px (bottom and side) borders Status in Ayatana Design: Fix Committed Status in Themes for Ubuntu: Triaged Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Back in 11.04 it was decided to go borderless but was reverted mainly because of unity-2d. Since then users that wish this could easily adjust in metacity-1. Now that's gone with the unity-window decorator. Dark windows look bad with the light grey? 1 px. border, particuarly some video players, gnome-terminal ect. (I understand that without a border 2 overlaping terminals may be weird but overall borderless looks better in general use Or at the least somehow color it something less obvious distracting. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140217-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Feb 17 20:37:35 2014 InstallationDate: Installed on 2014-02-17 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140217) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1281368/+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 994892] Re: Launcher - tooltips don't deal correctly with text size change
That seems fixed, thanks Marco! ** Changed in: unity (Ubuntu) Status: Triaged = Fix Released ** Changed in: unity Status: Triaged = 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/994892 Title: Launcher - tooltips don't deal correctly with text size change Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Using unity 5.12: - open system settings - go to a11y panel, change the text size - go over the launcher, notice how the tooltip padding is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/994892/+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 1282798] Re: [FFe] Provide a lock screen and unlock dialogs in Unity
@laney: you can configure it in ccsm but apparently that's not need, super-L should work out of the box for locking. We need to patch the gnome-screensaver api users though I guess (at least indicator-session and unity-settings-daemon) -- 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/1282798 Title: [FFe] Provide a lock screen and unlock dialogs in Unity Status in Unity: In Progress Status in “unity” package in Ubuntu: Incomplete Bug description: [FFe] The merge proposal for this work missed the feature freeze dealine by a few hours and requires a freeze exception. This bug replaces the original FFe file under bug #878836. --- original description --- We need to provide a thematically compatible lock screen and unlock dialogs in Unity, consistent with the unity-greeter authentication dialog used in LightDM. This will replace gnome-screenlocker. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1282798/+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 1287854] [NEW] newly created windows get progressively smaller
*** This bug is a duplicate of bug 1287472 *** https://bugs.launchpad.net/bugs/1287472 Public bug reported: Since I dist-upgraded this morning, newly created windows get progressively smaller. Steps to reproduce: 1- Click middle button on firefox in launcher repeatedly 2- Notice Firefox windows are opening at a smaller and smaller size Not sure if this was caused by which of the following: compiz 1:0.9.11+14.04.20140303-0ubuntu1 unity 7.1.2+14.04.20140303-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 4 13:52:10 2014 InstallationDate: Installed on 2013-11-26 (97 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-17 (45 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1287854 Title: newly created windows get progressively smaller Status in “unity” package in Ubuntu: New Bug description: Since I dist-upgraded this morning, newly created windows get progressively smaller. Steps to reproduce: 1- Click middle button on firefox in launcher repeatedly 2- Notice Firefox windows are opening at a smaller and smaller size Not sure if this was caused by which of the following: compiz 1:0.9.11+14.04.20140303-0ubuntu1 unity 7.1.2+14.04.20140303-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 4 13:52:10 2014 InstallationDate: Installed on 2013-11-26 (97 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-17 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1287854/+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 1287853] [NEW] [regression] Failing Tooltip/Quicklist Autopilot tests with Unity package version 7.1.2+14.04.20140303-0ubuntu1
Public bug reported: With Unity package version 7.1.2+14.04.20140303-0ubuntu1, 6 new Autopilot failures occur around Quicklists and Tooltips. These are: unity.tests.test_quicklist.QuicklistActionTests.test_quicklist_action_uses_startup_notification unity.tests.test_spread.SpreadTests.test_spread_hides_icon_tooltip unity.tests.launcher.test_icon_behavior.LauncherIconsTests.test_bfb_tooltip_disappear_when_dash_is_opened unity.tests.test_quicklist.QuicklistActionTests.test_right_click_opens_quicklist_if_already_open unity.tests.launcher.test_tooltips.LauncherTooltipTests.test_launcher_tooltip_show unity.tests.test_quicklist.QuicklistActionTests.test_right_clicking_same_icon_doesnt_reopen_ql ** Affects: unity Importance: High Status: Triaged ** Affects: unity (Ubuntu) Importance: High Status: Triaged ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity Importance: Undecided = High ** Changed in: unity (Ubuntu) Importance: Undecided = High ** Changed in: unity Status: New = Triaged ** Changed in: unity (Ubuntu) Status: New = Triaged -- 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/1287853 Title: [regression] Failing Tooltip/Quicklist Autopilot tests with Unity package version 7.1.2+14.04.20140303-0ubuntu1 Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: With Unity package version 7.1.2+14.04.20140303-0ubuntu1, 6 new Autopilot failures occur around Quicklists and Tooltips. These are: unity.tests.test_quicklist.QuicklistActionTests.test_quicklist_action_uses_startup_notification unity.tests.test_spread.SpreadTests.test_spread_hides_icon_tooltip unity.tests.launcher.test_icon_behavior.LauncherIconsTests.test_bfb_tooltip_disappear_when_dash_is_opened unity.tests.test_quicklist.QuicklistActionTests.test_right_click_opens_quicklist_if_already_open unity.tests.launcher.test_tooltips.LauncherTooltipTests.test_launcher_tooltip_show unity.tests.test_quicklist.QuicklistActionTests.test_right_clicking_same_icon_doesnt_reopen_ql To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1287853/+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 1287854] Re: newly created windows get progressively smaller
*** This bug is a duplicate of bug 1287472 *** https://bugs.launchpad.net/bugs/1287472 ** This bug has been marked a duplicate of bug 1287472 compiz unnecessarily shrinks new windows -- 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/1287854 Title: newly created windows get progressively smaller Status in “unity” package in Ubuntu: New Bug description: Since I dist-upgraded this morning, newly created windows get progressively smaller. Steps to reproduce: 1- Click middle button on firefox in launcher repeatedly 2- Notice Firefox windows are opening at a smaller and smaller size Not sure if this was caused by which of the following: compiz 1:0.9.11+14.04.20140303-0ubuntu1 unity 7.1.2+14.04.20140303-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 4 13:52:10 2014 InstallationDate: Installed on 2013-11-26 (97 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-17 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1287854/+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 1287853] Re: [regression] Failing Tooltip/Quicklist Autopilot tests with Unity package version 7.1.2+14.04.20140303-0ubuntu1
Failing tests ** Attachment added: Falcon_04.03.14-112534.log https://bugs.launchpad.net/unity/+bug/1287853/+attachment/4007044/+files/Falcon_04.03.14-112534.log -- 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/1287853 Title: [regression] Failing Tooltip/Quicklist Autopilot tests with Unity package version 7.1.2+14.04.20140303-0ubuntu1 Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: With Unity package version 7.1.2+14.04.20140303-0ubuntu1, 6 new Autopilot failures occur around Quicklists and Tooltips. These are: unity.tests.test_quicklist.QuicklistActionTests.test_quicklist_action_uses_startup_notification unity.tests.test_spread.SpreadTests.test_spread_hides_icon_tooltip unity.tests.launcher.test_icon_behavior.LauncherIconsTests.test_bfb_tooltip_disappear_when_dash_is_opened unity.tests.test_quicklist.QuicklistActionTests.test_right_click_opens_quicklist_if_already_open unity.tests.launcher.test_tooltips.LauncherTooltipTests.test_launcher_tooltip_show unity.tests.test_quicklist.QuicklistActionTests.test_right_clicking_same_icon_doesnt_reopen_ql To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1287853/+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 1208019] Re: Eclipse menus doesn't show up in Saucy
have the same problem. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in Eclipse: Confirmed Status in Unity GTK+ module: Confirmed Status in “oracle-jdk7-installer” package in Ubuntu: Triaged Status in “unity-gtk-module” package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify /usr/share/applications/eclipse.desktop to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1208019/+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 951496] Re: indicator-datetime-session severely leaks memory
*** This bug is a duplicate of bug 829967 ***
https://bugs.launchpad.net/bugs/829967
** This bug has been marked a duplicate of bug 829967
indicator-datetime leaks memory
--
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/951496
Title:
indicator-datetime-session severely leaks memory
Status in The Date and Time Indicator:
Invalid
Status in “geoclue” package in Ubuntu:
Fix Released
Status in “indicator-datetime” package in Ubuntu:
Incomplete
Bug description:
After the most recent update to 0.3.91-0ubuntu1, indicator-datetime-session's
memory increases at a rate of ~5MB/s, rendering my system unusable in a couple
of minutes. Any advice on how to debug this issue? The service is always
respawned after I kill it, making it impossible to directly run it in a
terminal -- is there a way to prevent that? The issue persists even if I switch
off the date display in the indicator bar. If I do an strace to the running
process, the following seems to be repeated in an infinite loop:
open(/usr/share/zoneinfo/Europe/Paris, O_RDONLY) = 14
fstat(14, {st_mode=S_IFREG|0644, st_size=2945, ...}) = 0
mmap(NULL, 2945, PROT_READ, MAP_PRIVATE, 14, 0) = 0x7fd1a6bd9000
close(14) = 0
munmap(0x7fd1a6bd9000, 2945)= 0
open(/usr/share/zoneinfo/UTC, O_RDONLY) = 14
fstat(14, {st_mode=S_IFREG|0644, st_size=118, ...}) = 0
mmap(NULL, 118, PROT_READ, MAP_PRIVATE, 14, 0) = 0x7fd1a6bd9000
close(14) = 0
munmap(0x7fd1a6bd9000, 118) = 0
open(/usr/share/zoneinfo/Europe/Paris, O_RDONLY) = 14
fstat(14, {st_mode=S_IFREG|0644, st_size=2945, ...}) = 0
mmap(NULL, 2945, PROT_READ, MAP_PRIVATE, 14, 0) = 0x7fd1a6bd9000
close(14) = 0
munmap(0x7fd1a6bd9000, 2945)= 0
open(/usr/share/zoneinfo/America/Los_Angeles, O_RDONLY) = 15
fstat(15, {st_mode=S_IFREG|0644, st_size=2819, ...}) = 0
mmap(NULL, 2819, PROT_READ, MAP_PRIVATE, 15, 0) = 0x7fd1a6bd9000
close(15) = 0
munmap(0x7fd1a6bd9000, 2819)= 0
poll([{fd=3, events=POLLIN}, {fd=10, events=POLLIN}, {fd=12, events=POLLIN},
{fd=11, events=POLLIN}], 4, 0) = 2 ([{fd=3, revents=POLLIN}, {fd=11,
revents=POLLIN}])
read(3, \1\0\0\0\0\0\0\0, 16) = 8
sendmsg(11, {msg_name(0)=NULL,
msg_iov(2)=[{l\1\0\1\0\0\0\\r\4\0\225\0\0\0\1\1o\0(\0\0\0/org/fre...,
168}, {, 0}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 168
sendmsg(11, {msg_name(0)=NULL,
msg_iov(2)=[{l\1\0\1\0\0\0\0001\r\4\0\233\0\0\0\1\1o\0(\0\0\0/org/fre...,
176}, {, 0}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 176
write(3, \1\0\0\0\0\0\0\0, 8) = 8
recvmsg(11, {msg_name(0)=NULL,
msg_iov(1)=[{l\4\1\1\35\0\0\0F\336b\1\247\0\0\0\1\1o\0(\0\0\0/org/fre...,
2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 325
write(3, \1\0\0\0\0\0\0\0, 8) = 8
write(3, \1\0\0\0\0\0\0\0, 8) = 8
write(3, \1\0\0\0\0\0\0\0, 8) = 8
recvmsg(11, {msg_name(0)=NULL,
msg_iov(1)=[{l\3\1\1:\0\0\0I\336b\1w\0\0\0\6\1s\0\6\0\0\0:1.354\0\0...,
2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 194
write(3, \1\0\0\0\0\0\0\0, 8) = 8
recvmsg(11, 0x7fff9e33d3d0, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource
temporarily unavailable)
write(3, \1\0\0\0\0\0\0\0, 8) = 8
poll([{fd=3, events=POLLIN}, {fd=10, events=POLLIN}, {fd=12, events=POLLIN},
{fd=11, events=POLLIN}], 4, 0) = 1 ([{fd=3, revents=POLLIN}])
read(3, \6\0\0\0\0\0\0\0, 16) = 8
poll([{fd=3, events=POLLIN}, {fd=10, events=POLLIN}, {fd=12, events=POLLIN},
{fd=11, events=POLLIN}], 4, 0) = 0 (Timeout)
read(3, 0x7fff9e33d5d0, 16) = -1 EAGAIN (Resource temporarily
unavailable)
write(2, \nIndicator-Datetime-WARNING **: ..., 117) = 117
poll([{fd=3, events=POLLIN}, {fd=10, events=POLLIN}, {fd=12, events=POLLIN},
{fd=11, events=POLLIN}], 4, 0) = 0 (Timeout)
read(3, 0x7fff9e33d5d0, 16) = -1 EAGAIN (Resource temporarily
unavailable)
write(2, \nIndicator-Datetime-WARNING **: ..., 72) = 72
sendmsg(11, {msg_name(0)=NULL,
msg_iov(2)=[{l\1\0\1\0\0\0\0002\r\4\0\215\0\0\0\1\1o\0(\0\0\0/org/fre...,
160}, {, 0}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 160
write(8, \1\0\0\0\0\0\0\0, 8) = 8
write(7, \1\0\0\0\0\0\0\0, 8) = 8
futex(0x7fd1a000b780, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7fd1a000b2e0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x20e7e00, FUTEX_WAKE_PRIVATE, 1) = 1
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: indicator-datetime 0.3.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CheckboxSubmission: 476acdb7217a83354f628beaa5c14f06
[Dx-packages] [Bug 1287850] [NEW] Time and Date settings... button does not work
Public bug reported: steps On flo 1. Pull down the date/time indicator 2. Click Time Date settings... Result: nothing happens Expected: Settings panel is launched ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- 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/1287850 Title: Time and Date settings... button does not work Status in “indicator-datetime” package in Ubuntu: New Bug description: steps On flo 1. Pull down the date/time indicator 2. Click Time Date settings... Result: nothing happens Expected: Settings panel is launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1287850/+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 829648] Re: [ffe] No easy way to turn the sound menu on/off
** Changed in: unity-control-center (Ubuntu) Importance: Undecided = Medium -- 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/829648 Title: [ffe] No easy way to turn the sound menu on/off Status in Sound Menu: In Progress Status in “indicator-sound” package in Ubuntu: In Progress Status in “unity-control-center” package in Ubuntu: In Progress Bug description: indicator-sound 0.7.6-0ubuntu1, Ubuntu Ocelot 1. Try to work out how to hide the sound menu. What happens: There's no obvious way to do it (short of uninstalling the package). What should happen: At the bottom left corner of the System Settings “Sound” panel should be a checkbox, “Show sound volume in the menu bar”. It should be checked by default for a new user account. Whenever it is checked, the sound menu should be present in the menu bar. https://wiki.ubuntu.com/SoundMenu#presence [Reported by Eustace in http://www.omgubuntu.co.uk/2011/08/power- cog-icon-oneiric/#comment-291049247.] To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/829648/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
** Project changed: unity-control-center = unity-control-center (Ubuntu) ** Changed in: unity-control-center (Ubuntu) Importance: Undecided = Low -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Invalid Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: In Progress Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1252942] Re: Time and Date Settings does not respond when adding second location and closes
** Project changed: unity-control-center = unity-control-center (Ubuntu) ** Changed in: unity-control-center (Ubuntu) Status: New = Triaged ** Changed in: unity-control-center (Ubuntu) Importance: Undecided = Medium ** No longer affects: 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/1252942 Title: Time and Date Settings does not respond when adding second location and closes Status in “unity-control-center” package in Ubuntu: Triaged Bug description: OS info Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy Kernel : 3.11.0-13-generic Settings enabled : In Time and Date Settings, I have the following settings enabled : Time : 'Automatically from the Internet ' Clock : 'Show a clock in the menu bar' 'Weekday' 'Date and month' 'Seconds' '12-hour time' 'Monthly calendar' 'Time in other locations' When I encounter the bug: 1. Click on Choose Locations for 'Time in other locations' 2. Click on '+' (Add) twice --- Results in Nonresponsiveness and Abnormal Termination of Time Date Settings (OR) 2. Add a location. 3. Adding a second location --- Results in Nonresponsiveness and Abnormal Termination of Time Date Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1252942/+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 1283171] Re: Visual corruption on window buttons
** Changed in: unity (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 unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1283171 Title: Visual corruption on window buttons Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: My window buttons have corruption... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,imgpng,gnomecompat,scale,workarounds,mousepoll,regex,wall,move,place,vpswitch,resize,unitymtgrabhandles,snap,session,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Fri Feb 21 18:51:40 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-06-29 (601 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-20 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283171/+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 1283448] Re: resizing loop on high-dpi screen
I must have forgotten the video that illustrates the issue. It is happening with other dialog boxes in other applications as well, although I don't know to which package/component the bug belongs. ** Attachment added: dconf-infinite-resizing-loop.ogg https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1283448/+attachment/4007352/+files/dconf-infinite-resizing-loop.ogg -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1283448 Title: resizing loop on high-dpi screen Status in “d-conf” package in Ubuntu: New Bug description: When the global scaling factor is set to 2, dconf-editor occasionally starts changing its window size causing very high CPU activity. This occurs for example while searching: It appears dconf-editor tries to adjust the window dimensions to the size of the content. It also happens when (then) resizing the window afterwards, it tries to revert to the previous window size. This causes very high CPU activity and freezes the window content. This does not happen when the global scaling factor is set to 1. It could be related to the new window resizing method that updates the window content. org.gnome.desktop.interface.scaling-factor = 2 org.gnome.desktop.interface.text-scaling-factor = 1.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dconf-editor 0.19.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 22 14:31:11 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (19 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: d-conf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1283448/+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 1256590] Re: J. Random User Showing In Unity Power Menu Indicator
Just got hit by this, 13.10 fully updated. Guest session has been
recently used by family members, though has also been used before too
and haven't seen this before.
There is nothing strange in /etc/passwd afaik and this user is not
visible in User settings.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to ido in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1256590
Title:
J. Random User Showing In Unity Power Menu Indicator
Status in “ido” package in Ubuntu:
Confirmed
Bug description:
Yesterday I encountered an issue that was very concerning, at least
until I investigated a bit more, and found that it may only be due to
debug/test code that's still be present in released software. The
search I made brought me here. Please redirect me if I'm in the wrong
place.
J. Random User appeared in the Ubuntu 13.10 (x86_64) Unity Power
indicator list, below 'Lock' and above '{my user name}'.
This was only noticed as I was about to lock the screen, which I do a
number of times per day, however, this time J. Random User was
visible.
There was no User Account for that entry in System Settings User Accounts.
There was no one else logged onto the machine except my own username (checked
by '$ w').
There seemed to be no rogue processes running (checked in log and current
processes).
From a security point of view, it was very concerning. But after my
searches on the matter, I belive the machine not to be compromised,
but tickled by 'developer test code'.
Restarting the computer removed the issue.
It could be coincidence, but the only bit of new software I tried (for
the first time ever) was the Remmina Remote Desktop Client to see if
was interested to remotely connect to another computer on the home
network. After restarting my computer and running that software again,
it did not cause a J. Random User to appear in the indicator, so it
could be a red-herring.
It could also be related to this? :
https://code.launchpad.net/~larsu/ido/custom-menu-items/+merge/165498
Hope you know something about it, or can redirect this bug report
elsewhere.
Thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1256590/+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 1287934] [NEW] Menu present on both window and panel.
Public bug reported: Intermittent and erratic behaviour from window menus, behaviour set to show on top panel but are shown in both panel and window as per screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 4 21:41:06 2014 InstallationDate: Installed on 2013-12-29 (64 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131229) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: Screenshot from 2014-03-04 21:47:54.jpg https://bugs.launchpad.net/bugs/1287934/+attachment/4007400/+files/Screenshot%20from%202014-03-04%2021%3A47%3A54.jpg -- 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/1287934 Title: Menu present on both window and panel. Status in “unity” package in Ubuntu: New Bug description: Intermittent and erratic behaviour from window menus, behaviour set to show on top panel but are shown in both panel and window as per screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 4 21:41:06 2014 InstallationDate: Installed on 2013-12-29 (64 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131229) 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/1287934/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
This is the full list of API changes for gnome-desktop, keep in mind that most of these were moved into display-config (and/or made redundant by those changes). There are no rdepends in the archive that use any of these (apart from g-s-d/g-c-c and u-s-d/u-c-c which already have patches prepared on this FFe) Removed: gnome_rr_screen_set_size gnome_rr_screen_get_timestamps gnome_rr_screen_set_primary_output gnome_rr_output_is_connected gnome_rr_output_get_backlight_min gnome_rr_output_get_backlight_max gnome_rr_output_get_size_inches gnome_rr_crtc_set_config_with_time gnome_rr_output_get_connector_type gnome_rr_config_save gnome_rr_config_apply_from_filename_with_time gnome_rr_config_apply_with_time gnome_rr_config_get_backup_filename gnome_rr_config_get_intended_filename gnome_rr_config_load_filename gnome_rr_config_new_stored Changed: gnome_rr_output_is_laptop - gnome_rr_output_is_builtin_display gnome_rr_output_get_backlight (remove gerror param) gnome_rr_output_get_ids_from_edid (type changes for some params) gnome_rr_output_get_width_mm - gnome_rr_output_get_physical_size gnome_rr_output_get_height_mm - gnome_rr_output_get_physical_sizels gnome_idle_monitor_new_for_device (adds gerror) -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Invalid Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: In Progress Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1287853] Re: [regression] Failing Tooltip/Quicklist Autopilot tests with Unity package version 7.1.2+14.04.20140303-0ubuntu1
** Changed in: unity Assignee: (unassigned) = Brandon Schaefer (brandontschaefer) ** Changed in: unity (Ubuntu) Status: Triaged = Confirmed ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Brandon Schaefer (brandontschaefer) ** Changed in: unity (Ubuntu) Status: Confirmed = In Progress ** Changed in: unity Status: Triaged = In Progress ** Branch linked: lp:~brandontschaefer/unity/lp.1287853-fix -- 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/1287853 Title: [regression] Failing Tooltip/Quicklist Autopilot tests with Unity package version 7.1.2+14.04.20140303-0ubuntu1 Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: With Unity package version 7.1.2+14.04.20140303-0ubuntu1, 6 new Autopilot failures occur around Quicklists and Tooltips. These are: unity.tests.test_quicklist.QuicklistActionTests.test_quicklist_action_uses_startup_notification unity.tests.test_spread.SpreadTests.test_spread_hides_icon_tooltip unity.tests.launcher.test_icon_behavior.LauncherIconsTests.test_bfb_tooltip_disappear_when_dash_is_opened unity.tests.test_quicklist.QuicklistActionTests.test_right_click_opens_quicklist_if_already_open unity.tests.launcher.test_tooltips.LauncherTooltipTests.test_launcher_tooltip_show unity.tests.test_quicklist.QuicklistActionTests.test_right_clicking_same_icon_doesnt_reopen_ql To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1287853/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage
I had the same issue... turned out to be an issue with my mouse. I have a Microsoft Sculpt Keyboard + accompanying mouse and a RAT7. The MS mouse was turned off... the RAT 7 was plugged in. O tried for two days to stablize everyhting Ubuntu 13.10, 14.04, 12.0, Suse... problem was reoccuring and because everybody was suspecting an issue with X-server i never bother unplugging the RAT7. Now that I did. Everything works perfectly. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: Fix Committed Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Released Status in “indicator-appmenu” source package in Saucy: Fix Released Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 1288028] [NEW] [regression] Clicking on unity's panel does not raise a maximized window
Public bug reported: With one maximized window below an unmaximized window, clicking on the Unity panel (with the maximized window focused) does not raise the maximized window. This happens with both focus-follows-mouse and focus- follows-click, although the latter is harder to trigger with normal usage. Steps to reproduce (with focus follows mouse): 1. Open two windows. Maximize one (let's call this A), and leave one unmaximized (let's call this B). 2. Raise window B so that B is in front of A. 3. Move mouse over window A to focus it. 4. Move mouse up to the unity panel while keeping window A focused. 5. Click on an empty space in the panel. Observed behaviour: window A is not raised to the top, but it should. This used to work in Ubuntu 13.10, and 13.04, iirc. This bug also occurs with focus-follows-click: Steps to reproduce (with focus follows click): 1. Open two windows. Maximize one (let's call this A), and leave one unmaximized (let's call this B). 2. Raise window B so that B is in front of A. 3. Alt+RightClick on window B to bring up the window's context menu and enable the Always on top option. 4. Click on window A to focus it. Window B should remain in front of window A. 5. Alt+RightClick on window B to bring up the window's context menu, and disable the Always on top option. Window A should remain focused after this action. 6. Click on an empty space in the panel. Observed behaviour: Window A is not raised to the top, but it should. I'm not sure if this worked in previous releases. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140228-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell] CurrentDesktop: Unity Date: Wed Mar 5 10:36:21 2014 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-03 (1 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug regression-release trusty ** Tags added: regression-release -- 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/1288028 Title: [regression] Clicking on unity's panel does not raise a maximized window Status in “unity” package in Ubuntu: New Bug description: With one maximized window below an unmaximized window, clicking on the Unity panel (with the maximized window focused) does not raise the maximized window. This happens with both focus-follows-mouse and focus-follows-click, although the latter is harder to trigger with normal usage. Steps to reproduce (with focus follows mouse): 1. Open two windows. Maximize one (let's call this A), and leave one unmaximized (let's call this B). 2. Raise window B so that B is in front of A. 3. Move mouse over window A to focus it. 4. Move mouse up to the unity panel while keeping window A focused. 5. Click on an empty space in the panel. Observed behaviour: window A is not raised to the top, but it should. This used to work in Ubuntu 13.10, and 13.04, iirc. This bug also occurs with focus-follows-click: Steps to reproduce (with focus follows click): 1. Open two windows. Maximize one (let's call this A), and leave one unmaximized (let's call this B). 2. Raise window B so that B is in front of A. 3. Alt+RightClick on window B to bring up the window's context menu and enable the Always on top option. 4. Click on window A to focus it. Window B should remain in front of window A. 5. Alt+RightClick on window B to bring up the window's context menu, and disable the Always on top option. Window A should remain focused after this action. 6. Click on an empty space in the panel. Observed behaviour: Window A is not raised to the top, but it should. I'm not sure if this worked in previous releases. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140228-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell] CurrentDesktop: Unity Date: Wed Mar 5 10:36:21 2014 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-03 (1 days ago) To manage notifications about this bug go
[Dx-packages] [Bug 1234458] Re: Indicator stuck on mouse icon, along with estimating...
** Branch linked: lp:~charlesk/indicator-power/lp-1234458 -- 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/1234458 Title: Indicator stuck on mouse icon, along with estimating... Status in One Hundred Papercuts: Triaged Status in The Power Indicator: Triaged Status in “indicator-power” package in Ubuntu: Triaged Bug description: indicator-power 12.10.6+13.10.20130918.2-0ubuntu1, Ubuntu 13.10 My power indicator is stuck on the mouse icon. When I click on it, it says Mouse (estimating). Why is it stuck on estimating? Why show the icon at all if I'm using a Logitech mouse with a battery? https://wiki.ubuntu.com/Power#time-presentation: The brief time-remaining string for a component should be: * the time remaining for it to empty or fully charge, if estimable, in H:MM format; otherwise * 'estimating…' if the time remaining has been inestimable for less than 30 seconds; otherwise * 'unknown' if the time remaining has been inestimable for between 30 seconds and one minute; otherwise * the empty string. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1234458/+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 1288100] [NEW] compiz crashed with SIGSEGV in FT_Load_Glyph()
Public bug reported: maybe skype ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 5 11:30:57 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-02-09 (24 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140208) ProcCmdline: compiz ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=ru_RU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f15826be7e0: mov%rdx,0x10(%rax) PC (0x7f15826be7e0) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace trusty ** Information type changed from Private to Public -- 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/1288100 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() Status in “unity” package in Ubuntu: New Bug description: maybe skype ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 5 11:30:57 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-02-09 (24 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140208) ProcCmdline: compiz ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=ru_RU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f15826be7e0:mov%rdx,0x10(%rax) PC (0x7f15826be7e0) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() 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/ubuntu/+source/unity/+bug/1288100/+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
