[Dx-packages] [Bug 406626] Invitation to connect on LinkedIn
LinkedIn Bug, I'd like to add you to my professional network on LinkedIn. - Sajithmohan Sajithmohan VK Software Engineer at Innoz Technologies Pvt.Ltd Payyannur Area, India Confirm that you know Sajithmohan VK: https://www.linkedin.com/e/-t0m7y8-hoxxuysm-1q/isd/18549885231/lGN7m6kq/?hs=false&tok=1ukghBDQI1CC01 -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/-t0m7y8-hoxxuysm-1q/zr0b4Glh7dla4LItFgDR-PxhKIE7Q1zLvr0VI-q/goo/406626%40bugs%2Elaunchpad%2Enet/20061/I6059162397_1/?hs=false&tok=1d6e6J28A1CC01 (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. -- 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/406626 Title: Deleted Items Folder inconsistently named in en_GB localisation Status in The Gnome Panel Applets: Fix Released Status in GNOME Common Scripts: Expired Status in Gnome Documentation Project: Expired Status in GVFS: Fix Released Status in One Hundred Papercuts: Fix Released Status in Nautilus: Fix Released Status in Ubuntu Manual: Fix Released Status in Ubuntu Translations: Fix Released Status in “gnome-applets” package in Ubuntu: Fix Released Status in “transmission” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: # This bug has been fixed and closed. - If you find more applications where the Trash has not been renamed to Rubbish bin, in en_GB, Kindly refrain from adding the bug task here. Instead, open NEW bug reports(With a mention of this bug number). # The deleted items folder is inconsistently named and is referred to as both Wastebasket and Deleted items, Ubuntu offers to 'Empty Deleted Items' but the window is headed Wastebasket. The URL to deleted items is also trash:/// in nautilus but this is possibly a seperate issue. An effect of this can be seen in #115661 also. This could confuse new users and it should be a simple enough fix simply changing strings, so I believe it is a papercut. - from the Doc Team: the recommended term is now "Rubbish Bin"! - To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-applets/+bug/406626/+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 1243069] Re: Launcher does not reveal when autohide is on
I am also having the same issue. I am on Ubuntu 13.04 32 bit. With auto hide enable my launcher never reveals itself(with any type of mouse movement to the left of the screen) unless I press the super key. Config Processor: Intel® Core™ i5 CPU M 480 @ 2.67GHz × 4 Graphics: Gallium 0.4 on AMD RV730 CCSM 0.9.10.2 I tried the various solutions provided on askubuntu and ubuntuforums but no use till now. -- 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/1243069 Title: Launcher does not reveal when autohide is on Status in “unity” package in Ubuntu: Confirmed Bug description: I use a dual screen setup and autohide with the launcher on the left. After the 13.10 upgrade the autohide feature is broken : - The launcher does not reveal anymore with the mouse (it reveals with the keyboard shortcut). - I can't move the mouse to the second monitor : the cursor is stuck on the right border of the left monitor. If I move the mouse top right and move fast I can pass to the second monitor) I tried different settings in ccsm in vain. I could not find any similar issues report except this one : http://askubuntu.com/questions/363205/13-10-auto-hidelauncher-breaks- multiple-monitor-setup ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,regex,place,move,gnomecompat,imgpng,grid,resize,mousepoll,session,vpswitch,snap,animation,workarounds,expo,wall,ezoom,staticswitcher,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 22 09:19:09 2013 DistUpgraded: 2013-10-18 12:53:39,653 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.16, 3.11.0-12-generic, x86_64: installed virtualbox, 4.2.16, 3.8.0-31-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 6350 [1028:2126] InstallationDate: Installed on 2011-06-08 (866 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MachineType: Dell Inc. OptiPlex 990 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=c4c9bb00-bea9-47e8-9175-82937fe761ef ro radeon.agpmode=-1 quiet splash i915.semaphores=1 vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-10-18 (3 days ago) dmi.bios.date: 11/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/24/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 3:1.12.4+git20121105-makson1~ppa2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 2:2.7.3+git20120928~quantal2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 2:6.14.6+git20120928~quantal1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 3:2.20.8+git20120928~quantal2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 2:1.0.2+git20120928~quantal1 xserver.bootTime: Mon Oct 21 15:19:46 2013 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputUSB Optical MouseMOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 3:1.12.4+git20121105-makson1~ppa2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1243069/+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 1258863] Re: Indicators should still provide xdg autostart & dbus
** Branch linked: lp:~xnox/indicator-sound/unbreak-ubiquity -- 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/1258863 Title: Indicators should still provide xdg autostart & dbus Status in Sound Menu: Confirmed Status in “indicator-sound” package in Ubuntu: Confirmed Bug description: In bug #1185565, indicators are dropping xdg autostart files & dbus activation files. This breaks sessions which are not managed by upstart. One can have the best of the both worlds. Under upstart user-sessions, /usr/share/upstart/xdg/ is added to XDG_CONFIG_DIRS, thus one can place an override autostart/indicator-$foo.desktop file there which declares "Hidden=true" and thus under upstart managed session the xdg-autostart file will be ingored. Similarly dbus file is re-introduced, as to allow for dbus activation of the indicators. Patch to follow. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1258863/+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 1258863] Re: Indicators should still provide xdg autostart & dbus
at the moment indicator-sound is broken in ubiquity installer. ** Changed in: indicator-sound Status: New => Confirmed ** Also affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-sound (Ubuntu) Status: New => Confirmed ** Changed in: indicator-sound (Ubuntu) Importance: Undecided => High -- 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/1258863 Title: Indicators should still provide xdg autostart & dbus Status in Sound Menu: Confirmed Status in “indicator-sound” package in Ubuntu: Confirmed Bug description: In bug #1185565, indicators are dropping xdg autostart files & dbus activation files. This breaks sessions which are not managed by upstart. One can have the best of the both worlds. Under upstart user-sessions, /usr/share/upstart/xdg/ is added to XDG_CONFIG_DIRS, thus one can place an override autostart/indicator-$foo.desktop file there which declares "Hidden=true" and thus under upstart managed session the xdg-autostart file will be ingored. Similarly dbus file is re-introduced, as to allow for dbus activation of the indicators. Patch to follow. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1258863/+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 1185565] Re: Indicators should have Upstart jobs
given how similar all the indicators are, i'm not sure why there is a unique job for each one: instance $INDICATOR export INDICATOR start on indicators-loaded or indicator-services-start stop on desktop-end or indicator-services-end respawn exec /usr/lib/x86_64-linux-gnu/indicator-$INDICATOR/indicator-$INDICATOR-service and then something else, e.g. can decide which indicators are wanted and simply do: start indicator INDICATOR=sound Such that to avoid boilerplate indicator-*.conf jobs. Each instance can individually be stopped, startered, restarted and gets it's own log file Similarly there is upstart-dbus-bridge, such that instead the indicators can do "start on dbus INTERFACE=com.ubuntu.foo", so I don't think removing dbus activation gains us anything, so far it only broke showing indicators in the ubiquity-dm and non-upstart mananged user-sessions where indicators can be used. At the moment, all user sessions on the desktop can be fully started without being managed by upstart and users can disable that. -- 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, dx-packages, dx-packages, dx-packages https://bugs.launchpad.net/bugs/1185565 Title: Indicators should have Upstart jobs Status in Application Indicators: Fix Committed Status in The Date and Time Indicator: Fix Committed Status in Indicator Location: Fix Committed Status in Network Menu: Fix Released Status in The Power Indicator: Fix Committed Status in The Session Menu: Fix Committed Status in Sound Menu: Fix Committed Status in The Sync Menu: Fix Committed Status in Libindicator: Confirmed Status in Unity: Fix Released Status in “indicator-application” package in Ubuntu: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-power” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “indicator-sync” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: In Progress Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: Indicators should move over to using the upstart jobs to get better logging and management of their processes. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1185565/+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 1185565] Re: Indicators should have Upstart jobs
I agree with larsu on this one. Can we revert this? Or instead e.g. fix it properly - rebase upstart-dbus activation patches and still use dbus activation. -- 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, dx-packages, dx-packages, dx-packages https://bugs.launchpad.net/bugs/1185565 Title: Indicators should have Upstart jobs Status in Application Indicators: Fix Committed Status in The Date and Time Indicator: Fix Committed Status in Indicator Location: Fix Committed Status in Network Menu: Fix Released Status in The Power Indicator: Fix Committed Status in The Session Menu: Fix Committed Status in Sound Menu: Fix Committed Status in The Sync Menu: Fix Committed Status in Libindicator: Confirmed Status in Unity: Fix Released Status in “indicator-application” package in Ubuntu: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-power” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “indicator-sync” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: In Progress Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: Indicators should move over to using the upstart jobs to get better logging and management of their processes. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1185565/+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 1243069] Re: Launcher does not reveal when autohide is on
Same as initial report. With launcher auto-hide enabled, I can get to and from the second monitor only by moving the mouse quickly across the area covered by the panel and _maybe_ the bottom edge of the screen. I'm a little surprised this isn't more widely reported.I'm also using the radeon driver ? Does it only affect people using 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/1243069 Title: Launcher does not reveal when autohide is on Status in “unity” package in Ubuntu: Confirmed Bug description: I use a dual screen setup and autohide with the launcher on the left. After the 13.10 upgrade the autohide feature is broken : - The launcher does not reveal anymore with the mouse (it reveals with the keyboard shortcut). - I can't move the mouse to the second monitor : the cursor is stuck on the right border of the left monitor. If I move the mouse top right and move fast I can pass to the second monitor) I tried different settings in ccsm in vain. I could not find any similar issues report except this one : http://askubuntu.com/questions/363205/13-10-auto-hidelauncher-breaks- multiple-monitor-setup ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,regex,place,move,gnomecompat,imgpng,grid,resize,mousepoll,session,vpswitch,snap,animation,workarounds,expo,wall,ezoom,staticswitcher,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 22 09:19:09 2013 DistUpgraded: 2013-10-18 12:53:39,653 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.16, 3.11.0-12-generic, x86_64: installed virtualbox, 4.2.16, 3.8.0-31-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 6350 [1028:2126] InstallationDate: Installed on 2011-06-08 (866 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MachineType: Dell Inc. OptiPlex 990 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=c4c9bb00-bea9-47e8-9175-82937fe761ef ro radeon.agpmode=-1 quiet splash i915.semaphores=1 vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-10-18 (3 days ago) dmi.bios.date: 11/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/24/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 3:1.12.4+git20121105-makson1~ppa2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 2:2.7.3+git20120928~quantal2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 2:6.14.6+git20120928~quantal1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 3:2.20.8+git20120928~quantal2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 2:1.0.2+git20120928~quantal1 xserver.bootTime: Mon Oct 21 15:19:46 2013 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputUSB Optical MouseMOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 3:1.12.4+git20121105-makson1~ppa2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1243069/+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 968533] Re: Alt-tab to Firefox sends Firefox to 100% CPU; unity-panel-service to 80% CPU and hud-service to 20-80% CPU
@xavier: I agree the bugs are similar, but they are not the same and we need to be sure both are fixed. See comment #24. -- 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/968533 Title: Alt-tab to Firefox sends Firefox to 100% CPU; unity-panel-service to 80% CPU and hud-service to 20-80% CPU Status in Unity: Confirmed Status in “indicator-appmenu” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I've been seeing UI hangs after switching tabs in Firefox, and switching from other applications to Firefox. It can take 3-8 seconds to change *tab*. During this time the CPU is maxed out; typical output from 'top' during this period shows 'hud- service' and 'unity-panel-service' combined using about the same CPU as Firefox itself: 100 10.4 26:07.73 firefox 53 0.6 6:14.86 hud-service 38 1.5 6:42.14 unity-panel-service I suspect that the change is causing a (an inefficient) re-index related to updated menu structures. (Eg. something like the history menu, although I can't see what it is as don't currently have a menu bar). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/968533/+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 1258797] [NEW] Unity DASH is slow with ati/amd GPU
Public bug reported: Hi, I am using Ubuntu 12.04.3 on my laptop with HD3200 GPU and opensource drivers. Whenever I open DASH, moving among apps icons is extremely slow. The white box moves very slowly and so we do not know whether we have the app choosen by mouse or not. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-34.49~precise1-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,mousepoll,move,imgpng,grid,resize,place,session,regex,unitymtgrabhandles,wall,snap,vpswitch,animation,fade,workarounds,expo,ezoom,scale,unityshell] CompositorRunning: compiz Date: Sat Dec 7 18:22:55 2013 DistUpgraded: 2012-07-06 20:21:43,086 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780M [Mobility Radeon HD 3200] [1002:9612] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30e4] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110918) MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic root=UUID=5385126e-acf9-49d6-ba3c-f8dd397af2c2 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to precise on 2012-07-06 (518 days ago) dmi.bios.date: 09/14/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68GPP Ver. F.0E dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30E4 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.20 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68GPPVer.F.0E:bd09/14/2009:svnHewlett-Packard:pn:pvrF.0E:rvnHewlett-Packard:rn30E4:rvrKBCVersion94.20:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.0E dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.12-0ubuntu3 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.3 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 precise running-unity third-party-packages 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/1258797 Title: Unity DASH is slow with ati/amd GPU Status in “unity” package in Ubuntu: New Bug description: Hi, I am using Ubuntu 12.04.3 on my laptop with HD3200 GPU and opensource drivers. Whenever I open DASH, moving among apps icons is extremely slow. The white box moves very slowly and so we do not know whether we have the app choosen by mouse or not. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-34.49~precise1-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,mousepoll,move,imgpng,grid,resize,place,session,regex,unitymtgrabhandles,wall,snap,vpswitch,animation,fade,workarounds,expo,ezoom,scale,unityshell] CompositorRunning: compiz Date: Sat Dec 7 18:22:55 2013 DistUpgraded: 2012-07-06 20:21:43,086 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780M [Mobility Radeon HD 3200] [1002:9612] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30e4] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110918) MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic root=UUID=5385126e-acf9-49d6-ba3c-f8dd397af2c2 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to precise on 2012-07-06 (518 days ago) dmi.bios.date: 09/14/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68GPP Ver. F.0E dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30E4 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.20 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68GPPVer.F.0E:bd09/14/2009:svnHewlett-Packard:pn:pvrF.0E:rvnHewlett-Packard:rn30E4:rvrKBCVersion94.20:cvnHewlett-Packard:ct10:cvr: dmi.product.versio
[Dx-packages] [Bug 1248245] Re: calendar indicator always opens with wrong date
*** This bug is a duplicate of bug 1209386 *** https://bugs.launchpad.net/bugs/1209386 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New => Confirmed -- 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/1248245 Title: calendar indicator always opens with wrong date Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: The unity calendar indicator invariably opens with a day highlighted that is not "today", always in the past, sometimes in the wrong month. I'd expect when i click the time to see the calendar to be looking at the current month and have the current day highlighted. Like cal on the command line. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131016.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Nov 5 11:13:42 2013 InstallationDate: Installed on 2013-09-17 (48 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130917) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1248245/+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 1258782] Re: sound is not reenabled when unmuting (multimedia key mute)
** Package changed: indicator-sound (Ubuntu) => xfce4-volumed (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1258782 Title: sound is not reenabled when unmuting (multimedia key mute) Status in “xfce4-volumed” package in Ubuntu: New Bug description: Since using Ubuntu 13.10 and XFCE (as Gnome is completely unusable by now, but I guess that's rather a feature than a bug), pressing the "mute" multimedia key does not reenable sound after muting. After logging into a freshly booted system, pressing the "mute" multimedia key results in: - The sound-indicator applet shows the "muted" symbol. - Sound is muted. - alsamixer shows that Master, Headphone and PCM switched from open (OO) to muted (MM). Pressing the "mute" key again results in: - The sound-indicator applet again shows its normal state (in my case a mouseover gives "Master: 65%"). - Still hearing no sound. - alsamixer shows that Master has been unmuted, but Headphone and PCM are still muted. Expected behavior: I should be hearing sound again, Headphone and PCM should also be unmuted. Workaround: Use alsamixer to manually unmute (navigate to Headphone and PCM, press 'M' key) channels. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-sound 12.10.2+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sat Dec 7 16:06:15 2013 InstallationDate: Installed on 2012-07-06 (519 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: indicator-sound UpgradeStatus: Upgraded to saucy on 2013-10-17 (51 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1258782/+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 1244680] Re: Clock freezes after changing timezone
Marking High/Triaged since I have confirmed it and experienced it. ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided => High ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed => Triaged -- 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/1244680 Title: Clock freezes after changing timezone Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: The time in the datetime indicator freezes when you change the timezone. To reproduce: 1) Note the current time in the datetime indicator 2) Change the system timezone, such as by clicking a different timezone in the datetime indicator menu or changing timezone in the date/time system settings app Expected results: The clock in the datetime indicator updates to show the current time in the new timezone. The clock continues to function normally, updating the minutes/hours as time progresses Actual results: The clock in the datetime indicator freezes. It does not update to the new timezone and no longer updates the minutes/hours - it stays frozen at the time it displayed when you updated the timezone. The system time is not affected; running 'date' from a terminal displays the correct time. The menu in the datetime indicator will display the correct time. It's just the clock in the panel that is broken. This is 100% reproducible on my system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131016.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Oct 25 10:07:03 2013 InstallationDate: Installed on 2010-09-17 (1134 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: Upgraded to saucy on 2013-08-07 (78 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1244680/+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 1258782] [NEW] sound is not reenabled when unmuting (multimedia key mute)
Public bug reported: Since using Ubuntu 13.10 and XFCE (as Gnome is completely unusable by now, but I guess that's rather a feature than a bug), pressing the "mute" multimedia key does not reenable sound after muting. After logging into a freshly booted system, pressing the "mute" multimedia key results in: - The sound-indicator applet shows the "muted" symbol. - Sound is muted. - alsamixer shows that Master, Headphone and PCM switched from open (OO) to muted (MM). Pressing the "mute" key again results in: - The sound-indicator applet again shows its normal state (in my case a mouseover gives "Master: 65%"). - Still hearing no sound. - alsamixer shows that Master has been unmuted, but Headphone and PCM are still muted. Expected behavior: I should be hearing sound again, Headphone and PCM should also be unmuted. Workaround: Use alsamixer to manually unmute (navigate to Headphone and PCM, press 'M' key) channels. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-sound 12.10.2+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sat Dec 7 16:06:15 2013 InstallationDate: Installed on 2012-07-06 (519 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: indicator-sound UpgradeStatus: Upgraded to saucy on 2013-10-17 (51 days ago) ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1258782 Title: sound is not reenabled when unmuting (multimedia key mute) Status in “indicator-sound” package in Ubuntu: New Bug description: Since using Ubuntu 13.10 and XFCE (as Gnome is completely unusable by now, but I guess that's rather a feature than a bug), pressing the "mute" multimedia key does not reenable sound after muting. After logging into a freshly booted system, pressing the "mute" multimedia key results in: - The sound-indicator applet shows the "muted" symbol. - Sound is muted. - alsamixer shows that Master, Headphone and PCM switched from open (OO) to muted (MM). Pressing the "mute" key again results in: - The sound-indicator applet again shows its normal state (in my case a mouseover gives "Master: 65%"). - Still hearing no sound. - alsamixer shows that Master has been unmuted, but Headphone and PCM are still muted. Expected behavior: I should be hearing sound again, Headphone and PCM should also be unmuted. Workaround: Use alsamixer to manually unmute (navigate to Headphone and PCM, press 'M' key) channels. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-sound 12.10.2+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sat Dec 7 16:06:15 2013 InstallationDate: Installed on 2012-07-06 (519 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: indicator-sound UpgradeStatus: Upgraded to saucy on 2013-10-17 (51 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1258782/+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 1257889] Re: Left clicking launcher icons only works once on specific dual monitor setups
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1257889 When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New => Incomplete ** Changed in: unity Status: New => Incomplete -- 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/1257889 Title: Left clicking launcher icons only works once on specific dual monitor setups Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: I'm using a dual monitor setup with 1680x1050 and 2560x1440 screens. When the 1440p is aligned to the right or below the other screen, and the launcher is just on the 1440p screen, each individual icon on the launcher only reacts to a left click once. After that, left clicking does not launch the application anymore but middle, right click and dragging the icon still works. Having the 1440p on the left or above the other screen does not cause this bug. Also having the launcher placed on both screens at the same time does not cause it. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1257889/+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 1258121] Re: indicator time does not update time zone change
*** This bug is a duplicate of bug 1244680 *** https://bugs.launchpad.net/bugs/1244680 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1244680, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1244680 Clock freezes after changing timezone -- 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/1258121 Title: indicator time does not update time zone change Status in “indicator-datetime” package in Ubuntu: New Bug description: Indicator time does not update when I change time zone in "Date & Time Settings". To reproduce: 1. Open "Date & Time Settings..." in time indicator. 2. Change "Location" to other time zone (e.g. I change from "Saint Petersburg" to "London"). Expected behaviour: time in time indicator should change. Observed behaviour: time in time indicator shown in old time zone. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Dec 5 11:01:48 2013 InstallationDate: Installed on 2013-10-16 (49 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: Upgraded to saucy on 2013-11-07 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1258121/+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 1247671] Re: indicator time does not update upon location change
*** This bug is a duplicate of bug 1244680 *** https://bugs.launchpad.net/bugs/1244680 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1244680, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1244680 Clock freezes after changing timezone -- 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/1247671 Title: indicator time does not update upon location change Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: I recently travelled from my home area of Los Angeles to Hong Kong. While the time zone correctly was changed in settings, the indicator itself froze at the old time. killing the indicator-datetime-service process resulted in the correct local time being displayed. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131016.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Nov 4 05:12:32 2013 InstallationDate: Installed on 2013-01-14 (293 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64+mac (20121017.3) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: Upgraded to saucy on 2013-10-23 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1247671/+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 1258666] Re: I am not able to power off my computer using shutdown button.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1258666 When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: indicator-session (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1258666 Title: I am not able to power off my computer using shutdown button. Status in “indicator-session” package in Ubuntu: Incomplete Bug description: I am not able to power off my computer using shutdown button. It gets stuck. I have to use terminal to get it to halt. I'm using 12.04 and old PC with AMD 1.5ghz chip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1258666/+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 968533] Re: Alt-tab to Firefox sends Firefox to 100% CPU; unity-panel-service to 80% CPU and hud-service to 20-80% CPU
@pieleric: I confirm it has gotten worse in 13.10. The BookmarkMenuHider didn't do anything for me, probably because most of my bookmarks are sorted and thus still in the menu. after installing the addon. The ui.use_unity_menubar trick did it, but I agree it is a pity it also disables HUD completely. Ideally the bookmarks should not be exposed to HUD, as they are already accessible through Firefox address bar (Ctrl+L). @holocronweaver: this looks essentially like the same bug, why create a new one that is going to be closed as duplicate? -- 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/968533 Title: Alt-tab to Firefox sends Firefox to 100% CPU; unity-panel-service to 80% CPU and hud-service to 20-80% CPU Status in Unity: Confirmed Status in “indicator-appmenu” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I've been seeing UI hangs after switching tabs in Firefox, and switching from other applications to Firefox. It can take 3-8 seconds to change *tab*. During this time the CPU is maxed out; typical output from 'top' during this period shows 'hud- service' and 'unity-panel-service' combined using about the same CPU as Firefox itself: 100 10.4 26:07.73 firefox 53 0.6 6:14.86 hud-service 38 1.5 6:42.14 unity-panel-service I suspect that the change is causing a (an inefficient) re-index related to updated menu structures. (Eg. something like the history menu, although I can't see what it is as don't currently have a menu bar). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/968533/+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
