[Dx-packages] [Bug 1381069] Re: We should hide the player controls in the sound indicator until the music player is fixed to work with them
** Changed in: media-hub (Ubuntu) Assignee: (unassigned) = Thomas Voß (thomas-voss) ** Changed in: media-hub (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1381069 Title: We should hide the player controls in the sound indicator until the music player is fixed to work with them Status in “indicator-sound” package in Ubuntu: In Progress Status in “media-hub” package in Ubuntu: Fix Released Bug description: see these two bugs: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1378048 https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1361232 Essentially, the music player does not work with the sound menu, and the fix is involved. Until the default experience works, I suggest that we do not show these controls. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1381069/+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 1381871] Re: [wizard] volume notification showing up during wizard (with volume as 0)
Important to note is that if you go back and forth in the wizard, the bubble will be displayed multiple times. This suggests to me that the wizard indeed is triggering volume changes. ** Also affects: indicator-sound (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1381871 Title: [wizard] volume notification showing up during wizard (with volume as 0) Status in “indicator-sound” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Bug description: The volume notification shows up at the 'lock security' page on the wizard, showing volume as 0. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 109 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-16 04:39:16 version version: 109 version ubuntu: 20141016 version device: 20141014-acf0142 version custom: 1413412663 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1381871/+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 1378618] Re: volume notification looks bad when an indicator is open
This has been circulated enough, let's just use this bug then, I added the relevant tasks for i-sound and settings app so that they tell the backend when not to trigger the bubble. ** Also affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1378618 Title: volume notification looks bad when an indicator is open Status in Ubuntu UX bugs: Confirmed Status in “indicator-sound” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity8” package in Ubuntu: In Progress Bug description: I found this while testing silo 11 with krilling #88. Steps to reproduce: Open an indicator. Press a volume button. (see the attached screenshot) You will see that the notification appears, but it's the same color as the header. It has no borders, so you can't tell it's a popup. It looks like the header changed to something that's no properly aligned. phablet@ubuntu-phablet:~$ apt-cache policy indicator-sound indicator-sound: Instalados: 12.10.2+14.10.20141007-0ubuntu1 Candidato: 12.10.2+14.10.20141007-0ubuntu1 Tabla de versión: *** 12.10.2+14.10.20141007-0ubuntu1 0 500 http://ppa.launchpad.net/ci-train-ppa-service/landing-011/ubuntu-rtm/ 14.09/main armhf Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1378618/+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 1354134] Re: HUD doen't search in bookmarks in firefox anymore
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: hud (Ubuntu) Status: New = Confirmed -- 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/1354134 Title: HUD doen't search in bookmarks in firefox anymore Status in Unity HUD: New Status in “hud” package in Ubuntu: Confirmed Bug description: Hi, I have just upgrade from 12.04 to 14.04 Sadly I lose a daily function for me How to reproduce: - Open firefox - Mark a website in bookmarks and change its name for foo - Restart firefox - Open the HUD and enter foo Result: the HUD doesn't display this bookmarks I think it is a regression, I used a lot this function on Ubuntu 12.04, it was my setup to go in my boobmarking website. Thank you Ubuntu 14.04 LTS x64, unity 7.2.2 Oh strange, I wanna take screenshot and I see an interresing behavior: How to reproduce this behavior: - Open firefox - Mark a website in bookmarks and change its name for foo - Restart firefox - Open the HUD and enter foo Result: the HUD doesn't display this bookmarks - But now keep firefox open - Open/close the dash... - retry to enter foo in HUD Result 2.0 : the HUD display this bookmarks (screenshot3.png) I hope it will help you To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1354134/+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 1242007] Re: Dash finds no applications
*** This bug is a duplicate of bug 1301392 *** https://bugs.launchpad.net/bugs/1301392 ** This bug has been marked a duplicate of bug 1301392 DASH do not show installed applications -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1242007 Title: Dash finds no applications Status in “unity-lens-applications” package in Ubuntu: Confirmed Bug description: After upgrade from raring to saucy, the dash doesn't return any application results. If I search in dash home, it gives me only files and folders if I look for 'firefox' or 'terminal'. If I go to the applications lens, it says Sorry, there is nothing that matches your search. even if I type in no text. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-lens-applications 7.1.0+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sat Oct 19 13:58:35 2013 InstallationDate: Installed on 2012-11-10 (342 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: unity-lens-applications UpgradeStatus: Upgraded to saucy on 2013-10-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1242007/+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 1068926] Re: compiz crashes with fglrx installed in 12.04
** No longer affects: fglrx -- 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/1068926 Title: compiz crashes with fglrx installed in 12.04 Status in Compiz: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: compiz crashes with 12.10 on startup with fglrx installed, it works when i remove fglrx i just see the wallpaper and the desktop icons (unity doesn't get loaded) i will try to gather information if you tell me how :) (i still can open the terminal in my crashed session with strg + alt + t) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Sat Oct 20 03:10:08 2012 DistUpgraded: 2012-10-19 00:28:50,706 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: lg4l, 0.12, 3.0.0-17-generic, x86_64: installed lg4l, 0.12, 3.2.0-31-generic, x86_64: installed lg4l, 0.12, 3.5.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4870] [1002:9440] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited Device [174b:0851] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MachineType: Gigabyte Technology Co., Ltd. GA-MA790X-UD4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=6da4a145-40fd-4bbe-8331-7398f2304ceb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to quantal on 2012-10-18 (1 days ago) dmi.bios.date: 01/05/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-MA790X-UD4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd01/05/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790X-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790X-UD4:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790X-UD4 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.8.4-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1068926/+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 1382020] [NEW] ido ftbfs in utopic
Public bug reported: ido ftbfs in utopic, on every architecture. seen in http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140914-utopic.html GISCAN Ido3-0.1.gir idomessagedialog.c:251: Warning: Ido3: @Varargs parameter is deprecated, please use @... instead: * @Varargs: arguments for @message_format ^ idomessagedialog.c:315: Warning: Ido3: @Varargs parameter is deprecated, please use @... instead: * @Varargs: arguments for @message_format. They will be escaped to allow valid XML. ^ idoprogressmenuitem.c:2: Error: Ido3: identifier not found on the first line: * Copyright 2013 Canonical Ltd. ^ GICOMP Ido3-0.1.gir /usr/bin/vapigen --library=Ido3-0.1 \ --pkg gtk+-3.0 \ Ido3-0.1.gir Generation succeeded - 0 warning(s) ** Affects: ido (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs -- 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/1382020 Title: ido ftbfs in utopic Status in “ido” package in Ubuntu: Confirmed Bug description: ido ftbfs in utopic, on every architecture. seen in http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140914-utopic.html GISCAN Ido3-0.1.gir idomessagedialog.c:251: Warning: Ido3: @Varargs parameter is deprecated, please use @... instead: * @Varargs: arguments for @message_format ^ idomessagedialog.c:315: Warning: Ido3: @Varargs parameter is deprecated, please use @... instead: * @Varargs: arguments for @message_format. They will be escaped to allow valid XML. ^ idoprogressmenuitem.c:2: Error: Ido3: identifier not found on the first line: * Copyright 2013 Canonical Ltd. ^ GICOMP Ido3-0.1.gir /usr/bin/vapigen --library=Ido3-0.1 \ --pkg gtk+-3.0 \ Ido3-0.1.gir Generation succeeded - 0 warning(s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1382020/+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 1366351] Re: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings-daemon goes away
This bug was fixed in the package unity - 7.3.1+14.10.20141015-0ubuntu1 --- unity (7.3.1+14.10.20141015-0ubuntu1) utopic; urgency=low [ Iain Lane ] * When grabbing keys, try prefixing XF86 if the key isn't found. GNOME gives us unprefixed keys sometimes. (LP: #1302885) [ Brandon Schaefer ] * Remove bad tests that randomly fail [ handsome_feng445865...@qq.com ] * added support for getting the distro name from /etc/os-release (LP: #1329584) [ Marco Trevisan (Treviño) ] * LockScreenController: wait the primary shield to get the grab before setting the session locked * GLibSignal: don't call callback function if the object_ value is not matching the CB (LP: #1366351) -- Ubuntu daily release ps-jenk...@lists.canonical.com Wed, 15 Oct 2014 12:56:50 + ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1366351 Title: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings- daemon goes away Status in Compiz: Invalid Status in Unity: In Progress Status in “compiz” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Bug description: Compiz crashes when unity-settings-daemon goes away. Simple reproducer: killall -SEGV unity-settings-daemon. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1 Uname: Linux 3.16.0-13-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 6 10:48:43 2014 Disassembly: = 0x0: Cannot access memory at address 0x0 DistUpgraded: 2014-09-01 18:03:23,330 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R9 270X] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:04a1] InstallationDate: Installed on 2014-03-24 (166 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: MSI MS-7640 ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LD_LIBRARY_PATH=set LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-13-generic root=UUID=2696ea28-d88b-431c-a1fa-1e0f297ee664 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: ?? () 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 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: compiz crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to utopic on 2014-09-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.15 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 890FXA-GD70 (MS-7640) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.15:bd10/31/2012:svnMSI:pnMS-7640:pvr1.0:rvnMSI:rn890FXA-GD70(MS-7640):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7640 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
[Dx-packages] [Bug 1329584] Re: The label in the panel menu doesn't match the /etc/os-release NAME
This bug was fixed in the package unity - 7.3.1+14.10.20141015-0ubuntu1 --- unity (7.3.1+14.10.20141015-0ubuntu1) utopic; urgency=low [ Iain Lane ] * When grabbing keys, try prefixing XF86 if the key isn't found. GNOME gives us unprefixed keys sometimes. (LP: #1302885) [ Brandon Schaefer ] * Remove bad tests that randomly fail [ handsome_feng445865...@qq.com ] * added support for getting the distro name from /etc/os-release (LP: #1329584) [ Marco Trevisan (Treviño) ] * LockScreenController: wait the primary shield to get the grab before setting the session locked * GLibSignal: don't call callback function if the object_ value is not matching the CB (LP: #1366351) -- Ubuntu daily release ps-jenk...@lists.canonical.com Wed, 15 Oct 2014 12:56:50 + ** Changed in: unity (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/1329584 Title: The label in the panel menu doesn't match the /etc/os-release NAME Status in Ubuntu Kylin: Confirmed Status in Unity: New Status in Unity 7.2 series: New Status in “unity” package in Ubuntu: Fix Released Bug description: The desktop name Ubuntu Desktop can't change to Ubuntu Kylin Desktop,it is not convenient for us to change it to our Special symbol. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1329584/+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 1363959] Re: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle()
This bug was fixed in the package nux - 4.0.7+14.10.20141007-0ubuntu1 --- nux (4.0.7+14.10.20141007-0ubuntu1) utopic; urgency=low [ Marco Trevisan (Treviño) ] * WindowCompositor: don't try to use an null dnd_area pointer (LP: #1363959) -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 07 Oct 2014 14:14:14 + ** Changed in: nux (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1363959 Title: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle() Status in Nux: In Progress Status in Nux trusty series: In Progress Status in “nux” package in Ubuntu: Fix Released Bug description: Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 compiz: Geïnstalleerd: 1:0.9.12+14.10.20140812-0ubuntu1 Kandidaat: 1:0.9.12+14.10.20140812-0ubuntu1 Versietabel: *** 1:0.9.12+14.10.20140812-0ubuntu1 0 500 http://nl.archive.ubuntu.com/ubuntu/ utopic/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu1 Architecture: i386 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: Mon Sep 1 12:30:05 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] InstallationDate: Installed on 2014-08-29 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha i386 (20140826) MachineType: ASUSTeK Computer INC. 1001PX ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANGUAGE=nl_NL XDG_RUNTIME_DIR=set LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-11-generic root=UUID=e2155ee3-e907-44c0-b6e7-f0608f136055 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0xb0d08ed1 _ZN3nux16WindowCompositor13DndEventCycleERNS_5EventE+257: mov(%edx),%ecx PC (0xb0d08ed1) ok source (%edx) (0x) not located in a known VMA region (needed readable region)! destination %ecx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: nux::WindowCompositor::DndEventCycle(nux::Event) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 nux::WindowCompositor::ProcessEvent(nux::Event) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 nux::WindowThread::DoProcessEvent(nux::Event) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 nux::WindowThread::ProcessEvent(nux::Event) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 nux::nux_event_dispatch(_GSource*, int (*)(void*), void*) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 Title: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd02/18/2011:svnASUSTeKComputerINC.:pn1001PX:pvrx.x:rvnASUSTeKComputerINC.:rn1001PX:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PX dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Sep 1
[Dx-packages] [Bug 1302885] Re: Media keyboard shortcuts not working
This bug was fixed in the package unity - 7.3.1+14.10.20141015-0ubuntu1 --- unity (7.3.1+14.10.20141015-0ubuntu1) utopic; urgency=low [ Iain Lane ] * When grabbing keys, try prefixing XF86 if the key isn't found. GNOME gives us unprefixed keys sometimes. (LP: #1302885) [ Brandon Schaefer ] * Remove bad tests that randomly fail [ handsome_feng445865...@qq.com ] * added support for getting the distro name from /etc/os-release (LP: #1329584) [ Marco Trevisan (Treviño) ] * LockScreenController: wait the primary shield to get the grab before setting the session locked * GLibSignal: don't call callback function if the object_ value is not matching the CB (LP: #1366351) -- Ubuntu daily release ps-jenk...@lists.canonical.com Wed, 15 Oct 2014 12:56:50 + ** Changed in: unity (Ubuntu) Status: Confirmed = 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/1302885 Title: Media keyboard shortcuts not working Status in “unity” package in Ubuntu: Fix Released Bug description: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302885/+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 1329584] Re: The label in the panel menu doesn't match the /etc/os-release NAME
** Changed in: ubuntukylin Status: Confirmed = 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/1329584 Title: The label in the panel menu doesn't match the /etc/os-release NAME Status in Ubuntu Kylin: Fix Committed Status in Unity: New Status in Unity 7.2 series: New Status in “unity” package in Ubuntu: Fix Released Bug description: The desktop name Ubuntu Desktop can't change to Ubuntu Kylin Desktop,it is not convenient for us to change it to our Special symbol. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1329584/+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 1381871] Re: [wizard] volume notification showing up during wizard (with volume as 0)
** Changed in: indicator-sound (Ubuntu) Status: New = Confirmed ** Changed in: ubuntu-system-settings (Ubuntu) Status: Confirmed = Invalid -- 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/1381871 Title: [wizard] volume notification showing up during wizard (with volume as 0) Status in “indicator-sound” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: The volume notification shows up at the 'lock security' page on the wizard, showing volume as 0. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 109 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-16 04:39:16 version version: 109 version ubuntu: 20141016 version device: 20141014-acf0142 version custom: 1413412663 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1381871/+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 1380457] Re: lock screen not working
** Changed in: unity (Ubuntu) Status: Invalid = New ** Information type changed from Private Security to Public Security -- 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/1380457 Title: lock screen not working Status in “unity” package in Ubuntu: New Bug description: The lock screen on Ubuntu 14.04.1 LTS is not working for some reason, .it wants to lock...however the screen just bounces...would appreciate any insight here...thanks... I believe the package for the lockscreen is gnome-screensaver I expected the screen to lock. Instead the screen just bounces and doesn't lock. this happened after i updated to the new version of ubuntu. here is a video of it not locking: http://youtu.be/RCCepVCQ0Zo Here is the auth.log for when I tried to lock the screen Oct 12 22:58:15 jorge-MS-7788 compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Oct 12 22:58:15 jorge-MS-7788 compiz: PAM adding faulty module: pam_kwallet.so Oct 12 22:58:15 jorge-MS-7788 compiz: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin was met by user jorge kind regards thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1380457/+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 1381871] Re: [wizard] volume notification showing up during wizard (with volume as 0)
** Branch linked: lp:~larsu/indicator-sound/lp1381871 -- 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/1381871 Title: [wizard] volume notification showing up during wizard (with volume as 0) Status in “indicator-sound” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: The volume notification shows up at the 'lock security' page on the wizard, showing volume as 0. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 109 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-16 04:39:16 version version: 109 version ubuntu: 20141016 version device: 20141014-acf0142 version custom: 1413412663 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1381871/+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 1382020] Re: ido ftbfs in utopic
** Branch linked: lp:~ted/ido/lp1382020-ftbfs -- 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/1382020 Title: ido ftbfs in utopic Status in “ido” package in Ubuntu: Confirmed Bug description: ido ftbfs in utopic, on every architecture. seen in http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140914-utopic.html GISCAN Ido3-0.1.gir idomessagedialog.c:251: Warning: Ido3: @Varargs parameter is deprecated, please use @... instead: * @Varargs: arguments for @message_format ^ idomessagedialog.c:315: Warning: Ido3: @Varargs parameter is deprecated, please use @... instead: * @Varargs: arguments for @message_format. They will be escaped to allow valid XML. ^ idoprogressmenuitem.c:2: Error: Ido3: identifier not found on the first line: * Copyright 2013 Canonical Ltd. ^ GICOMP Ido3-0.1.gir /usr/bin/vapigen --library=Ido3-0.1 \ --pkg gtk+-3.0 \ Ido3-0.1.gir Generation succeeded - 0 warning(s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1382020/+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 1381871] Re: [wizard] volume notification showing up during wizard (with volume as 0)
** Changed in: indicator-sound (Ubuntu) Assignee: (unassigned) = Lars Uebernickel (larsu) ** Changed in: indicator-sound (Ubuntu) Status: Confirmed = In Progress -- 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/1381871 Title: [wizard] volume notification showing up during wizard (with volume as 0) Status in “indicator-sound” package in Ubuntu: In Progress Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: The volume notification shows up at the 'lock security' page on the wizard, showing volume as 0. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 109 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-16 04:39:16 version version: 109 version ubuntu: 20141016 version device: 20141014-acf0142 version custom: 1413412663 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1381871/+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 1323871] Re: Lag when adjusting sound
On Utopic everything seems to be good ^_^
--
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/1323871
Title:
Lag when adjusting sound
Status in “indicator-sound” package in Ubuntu:
Confirmed
Bug description:
When I adjust the volume - either by hovering the cursor over the
indicator and scroling, or by clicking on the indicator and dragging
the widget - the volume will jump up and down rather than smoothly
increasing or decreasing.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings':
(true, '', []), 'mic-volume': (true, '', [0.1600189208984375]), 'scroll':
(true, 'i', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop':
(true, '', [{'running': false, 'state': 'Paused'}]),
'previous.rhythmbox.desktop': (true, '', []), 'volume': (true, 'i',
[0.5999298095703125]), 'root': (true, '', [{'title': 'Sound',
'accessible-desc': 'Volume (59%)', 'icon': ('themed',
['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume',
'audio']), 'visible': true}]), 'play.rhythmbox.desktop': (true, '',
['Paused']), 'play-playlist.rhythmbox.desktop': (true, 's', []),
'next.rhythmbox.desktop': (true, '', [])},)
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 27 17:35:28 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-22 (94 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140221)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1323871/+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 1342151] Re: [Indicators] Silent mode control in the indicator
this is not in rtm yet ** Changed in: ubuntu-ux Status: Triaged = Fix Committed ** Also affects: indicator-sound Importance: Undecided Status: New ** No longer affects: indicator-sound ** Changed in: indicator-sound (Ubuntu) Status: Fix Released = In Progress -- 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/1342151 Title: [Indicators] Silent mode control in the indicator Status in Ubuntu UX bugs: Fix Committed Status in “indicator-sound” package in Ubuntu: In Progress Bug description: Should the indicator expose the control for silent mode for easy access? Implementing in settings now but would like to leverage a common implementation -- I've attached a wireframe which shows an additional setting in the sound indicator for turning on and off silent mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1342151/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
I'm not sure whether this scipt were posted here. = #!/bin/bash case $1 in thaw|resume) nmcli nm sleep false ;; *) ;; esac exit $? #save it in /etc/pm/sleep.d/wakenet.sh -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in “systemd-shim” package in Ubuntu: Confirmed Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+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 1380457] Re: lock screen not working
** Changed in: unity (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/1380457 Title: lock screen not working Status in “unity” package in Ubuntu: Fix Released Bug description: The lock screen on Ubuntu 14.04.1 LTS is not working for some reason, .it wants to lock...however the screen just bounces...would appreciate any insight here...thanks... I believe the package for the lockscreen is gnome-screensaver I expected the screen to lock. Instead the screen just bounces and doesn't lock. this happened after i updated to the new version of ubuntu. here is a video of it not locking: http://youtu.be/RCCepVCQ0Zo Here is the auth.log for when I tried to lock the screen Oct 12 22:58:15 jorge-MS-7788 compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Oct 12 22:58:15 jorge-MS-7788 compiz: PAM adding faulty module: pam_kwallet.so Oct 12 22:58:15 jorge-MS-7788 compiz: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin was met by user jorge kind regards thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1380457/+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 1311316] Re: After locking screen there is no input field to type password for unlock
Same as #42 When the mouse is moved to keep the screen awake (as it's fading to black), i'll see this afterwards. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1378919] Re: After going to lock screen - sometimes can't log back in as not prompted for password - maybe not a unity bug
This might be a different bug but I highly doubt it as the original bug behaviour followed: In the dash (right? When pressing Win-start) all icons suddenly stopped appearing. What had happened just before: I closed firefox (that had gotten slow) and updated firefox and more: 2014-10-16 14:30:47 upgrade firefox:amd64 34.0~b1+build1-0ubuntu0.14.04.1~ricotz1 34.0~b1+build2-0ubuntu0.14.04.1~ricotz1 2014-10-16 14:30:52 upgrade firefox-locale-en:amd64 34.0~b1+build1-0ubuntu0.14.04.1~ricotz1 34.0~b1+build2-0ubuntu0.14.04.1~ricotz1 2014-10-16 14:30:54 status installed man-db:amd64 2.6.7.1-1ubuntu1 2014-10-16 14:30:54 status installed gnome-menus:amd64 3.10.1-0ubuntu2 2014-10-16 14:30:55 status installed desktop-file-utils:amd64 0.22-1ubuntu1 2014-10-16 14:30:55 status installed bamfdaemon:amd64 0.5.1+14.04.20140409-0ubuntu1 2014-10-16 14:30:56 status installed mime-support:all 3.54ubuntu1 2014-10-16 14:30:59 status installed firefox:amd64 34.0~b1+build2-0ubuntu0.14.04.1~ricotz1 2014-10-16 14:30:59 status installed firefox-locale-en:amd64 34.0~b1+build2-0ubuntu0.14.04.1~ricotz1 Note the icons did not appear afterwards even though firefox was not running - memory may mave been limitted before when firefox was running but should have freed up when I closed it; nothing much else was running so it should not - still - be a problem in the dash. That is, it should not have happened, but in case it did, should have recovered. [I highly doubt the firefox update or others have anything to do with the icons gone as everything worked after a restart.] just preceded but is probably really just a coincidence except may have eaten up memory Then I reopened (the just updated) firefox that worked fine and had to lock the screen. There it was again, no entry field for the password. All was well after a restart before updating anything more. And also after fully updating (I believe these should have prevented the bug if installed according to their changelogs): 2014-10-16 15:08:29 upgrade thunderbird:amd64 1:31.1.2+build1-0ubuntu0.14.04.1 1:31.2.0+build2-0ubuntu0.14.04.1 2014-10-16 15:08:33 upgrade thunderbird-gnome-support:amd64 1:31.1.2+build1-0ubuntu0.14.04.1 1:31.2.0+build2-0ubuntu0.14.04.1 2014-10-16 15:17:15 upgrade bash:amd64 4.3-7ubuntu1.4 4.3-7ubuntu1.5 2014-10-16 15:17:19 upgrade libgl1-mesa-dri:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:21 upgrade libgbm1:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:21 upgrade libgles2-mesa:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:22 upgrade libgl1-mesa-glx:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:23 upgrade libwayland-egl1-mesa:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:23 upgrade libegl1-mesa-drivers:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:24 upgrade libglapi-mesa:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:25 upgrade libopenvg1-mesa:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:26 upgrade libegl1-mesa:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:27 upgrade libvncserver0:amd64 0.9.9+dfsg-1ubuntu1 0.9.9+dfsg-1ubuntu1.1 2014-10-16 15:17:27 upgrade libxatracker2:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:31 upgrade gnome-calculator:amd64 1:3.10.2-0ubuntu1.1 1:3.10.2-0ubuntu1.2 2014-10-16 15:17:41 upgrade linux-generic:amd64 3.13.0.37.44 3.13.0.38.45 2014-10-16 15:17:42 upgrade linux-image-generic:amd64 3.13.0.37.44 3.13.0.38.45 2014-10-16 15:17:53 upgrade linux-headers-generic:amd64 3.13.0.37.44 3.13.0.38.45 2014-10-16 15:17:53 upgrade linux-libc-dev:amd64 3.13.0-37.64 3.13.0-38.65 2014-10-16 15:17:55 upgrade python3-requests:all 2.2.1-1 2.2.1-1ubuntu0.1 2014-10-16 15:17:55 upgrade liboxideqt-qmlplugin:amd64 1.0.5-0ubuntu0.14.04.1 1.2.5-0ubuntu0.14.04.1 2014-10-16 15:17:56 upgrade liboxideqtcore0:amd64 1.0.5-0ubuntu0.14.04.1 1.2.5-0ubuntu0.14.04.1 2014-10-16 15:18:00 upgrade oxideqt-codecs:amd64 1.0.5-0ubuntu0.14.04.1 1.2.5-0ubuntu0.14.04.1 2014-10-16 15:08:34 status installed gnome-menus:amd64 3.10.1-0ubuntu2 2014-10-16 15:08:34 status installed desktop-file-utils:amd64 0.22-1ubuntu1 2014-10-16 15:08:34 status installed bamfdaemon:amd64 0.5.1+14.04.20140409-0ubuntu1 2014-10-16 15:08:35 status installed mime-support:all 3.54ubuntu1 2014-10-16 15:08:36 status installed man-db:amd64 2.6.7.1-1ubuntu1 2014-10-16 15:08:37 status installed thunderbird:amd64 1:31.2.0+build2-0ubuntu0.14.04.1 2014-10-16 15:08:37 status installed thunderbird-gnome-support:amd64 1:31.2.0+build2-0ubuntu0.14.04.1 2014-10-16 15:17:17 status installed man-db:amd64 2.6.7.1-1ubuntu1 2014-10-16 15:17:17 status installed install-info:amd64 5.2.0.dfsg.1-2 2014-10-16 15:17:18 status installed bash:amd64 4.3-7ubuntu1.5 2014-10-16 15:18:01 status installed libglib2.0-0:amd64 2.40.2-0ubuntu1 2014-10-16 15:18:01 status installed man-db:amd64 2.6.7.1-1ubuntu1 2014-10-16 15:18:01 status installed gnome-menus:amd64 3.10.1-0ubuntu2 2014-10-16
[Dx-packages] [Bug 1378919] Re: After going to lock screen - sometimes can't log back in as not prompted for password - maybe not a unity bug
I'm not even sure if the lock-screen and dash are the same program (unity?), in case they are different and I just happened to trigger two bugs at once then memory being low (or low in the past) very probably is the common cause. I do not care too much about the dash (file bug separatly?) but the lockscreen is a critical one. I do not know how to flag is as such. ** Summary changed: - After going to lock screen - sometimes can't log back in as not prompted for password - maybe not a unity bug + After going to lock screen - sometimes can't log back in as not prompted for password - maybe not a unity bug (and icons can go missing in dash) -- 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/1378919 Title: After going to lock screen - sometimes can't log back in as not prompted for password - maybe not a unity bug (and icons can go missing in dash) Status in “unity” package in Ubuntu: Confirmed Bug description: Expected: Under my name on login screen I should see the field to put in my password. [I took a picture, but probably not to helpful?] [Just a guess, could it be malloc not returning memory if memory tight?] uptime 16:12:36 up 9 days I update all that matters when I reset. At least unity: 2014-09-29 08:19:43 status installed unity:amd64 7.2.3+14.04.20140826-0ubuntu1 /var/log/dpkg.log.1:2014-09-26 13:50:09 status installed libglib2.0-0:amd64 2.40.2-0ubuntu1 /var/log/dpkg.log.1:2014-09-26 13:50:10 status installed libglib2.0-bin:amd64 2.40.2-0ubuntu1 /var/log/dpkg.log.1:2014-09-29 08:19:42 status installed libglib2.0-0:amd64 2.40.2-0ubuntu1 There are exections that I do not think matters: See: https://bugs.launchpad.net/unity/+bug/1378879 for bug that I manually submitted. [Then I couldn't run ubuntu-bug unity after pressing Win-start button. I still haven't reset machine and still can't but noticed I could from a shell.] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Oct 8 16:00:40 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-36-generic, x86_64: installed bbswitch, 0.7, 3.13.0-37-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-36-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-37-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108GL [Quadro 600] [10de:0df8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0835] InstallationDate: Installed on 2014-08-26 (43 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Precision T1650 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=b342558f-2de5-4795-857d-67d51db3a726 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0X9M3X dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/31/2013:svnDellInc.:pnPrecisionT1650:pvr01:rvnDellInc.:rn0X9M3X:rvrA04:cvnDellInc.:ct6:cvr: dmi.product.name: Precision T1650 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1
[Dx-packages] [Bug 1380457] Re: lock screen not working
It seems that somehow my user got added to the nopasswordlogin group.I solved this by going into the terminal and typing in the command line: sudo gedit /etc/group and deleting my user name from the nopasswdlogin group in the text file and then saving the file again. Now I can lock the screen and the system requests a password on the ubuntu login screen. -- 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/1380457 Title: lock screen not working Status in “unity” package in Ubuntu: Fix Released Bug description: The lock screen on Ubuntu 14.04.1 LTS is not working for some reason, .it wants to lock...however the screen just bounces...would appreciate any insight here...thanks... I believe the package for the lockscreen is gnome-screensaver I expected the screen to lock. Instead the screen just bounces and doesn't lock. this happened after i updated to the new version of ubuntu. here is a video of it not locking: http://youtu.be/RCCepVCQ0Zo Here is the auth.log for when I tried to lock the screen Oct 12 22:58:15 jorge-MS-7788 compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Oct 12 22:58:15 jorge-MS-7788 compiz: PAM adding faulty module: pam_kwallet.so Oct 12 22:58:15 jorge-MS-7788 compiz: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin was met by user jorge kind regards thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1380457/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked
If this is related to having two monitors, this is only one of numerous problems I have with 14.04 and dual monitor support, and that my two monitors are different sizes. 14.04 is simply terrible with dual screens. It seems the further we go to try to support the unified mobile/desktop UI for the casual user, the less useful we get for power users. If there's anything I can do to help diagnose this issue, please ask. I'm happy to help but don't have time to dig into any code. That's what I already spend the rest of my life doing. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1003950 Title: launcher does not show minimized update manager while clicked Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “update-manager” package in Ubuntu: Confirmed Status in “unity” source package in Precise: Fix Released Status in “update-manager” source package in Precise: Confirmed Status in “unity” source package in Quantal: Fix Released Status in “update-manager” source package in Quantal: Confirmed Bug description: Update manager is showing up in the dock but I can click on the icon all day and nothing happens. Similarly if I do Super-S or Super-W it doesn't show up anywhere. Even if I alt-tab to the application nothing shows up. This happens only when update manager runs on its own. If I kill it and then launch it myself it comes to the foreground just fine. I'm not 100% sure whether this is a unity, compiz, or update-manager bug but so far my bet is on unity. =Original Report= Bug #877444 is showing again in latest updates, please re-open it. This is the exact same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1003950/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked
Hi. I also see this problem frequently--probably every time that updates are available. I'm here because I saw it again this morning. I leave the computer on overnight (since suspend doesn't work for me in 14.04) and when I arrive at work in the morning, System Update is often running but won't appear. This morning when I clicked it, it switched to another workspace, but no window. Clicked it again, and it switched back to the first workspace, but still no window. Since 14.04 decided to do away with the Updates available in the gear menu, I don't even know how to launch system updates. There was a context-menu option on the launcher icon for the updater, which offered to install all available updates. I don't know if that would have worked, because I always review the updates before installing. I also have two monitors. Both are plugged in and turned on when I see the problem. Of course, at night the monitors are turned off, and that is when the updater usually gets launched. So perhaps it does have something to do with a cable plugged in (one is HDMI, one is DVI) with no attached monitor that is turned on. What's worse is I that when I hit Win-R to launch the run menu and type software updater, it happily lists it as an option (but only with the gears icon) and when I click it nothing happens. How is it that it's not accessible via the run menu? I actually came across this bug today because I couldn't figure out how to run the thing manually. I can do apt-get upgrade from the command line and have some idea of what's being installed, but not with the detail that the software updater provides. 14.04 has some nice touches, but I sure miss how solid 12.04 was... -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1003950 Title: launcher does not show minimized update manager while clicked Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “update-manager” package in Ubuntu: Confirmed Status in “unity” source package in Precise: Fix Released Status in “update-manager” source package in Precise: Confirmed Status in “unity” source package in Quantal: Fix Released Status in “update-manager” source package in Quantal: Confirmed Bug description: Update manager is showing up in the dock but I can click on the icon all day and nothing happens. Similarly if I do Super-S or Super-W it doesn't show up anywhere. Even if I alt-tab to the application nothing shows up. This happens only when update manager runs on its own. If I kill it and then launch it myself it comes to the foreground just fine. I'm not 100% sure whether this is a unity, compiz, or update-manager bug but so far my bet is on unity. =Original Report= Bug #877444 is showing again in latest updates, please re-open it. This is the exact same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1003950/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked
One other thing--I think Compiz tends to crash every night, because in the morning I find whatever windows I left open scattered around my first workspace. Perhaps this could be reproduced by launching the Software updater and then crashing Compiz? Or running 'compiz --replace'? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1003950 Title: launcher does not show minimized update manager while clicked Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “update-manager” package in Ubuntu: Confirmed Status in “unity” source package in Precise: Fix Released Status in “update-manager” source package in Precise: Confirmed Status in “unity” source package in Quantal: Fix Released Status in “update-manager” source package in Quantal: Confirmed Bug description: Update manager is showing up in the dock but I can click on the icon all day and nothing happens. Similarly if I do Super-S or Super-W it doesn't show up anywhere. Even if I alt-tab to the application nothing shows up. This happens only when update manager runs on its own. If I kill it and then launch it myself it comes to the foreground just fine. I'm not 100% sure whether this is a unity, compiz, or update-manager bug but so far my bet is on unity. =Original Report= Bug #877444 is showing again in latest updates, please re-open it. This is the exact same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1003950/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1378048] Re: Forward button does not work
Try to fix next iteration, controls are hidden right now ** Tags added: touch-2014-10-23 ** Changed in: media-hub (Ubuntu) Importance: Undecided = Critical ** Changed in: media-hub (Ubuntu) Status: New = Confirmed ** Summary changed: - Forward button does not work + Make music controls work in the sound indicator ** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- 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/1378048 Title: Make music controls work in the sound indicator Status in “indicator-sound” package in Ubuntu: Incomplete Status in “media-hub” package in Ubuntu: Confirmed Bug description: Steps: 1. Play an album in the music player 2. Pull down sound indicator 3. Click forward button Observed: the music does not advance Expected: the music advances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1378048/+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 1342151] Re: [Indicators] Silent mode control in the indicator
** Tags removed: touch-2014-10-16 ** Tags added: touch-2014-10-23 -- 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/1342151 Title: [Indicators] Silent mode control in the indicator Status in Ubuntu UX bugs: Fix Committed Status in “indicator-sound” package in Ubuntu: In Progress Bug description: Should the indicator expose the control for silent mode for easy access? Implementing in settings now but would like to leverage a common implementation -- I've attached a wireframe which shows an additional setting in the sound indicator for turning on and off silent mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1342151/+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 1381871] Re: [wizard] volume notification showing up during wizard (with volume as 0)
FWIW, fixed in rtm krillin image 112. ** Changed in: indicator-sound (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1381871 Title: [wizard] volume notification showing up during wizard (with volume as 0) Status in “indicator-sound” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: The volume notification shows up at the 'lock security' page on the wizard, showing volume as 0. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 109 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-16 04:39:16 version version: 109 version ubuntu: 20141016 version device: 20141014-acf0142 version custom: 1413412663 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1381871/+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 1382307] [NEW] reply to SMS fails silently if no default SIM is set
Public bug reported: In krillin rtm image 112, I noticed that there is a silent failure if the user tries to respond to a SMS message via indicator if no default SIM has been set for SMS. After choosing a SIM in the messaging app, replies via indicator work fine... but until then, replies are silently eaten. It should probably either prompt for a SIM or give a delivery error. ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Tags: rtm14 ue -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1382307 Title: reply to SMS fails silently if no default SIM is set Status in “indicator-messages” package in Ubuntu: New Bug description: In krillin rtm image 112, I noticed that there is a silent failure if the user tries to respond to a SMS message via indicator if no default SIM has been set for SMS. After choosing a SIM in the messaging app, replies via indicator work fine... but until then, replies are silently eaten. It should probably either prompt for a SIM or give a delivery error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1382307/+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 1371764] Re: Screen does not lock when an unity indicator is open
** 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/1371764 Title: Screen does not lock when an unity indicator is open Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: 1. Open an unity Indicator 2. Close the laptop lid¹ Expected behavior: 3. The indicator menu should be closed and the screen is locked Actual behavior: 3. The screen is not locked with the menu visible, it gets locked as soon as the menu is closed. [1] instead of this action, you can also run the script below just before opening an indicator: sleep 3 gdbus call --session --dest com.canonical.Unity \ --object-path /com/canonical/Unity/Session \ --method com.canonical.Unity.Session.Lock PS: This is a special case of bug #49579, although this applies only to the unity indicators. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1371764/+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 1366351] Re: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings-daemon goes away
** 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/1366351 Title: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings- daemon goes away Status in Compiz: Invalid Status in Unity: Fix Committed Status in “compiz” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Bug description: Compiz crashes when unity-settings-daemon goes away. Simple reproducer: killall -SEGV unity-settings-daemon. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1 Uname: Linux 3.16.0-13-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 6 10:48:43 2014 Disassembly: = 0x0: Cannot access memory at address 0x0 DistUpgraded: 2014-09-01 18:03:23,330 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R9 270X] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:04a1] InstallationDate: Installed on 2014-03-24 (166 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: MSI MS-7640 ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LD_LIBRARY_PATH=set LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-13-generic root=UUID=2696ea28-d88b-431c-a1fa-1e0f297ee664 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: ?? () 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 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: compiz crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to utopic on 2014-09-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.15 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 890FXA-GD70 (MS-7640) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.15:bd10/31/2012:svnMSI:pnMS-7640:pvr1.0:rvnMSI:rn890FXA-GD70(MS-7640):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7640 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Sep 6 10:48:05 2014 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu9 xserver.video_driver: fglrx To manage notifications about this bug go to:
[Dx-packages] [Bug 1329584] Re: The label in the panel menu doesn't match the /etc/os-release NAME
** Changed in: unity Status: New = 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/1329584 Title: The label in the panel menu doesn't match the /etc/os-release NAME Status in Ubuntu Kylin: Fix Committed Status in Unity: Fix Committed Status in Unity 7.2 series: New Status in “unity” package in Ubuntu: Fix Released Bug description: The desktop name Ubuntu Desktop can't change to Ubuntu Kylin Desktop,it is not convenient for us to change it to our Special symbol. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1329584/+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 1300650] Re: Should use separate schema for launcher items
** Changed in: unity Status: Fix Released = 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/1300650 Title: Should use separate schema for launcher items Status in The Sevilerow project: New Status in Unity: Fix Committed Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu: Won't Fix Status in “unity” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Bug description: We're using the schema from unity for launcher items, but we should instead use a custom one, since unity7 will never support click packages, so they're not compatible already. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity8 7.84+14.04.20140327.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14-0ubuntu1 Architecture: armhf Date: Tue Apr 1 09:30:11 2014 InstallationDate: Installed on 2014-04-01 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140401) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/sevilerow/+bug/1300650/+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 1380457] Re: lock screen not working
** Changed in: unity 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/1380457 Title: lock screen not working Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: The lock screen on Ubuntu 14.04.1 LTS is not working for some reason, .it wants to lock...however the screen just bounces...would appreciate any insight here...thanks... I believe the package for the lockscreen is gnome-screensaver I expected the screen to lock. Instead the screen just bounces and doesn't lock. this happened after i updated to the new version of ubuntu. here is a video of it not locking: http://youtu.be/RCCepVCQ0Zo Here is the auth.log for when I tried to lock the screen Oct 12 22:58:15 jorge-MS-7788 compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Oct 12 22:58:15 jorge-MS-7788 compiz: PAM adding faulty module: pam_kwallet.so Oct 12 22:58:15 jorge-MS-7788 compiz: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin was met by user jorge kind regards thanks To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1380457/+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 1379499] Re: mouse pointer converted into half thumbnail
** Changed in: unity 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/1379499 Title: mouse pointer converted into half thumbnail Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Hallo TESTCASE: open an image with image viewer or gimp, left click to drag, release and the bug appear Actually I cannot find a way to make it return to the original state except restart. Interesting to note that if I record with the screencaster the bug is not showed in the movie even if it was existing during the record. See attached movies. Best regards ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 BootLog: * Starting userspace bootsplash utility[164G[ OK ] Loading the saved-state of the serial devices... /dev/ttyS0 at 0x03f8 (irq = 4) is a 16550A * Setting up X socket directories... [170G [164G[ OK ] 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: Thu Oct 9 21:55:46 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] MachineType: Gigabyte Technology Co., Ltd. H55M-S2H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=cc32d8a8-ff79-4de8-a08c-5900afa16b6c ro splash quiet nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: H55M-S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd08/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-S2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H55M-S2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Oct 9 21:50:10 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 input USB Keyboard KEYBOARD, id 8 input USB Keyboard KEYBOARD, id 9 inputPIXART USB OPTICAL MOUSE MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 19222 vendor HSD xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1379499/+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 1380320] Re: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad
** Changed in: unity Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1380320 Title: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: This is a REGRESSION. This used to work fine. I don't know when exactly it broke. Steps to reproduce: Test 1 and Test 2 should both behave the same as test 2, but test 1 gives nonsense and dangerous results. --Test 1-- - place finger 1 on the touchpad - move the finger around while keeping it in contact with the touchpad = the mouse cursor moves around as expected - with another finger 2, press the left button and hold it, while finger 1 is still on the touchpad, at point A - (*) move finger 1 around on the touchpad to some other point B, then stop moving it - move finger 1 around again, to point C - only then, release the left button -- Test 2 -- - place finger 1 on the touchpad - move the finger around as in test 1 - take finger 1 away from the touchpad, leaving the cursor at point A - with another finger 2, press the left button and hold it - place finger 1 on the touchpad again and move it around, then stop at point B. - Move finger 1 a bit more, to point C - release the left button Expected result: OBVIOUSLY, in both cases, the behavior should be the same. A left button press should be registered at point A, then a drag movement to B and then C, and then a button release. If, for example, at point A you hit something draggable, the result is that you drag it and drop to point C Observed result: Test 2 behaves as expected However, in test 1, nothing happens when you actually press the button. Instead, a button press is registered when finger 1 pauses at point B. That is, everything behaves as if you had pressed the mouse button at a completely different place and time than you did. The result is dragging from point B to point C. The consequences can be disastrous. This can lead to data loss, because a click may be registered on a button that delete things, or the drag-and-move operation that is executed (completely unrelated to the real action of the user) may be that of moving an object to a place where you're not supposed to move it (e.g. moving a file to the trash or whatever). This can literally result in formatting your hard drive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Oct 12 17:17:03 2014 InstallationDate: Installed on 2013-10-11 (365 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1380320/+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 1378919] Re: After going to lock screen - sometimes can't log back in as not prompted for password - maybe not a unity bug (and icons can go missing in dash)
** Changed in: unity Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1378919 Title: After going to lock screen - sometimes can't log back in as not prompted for password - maybe not a unity bug (and icons can go missing in dash) Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Expected: Under my name on login screen I should see the field to put in my password. [I took a picture, but probably not to helpful?] [Just a guess, could it be malloc not returning memory if memory tight?] uptime 16:12:36 up 9 days I update all that matters when I reset. At least unity: 2014-09-29 08:19:43 status installed unity:amd64 7.2.3+14.04.20140826-0ubuntu1 /var/log/dpkg.log.1:2014-09-26 13:50:09 status installed libglib2.0-0:amd64 2.40.2-0ubuntu1 /var/log/dpkg.log.1:2014-09-26 13:50:10 status installed libglib2.0-bin:amd64 2.40.2-0ubuntu1 /var/log/dpkg.log.1:2014-09-29 08:19:42 status installed libglib2.0-0:amd64 2.40.2-0ubuntu1 There are exections that I do not think matters: See: https://bugs.launchpad.net/unity/+bug/1378879 for bug that I manually submitted. [Then I couldn't run ubuntu-bug unity after pressing Win-start button. I still haven't reset machine and still can't but noticed I could from a shell.] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Oct 8 16:00:40 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-36-generic, x86_64: installed bbswitch, 0.7, 3.13.0-37-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-36-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-37-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108GL [Quadro 600] [10de:0df8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0835] InstallationDate: Installed on 2014-08-26 (43 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Precision T1650 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=b342558f-2de5-4795-857d-67d51db3a726 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0X9M3X dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/31/2013:svnDellInc.:pnPrecisionT1650:pvr01:rvnDellInc.:rn0X9M3X:rvrA04:cvnDellInc.:ct6:cvr: dmi.product.name: Precision T1650 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Sep 29 08:35:11 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1378919/+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 1378177] Re: Turn screen off when invactive timeout doesn't work
** Changed in: unity Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1378177 Title: Turn screen off when invactive timeout doesn't work Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I left my laptop open and running tonight when away. When I returned 1.5 hours later, my screen was still on, all black except for a white mouse pointer. I locked the screen with the windows+L combo and walked away when the lock screen displayed properly. The Brightness Lock section of the control panel shows Turn screen off when inactive for: 5 minutes. Lock is turned on, Lock screen after: 5 minutes, and Require my password when waking from suspend. I didn't suspend, and I manually locked before leaving. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Oct 6 21:42:24 2014 InstallationDate: Installed on 2012-10-18 (718 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-12 (178 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1378177/+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 1380878] Re: lock screen doesnt work
** Changed in: unity 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/1380878 Title: lock screen doesnt work Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: The lock screen on Ubuntu 14.04.1 LTS is not working for some reason, .it wants to lock...however the screen just bounces...would appreciate any insight here...thanks... I believe the package for the lockscreen is gnome-screensaver I expected the screen to lock. Instead the screen just bounces and doesn't lock. this happened after i updated to the new version of ubuntu. here is a video of it not locking: http://youtu.be/RCCepVCQ0Zo Here is the auth.log for when I tried to lock the screen Oct 12 22:58:15 jorge-MS-7788 compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Oct 12 22:58:15 jorge-MS-7788 compiz: PAM adding faulty module: pam_kwallet.so Oct 12 22:58:15 jorge-MS-7788 compiz: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin was met by user jorge kind regards thanks To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1380878/+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 1382307] Re: reply to SMS (via indicator) fails silently if no default SIM is set
** Summary changed: - reply to SMS fails silently if no default SIM is set + reply to SMS (via indicator) fails silently if no default SIM is set -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1382307 Title: reply to SMS (via indicator) fails silently if no default SIM is set Status in “indicator-messages” package in Ubuntu: New Bug description: In krillin rtm image 112, I noticed that there is a silent failure if the user tries to respond to a SMS message via indicator if no default SIM has been set for SMS. After choosing a SIM in the messaging app, replies via indicator work fine... but until then, replies are silently eaten. It should probably either prompt for a SIM or give a delivery error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1382307/+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 1302885] Re: Media keyboard shortcuts not working
** Changed in: unity Importance: Undecided = Medium ** Changed in: unity Status: New = Fix Released ** Changed in: unity Assignee: (unassigned) = Iain Lane (laney) ** Changed in: unity Status: Fix Released = Fix Committed ** Changed in: unity Milestone: None = 7.3.1 -- 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/1302885 Title: Media keyboard shortcuts not working Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1302885/+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 1097991] Re: Port to new barrier event API
** Changed in: unity Status: Fix Committed = 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/1097991 Title: Port to new barrier event API Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Committed Status in “unity” source package in Raring: Fix Committed Bug description: The pointer barrier event API we've patched in to libXfixes has moved upstream in Xserver 1.14. However, the API has changed. The barrier events and pointer release API is now in the input lib, libXi as of version 1.6.99.1 . It should be reasonably easy to port to the new API: Peter Hutterer's blog post¹ describes how to use it. The main differences are that you need to add the barrier event mask to the XI event mask, rather than window event mask, and that it now uses generic events, so you need to allocate the event data before using it and free the event data after using it XGetEventData/XFreeEventData. ¹: http://who-t.blogspot.com.au/2012/12/whats-new-in-xi-23-pointer- barrier.html To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1097991/+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 1342151] Re: [Indicators] Silent mode control in the indicator
Updated status to match Ubuntu and Ubuntu RTM status. Also the design has not be updated so it's still not completed on the Ubuntu UX side of things. ** Also affects: indicator-sound (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: indicator-sound (Ubuntu RTM) Status: New = In Progress ** Changed in: indicator-sound (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: indicator-sound (Ubuntu RTM) Assignee: (unassigned) = Ted Gould (ted) ** Changed in: indicator-sound (Ubuntu) Status: In Progress = Fix Released ** Changed in: ubuntu-ux Status: Fix Committed = Confirmed -- 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/1342151 Title: [Indicators] Silent mode control in the indicator Status in Ubuntu UX bugs: Confirmed Status in “indicator-sound” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu RTM: In Progress Bug description: Should the indicator expose the control for silent mode for easy access? Implementing in settings now but would like to leverage a common implementation -- I've attached a wireframe which shows an additional setting in the sound indicator for turning on and off silent mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1342151/+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 1371764] Re: Screen does not lock when an unity indicator is open
** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1371764 Title: Screen does not lock when an unity indicator is open Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: 1. Open an unity Indicator 2. Close the laptop lid¹ Expected behavior: 3. The indicator menu should be closed and the screen is locked Actual behavior: 3. The screen is not locked with the menu visible, it gets locked as soon as the menu is closed. [1] instead of this action, you can also run the script below just before opening an indicator: sleep 3 gdbus call --session --dest com.canonical.Unity \ --object-path /com/canonical/Unity/Session \ --method com.canonical.Unity.Session.Lock PS: This is a special case of bug #49579, although this applies only to the unity indicators. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1371764/+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 1059275] Re: reset now deprecated, man page not updated
** Changed in: unity Milestone: 7.3.2 = 7.3.1 -- 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/1059275 Title: reset now deprecated, man page not updated Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Fix Released Bug description: Run unity --reset as recommended by the man page:- ERROR: the reset option is now deprecated Man page says:- --reset This option allows the user to reset profile parameters in compiz and restart the Unity shell with default settings. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1059275/+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 1329584] Re: The label in the panel menu doesn't match the /etc/os-release NAME
** Changed in: ubuntukylin Status: Fix Committed = Fix Released ** Changed in: unity Status: Fix Committed = 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/1329584 Title: The label in the panel menu doesn't match the /etc/os-release NAME Status in Ubuntu Kylin: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: New Status in “unity” package in Ubuntu: Fix Released Bug description: The desktop name Ubuntu Desktop can't change to Ubuntu Kylin Desktop,it is not convenient for us to change it to our Special symbol. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1329584/+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 1170647] Re: After minimizing an external media, clicking on the Files icon on the Launcher doesn't restore the minimized window, but opens a new one
I'm a newcommer from windows. This problem exists in my ubuntu 14.04 x64 kernel 3.13.0-37-generic everything updated! there are several workrounds, but it's really annoying -- 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/1170647 Title: After minimizing an external media, clicking on the Files icon on the Launcher doesn't restore the minimized window, but opens a new one Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: *** ISSUE *** HOW TO REPRODUCE 1. Connect a removable media to the computer. 2. On the launcher, click on the Files icon. 3. On the left sidebar, click on the removable media icon or the trash. 4. Minimize the window. 5. Click on the Files icon. EXPECTED BEHAVIOUR - The Files window to be maximized. REAL BEHAVIOUR - A new window is opened. RELEVANT DETAILS - The only way to navigate between windows at this moment is to use the control + tabulation key combination, or to click again on the Files icon so windows are exposed. ** SOLUTION ** WORK-AROUND - On the launcher, left click on the Files icon and select the unlock from Launcher option. FIX - The launcher icon for Files to be treated the same way as if it was unlocked. REGRESSION POTENTIAL - Clicking on the Files icon won't send the user to its home folder, but to the latest opened Files window. TECHNICAL INFO ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38' b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1170647/+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 1382307] Re: reply to SMS (via indicator) fails silently if no default SIM is set
** Description changed: + Consider this invalid for now... unable to reproduce the issue on a + fresh-flashed phone, and by default it actually does ask the user to + pick a SIM even when replying from an indicator on a locked phone. + + - + In krillin rtm image 112, I noticed that there is a silent failure if the user tries to respond to a SMS message via indicator if no default SIM has been set for SMS. After choosing a SIM in the messaging app, replies via indicator work fine... but until then, replies are silently eaten. It should probably either prompt for a SIM or give a delivery error. ** Changed in: indicator-messages (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1382307 Title: reply to SMS (via indicator) fails silently if no default SIM is set Status in “indicator-messages” package in Ubuntu: Invalid Bug description: Consider this invalid for now... unable to reproduce the issue on a fresh-flashed phone, and by default it actually does ask the user to pick a SIM even when replying from an indicator on a locked phone. - In krillin rtm image 112, I noticed that there is a silent failure if the user tries to respond to a SMS message via indicator if no default SIM has been set for SMS. After choosing a SIM in the messaging app, replies via indicator work fine... but until then, replies are silently eaten. It should probably either prompt for a SIM or give a delivery error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1382307/+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 1340477] Re: The HUD doesn't support scaling on HiDPI monitors
Hello there. I use 14.04 on my HTPC as a Netflix (Chrome) and XBMC system (which works exceptionally well might I add). Due to it being a home theatre system, I ramp up the display scaling quite a lot (2.0). I noticed the HUD did not compliment display scaling, as mentioned in the bug report above. To date, this system has only been a regular, vanilla 14.04 instance with whatever updates that come down the main pipe. After finding this bug report, I enabled -proposed and did a full apt- get update and apt-get dist-upgrade. I pulled down Unity 7.2.3. Not only does the HUD now compliment the display scaling, but my mouse cursor is also adequately sized as well. Upon initial use, I have found no regressions or issues to report, however I admit I've only been booted into the system for a few moments following the update to 7.2.3. Given the HTPC gets a decent amount of use as we have no cable TV, I'll bookmark this report and comment if I run in to anything else. Thank you for your hard work, dedication, and time. It's appreciated by us users! -- 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/1340477 Title: The HUD doesn't support scaling on HiDPI monitors Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] The HUD is not scaled on HiDPI monitors [Test case] 1. From Unity Control Center - Displays - Change the monitor scaling to somewhat different from 1.0 (might be both bigger and smaller, your choice). 2. Open the Hud 3. Both the view, the text and the search results should be properly scaled to match current monitor scaling factor [Regression potential] Very low, but the hud might have visual issues (nothing found so far) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1340477/+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
