[Dx-packages] [Bug 1241101]
(In reply to Marc-Andre Laperle from comment #54) > (In reply to Taehoon Kwak from comment #53) > > I found that the crash occurs because a new Radio menu is created with > > *empty label* > > for which unity_gtk_action_group_get_state_name() returns null and this ends > > up with a null-pointer dereference at g_str_hash(). > > Would it be a good idea to fix unity_gtk_action_group_get_state_name to that > it returns an empty string instead of null? I'm thinking it would be good to > fix the root cause for other programs and earlier versions of Eclipse. My patch is a workaround that changes uses of Unity. Patching Unity seems a nice idea, yet I am not sure of any side effect -- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in gtk+2.0 package in Ubuntu: Triaged Status in unity package in Ubuntu: Invalid Status in gtk+2.0 package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1333158] Re: scaling doesn't affect firefox and thunderbird
Also broken for Thunderbird. Could we please reopen this bug? -- 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/1333158 Title: scaling doesn't affect firefox and thunderbird Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in ubufox package in Ubuntu: Invalid Status in unity package in Ubuntu: Invalid Bug description: If you use "Scale for menu and title bars" in the Displays Tab, this doesn't affect Firefox. please add this to the Unity Desktop Integration: about:config in Firefox and search for layout.css.devPixelsPerPx set this value to the same scale factor as in unity-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1333158/+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 1333158] Re: scaling doesn't affect firefox and thunderbird
Was this fix ever released? This is totally broken for me in wily!! -- 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/1333158 Title: scaling doesn't affect firefox and thunderbird Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in ubufox package in Ubuntu: Invalid Status in unity package in Ubuntu: Invalid Bug description: If you use "Scale for menu and title bars" in the Displays Tab, this doesn't affect Firefox. please add this to the Unity Desktop Integration: about:config in Firefox and search for layout.css.devPixelsPerPx set this value to the same scale factor as in unity-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1333158/+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 1333158] Re: scaling doesn't affect firefox and thunderbird
Oh seems i have to set layout.css.devPixelsPerPx to -1 manually? Also, doesn't seem to affect the scrollbar. -- 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/1333158 Title: scaling doesn't affect firefox and thunderbird Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in ubufox package in Ubuntu: Invalid Status in unity package in Ubuntu: Invalid Bug description: If you use "Scale for menu and title bars" in the Displays Tab, this doesn't affect Firefox. please add this to the Unity Desktop Integration: about:config in Firefox and search for layout.css.devPixelsPerPx set this value to the same scale factor as in unity-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1333158/+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 1466820] Re: Notification by sound or vibration doesn't work
Sorry, I forgot to update this. The bug doesn't occur anymore. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1466820 Title: Notification by sound or vibration doesn't work Status in Ubuntu Clock App: Invalid Status in indicator-datetime package in Ubuntu: Invalid Bug description: Since I updated to the newest version of the alarm-clock-app, there is no notification by sound or vibration anymore. But the screen notification is displayed. * I deleted all the alarms and recreated them * I tried silent and non silent mode and different volume setting * I even tried it with headphones and without As suggested I attached the files in .local/share/evolution/tasks Device: BQ Aquarius E4.5 Channel: stable OS: 15.04 r23 ubuntu-clock-app 3.3.280.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1466820/+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 1492437] Re: Unity Crash when trying to "unlock from launcher" a disk drive icon
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1492437 Title: Unity Crash when trying to "unlock from launcher" a disk drive icon Status in unity package in Ubuntu: Confirmed Bug description: After the latest updates (proposed repositories enabled), I noticed that when I try to "unlock from launcher" a partition (internal), this with the disk drive icon, unity crashes. Fortunately, it restores itself quite quickly. Another behaviour, if it's not crash, is to do nothing. It does not unlock/remove the the launcher icon at all. I was able to screen-recording the problem https://www.youtube.com/watch?v=YvK3kppx1rg ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20150825-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 355.11 Wed Aug 26 16:35:41 PDT 2015 GCC version: gcc version 5.2.1 20150903 (Ubuntu 5.2.1-16ubuntu1) ApportVersion: 2.18-0ubuntu9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Sep 4 22:07:33 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.1.6-999-bfq, x86_64: installed bbswitch, 0.7, 4.2.0-7-generic, x86_64: installed nvidia-355, 355.11, 4.1.6-999-bfq, x86_64: installed nvidia-355, 355.11, 4.2.0-7-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-10-24 (315 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: MSI MS-7623 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=170bb898-7aa9-4678-8e80-58a445647f93 ro SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/28/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V17.10 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 880GMA-E45 (MS-7623) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV17.10:bd02/28/2011:svnMSI:pnMS-7623:pvr3.0:rvnMSI:rn880GMA-E45(MS-7623):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.name: MS-7623 dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Fri Sep 4 20:01:51 2015 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1492437/+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 1467588] Re: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (process:1
What worked for me, is commenting out the lines with False in the /usr/share/gstreamer-properties/gstreamer-properties.ui. -- 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/1467588 Title: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (process:17035): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (process:17035): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 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 Date: Mon Jun 22 16:56:16 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-18-generic, x86_64: installed virtualbox, 4.3.26, 3.19.0-20-generic, x86_64: installed virtualbox, 4.3.26, 3.19.0-21-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1854] InstallationDate: Installed on 2015-06-02 (20 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP 2000 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=9ac32e8e-1bbd-4aa9-8f25-2b79e4052d96 ro quiet splash SourcePackage: unity UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: dmi.bios.date: 06/13/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.3A dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG3400HTV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.3A:bd06/13/2013:svnHewlett-Packard:pnHP2000NotebookPC:pvr088F130059160:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 2000 Notebook PC dmi.product.version: 088F130059160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 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.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Jun 22 15:28:27 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 845 vendor LGD xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1467588/+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 1492437] [NEW] Unity Crash when trying to "unlock from launcher" a disk drive icon
Public bug reported: After the latest updates (proposed repositories enabled), I noticed that when I try to "unlock from launcher" a partition (internal), this with the disk drive icon, unity crashes. Fortunately, it restores itself quite quickly. Another behaviour, if it's not crash, is to do nothing. It does not unlock/remove the the launcher icon at all. I was able to screen-recording the problem https://www.youtube.com/watch?v=YvK3kppx1rg ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20150825-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 355.11 Wed Aug 26 16:35:41 PDT 2015 GCC version: gcc version 5.2.1 20150903 (Ubuntu 5.2.1-16ubuntu1) ApportVersion: 2.18-0ubuntu9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Sep 4 22:07:33 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.1.6-999-bfq, x86_64: installed bbswitch, 0.7, 4.2.0-7-generic, x86_64: installed nvidia-355, 355.11, 4.1.6-999-bfq, x86_64: installed nvidia-355, 355.11, 4.2.0-7-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-10-24 (315 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: MSI MS-7623 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=170bb898-7aa9-4678-8e80-58a445647f93 ro SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/28/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V17.10 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 880GMA-E45 (MS-7623) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV17.10:bd02/28/2011:svnMSI:pnMS-7623:pvr3.0:rvnMSI:rn880GMA-E45(MS-7623):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.name: MS-7623 dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Fri Sep 4 20:01:51 2015 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu5 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug possible-manual-nvidia-install ubuntu wily -- 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/1492437 Title: Unity Crash when trying to "unlock from launcher" a disk drive icon Status in unity package in Ubuntu: New Bug description: After the latest updates (proposed repositories enabled), I noticed that when I try to "unlock from launcher" a partition (internal), this with the disk drive icon, unity crashes. Fortunately, it restores itself quite quickly. Another behaviour, if it's not crash, is to do nothing. It does not unlock/remove the the launcher icon at all. I was able to screen-recording the problem https://www.youtube.com/watch?v=YvK3kppx1rg ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20150825-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 355.11 Wed Aug 26 16:35:41 PDT 2015 GCC version: gcc version 5.2.1 20150903 (Ubuntu 5.2.1-16ubuntu1) ApportVersion: 2.18-0ubuntu9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Sep 4 22:07:33 2015 DistUpgraded: Fresh install DistroCodename
[Dx-packages] [Bug 1067020] Re: accounts-daemon hangs on GDM login
** Tags added: precise -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1067020 Title: accounts-daemon hangs on GDM login Status in accountsservice package in Ubuntu: Confirmed Bug description: root@xxx:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 12.04.1 LTS Release: 12.04 Codename: precise root@xxx:~# uname -a Linux beefy 3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux accountsservice Version: 0.6.15-2ubuntu9.4 Upon authorization using GDM, the accounts-daemon process hangs the login by consuming 100% CPU on a single processor and rapidly consuming all system memory. GDM will not continue with the login until the accounts-daemon process is killed. I'm using SSSD as the backend authentication module in PAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1067020/+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 1241101]
(In reply to Taehoon Kwak from comment #53) > I found that the crash occurs because a new Radio menu is created with > *empty label* > for which unity_gtk_action_group_get_state_name() returns null and this ends > up with a null-pointer dereference at g_str_hash(). Would it be a good idea to fix unity_gtk_action_group_get_state_name to that it returns an empty string instead of null? I'm thinking it would be good to fix the root cause for other programs and earlier versions of Eclipse. -- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in gtk+2.0 package in Ubuntu: Triaged Status in unity package in Ubuntu: Invalid Status in gtk+2.0 package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1489037] Re: Change defaut alarm sound to "Alarm clock.ogg"
** Branch linked: lp:~charlesk/indicator-datetime/lp-1489037-change- default-alarm-sound -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1489037 Title: Change defaut alarm sound to "Alarm clock.ogg" Status in Canonical System Image: New Status in indicator-datetime package in Ubuntu: In Progress Bug description: With OTA-6 (as per bug 1354370), the default alarm sound has been changed from "Suru arpeggio.ogg" to "Alarm clock.ogg". Indicator- datetime will have to set this as default on its end. Note: Clock App will set "Alarm clock.ogg" as the default alarm sound for new alarms created by the user starting with clock app v3.5.362. This bug is to ensure that the fallback alarm played by indicator- datetime is also "Alarm clock.ogg" (which is used when the user sets an invalid alarm tone). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1489037/+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 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Changed in: ubuntu-ux 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/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: Fix Released Status in Ubuntu UX: Fix Released Status in Unity: Invalid Status in unity-notifications: Confirmed Status in indicator-network package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu: Triaged Status in unity package in Ubuntu: Invalid Status in unity-notifications package in Ubuntu: Fix Released Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1295762/+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 1286910] Re: Lock screen uses last active window's language instead of default keyboard language
Still affects me as well. Fix at https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/comments/19 doesn't work. -- 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/1286910 Title: Lock screen uses last active window's language instead of default keyboard language Status in Unity: New Status in gnome-screensaver package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Lock screen (gnome-screensaver) uses last active window's language (keyboard layout) instead of default keyboard language. Steps to reproduce this bug: 1. In the system Text Entry settings: 1a. add two or more languages to the input sources list, e.g. English (as first and default) and Russian (as second); 1b. Set hotkeys to switch sources (e.g. Ctrl+Shift or CapsLock). 1c. Select "Allow different sources for each window" radio button. 1d. Select "New windows use the default source" radio button. 2. Run any application (e.g. gedit) and switch keyboard to second input language (Russian). 3. Lock the screen (Ctrl+Alt+L) or just wait idle time. 4. See what language set by default for password input in the lock screen. Expected: lock screen uses first input language (English) by default. What happened instead: lock screen uses last active window's language (Russian). Ubuntu versions affected: Ubuntu 13.10, Ubuntu 14.04 (daily builds) gnome-screensaver versions: 3.6.1-0ubuntu7, 3.6.1-0ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1286910/+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 1241101]
Created attachment 256390 Patch Hi. I have looked into this problem and came up with the following workaround patch that still uses Unity and avoids the crash. I found that the crash occurs because a new Radio menu is created with *empty label* for which unity_gtk_action_group_get_state_name() returns null and this ends up with a null-pointer dereference at g_str_hash(). My suggestion is to modify _1gtk_1radio_1menu_1item_1new_1with_1label() in os.c to call gtk_radio_menu_item_new_with_label() with an arbitrary, non-empty string if the given string for label is for empty string (2nd parameter). In this patch, I used the string with one space (" ") as an arbitrary text. I confirmed that, with this patch, the test given by Thomas Singer passes and all tests in Test_org_eclipse_swt_widgets_MenuItem.java pass as well. Please let me know if you have any question or suggestion for this patch. Thanks. --- "a/bundles/org.eclipse.swt/Eclipse SWT PI/gtk/library/os.c" 2013-05-14 11:50:23.0 +0900 +++ "b/bundles/org.eclipse.swt/Eclipse SWT PI/gtk/library/os.c" 2015-09-04 19:49:40.768009600 +0900 @@ -13868,7 +13868,10 @@ JNIEXPORT jintLong JNICALL OS_NATIVE(_1gtk_1radio_1menu_1item_1new_1with_1label) jintLong rc = 0; OS_NATIVE_ENTER(env, that, _1gtk_1radio_1menu_1item_1new_1with_1label_FUNC); if (arg1) if ((lparg1 = (*env)->GetByteArrayElements(env, arg1, NULL)) == NULL) goto fail; - rc = (jintLong)gtk_radio_menu_item_new_with_label((GSList *)arg0, (const gchar *)lparg1); + if (lparg1[0] == '\0') + rc = (jintLong)gtk_radio_menu_item_new_with_label((GSList *)arg0, (const gchar *)" "); + else + rc = (jintLong)gtk_radio_menu_item_new_with_label((GSList *)arg0, (const gchar *)lparg1); fail: if (arg1 && lparg1) (*env)->ReleaseByteArrayElements(env, arg1, lparg1, 0); OS_NATIVE_EXIT(env, that, _1gtk_1radio_1menu_1item_1new_1with_1label_FUNC); -- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in gtk+2.0 package in Ubuntu: Triaged Status in unity package in Ubuntu: Invalid Status in gtk+2.0 package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+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
Re: [Dx-packages] [Bug 1072206] Re: [nvidia] Window content is black or transparent
Nope. Still happens to me too. On Fri, Sep 4, 2015, 8:50 AM Andrea Azzarone wrote: > Hi Gilles, > > looks weird, you are the first one to reconfirm the bug. How can you > reproduce it? Can you write it all the steps? Thanks. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1072206 > > Title: > [nvidia] Window content is black or transparent > > Status in Compiz: > Fix Released > Status in Compiz 0.9.11 series: > Fix Committed > Status in NVIDIA Drivers Ubuntu: > Invalid > Status in Unity: > Invalid > Status in compiz package in Ubuntu: > Fix Released > Status in unity package in Ubuntu: > Invalid > Status in compiz source package in Trusty: > Fix Released > > Bug description: > [ Impact ] > > With nVidia hardware from time to time window content is rendered > black or transparent. The problem manifests more frequently as > session uptime increases. > > Apparently the problem was caused by textures being cached and not > freed, resulting in memory exhaustion conditions. It turns out the > texture caching is unnecessary anyway. > > [ Test Case ] > > Verification requires an nVidia GPU with proprietary drivers. The > problem can not be reproduced at will, only after some time (depending > on resident GPU memory and usage) and even then only randomly and > unreliably. > > [ Regression Potential ] > > It is unlikely this change has the potential to introduce new > regressions. > > [ Other Info ] > > Fix was cherry-picked from the Ubuntu "Vivid Vervet" dev relase where > it has been in use for some weeks without problem. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/compiz/+bug/1072206/+subscriptions > -- 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/1072206 Title: [nvidia] Window content is black or transparent Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Committed Status in NVIDIA Drivers Ubuntu: Invalid Status in Unity: Invalid Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in compiz source package in Trusty: Fix Released Bug description: [ Impact ] With nVidia hardware from time to time window content is rendered black or transparent. The problem manifests more frequently as session uptime increases. Apparently the problem was caused by textures being cached and not freed, resulting in memory exhaustion conditions. It turns out the texture caching is unnecessary anyway. [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly and unreliably. [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu "Vivid Vervet" dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+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 1072206] Re: [nvidia] Window content is black or transparent
Hi Gilles, looks weird, you are the first one to reconfirm the bug. How can you reproduce it? Can you write it all the steps? Thanks. -- 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/1072206 Title: [nvidia] Window content is black or transparent Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Committed Status in NVIDIA Drivers Ubuntu: Invalid Status in Unity: Invalid Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in compiz source package in Trusty: Fix Released Bug description: [ Impact ] With nVidia hardware from time to time window content is rendered black or transparent. The problem manifests more frequently as session uptime increases. Apparently the problem was caused by textures being cached and not freed, resulting in memory exhaustion conditions. It turns out the texture caching is unnecessary anyway. [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly and unreliably. [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu "Vivid Vervet" dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+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 1492174] Re: Notebook does not shutdown when battery is critically low
** Package changed: ubuntu => d-conf (Ubuntu) ** Tags removed: bot-comment -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1492174 Title: Notebook does not shutdown when battery is critically low Status in d-conf package in Ubuntu: New Bug description: When the battery is discharged completely, notebooks hibernate instead of shutting down. To prevent the battery from getting damaged, it is important that the machine shuts down. This happens in ubuntu 15.04, power behavior was correct in 14.04 and in 14.10. In ubuntu 14.04 default gsettings for critical-battery-action are set to 'suspend'. In ubuntu 15.04 default gsettings for critical-battery-action are set to 'shutdown'. In ubuntu 15.10 default gsettings for critical-battery-action are set to 'suspend' back again. So the critical-battery-action setting has to be 'suspend' to shutdown notebooks completely! This seems to be a little bug in gsettings, as 'suspend' setting performs 'shutdown' action. It leads to unwanted behavior of machines when users change power settings by executing: "gsettings set org.gnome.settings-daemon.plugins.power critical-battery-action shutdown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1492174/+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 1047517] Re: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc()
** Changed in: gvfs (Ubuntu) Status: Confirmed => Invalid ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1047517 Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc() Status in Unity: Invalid Status in Unity 7.2 series: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: Invalid Status in unity package in Ubuntu: Invalid Bug description: Compiz crashed when I was trying the Preview. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity 6.4.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 CrashCounter: 1 Date: Fri Sep 7 18:49:48 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb0d448c2 : mov0x4(%eax),%ebp PC (0xb0d448c2) ok source "0x4(%eax)" (0x0005) not located in a known VMA region (needed readable region)! destination "%ebp" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: g_mount_spec_to_dbus_with_path () from /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() UpgradeStatus: Upgraded to quantal on 2012-09-07 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1047517/+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 1492174] [NEW] Notebook does not shutdown when battery is critically low
You have been subscribed to a public bug: When the battery is discharged completely, notebooks hibernate instead of shutting down. To prevent the battery from getting damaged, it is important that the machine shuts down. This happens in ubuntu 15.04, power behavior was correct in 14.04 and in 14.10. In ubuntu 14.04 default gsettings for critical-battery-action are set to 'suspend'. In ubuntu 15.04 default gsettings for critical-battery-action are set to 'shutdown'. In ubuntu 15.10 default gsettings for critical-battery-action are set to 'suspend' back again. So the critical-battery-action setting has to be 'suspend' to shutdown notebooks completely! This seems to be a little bug in gsettings, as 'suspend' setting performs 'shutdown' action. It leads to unwanted behavior of machines when users change power settings by executing: "gsettings set org.gnome.settings-daemon.plugins.power critical-battery-action shutdown" ** Affects: d-conf (Ubuntu) Importance: Undecided Status: New ** Tags: battery bot-comment management power -- Notebook does not shutdown when battery is critically low https://bugs.launchpad.net/bugs/1492174 You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1047517] Re: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc()
** Description changed: - Unity crashed when i was trying the Preview. + Compiz crashed when I was trying the Preview. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity 6.4.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 CrashCounter: 1 Date: Fri Sep 7 18:49:48 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcCmdline: compiz ProcEnviron: - PATH=(custom, no user) - LANG=de_DE.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + LANG=de_DE.UTF-8 + SHELL=/bin/bash SegvAnalysis: - Segfault happened at: 0xb0d448c2 : mov0x4(%eax),%ebp - PC (0xb0d448c2) ok - source "0x4(%eax)" (0x0005) not located in a known VMA region (needed readable region)! - destination "%ebp" ok - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0xb0d448c2 : mov0x4(%eax),%ebp + PC (0xb0d448c2) ok + source "0x4(%eax)" (0x0005) not located in a known VMA region (needed readable region)! + destination "%ebp" ok + Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: - g_mount_spec_to_dbus_with_path () from /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so - ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so - ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so - ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so - ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so + g_mount_spec_to_dbus_with_path () from /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so + ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so + ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so + ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so + ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() UpgradeStatus: Upgraded to quantal on 2012-09-07 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Project changed: unity => hundredpapercuts ** Changed in: hundredpapercuts Milestone: 7.3.3 => None ** No longer affects: hundredpapercuts ** No longer affects: unity (Ubuntu) ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Status: New => Invalid ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New => Invalid ** Changed in: unity (Ubuntu) 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/1047517 Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc() Status in Unity: Invalid Status in Unity 7.2 series: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: Invalid Status in unity package in Ubuntu: Invalid Bug description: Compiz crashed when I was trying the Preview. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity 6.4.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 CrashCounter: 1 Date: Fri Sep 7 18:49:48 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb0d448c2 : mov0x4(%eax),%ebp PC (0xb0d448c2) ok source "0x4(%eax)" (0x0005) not located in a known VMA region (needed readable region)! destination "%ebp" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: g_mount_spec_to_dbus_with_path () from /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() UpgradeStatus: Upgraded to quantal on 2012-09-07 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1047517/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More hel
[Dx-packages] [Bug 1072206] Re: [nvidia] Window content is black or transparent
Hi, I wasn't following this bug until today when I thought enough is enough. (It's been annoying me for quite some time) I'm skeptical of the "fix released" status, since I am *still* experiencing the described behaviour: black or transparent windows. Ubuntu 14.04 compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 nvidia-304-updates 304.125-0ubuntu0.0.2 Thanks to everybody for investigating this non-critical but very annoying bug! -- 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/1072206 Title: [nvidia] Window content is black or transparent Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Committed Status in NVIDIA Drivers Ubuntu: Invalid Status in Unity: Invalid Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in compiz source package in Trusty: Fix Released Bug description: [ Impact ] With nVidia hardware from time to time window content is rendered black or transparent. The problem manifests more frequently as session uptime increases. Apparently the problem was caused by textures being cached and not freed, resulting in memory exhaustion conditions. It turns out the texture caching is unnecessary anyway. [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly and unreliably. [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu "Vivid Vervet" dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+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 1359211] Re: Mouse cursor tiny when hovering unity elements in high DPI mode
** Changed in: unity (Ubuntu) Importance: Undecided => Medium ** Changed in: unity (Ubuntu) Importance: Medium => 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/1359211 Title: Mouse cursor tiny when hovering unity elements in high DPI mode Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: On a high DPI screen (220 DPI) the mouse cursor is really tiny when hovering unity elements. There are various keys in dconf to change the cursor's scale factor or size. I've managed to change it in a way that it looks normal when inside application windows, but its still tiny when on unity elements. I think this should be set automatically by the scale factor setting in system settings. (Using unity 7.3.1+14.10.20140811-0ubuntu1) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1359211/+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 1390625] Re: mouse cursor gets corrupted
Another bunch of updates + a reboot later… intermediate state of mouse of cursor is ok BUT once the drag and drop (to move a folder) is done the "double-cursored-with-a-folder-icon" is back as mouse-cursor… ** Attachment added: "Other Photo" https://bugs.launchpad.net/mesa/+bug/1390625/+attachment/4457265/+files/DSC_0063.jpg -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Fix Released Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when drag&dropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a drag&drop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ 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: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO 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: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+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 1367818] Re: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state.
The icon has changed, pls use this one. thx https://www.dropbox.com/work/Apps%20and%20Platform%20Team/9.%20Icons/Suru%20Icon%20Theme/status/81?preview =volume-min.png ** Description changed: - "When the sound is muted, the volume icon to the left of the volume slider should have a red "/" running through it." - "Add an explicit "Mute" button to the sound indicator menu." - "Pressing and holding the icon to the left of the volume slider should mute volume straight away." - -- - Desired resolution: Once the sound is muted icon should change but not the colour. We have an icon for muted https://www.dropbox.com/s/ciawzsrobdlk3fn/audio-output-none-panel.png?dl=0 + Desired resolution: Once the sound is muted icon should change but not the colour. We have an icon for muted + https://www.dropbox.com/work/Apps%20and%20Platform%20Team/9.%20Icons/Suru%20Icon%20Theme/status/81?preview=volume-min.png The behaviour has already been illustrated by MPT -- 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/1367818 Title: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state. Status in Canonical System Image: Fix Released Status in Ubuntu UX: Fix Committed Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu RTM: Fix Released Bug description: - "When the sound is muted, the volume icon to the left of the volume slider should have a red "/" running through it." - "Add an explicit "Mute" button to the sound indicator menu." - "Pressing and holding the icon to the left of the volume slider should mute volume straight away." -- Desired resolution: Once the sound is muted icon should change but not the colour. We have an icon for muted https://www.dropbox.com/work/Apps%20and%20Platform%20Team/9.%20Icons/Suru%20Icon%20Theme/status/81?preview=volume-min.png The behaviour has already been illustrated by MPT To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1367818/+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 1390625] Re: mouse cursor gets corrupted
Not totally fixed : the "intermediate" state of mouse cursor is wrong - while holding left click during dragging. ** Attachment added: "photo of screen, not screenshot" https://bugs.launchpad.net/ubuntu/+source/xorg-lts-utopic/+bug/1390625/+attachment/4457252/+files/DSC_0062.jpg -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Fix Released Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when drag&dropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a drag&drop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ 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: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO 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: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+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 1437192] Re: FTBFS with Qt 5.5: "cannot find -linput"
This bug was fixed in the package appmenu-qt5 - 0.3.0+15.10.20150903-0ubuntu1 --- appmenu-qt5 (0.3.0+15.10.20150903-0ubuntu1) wily; urgency=medium [ Timo Jyrinki ] * Build dep on libinput-dev for Qt 5.5. (LP: #1437192) -- CI Train Bot Thu, 03 Sep 2015 10:15:35 + ** Changed in: appmenu-qt5 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1437192 Title: FTBFS with Qt 5.5: "cannot find -linput" Status in appmenu-qt5 package in Ubuntu: Fix Released Status in qtubuntu package in Ubuntu: Fix Released Bug description: There seems to be some sort of new dependency, even though none were added in Qt 5.5's own build dependencies: --- g++ -std=c++11 -Wl,-no-undefined -Wl,-Bsymbolic-functions -Wl,-z,relro -shared -o libqpa-ubuntumirclient.so backingstore.o clipboard.o glcontext.o input.o integration.o nativeinterface.o platformservices.o plugin.o screen.o theme.o window.o moc_clipboard.o moc_input.o moc_plugin.o moc_screen.o moc_window.o -lmirclient -lmircommon -lubuntu_application_api -lQt5PlatformSupport -lfontconfig -lfreetype -lgthread-2.0 -pthread -lglib-2.0 -linput -lxkbcommon -ludev -lmtdev -lEGL -lQt5Gui -lQt5Sensors -lQt5DBus -lQt5Core -lGLESv2 -lpthread /usr/bin/ld: cannot find -linput --- That is, qtubuntu and appmenu-qt5 should apparently have a build dependency on 'libinput-dev': https://launchpad.net/ubuntu/+source/libinput More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting appmenu-qt5: https://launchpadlibrarian.net/202748418/buildlog_ubuntu-vivid-amd64.appmenu-qt5_0.3.0%2B15.04.20150121-0ubuntu4~vivid1~test1~qt550alpha1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1437192/+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 1437192] Re: FTBFS with Qt 5.5: "cannot find -linput"
** Branch linked: lp:ubuntu/wily-proposed/appmenu-qt5 -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1437192 Title: FTBFS with Qt 5.5: "cannot find -linput" Status in appmenu-qt5 package in Ubuntu: New Status in qtubuntu package in Ubuntu: Fix Released Bug description: There seems to be some sort of new dependency, even though none were added in Qt 5.5's own build dependencies: --- g++ -std=c++11 -Wl,-no-undefined -Wl,-Bsymbolic-functions -Wl,-z,relro -shared -o libqpa-ubuntumirclient.so backingstore.o clipboard.o glcontext.o input.o integration.o nativeinterface.o platformservices.o plugin.o screen.o theme.o window.o moc_clipboard.o moc_input.o moc_plugin.o moc_screen.o moc_window.o -lmirclient -lmircommon -lubuntu_application_api -lQt5PlatformSupport -lfontconfig -lfreetype -lgthread-2.0 -pthread -lglib-2.0 -linput -lxkbcommon -ludev -lmtdev -lEGL -lQt5Gui -lQt5Sensors -lQt5DBus -lQt5Core -lGLESv2 -lpthread /usr/bin/ld: cannot find -linput --- That is, qtubuntu and appmenu-qt5 should apparently have a build dependency on 'libinput-dev': https://launchpad.net/ubuntu/+source/libinput More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting appmenu-qt5: https://launchpadlibrarian.net/202748418/buildlog_ubuntu-vivid-amd64.appmenu-qt5_0.3.0%2B15.04.20150121-0ubuntu4~vivid1~test1~qt550alpha1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1437192/+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