[Dx-packages] [Bug 922129] Re: notify-osd crashed with signal 5 in _XReply()
** Tags removed: systemd-boot -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/922129 Title: notify-osd crashed with signal 5 in _XReply() Status in “notify-osd” package in Ubuntu: Confirmed Bug description: ? ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: notify-osd 0.9.32-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-10.18-generic-pae 3.2.1 Uname: Linux 3.2.0-10-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Thu Jan 26 11:55:47 2012 EcryptfsInUse: Yes ExecutablePath: /usr/lib/notify-osd/notify-osd GtkTheme: Ambiance IconTheme: ubuntu-mono-dark InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: LENOVO 42992PG ProcCmdline: /usr/lib/notify-osd/notify-osd ProcEnviron: LC_TIME=en_US.UTF-8 LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-10-generic-pae root=UUID=cf836212-0e99-4a2c-aee5-945d37d7dbef ro quiet splash resume=UUID=138776a3-daa1-4cf5-b056-028c8094244e vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.6+10ubuntu1 libgl1-mesa-glx 7.11-0ubuntu4 libdrm2 2.4.30-1ubuntu1 xserver-xorg-video-intel 2:2.17.0-1ubuntu3 xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu1 Signal: 5 SourcePackage: notify-osd StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6 XGetGeometry () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 gdk_window_get_geometry () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 Title: notify-osd crashed with signal 5 in _XReply() UdevDb: Error: [Errno 2] No such file or directory UpgradeStatus: Upgraded to precise on 2011-12-16 (41 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers WindowManager: No value set for `/desktop/gnome/session/required_components/windowmanager' dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 42992PG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn42992PG:pvrThinkPadX220Tablet:rvnLENOVO:rn42992PG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42992PG dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/922129/+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 1389336] Re: Use geoclue-2.0
Hey Michael, I though one of the issue is that the new version doesn't support plugins the same way, which means that if we port code we can't use our ubuntu geoip provider anymore. Did we decide it's fine to stop using that backend? -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in “empathy” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Status in “libunity-webapps” package in Ubuntu: New Status in “qtlocation-opensource-src” package in Ubuntu: New Status in “ubuntu-geoip” package in Ubuntu: New Status in “webkitgtk” package in Ubuntu: New Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+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 1385413] Re: unity_support_test has stopped unexpectedly
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/1385413 Title: unity_support_test has stopped unexpectedly Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Status in “virtualbox” package in Ubuntu: Confirmed Bug description: Performed the upgrade from Trusty to Utopic, after the required restart of the computer the 'Report a problem' dialog poped up saying that unity_support_test has stopped unexpectedly. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8 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 Date: Fri Oct 24 18:27:07 2014 DistUpgraded: 2014-10-24 17:54:14,577 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 4.3.18, 3.16.0-23-generic, i686: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-09-25 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=664043af-2956-48b2-baca-3609d1ee45c3 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: unity UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code -11: libGL error: pci id for fd 4: 80ee:beef, driver (null) OpenGL Warning: Assertion failed: thread && thread->netServer.conn && thread->netServer.conn->type==CR_VBOXHGCM && thread->bInjectThread, file /mnt/tinderbox/add-4.3/src/VBox/Additions/common/crOpenGL/pack/packspu_misc.c, line 562 UpgradeStatus: Upgraded to utopic on 2014-10-24 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 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 Oct 24 18:18:10 2014 xserver.configfile: default xserver.errors: AIGLX error: vboxvideo does not export required DRI extension AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: vboxvideo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1385413/+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 1385413] Re: unity_support_test has stopped unexpectedly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: virtualbox (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/1385413 Title: unity_support_test has stopped unexpectedly Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Status in “virtualbox” package in Ubuntu: Confirmed Bug description: Performed the upgrade from Trusty to Utopic, after the required restart of the computer the 'Report a problem' dialog poped up saying that unity_support_test has stopped unexpectedly. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8 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 Date: Fri Oct 24 18:27:07 2014 DistUpgraded: 2014-10-24 17:54:14,577 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 4.3.18, 3.16.0-23-generic, i686: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-09-25 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=664043af-2956-48b2-baca-3609d1ee45c3 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: unity UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code -11: libGL error: pci id for fd 4: 80ee:beef, driver (null) OpenGL Warning: Assertion failed: thread && thread->netServer.conn && thread->netServer.conn->type==CR_VBOXHGCM && thread->bInjectThread, file /mnt/tinderbox/add-4.3/src/VBox/Additions/common/crOpenGL/pack/packspu_misc.c, line 562 UpgradeStatus: Upgraded to utopic on 2014-10-24 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 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 Oct 24 18:18:10 2014 xserver.configfile: default xserver.errors: AIGLX error: vboxvideo does not export required DRI extension AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: vboxvideo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1385413/+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 1385413] Re: unity_support_test has stopped unexpectedly
I see the same. In VirtualBox 4.3.12 on Windows 7, with a Ubuntu 14.10 guest, unity_support_test dies when 3D acceleration is enabled: $ /usr/lib/nux/unity_support_test -p libGL error: pci id for fd 4: 80ee:beef, driver (null) OpenGL Warning: Assertion failed: thread && thread->netServer.conn && thread->netServer.conn->type==CR_VBOXHGCM && thread->bInjectThread, file /mnt/tinderbox/add-4.3/src/VBox/Additions/common/crOpenGL/pack/packspu_misc.c, line 562 Segmentation fault (core dumped) A gdb backtrace, in case it's of use: #0 0x7336a5ba in ?? () from /usr/lib/x86_64-linux-gnu/VBoxOGLpackspu.so #1 0x7367f3c5 in ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so #2 0x736a0f8c in ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so #3 0x736a57eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so #4 0x74c4d0a5 in start_thread (arg=0x722c0700) at pthread_create.c:309 #5 0x76d2484d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 -- 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/1385413 Title: unity_support_test has stopped unexpectedly Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Status in “virtualbox” package in Ubuntu: Confirmed Bug description: Performed the upgrade from Trusty to Utopic, after the required restart of the computer the 'Report a problem' dialog poped up saying that unity_support_test has stopped unexpectedly. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8 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 Date: Fri Oct 24 18:27:07 2014 DistUpgraded: 2014-10-24 17:54:14,577 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 4.3.18, 3.16.0-23-generic, i686: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-09-25 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=664043af-2956-48b2-baca-3609d1ee45c3 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: unity UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code -11: libGL error: pci id for fd 4: 80ee:beef, driver (null) OpenGL Warning: Assertion failed: thread && thread->netServer.conn && thread->netServer.conn->type==CR_VBOXHGCM && thread->bInjectThread, file /mnt/tinderbox/add-4.3/src/VBox/Additions/common/crOpenGL/pack/packspu_misc.c, line 562 UpgradeStatus: Upgraded to utopic on 2014-10-24 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 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 Oct 24 18:18:10 2014 xserver.configfile: default xserver.errors: AIGLX error: vboxvideo does not export required DRI extension AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: vboxv
[Dx-packages] [Bug 1390040] Re: unity-panel-service crashed with SIGSEGV in strrchr()
*** This bug is a duplicate of bug 1332968 *** https://bugs.launchpad.net/bugs/1332968 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1332968, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1390040/+attachment/4254427/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1390040/+attachment/4254429/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1390040/+attachment/4254432/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1390040/+attachment/4254433/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1390040/+attachment/4254434/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1390040/+attachment/4254435/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1390040/+attachment/4254436/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1332968 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1390040 Title: unity-panel-service crashed with SIGSEGV in strrchr() Status in “unity” package in Ubuntu: New Bug description: My menu bars were showing and disappearing multiple times within 10s or so. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity-services 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.18.0-031800rc3-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Nov 6 12:21:46 2014 ExecutablePath: /usr/lib/unity/unity-panel-service ProcCmdline: /usr/lib/unity/unity-panel-service SegvAnalysis: Segfault happened at: 0x7fb6d35151f5 : movdqu (%rdi),%xmm0 PC (0x7fb6d35151f5) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: strrchr () at ../sysdeps/x86_64/strrchr.S:32 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: unity-panel-service crashed with SIGSEGV in strrchr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1390040/+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 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
** Changed in: nux/trusty Status: In Progress => Fix Committed -- 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/1337244 Title: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout() Status in Nux: Fix Committed Status in Nux trusty series: Fix Committed Status in “nux” package in Ubuntu: Fix Released Status in “nux” source package in Trusty: Fix Released Bug description: [Impact] Unity crashes when unlocking the session [Test case 1] 1. Lock the session 2. Unlock the session 3. No crash should happen [Test case 2] 1. Use unity in multi-monitor setup 2. Lock the session 3. Detach one of the monitors 4. Make sure the lockscreen updates (sometimes it's needed to switch to tty1 and back) 5. No crash should happen [Regression potential] None Hi, this is basically the same bug as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing this bug on trusty, with the latest Unity version (unity 7.2.1+14.04.20140513-0ubuntu2). I already mentioned in that bug that I was still seeing it quite a while ago, but got no reply to that. Crashes are being experienced in multiple machines, while unlocking the screen. The stacktraces vary, but they always fail in the same function and same line. First stacktrace: #0 0x0410 in ?? () #1 0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x22c1990) at ./WindowThread.cpp:318 #2 0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x22c1990, clip=...) at ./WindowThread.cpp:1627 #3 0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd4c0c20748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd4d4f2eed4 in PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) () from /usr/lib/compiz/libopengl.so #7 0x7fd4d556944f in CompositeScreen::paint(std::list >&, unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd4e12c053d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fd4df29ece5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd4df29f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd4e127b0eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () Second stacktrace (different machine): #0 0x7f0058407ed0 in nux_area_accessible_check_pending_notification () from /usr/lib/compiz/libunityshell.so #1 0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x1d530e0) at ./WindowThread.cpp:318 #2 0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627 #3 0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7f00583e6748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7f00705e2ed4 in PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) () from /usr/lib/compiz/libopengl.so #7 0x7f0070c1d44f in CompositeScreen::paint(std::list >&, unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7f007879b53d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123
[Dx-packages] [Bug 1228093] Re: Dash content flickers when the touchpad is used to scroll it.
** Changed in: nux/trusty Status: In Progress => Fix Committed -- 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/1228093 Title: Dash content flickers when the touchpad is used to scroll it. Status in Nux: Fix Committed Status in Nux trusty series: Fix Committed Status in “nux” package in Ubuntu: Fix Released Status in “nux” source package in Trusty: Fix Released Bug description: [Impact] Dash content flickers when two-finger scrolling on the touchpad [Test case] 1. Enable two fingers scroll from Unity Control Center -> Mouse and Touchpad 2. Open the unity dash, expand the search results and start scrolling vertically 3. Content should not flicker and should ignore horizontal scroll events [Regression potential] Scrolling on dash content does not work properly To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1228093/+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
Thanks, it seems indeed another problem. Can you please open another bug (like "unity crashes in unity::UnityScreen::paintDisplay", using ubuntu-bug /var/crash/_usr_bin_compiz.1000.crash)? It would also be nice, if you could (from gdb), do: print gpu_device print *gpu_device print gpu_device->backup_texture0_ print *(gpu_device->backup_texture0_) print gpu_device->backup_texture0_->_NumMipLevel print gpu_device->backup_texture0_->_SurfaceArray -- 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= LANG=en_US.UTF-8 XDG_RUNTIME_DIR= 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 sha
[Dx-packages] [Bug 1297150] Re: Unity "quit" button doesn't do anything when Wine application is frozen
I'm not sure whether this is a bug in Unity... When launching a wine application here, then killall -STOP it.exe, the window freezes and when trying to close it the unity force-quit dialog shows up as it happens with other applications. And it also seems to do what is expected. ** Changed in: unity (Ubuntu) Status: New => Incomplete ** Changed in: unity Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1297150 Title: Unity "quit" button doesn't do anything when Wine application is frozen Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Status in “wine1.6” package in Ubuntu: Triaged Bug description: A Wine app that freezes up can be in a state where it is unkillable by using the interface. Killing the process in a terminal, or doing a wineserver -k command, can solve the situation, however there is no way to do this within Unity even after repeated "quit" demands. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1297150/+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
** Also affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: Confirmed => Incomplete ** Changed in: unity Status: Confirmed => Incomplete ** Tags added: lockscreen -- 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: Incomplete Status in “unity” package in Ubuntu: Incomplete Status in “unity-settings-daemon” package in Ubuntu: New 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 1379031] Re: Screen doesn't lock anymore
Mh, is Super+L working instead? ** Tags added: lockscreen ** Changed in: unity Status: New => Incomplete ** Changed in: unity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1379031 Title: Screen doesn't lock anymore Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: The automatic screen locking doesn't work anymore in utopic. I can reproduce this on two different machines. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-desktop 1.327 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 8 16:56:44 2014 InstallationDate: Installed on 2014-07-25 (75 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: ubuntu-meta SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to utopic on 2014-09-04 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1379031/+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 1379474] Re: unity://running-apps position in launcher ignored during startup
** Changed in: unity Status: New => Triaged ** Changed in: unity (Ubuntu) Status: New => Triaged ** Changed in: unity Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity (Ubuntu) Importance: Undecided => Medium ** Changed in: unity Importance: Undecided => Medium ** Changed in: unity Milestone: None => 7.3.1 ** Changed in: unity/7.2 Importance: Undecided => Medium ** Changed in: unity/7.2 Status: New => Triaged ** Changed in: unity/7.2 Milestone: None => 7.2.4 ** Changed in: unity/7.2 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1379474 Title: unity://running-apps position in launcher ignored during startup Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: IN SHORT: The position of unity://running-apps in the dconf setting /com/canonical/unity/launcher/favorites is being ignored during startup (login). DETAILED INFORMATION: I will explain this using an example, which makes it easier to explain and understand. Suppose that I have Nautilus and Firefox (+ workspaces and devices) pinned to the Unity launcher, in that order. When I open, for example, gedit, its icon appears below Firefox. "dconf read /com/canonical/unity/launcher/favorites" returns: ['application://nautilus.desktop', 'application://firefox.desktop', 'unity://running-apps', 'unity://expo-icon', 'unity://devices'] If I move Firefox's icon to below gedit (not pinned), any new applications that I open that are not pinned appear above Firefox's icon, even after closing gedit. "dconf read /com/canonical/unity/launcher/favorites" now returns: ['application://nautilus.desktop', 'unity://running-apps', 'unity://expo-icon', 'unity://devices', 'application://firefox.desktop'] 'unity://running-apps' represents the applications that are not pinned, and defines where those applications should appear in the launcher. At least that's what it looks like. The problem is that, after restarting the session or rebooting, 'unity://running-apps' is ignored, and apps that are not pinned appear below the last "application://..." icon, even if it's the last one. But "dconf read /com/canonical/unity/launcher/favorites" still returns: ['application://nautilus.desktop', 'unity://running-apps', 'unity://expo-icon', 'unity://devices', 'application://firefox.desktop'] The "favorites" are also maintained in gsettings: "gsettings get com.canonical.Unity.Launcher favorites" returns the same results above. IMPACT: Because of this bug, users cannot pin applications to the "bottom" of the launcher, as unpinned apps will always appear below the last pinned application. 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: Thu Oct 9 19:14:09 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-17 (114 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1379474/+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 1377297] Re: Spread (Super+W) breaks minimized windows rendering
I can't reproduce this, are you using nvidia? ** Changed in: unity Status: New => Incomplete ** Changed in: unity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1377297 Title: Spread (Super+W) breaks minimized windows rendering Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: If you use spread while some of your windows are minimized and you try to open one of them after closing the spread, they are rendered badly (a black rectangle). Test case: 1-Minimize a terminal window for instance 2-Press Super+W to enable spread 3-Press again Super+W to close the spread 4-Click on your terminal window on your launcher To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1377297/+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 1380906] Re: Middle-mouse-button paste no longer works in 14.04
** No longer affects: unity ** Also affects: ubuntu (Ubuntu) Importance: Undecided Status: New ** No longer affects: unity (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1380906 Title: Middle-mouse-button paste no longer works in 14.04 Status in “ubuntu” package in Ubuntu: New Bug description: After the upgrade to 14.04 the paste of the previously highlighted text no longer seems to work. And since it is a rather important feature for me, it makes my job much more difficult. What i do: Highlight some text Press middle button on the mouse What i expect to happen: The highlighted text needs to appear where i click What actually happens: /dev/null 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: Tue Oct 14 10:12:26 2014 InstallationDate: Installed on 2014-10-02 (11 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu/+bug/1380906/+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 1386872] Re: Incorrect termination Firefox when shutdown Ubuntu
** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: unity Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1386872 Title: Incorrect termination Firefox when shutdown Ubuntu Status in Unity: Won't Fix Status in “gnome-session” package in Ubuntu: New Status in “unity” package in Ubuntu: Won't Fix Bug description: 1. In Firefox go to Preference -> General tab, choose Show my windows and tabs from last time in When Firefox starts field. 2. Shutdown Ubuntu 3. Start Ubuntu 4. Open Firefox Actual result: Firefox opens with message "Firefox was not closed properly" ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 22:20:52 2014 InstallationDate: Installed on 2014-10-25 (3 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386872/+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 1385441] Re: Can't unlock the screen in Ubuntu 14.10
** Tags added: lockscreen ** Changed in: unity Status: New => Incomplete ** Changed in: unity (Ubuntu) Status: New => Incomplete ** Changed in: unity Assignee: (unassigned) => Andrea Azzarone (andyrock) -- 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/1385441 Title: Can't unlock the screen in Ubuntu 14.10 Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: The bug is similar to the one reported in https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1314095 (Unity Lockscreen in 14.04 can't unlock when using LDAP account) The difference is that I don't have an LDAP account just a local one, the box was working well in 14.04 and after upgrade to 14.10 I can't unlock the screen. Changing /sbin/unix_chkpwd to setuid does the trick too. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1385441/+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 1385866] Re: Unity mouse clicks not honoring xorg.conf settings
** No longer affects: unity (Ubuntu) ** Also affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New ** No longer affects: unity -- 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/1385866 Title: Unity mouse clicks not honoring xorg.conf settings Status in “unity-settings-daemon” package in Ubuntu: New Bug description: My laptop has a synaptics compatible mousepad which unity by default configures with the bottom right corner as right click and top right corner as middle click. This is annoying for a large number of reasons because Unity also fails to disable click while typing in most of the cases (the time threshold is too short). Anyway. I have my xorg.conf set to disable this corners: # /usr/share/X11/xorg.conf.d/50-synaptics.conf Section "InputClass" Identifier "touchpad catchall" Driver "synaptics" MatchIsTouchpad "on" Option "RBCornerButton" "0" Option "RTCornerButton" "0" Option "VertEdgeScroll" "off" Option "HorizEdgeScroll" "off" This works in any other environment but Unity. Please fix this annoying behavior. 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 26 09:25:50 2014 InstallationDate: Installed on 2014-02-18 (250 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-21 (188 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1385866/+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 1386714] Re: Window Spread search conflicts in maximization of open windows
*** This bug is a duplicate of bug 1316265 *** https://bugs.launchpad.net/bugs/1316265 ** This bug has been marked a duplicate of bug 1316265 Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering -- 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/1386714 Title: Window Spread search conflicts in maximization of open windows Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: To reproduce the bug: 1. open multiple windows; 2. open Window Spread/Scale (Super+W); 3. search for a window and select it; 4. now switch to another window without using Window Spread again; 5. try to maximize/unmaximize window. You will see the maximized window is expanded horizontally and vertically, but there are two title bars i.e. the window keeps its title bar separate from the top indicator bar even after maximization. This bug doesn't affect windows opened after window spread search. Opening Window Spread again without searching will fix the bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 Uname: Linux 3.16.0-031600-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: Tue Oct 28 17:28:34 2014 InstallationDate: Installed on 2014-10-02 (25 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386714/+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 1387711] Re: Unity doesn't respect NET_WM_ALLOWED_ACTIONS
** Tags added: decorations ** Tags removed: decorations ** Tags added: new-decorations -- 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/1387711 Title: Unity doesn't respect NET_WM_ALLOWED_ACTIONS Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: According to http://standards.freedesktop.org/wm-spec/latest/ar01s05.html : Atoms present in the list indicate allowed actions, atoms not present in the list indicate actions that are not supported for this window. The Window Manager MUST keep this property updated to reflect the actions which are currently "active" or "sensitive" for a window. However, if I set NET_WM_ALLOWED_ACTIONS to a list not containing NET_WM_ACTION_RESIZE (along with the MAXIMIZE atoms), I can still resize/maximize the window using the mouse. Only by forcing min and max size in the WM normal hints can I achieve the desired behavior. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,compiztoolbox,vpswitch,move,gnomecompat,grid,place,regex,imgpng,resize,annotate,mousepoll,wobbly,session,animation,fade,animationaddon,cube,rotate,workarounds,unitymtgrabhandles,cubeaddon,trailfocus,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Thu Oct 30 15:19:30 2014 InstallationDate: Installed on 2011-05-11 (1267 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-10-27 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1387711/+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 1387711] Re: Unity doesn't respect NET_WM_ALLOWED_ACTIONS
We do care about that paramter, and so does compiz, but it looks like that your test case is wrong, in fact using xprop on it, I'm getting this output http://pastebin.ubuntu.com/8851664/ (and as you can see _NET_WM_ACTION_RESIZE is present there) ** Changed in: unity Status: New => Incomplete ** Changed in: unity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1387711 Title: Unity doesn't respect NET_WM_ALLOWED_ACTIONS Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: According to http://standards.freedesktop.org/wm-spec/latest/ar01s05.html : Atoms present in the list indicate allowed actions, atoms not present in the list indicate actions that are not supported for this window. The Window Manager MUST keep this property updated to reflect the actions which are currently "active" or "sensitive" for a window. However, if I set NET_WM_ALLOWED_ACTIONS to a list not containing NET_WM_ACTION_RESIZE (along with the MAXIMIZE atoms), I can still resize/maximize the window using the mouse. Only by forcing min and max size in the WM normal hints can I achieve the desired behavior. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,compiztoolbox,vpswitch,move,gnomecompat,grid,place,regex,imgpng,resize,annotate,mousepoll,wobbly,session,animation,fade,animationaddon,cube,rotate,workarounds,unitymtgrabhandles,cubeaddon,trailfocus,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Thu Oct 30 15:19:30 2014 InstallationDate: Installed on 2011-05-11 (1267 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-10-27 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1387711/+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 1386872] Re: Incorrect termination Firefox when shutdown Ubuntu
** Changed in: gnome-session (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/1386872 Title: Incorrect termination Firefox when shutdown Ubuntu Status in Unity: Won't Fix Status in “gnome-session” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Won't Fix Bug description: 1. In Firefox go to Preference -> General tab, choose Show my windows and tabs from last time in When Firefox starts field. 2. Shutdown Ubuntu 3. Start Ubuntu 4. Open Firefox Actual result: Firefox opens with message "Firefox was not closed properly" ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 22:20:52 2014 InstallationDate: Installed on 2014-10-25 (3 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386872/+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 1389220] Re: Moving windows cause jump so that title bar is under the compiz main title bar of the desktop below the current, i.e. window unmovable
** Changed in: unity Status: New => Triaged ** Changed in: unity (Ubuntu) Status: New => Triaged ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New ** No longer affects: unity (Ubuntu) ** Changed in: unity Status: Triaged => Won't Fix ** Changed in: compiz (Ubuntu) Status: New => Triaged ** Changed in: unity Status: Won't Fix => Invalid ** Also affects: compiz Importance: Undecided Status: New ** Changed in: compiz Status: New => Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1389220 Title: Moving windows cause jump so that title bar is under the compiz main title bar of the desktop below the current, i.e. window unmovable Status in Compiz: Triaged Status in Unity: Invalid Status in “compiz” package in Ubuntu: Triaged Bug description: Moving windows (e.g `gnome-terminal` or `gnome-system-monitor`) with mouse dragging sometimes causes the window to jump to the desktop (I have 4) below the current (where the move action takes place) and its title bar then to be placed right under the man title bar of the compiz desktop (the one which switches to the title bar of the current active window). It is then unmovable. The jump occurs when the lower margin of the titlebar reaches ~2 cm over the lower screen border. When I click on the desktop switcher applet I can see that the window is display like its titlebar would still be on the upper screen. The mouse is not movable below the lower screen border (I can still see the tip of the cursor at the buttom). Changing the resolution doesn't change the behavior. It occurs on both desktops which are on the screen of my laptop as well as on screen which are attached via D-SUB. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.16.7-031607-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Tue Nov 4 13:56:26 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3904] MachineType: LENOVO 20221 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.7-031607-generic root=ZFS=rpool2/ROOT/ubuntu-utopic-1 boot=zfs bootfs=rpool2/ROOT/ubuntu-utopic-1 rpool=rpool2 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch 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: Tue Nov 4 12:03:28 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5557 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1389220/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Po
[Dx-packages] [Bug 1384384] Re: memory leak - /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk
** Changed in: unity Status: New => Invalid ** No longer affects: unity (Ubuntu) ** Also affects: indicator-keyboard Importance: Undecided Status: New ** Also affects: indicator-keyboard (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1384384 Title: memory leak - /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk Status in Indicator keyboard: New Status in Unity: Invalid Status in “indicator-keyboard” package in Ubuntu: New Bug description: indicator-keyboard: Installed: 0.0.0+14.04.20140410.1-0ubuntu1 Candidate: 0.0.0+14.04.20140410.1-0ubuntu1 Version table: *** 0.0.0+14.04.20140410.1-0ubuntu1 0 500 http://mirrors.cat.pdx.edu/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ***begin** from htop - take a look at RES as time goes by: PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command 34613 lightdm20 0 665M 216M 8792 S 27.2 0.1 3:48.53 /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk a little later PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command 34613 lightdm20 0 697M 248M 8792 S 26.1 0.1 5:38.43 /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk and again later PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command 34613 lightdm20 0 783M 307M 8796 S 0.0 0.1 10:23.49 /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk this is roughly 50% growth. Probably not required for this application... The thing is that I noticed this this this morning because RES actually said: 12.8 GIG. *zomg* That seems excessive for a keyboard indicator. It appears to be reading the same file over and over and again but perhaps not doing so correctly. Using strace we can see that while there are just as many munmap as mmaps: % time seconds usecs/call callserrors syscall -- --- --- - - 56.480.553369559099 wait4 37.950.371828375699 clone 1.900.018603 1 17771 poll 1.760.017267 1 26659 17672 recvmsg 0.880.008589 1 8835 writev 0.210.002027 1 3002 read 0.120.001182 1 867 198 open 0.120.001173 2 669 munmap 0.080.000789 1 60663 futex 0.080.000739 4 198 unlink 0.070.000655 1 443 write 0.070.000641 1 669 mmap 0.060.000594 1 65458 stat 0.050.000490 1 703 close 0.050.000482 1 693 lseek 0.040.000414 1 654 fstat 0.040.000365 1 387 access 0.020.000233 233 1 restart_syscall 0.020.000166 1 198 198 lstat 0.020.000160 296 pwrite 0.000.36 133 eventfd2 0.000.00 0 1 recvfrom 0.000.00 0 2 getdents 0.000.00 0 1 openat -- --- --- - - 100.000.979802 63340 18189 total So perhaps it is leaking with more traditional mallocs. In any event, over time, this thing consumes massive quantities of memory, which is probably a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-keyboard/+bug/1384384/+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 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
** Changed in: compiz 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/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, you can't enter your password in the lockscreen. [Test case] This will work only in the case that your lockscreen is set (from unity control center, lock pane) to lock immediately (when screen turns off). 1. Open a window that will hold the grab, such as the ssh password dialog or a virtual machine (such as virtualbox in fullscreen). 2. Wait for the lock screen to activate [1]. 3. The screen won't be locked, since it's not possible to steal drag to another window. [Regression potential] For the same reason of lp:49579, we can't lock the screen (yet) if something takes the grab in X, or we won't able to get input back. This is not a regression because it has never been possible in Ubuntu before, while when we tried that, it caused this bug. A possible source of regression might be that we now try to grab/ungrab the screen (the only X reliable way for grab checking), when showing the dash/hud or the lockscreen itself, and this might slow things down a little, but from measurements done this slow down is generally about 2ms, so nothing to worry about. * Compiz Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff * [1] You can use this to reduce the locking delay: gsettings set org.gnome.desktop.session idle-delay 5 and resetting it with: gsettings reset org.gnome.desktop.session idle-delay --- Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+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 727904] Re: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken
** Changed in: compiz 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/727904 Title: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Committed 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 Status in “unity” source package in Trusty: Invalid Bug description: To reproduce: Open two Chrome windows and two Firefox windows. Drag a .html file over the Chrome icon in the Launcher. A spread of the two Chrome windows should appear. Then continue the same drag, and drag the file over the Firefox icon in the Launcher. Nothing happens, the Chrome spread is still displayed. Desired behaviour; After a spread appears as a result of the user dragging a file over a application icon in the Launcher, if the user then drags the file over a different application icon (where the application is also a valid drop receptacle for the file type) the spread should switch to the newly selected application. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/727904/+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 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application
** Changed in: compiz 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/607796 Title: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Committed Status in One Hundred Papercuts: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. [Test Case] 1) Open two windows instances of the same application (say firefox) 2) Drag a file from the file-manager or the desktop and hover the firefox icon 3) After one second the firefox icon is hovered, the spread will occur 4) You should be able to hover one of the firefox windows and it should show a spinner, after 750ms (by default) the hovered windows should be focused and raised 5) You should now be able to drop the content you're dragging (if the selected application supports that content). [Regression Potential] This codepath was mostly disabled in the current compiz and unity code because it was buggy, so the regression potential is very low, although it might happen that, if some race-condition happens, when closing the scale the launcher might be still painted as if it would be in scale mode (desaturated) even if it's not the case anymore. *** SRU debdiff links *** The Unity SRU debdiff for this can be found at https://launchpadlibrarian.net/180013321/unity-7.2.2-trusty-sru.debdiff. The Compiz SRU debdiff for this can be found at https://launchpadlibrarian.net/180013356/compiz-0.9.11.2-trusty- sru.debdiff ### Bug #727903 needs to be fixed at the same time. --- History: This bug had been previously fixed as "buggybutclosed" for Unity on 2011-04-18, leaving this function with other bugs: https://bugs.launchpad.net/ayatana-design/+bug/727903 https://bugs.launchpad.net/ayatana-design/+bug/727904 https://bugs.launchpad.net/ayatana-design/+bug/727902 https://bugs.launchpad.net/ayatana-design/+bug/764424 https://bugs.launchpad.net/ayatana-design/+bug/832988 On 2011-10-18, it was reopened for regression in Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/607796/+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 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application
Finally , after 3 years of waiting, thanks to everyone involved. On Thu, Nov 6, 2014 at 2:28 PM, Stephen M. Webb wrote: > ** Changed in: compiz >Status: Fix Committed => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/607796 > > Title: > Launcher, Window management - Dragging and holding a selection over an > entry in the Launcher should spread out windows belonging to that > application > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ayatana-design/+bug/607796/+subscriptions > -- *Alket Rexhepi* *Developer* *skype* alket.rexhepi -- 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/607796 Title: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Committed Status in One Hundred Papercuts: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. [Test Case] 1) Open two windows instances of the same application (say firefox) 2) Drag a file from the file-manager or the desktop and hover the firefox icon 3) After one second the firefox icon is hovered, the spread will occur 4) You should be able to hover one of the firefox windows and it should show a spinner, after 750ms (by default) the hovered windows should be focused and raised 5) You should now be able to drop the content you're dragging (if the selected application supports that content). [Regression Potential] This codepath was mostly disabled in the current compiz and unity code because it was buggy, so the regression potential is very low, although it might happen that, if some race-condition happens, when closing the scale the launcher might be still painted as if it would be in scale mode (desaturated) even if it's not the case anymore. *** SRU debdiff links *** The Unity SRU debdiff for this can be found at https://launchpadlibrarian.net/180013321/unity-7.2.2-trusty-sru.debdiff. The Compiz SRU debdiff for this can be found at https://launchpadlibrarian.net/180013356/compiz-0.9.11.2-trusty- sru.debdiff ### Bug #727903 needs to be fixed at the same time. --- History: This bug had been previously fixed as "buggybutclosed" for Unity on 2011-04-18, leaving this function with other bugs: https://bugs.launchpad.net/ayatana-design/+bug/727903 https://bugs.launchpad.net/ayatana-design/+bug/727904 https://bugs.launchpad.net/ayatana-design/+bug/727902 https://bugs.launchpad.net/ayatana-design/+bug/764424 https://bugs.launchpad.net/ayatana-design/+bug/832988 On 2011-10-18, it was reopened for regression in Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/607796/+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 1385441] Re: Can't unlock the screen in Ubuntu 14.10
Does it work with gnomes screensaver? On 6 Nov 2014 14:15, "Marco Trevisan (Treviño)" wrote: > ** Tags added: lockscreen > > ** Changed in: unity >Status: New => Incomplete > > ** Changed in: unity (Ubuntu) >Status: New => Incomplete > > ** Changed in: unity > Assignee: (unassigned) => Andrea Azzarone (andyrock) > > -- > You received this bug notification because you are subscribed to Unity. > https://bugs.launchpad.net/bugs/1385441 > > Title: > Can't unlock the screen in Ubuntu 14.10 > > Status in Unity: > Incomplete > Status in “unity” package in Ubuntu: > Incomplete > > Bug description: > The bug is similar to the one reported in > https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1314095 (Unity > Lockscreen in 14.04 can't unlock when using LDAP account) > > The difference is that I don't have an LDAP account just a local one, > the box was working well in 14.04 and after upgrade to 14.10 I can't unlock > the screen. > Changing /sbin/unix_chkpwd to setuid does the trick too. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/unity/+bug/1385441/+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/1385441 Title: Can't unlock the screen in Ubuntu 14.10 Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: The bug is similar to the one reported in https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1314095 (Unity Lockscreen in 14.04 can't unlock when using LDAP account) The difference is that I don't have an LDAP account just a local one, the box was working well in 14.04 and after upgrade to 14.10 I can't unlock the screen. Changing /sbin/unix_chkpwd to setuid does the trick too. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1385441/+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 1281370] Re: Unity should use "Normal" resize mode by default
** Changed in: compiz 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/1281370 Title: Unity should use "Normal" resize mode by default Status in Compiz: Fix Released Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Unity resize mode should be use "live" resizing mode by default, as said by designers after testing it with new unity decorations: 16:38:04 I just tested the live resizing 16:38:12 it works great! 16:38:19 at long, long last, great to have it back 16:38:28 +1 to switch on by default To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1281370/+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 1104236] Re: [regression] Unity show desktop fade out makes them invisible in spread.
** Changed in: compiz 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/1104236 Title: [regression] Unity show desktop fade out makes them invisible in spread. Status in Compiz: Fix Released Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: This looks like a regression. Bug 88 describes what we now have in current trunk again. STR: 1. Open 2 application windows, e.g. gnome-terminal 2. Alt-tab to show desktop 3. Click on gnome-terminal icon with 2 pips on the launcher Expected results: Two windows are displayed in spread. Actual results: One window is displayed in spread with another one still being there, the outline appears on hover but the window itself is not displayed. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.01.21bzr3064pkg0raring147 [origin: LP-PPA-unity-team-staging] ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity Date: Thu Jan 24 19:08:09 2013 InstallationDate: Installed on 2013-01-04 (20 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130104) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ADDITION: Furthermore "Show desktop" shows desktop on all workspaces which is not desired behavior. This makes the issue even worse, because you can only use the launcher and alt-tab to navigate between the windows which results in a big usability bug. The following video demonstrates this: http://ubuntuone.com/4zt3CfDbgOZmanRGBCrbeE To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1104236/+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 992697] Re: Window management - 'Ctrl-Alt-Numpad 4' and 'Ctrl-Alt-Numpad 6' window placement shortcuts are broken
** Changed in: compiz 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/992697 Title: Window management - 'Ctrl-Alt-Numpad 4' and 'Ctrl-Alt-Numpad 6' window placement shortcuts are broken Status in Autopilot: Fix Released Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Compiz 0.9.10 series: Fix Committed Status in Unity: Fix Released Status in “autopilot” package in Ubuntu: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: The "Ctrl + Alt + numpad 4" and "Ctrl + Alt + numpad 6" keyboard shortcuts are not working in 13.04. See bug #878820 for the full specification of the numpad window placement shortcuts. Quoting from this bug: "Ctrl-Alt-Numpad 4 - Place window on the left side of the screen in *semi-maximised* state (it is important that the window is actually semi-maximised, not just the same size and position as a semi- maximised window) Pressing a second time does nothing. Ctrl-Alt-Numpad 6 - Place window on the right side of the screen (it is important that the window is actually semi-maximised, not just the same size and position as a semi-maximised window). Pressing a second time does nothing." HOWTO: The solution we want here are additional shortcuts to semi-maximize windows vertically and move them to left/right half of the screen... The best way to achieve that: 1. Remove the changing of the standard shortcuts by debian/patches/ubuntu-config.patch, so the original ones will work again. 2. Add 2 quasi-duplicated shortcuts with the functions to semi-maximize windows vertically and move them to left/right half of the screen to Grid and make those functions use "Ctrl + Super + Cursor Left or Right" on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot/+bug/992697/+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 766191] Re: Spread causes Compiz's 'scale' plugin to inaccurately pad the right/left edges of the screen
** Changed in: compiz 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/766191 Title: Spread causes Compiz's 'scale' plugin to inaccurately pad the right/left edges of the screen Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: When using Unity with two windows of the same size open, activating compiz's 'scale' causes inconsistent padding at either sides of the screen. This is because the scale plugin does not factor the Unity launcher's width into the calculations; therefore, the left edge of the screen has less padding than the right edge. The problem detailed with measurement: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/766191/+attachment/2457195/+files/pic1.png I think scaling should be done considering the screen width minus the dock width. This may seem very tricky to pull out since scale is a compiz plugin and so on, but, again, like it is and when windows get under the dock, it feels strange. Cheers. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/766191/+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 1280616] Re: When launcher is in autohide mode the launcher icons are not clickable
** Changed in: compiz 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/1280616 Title: When launcher is in autohide mode the launcher icons are not clickable Status in Compiz: Fix Released Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Setting the launcher in autohide, then it's not possible to click on launcher items when the spread is open (it's terminated instead). Also the spreaded windows doesn't take in consideration the size of launcher as x offset. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1280616/+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 727904] Re: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken
** Changed in: compiz/0.9.11 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/727904 Title: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Released 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 Status in “unity” source package in Trusty: Invalid Bug description: To reproduce: Open two Chrome windows and two Firefox windows. Drag a .html file over the Chrome icon in the Launcher. A spread of the two Chrome windows should appear. Then continue the same drag, and drag the file over the Firefox icon in the Launcher. Nothing happens, the Chrome spread is still displayed. Desired behaviour; After a spread appears as a result of the user dragging a file over a application icon in the Launcher, if the user then drags the file over a different application icon (where the application is also a valid drop receptacle for the file type) the spread should switch to the newly selected application. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/727904/+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 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application
** Changed in: compiz/0.9.11 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/607796 Title: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Released Status in One Hundred Papercuts: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. [Test Case] 1) Open two windows instances of the same application (say firefox) 2) Drag a file from the file-manager or the desktop and hover the firefox icon 3) After one second the firefox icon is hovered, the spread will occur 4) You should be able to hover one of the firefox windows and it should show a spinner, after 750ms (by default) the hovered windows should be focused and raised 5) You should now be able to drop the content you're dragging (if the selected application supports that content). [Regression Potential] This codepath was mostly disabled in the current compiz and unity code because it was buggy, so the regression potential is very low, although it might happen that, if some race-condition happens, when closing the scale the launcher might be still painted as if it would be in scale mode (desaturated) even if it's not the case anymore. *** SRU debdiff links *** The Unity SRU debdiff for this can be found at https://launchpadlibrarian.net/180013321/unity-7.2.2-trusty-sru.debdiff. The Compiz SRU debdiff for this can be found at https://launchpadlibrarian.net/180013356/compiz-0.9.11.2-trusty- sru.debdiff ### Bug #727903 needs to be fixed at the same time. --- History: This bug had been previously fixed as "buggybutclosed" for Unity on 2011-04-18, leaving this function with other bugs: https://bugs.launchpad.net/ayatana-design/+bug/727903 https://bugs.launchpad.net/ayatana-design/+bug/727904 https://bugs.launchpad.net/ayatana-design/+bug/727902 https://bugs.launchpad.net/ayatana-design/+bug/764424 https://bugs.launchpad.net/ayatana-design/+bug/832988 On 2011-10-18, it was reopened for regression in Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/607796/+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 1389761] Re: Don't show the volume overlay when changing the volume with the slider
** Changed in: indicator-sound (Ubuntu)
Status: New => Triaged
** Changed in: indicator-sound (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1389761
Title:
Don't show the volume overlay when changing the volume with the slider
Status in “indicator-sound” package in Ubuntu:
Triaged
Bug description:
The overlay and the slider are redundant when the user changes the
volume with the slider and the overlay shouldn't be displayed.
ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1
Uname: Linux 3.4.67 armv7l
ActionStates: ({'mediaplayer-app.desktop.greeter': (true, signature '',
[<{'running': , 'state': <'Paused'>}>]), 'mute': (true, '', []),
'phone-settings': (true, '', []), 'mic-volume': (true, '', [<1.0>]), 'scroll':
(true, 'i', []), 'high-volume': (true, '', []),
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings':
(true, '', []), 'mediaplayer-app.desktop': (true, '', [<{'running': ,
'state': <'Paused'>}>]), 'play.mediaplayer-app.desktop': (true, '',
[<'Paused'>]), 'volume': (true, 'i', [<1.0>]), 'next.mediaplayer-app.desktop':
(true, '', []), 'root': (true, '', [<{'title': <'Son'>, 'accessible-desc':
<'Volume (100%)'>, 'icon': <('themed', <['audio-volume-high-panel',
'audio-volume-high', 'audio-volume', 'audio']>)>, 'visible': }>]),
'previous.mediaplayer-app.desktop': (true, '', []), 'silent-mode': (true, '',
[])},)
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
Date: Wed Nov 5 16:58:35 2014
InstallationDate: Installed on 2014-11-05 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf
(20141105-120036)
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/1389761/+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 1389725] Re: g_app_info warning on start (utouch)
** Changed in: indicator-messages (Ubuntu) Status: New => Triaged -- 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/1389725 Title: g_app_info warning on start (utouch) Status in “indicator-messages” package in Ubuntu: Triaged Bug description: Using rtm 143, indicator-messages displays warnings on start backtrace of one of those #0 g_log (log_domain=0xb6f87914 "GLib-GIO", log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, format=0xb6e247d4 "%s: assertion '%s' failed") at /build/buildd/glib2.0-2.41.5/./glib/gmessages.c:1075 #1 0xb6dedd62 in g_return_if_fail_warning (log_domain=, pretty_function=, expression=) at /build/buildd/glib2.0-2.41.5/./glib/gmessages.c:1088 #2 0xb6ef610c in g_app_info_equal (appinfo1=0x4e088, appinfo2=0x0) at /build/buildd/glib2.0-2.41.5/./gio/gappinfo.c:132 #3 0x000170d2 in g_app_info_is_default_for_uri_scheme ( uri_scheme=0x1d63c "mailto", info=0x4e088) at im-desktop-menu.c:87 #4 im_desktop_menu_app_added (applist=, app_id=0x50b80 "telephony-service-call", app_info=0x4e088, user_data=0x3fe40) at im-desktop-menu.c:176 #5 0x000173ee in im_desktop_menu_constructed (object=0x3fe40) at im-desktop-menu.c:380 #6 0xb6e96fae in g_object_new_internal (class=class@entry=0x0, params=params@entry=0xbefff354, n_params=n_params@entry=1) at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1814 #7 0xb6e98650 in g_object_new_valist (object_type=object_type@entry=346680, first_property_name=first_property_name@entry=0x1d054 "application-list", var_args=..., var_args@entry=...) at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:2034 #8 0xb6e987ec in g_object_new (object_type=346680, first_property_name=0x1d054 "application-list") at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1617 #9 0x00017510 in im_desktop_menu_new (applist=) at im-desktop-menu.c:427 #10 0x00014d16 in main (argc=, argv=) at messages-service.c:277 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1389725/+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 1385413] Re: unity_support_test has stopped unexpectedly
Stacktrace shows a crash in the VirtualBox video driver. I strongly suspect a problem in the VirtualBox video driver. ** 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/1385413 Title: unity_support_test has stopped unexpectedly Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Status in “virtualbox” package in Ubuntu: Confirmed Bug description: Performed the upgrade from Trusty to Utopic, after the required restart of the computer the 'Report a problem' dialog poped up saying that unity_support_test has stopped unexpectedly. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8 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 Date: Fri Oct 24 18:27:07 2014 DistUpgraded: 2014-10-24 17:54:14,577 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 4.3.18, 3.16.0-23-generic, i686: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-09-25 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=664043af-2956-48b2-baca-3609d1ee45c3 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: unity UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code -11: libGL error: pci id for fd 4: 80ee:beef, driver (null) OpenGL Warning: Assertion failed: thread && thread->netServer.conn && thread->netServer.conn->type==CR_VBOXHGCM && thread->bInjectThread, file /mnt/tinderbox/add-4.3/src/VBox/Additions/common/crOpenGL/pack/packspu_misc.c, line 562 UpgradeStatus: Upgraded to utopic on 2014-10-24 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 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 Oct 24 18:18:10 2014 xserver.configfile: default xserver.errors: AIGLX error: vboxvideo does not export required DRI extension AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: vboxvideo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1385413/+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 1386114] Re: compiz crashed with SIGABRT in __libc_message()
** Information type changed from Private to Public -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1386114 Title: compiz crashed with SIGABRT in __libc_message() Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: apparently random crash soon after logging in ProblemType: Crash 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 CurrentDesktop: Unity Date: Mon Oct 27 09:58:31 2014 ExecutablePath: /usr/bin/compiz ProcCmdline: compiz ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity StacktraceTop: __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fc9f533a668 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ptr=, str=0x7fc9f533a830 "double free or corruption (fasttop)", action=1) at malloc.c:4996 _int_free (av=, p=, have_lock=0) at malloc.c:3840 ft_glyphslot_free_bitmap () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGABRT in __libc_message() UpgradeStatus: Upgraded to trusty on 2014-05-07 (172 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark www-data To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386114/+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 1386114] Re: compiz crashed with SIGABRT in __libc_message()
** 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/1386114 Title: compiz crashed with SIGABRT in __libc_message() Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: apparently random crash soon after logging in ProblemType: Crash 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 CurrentDesktop: Unity Date: Mon Oct 27 09:58:31 2014 ExecutablePath: /usr/bin/compiz ProcCmdline: compiz ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity StacktraceTop: __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fc9f533a668 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ptr=, str=0x7fc9f533a830 "double free or corruption (fasttop)", action=1) at malloc.c:4996 _int_free (av=, p=, have_lock=0) at malloc.c:3840 ft_glyphslot_free_bitmap () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGABRT in __libc_message() UpgradeStatus: Upgraded to trusty on 2014-05-07 (172 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark www-data To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386114/+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 1386114] Re: compiz crashed with SIGABRT in __libc_message()
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/1386114 Title: compiz crashed with SIGABRT in __libc_message() Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: apparently random crash soon after logging in ProblemType: Crash 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 CurrentDesktop: Unity Date: Mon Oct 27 09:58:31 2014 ExecutablePath: /usr/bin/compiz ProcCmdline: compiz ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity StacktraceTop: __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fc9f533a668 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ptr=, str=0x7fc9f533a830 "double free or corruption (fasttop)", action=1) at malloc.c:4996 _int_free (av=, p=, have_lock=0) at malloc.c:3840 ft_glyphslot_free_bitmap () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGABRT in __libc_message() UpgradeStatus: Upgraded to trusty on 2014-05-07 (172 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark www-data To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386114/+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 984099] Re: compiz crashed with SIGSEGV in g_object_newv() from g_object_new() from g_volume_monitor_get() from unity::launcher::DeviceLauncherSection::DeviceLauncherSection() from
** Changed in: unity/6.0 Status: New => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/984099 Title: compiz crashed with SIGSEGV in g_object_newv() from g_object_new() from g_volume_monitor_get() from unity::launcher::DeviceLauncherSection::DeviceLauncherSection() from unity::launcher::Controller::Impl::Impl() Status in Unity: Confirmed Status in Unity 5.0 series: New Status in Unity 6.0 series: Won't Fix Status in “unity” package in Ubuntu: Triaged Bug description: I was trying to log in to Unity 3D. I've crashed this way a number of times before -- it's repeatable. I've reported it several times. I've applied all updates to 12.04 as of 12 hours ago. Now, I'm logged in to KDE, since all Unity and all Gnome shells keep crashing. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: libnux-2.0-0 2.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 2.0.1-0ubuntu4 Architecture: amd64 CrashCounter: 1 Date: Tue Apr 17 05:48:15 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.2) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: nux StacktraceTop: ?? () from /usr/lib/gio/modules/libgioremote-volume-monitor.so g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_volume_monitor_get () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 unity::launcher::DeviceLauncherSection::DeviceLauncherSection() () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in g_object_newv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/984099/+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 981821] Re: compiz crashed with signal 7 in g_settings_get_value() from g_settings_get_strv() from unity::dash::HomeLens::Impl::FindLensPriority() from unity::dash::HomeLens::Impl::
** Changed in: unity/6.0 Status: New => Won't Fix -- 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, dx-packages https://bugs.launchpad.net/bugs/981821 Title: compiz crashed with signal 7 in g_settings_get_value() from g_settings_get_strv() from unity::dash::HomeLens::Impl::FindLensPriority() from unity::dash::HomeLens::Impl::EnsureCategoryAnnotation() Status in Unity: Confirmed Status in Unity 5.0 series: New Status in Unity 6.0 series: Won't Fix Status in “d-conf” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Running the latest Precise development build with all the updates. I expected no random error, but apport happened to pop up with this one. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: libunity-core-5.0-5 5.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Sat Apr 14 10:59:33 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120321) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 7 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: compiz crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/981821/+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 1389715] Re: [messaging-app] + [indicators] No message is either sent or stored in the messaging app when replying a message from the ‘quick reply’ on the notifications indicator me
** Package changed: indicators-client (Ubuntu) => indicator-messages (Ubuntu) -- 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/1389715 Title: [messaging-app] + [indicators] No message is either sent or stored in the messaging app when replying a message from the ‘quick reply’ on the notifications indicator menu. Status in “indicator-messages” package in Ubuntu: New Status in “messaging-app” package in Ubuntu: New Bug description: Built: r141 Steps to reproduce: 1. New incoming message. Go to the notifications indicator menu. 2. Tap on the list item to write a quick reply. 3. Send your reply. Actual behaviour: The message I've just sent is not stored in the messageing app, neither received by the contact. Expected behaviour: Messages sent through the 'quick reply' feature on the indicators menu shoud be stored in the messageing app and received by the recipient. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1389715/+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 1389715] [NEW] [messaging-app] + [indicators] No message is either sent or stored in the messaging app when replying a message from the ‘quick reply’ on the notifications indicator
You have been subscribed to a public bug: Built: r141 Steps to reproduce: 1. New incoming message. Go to the notifications indicator menu. 2. Tap on the list item to write a quick reply. 3. Send your reply. Actual behaviour: The message I've just sent is not stored in the messageing app, neither received by the contact. Expected behaviour: Messages sent through the 'quick reply' feature on the indicators menu shoud be stored in the messageing app and received by the recipient. ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- [messaging-app] + [indicators] No message is either sent or stored in the messaging app when replying a message from the ‘quick reply’ on the notifications indicator menu. https://bugs.launchpad.net/bugs/1389715 You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages 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 1332968] Re: unity-panel-service crashed with SIGSEGV in strrchr()
** Information type changed from Private to Public -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1332968 Title: unity-panel-service crashed with SIGSEGV in strrchr() Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: happens randomly ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity-services 7.3.0+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,mousepoll,imgpng,grid,snap,gnomecompat,place,move,wall,resize,regex,vpswitch,commands,unitymtgrabhandles,animation,session,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 CurrentDesktop: Unity Date: Sun Jun 22 14:25:58 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/lib/unity/unity-panel-service GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Mobility Radeon HD 5650 [104d:9071] InstallationDate: Installed on 2014-06-01 (20 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140510) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0c45:6409 Microdia Webcam Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Sony Corporation VPCEB2C5E ProcCmdline: /usr/lib/unity/unity-panel-service ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=c72ec9e3-fe9d-4672-8784-3117789d48f3 ro persistent quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7facdfcfe625 : movdqu (%rdi),%xmm0 PC (0x7facdfcfe625) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: strrchr () at ../sysdeps/x86_64/strrchr.S:32 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: unity-panel-service crashed with SIGSEGV in strrchr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 07/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0300Y8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0300Y8:bd07/20/2010:svnSonyCorporation:pnVPCEB2C5E:pvrC605XTV0:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCEB2C5E dmi.product.version: C605XTV0 dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu5 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-1ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Jun 21 05:15:14 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output HDMI-0 LVDS VGA-0 xserver.version: 2:1.15.1-0ubuntu5 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1332968/+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 1176078] Re: Cannot send file by email using unity dash
I use the System Settings to change my default email client and it works fine, even using the command-line MUA 'mutt'. How were you configuring your default email client? ** Also affects: unity-lens-files Importance: Undecided Status: New ** Changed in: unity Status: New => Invalid ** Also affects: unity-lens-files (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: Confirmed => Invalid ** Changed in: unity-lens-files Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1176078 Title: Cannot send file by email using unity dash Status in Unity: Invalid Status in Unity Files Lens: Incomplete Status in “unity” package in Ubuntu: Invalid Status in “unity-lens-files” package in Ubuntu: New Bug description: When searching for file using unity dash, and after finding the file, and clicking with the right button of the mouse and select email, nothing happens. This occurs when setting other email client as default other than thunderbird in system settings. Using the thunderbird as default email software, and proceding like described, behaves like expected. i installed the evolution email client and configured as default email client. It sould send email using other email client like evolution other than thunderbird. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri May 3 17:01:37 2013 InstallationDate: Installed on 2013-05-03 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1176078/+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 1022743] Re: Hardcoded Unity shortcuts responsible for several problems
** Changed in: compiz Milestone: 0.9.11.0 => None -- 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/1022743 Title: Hardcoded Unity shortcuts responsible for several problems Status in Compiz: Opinion Status in Unity: Opinion Status in “unity” package in Ubuntu: Opinion Bug description: 1. All the hardcoded Unity shortcuts (like Alt+Space, Ctrl+Tab or Super+Tab for example) are not shared with Compiz and the CCSM, so it is possible to double-bind the same keycombinations already used by Unity to other functions without CCSM even showing a warning about it... 2. There are conflicts with hardcoded Unity keycombinations, which are still adjustable via CCSM. Example: You are unable to change the shortcut for the Window Menu (Alt+Space), although the option is there (CCSM->General->Key Bindings->Window Menu) Changing the shortcut to anything else makes it snap back to Alt+Space. It is not possible to change the Mouse-shortcut, nor to use Alt+Button3 (Alt+rightMouseButton) for anything else than showing the window menu. Disabling the shortcut is also not possible. 3. If one can not assign hardcoded keybindings/key-mousebindings to anything else and is not able to disable them either, and one wants to use any program that utilizes the same keycombinations/key-mousecombinations (e.g. a game), it would not be possible to play it, because it would always bring up the hardcoded functions, no matter what... Examples: Alt+Space will always bring up the window menu (window accessibility), Alt+Button3 (RMB) also To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1022743/+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 1176078] Re: Cannot send file by email using unity dash
Hi, i changed the email client in system settings, but it was in 13.04. Now, maybe it is working, i'm no longer using ubuntu, i'll try install ubuntu 14.10 in a virtual machine, and reproduce using the same steps... -- 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/1176078 Title: Cannot send file by email using unity dash Status in Unity: Invalid Status in Unity Files Lens: Incomplete Status in “unity” package in Ubuntu: Invalid Status in “unity-lens-files” package in Ubuntu: New Bug description: When searching for file using unity dash, and after finding the file, and clicking with the right button of the mouse and select email, nothing happens. This occurs when setting other email client as default other than thunderbird in system settings. Using the thunderbird as default email software, and proceding like described, behaves like expected. i installed the evolution email client and configured as default email client. It sould send email using other email client like evolution other than thunderbird. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri May 3 17:01:37 2013 InstallationDate: Installed on 2013-05-03 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1176078/+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 1297150] Re: Unity "quit" button doesn't do anything when Wine application is frozen
Don't try it with a signal stopped process, try it with an actual hanging process. -- 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/1297150 Title: Unity "quit" button doesn't do anything when Wine application is frozen Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Status in “wine1.6” package in Ubuntu: Triaged Bug description: A Wine app that freezes up can be in a state where it is unkillable by using the interface. Killing the process in a terminal, or doing a wineserver -k command, can solve the situation, however there is no way to do this within Unity even after repeated "quit" demands. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1297150/+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 1389573] Re: Update-notifier window invisible in utopic
** 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/1389573 Title: Update-notifier window invisible in utopic Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Somehow I ended up with update-notifier not being visible on my utopic laptop. I can see it in the dock on the left, and I can interact with it that way (right-clicking to choose "install available software"), and I can even close it out from there. But I cannot cause its main window to appear on any desktop. Rebooting does not clear this problem, and it happens even with the reboot notifications. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: update-notifier 3.157 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 5 08:48:20 2014 InstallationDate: Installed on 2014-05-29 (159 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: update-notifier UpgradeStatus: Upgraded to utopic on 2014-10-24 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1389573/+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 1378852] Re: compiz crashed with SIGSEGV in unity::panel::PanelMenuView::UpdateTitleGradientTexture()
Mh, I can't reproduce this by using that game... Are you using it in windowed mode? In any case it would be nice if you could install the unity debug symbols and get a backtrace with gdb from your coredump (see https://wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages) ** Changed in: unity Status: New => Incomplete ** Changed in: unity (Ubuntu) Status: New => Incomplete ** Information type changed from Private to Public -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1378852 Title: compiz crashed with SIGSEGV in unity::panel::PanelMenuView::UpdateTitleGradientTexture() Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: Compiz crash after exiting an OpenGL application (the Oculus Rift demo "AAAaaaAAAaaaCULUS"). Seems to be reproducible: happened both times I tried. Running on Utopic, cleanly installed from daily of 06. Oct, with updates installed from one day later. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Wed Oct 8 21:29:51 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-10-07 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141006) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANGUAGE=en_AU:en XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f65662eb8f6 <_ZN5unity5panel13PanelMenuView26UpdateTitleGradientTextureEv+374>: mov (%rdi),%rax PC (0x7f65662eb8f6) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: unity::panel::PanelMenuView::UpdateTitleGradientTexture() () from /usr/lib/compiz/libunityshell.so unity::panel::PanelMenuView::Draw(nux::GraphicsEngine&, bool) () from /usr/lib/compiz/libunityshell.so nux::View::ProcessDraw(nux::GraphicsEngine&, bool) () from /usr/lib/x86_64-linux-gnu/libnux-4.0.so.0 nux::Layout::ProcessDraw(nux::GraphicsEngine&, bool) () from /usr/lib/x86_64-linux-gnu/libnux-4.0.so.0 unity::panel::PanelView::DrawContent(nux::GraphicsEngine&, bool) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in unity::panel::PanelMenuView::UpdateTitleGradientTexture() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1378852/+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 1380237] Re: Can't navigate through open files in Evince
** Changed in: unity Status: New => Incomplete ** Changed in: unity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1380237 Title: Can't navigate through open files in Evince Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: I have opened couple of PDFs in Evince. According to the procedure, I could switch/navigate through opened PDFs in Evince by pressing Alt+~ keys. But it doesn't work always. Most of the time it remain non- responsive. Even switching/navigating through different applications like Files, Evince also doesn't work when any PDF is kept open in full-screen mode. I just cannot switch applications using Alt+Tab. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1380237/+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 1380093] Re: autologin prevents the lock from working
** Tags added: lockscreen ** Changed in: unity Assignee: (unassigned) => Andrea Azzarone (andyrock) ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (andyrock) -- 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/1380093 Title: autologin prevents the lock from working Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: After upgrade to 14.04, I notice I can no longer lock my screen. After more debugging, it was due to the fact that I have autologin enabled. Autologin is needed, so when my machine starts up due to whatever reason. But I would like to be able to lock the screen, and thus require a password to unlock (per configuration) if needed (or when it goes idle). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10.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 CurrentDesktop: Unity Date: Sat Oct 11 09:49:21 2014 InstallationDate: Installed on 2013-08-29 (407 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-09-23 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1380093/+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 1297150] Re: Unity "quit" button doesn't do anything when Wine application is frozen
Is there anything we can use to reproduce this in an easy way? -- 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/1297150 Title: Unity "quit" button doesn't do anything when Wine application is frozen Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Status in “wine1.6” package in Ubuntu: Triaged Bug description: A Wine app that freezes up can be in a state where it is unkillable by using the interface. Killing the process in a terminal, or doing a wineserver -k command, can solve the situation, however there is no way to do this within Unity even after repeated "quit" demands. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1297150/+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 1389573] Re: Update-notifier window invisible in utopic
I don't think this is much related to unity, since I experienced this also in older versions of ubuntu (this problem has always been there ihmo). When the window is minimized, sometimes doesn't get mapped again, and this is not possible also using other window managers (or tool such as libwnck). ** Changed in: unity Status: Confirmed => Incomplete ** Changed in: unity (Ubuntu) Status: Confirmed => Incomplete ** Also affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** No longer affects: unity ** Changed in: unity (Ubuntu) Status: Incomplete => Opinion ** Changed in: unity (Ubuntu) Status: Opinion => Invalid ** Also affects: compiz Importance: Undecided Status: New ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1389573 Title: Update-notifier window invisible in utopic Status in Compiz: New Status in “compiz” package in Ubuntu: New Status in “unity” package in Ubuntu: Invalid Status in “update-notifier” package in Ubuntu: New Bug description: Somehow I ended up with update-notifier not being visible on my utopic laptop. I can see it in the dock on the left, and I can interact with it that way (right-clicking to choose "install available software"), and I can even close it out from there. But I cannot cause its main window to appear on any desktop. Rebooting does not clear this problem, and it happens even with the reboot notifications. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: update-notifier 3.157 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 5 08:48:20 2014 InstallationDate: Installed on 2014-05-29 (159 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: update-notifier UpgradeStatus: Upgraded to utopic on 2014-10-24 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1389573/+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 1389659] Re: spread should allow dragging windows to other monitor
** Changed in: unity Status: New => Triaged ** Changed in: unity (Ubuntu) Status: New => Triaged ** Changed in: unity Importance: Undecided => Wishlist ** Changed in: unity (Ubuntu) Importance: Undecided => Wishlist ** Tags added: spread -- 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/1389659 Title: spread should allow dragging windows to other monitor Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: It would be a nice feature if in the "Spread" of windows, you can drag windows to other monitor. It would be good for people who need to drag multiple windows to other monitor at a time. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1389659/+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 1389888] Re: unity not shown only desktop with new nvida 970 card
It looks like compiz has not started there, but please use "apport- collect 1389888" to provide us more informations. Also, check the output of: /usr/lib/nux/unity_support_test -p -- 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/1389888 Title: unity not shown only desktop with new nvida 970 card Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Hi I have a new Nvidia 970 card. This card is supported starting nvidia-343, so I installed them using ppa:xorg-edgers/ppa . After a reboot I see the login screen, I'm able to login but the top-right menu and the unity bar on the left side is missing. But I'm able to see my mouse and on a right-click I get a pop-menu. What I've done so far: - reinstalled ubuntu-desktop unity compizconfig-settings-manager I'm added my log files to help you. Can I do anything else to help you? I hope you can help me. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1389888/+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 1389676] Re: unity-launcher opens new nautilus instead of bring up existing window
*** This bug is a duplicate of bug 1170647 *** https://bugs.launchpad.net/bugs/1170647 ** This bug has been marked a duplicate of bug 1170647 After minimizing an external media, clicking on the "Files" icon on the Launcher doesn't restore the minimized window, but opens a new one -- 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/1389676 Title: unity-launcher opens new nautilus instead of bring up existing window Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: I have one nautilus window open but in background. I want to get this window back up to top through clicking on the launcher-icon that has the little arrow next to it, indicating, that there is an open window for nautilus somewhere. Then an new nautilus window pops up, starting in my homedir, the old one stays in background. $ lsb_release -rdDescription: Ubuntu 14.10 Release: 14.10 $ apt-cache policy unity8 unity8: Installiert: (keine) Installationskandidat: 8.00+14.10.20141013.2-0ubuntu1 Versionstabelle: 8.00+14.10.20141013.2-0ubuntu1 0 500 http://de.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages 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 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Nov 5 13:35:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-25 (375 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-10-28 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1389676/+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
I just started seeing this after I upgraded to 14.10. $ lsb_release -rd Description:Ubuntu 14.10 Release:14.10 $ unity --version unity 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/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 1289465] Re: Brightness icons are suboptimal
** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-themes -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1289465 Title: Brightness icons are suboptimal Status in “indicator-power” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “ubuntu-themes” package in Ubuntu: Fix Released Bug description: Ubuntu Trusty r188, Ubuntu 14.10 r2, Ubuntu 14.10 r152 1. Go to System Settings > "Battery". 2. Look at the icons at the ends of the "Display brightness" slider. What you see: * The minimum-brightness icon is a light bulb with no rays. * The maximum-brightness icon is a light bulb with rays and a lightning bolt inside it. What you should see: * The minimum-brightness bulb should have rays, because it is not zero brightness. * The maximum-brightness icon does not have a lightning bolt, because that is strongly associated with battery charging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1289465/+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 1390170] Re: Two system updates notifications shown
** Attachment added: "push client log at the time" https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1390170/+attachment/4254612/+files/ubuntu-push-client.log -- 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/1390170 Title: Two system updates notifications shown Status in “indicator-messages” package in Ubuntu: New Bug description: An update became available and the menu included two instances of the notification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1390170/+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 1390170] Re: Two system updates notifications shown
I think the push helper is the one that should be clearing the entry. ** Package changed: indicator-messages (Ubuntu) => ubuntu-system- settings (Ubuntu) -- 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/1390170 Title: Two system updates notifications shown Status in “ubuntu-system-settings” package in Ubuntu: Incomplete Bug description: An update became available and the menu included two instances of the notification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1390170/+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 1390170] [NEW] Two system updates notifications shown
Public bug reported: An update became available and the menu included two instances of the notification ** Affects: indicator-messages (Ubuntu) Importance: Medium Status: New ** Attachment added: "twoupdates.jpg" https://bugs.launchpad.net/bugs/1390170/+attachment/4254610/+files/twoupdates.jpg -- 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/1390170 Title: Two system updates notifications shown Status in “indicator-messages” package in Ubuntu: New Bug description: An update became available and the menu included two instances of the notification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1390170/+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
Will do. Thanks for the directions. -- 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= LANG=en_US.UTF-8 XDG_RUNTIME_DIR= 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: https://bugs.launchpad.net/compiz/+bug/1366351/
[Dx-packages] [Bug 1377297] Re: Spread (Super+W) breaks minimized windows rendering
I am, yes (with proprietary drivers). I can reproduce this everytime (ubuntu 14.10) Just tell me if you need any more information -- 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/1377297 Title: Spread (Super+W) breaks minimized windows rendering Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: If you use spread while some of your windows are minimized and you try to open one of them after closing the spread, they are rendered badly (a black rectangle). Test case: 1-Minimize a terminal window for instance 2-Press Super+W to enable spread 3-Press again Super+W to close the spread 4-Click on your terminal window on your launcher To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1377297/+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 750386] Re: compiz crashed with SIGABRT in raise() from abort() from __libc_message() from malloc_printerr() from _int_free()
** Changed in: compiz (Ubuntu) Status: Confirmed => Fix Released ** Changed in: compiz (Ubuntu Quantal) 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/750386 Title: compiz crashed with SIGABRT in raise() from abort() from __libc_message() from malloc_printerr() from _int_free() Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Oneiric: Fix Released Status in “unity” source package in Oneiric: Fix Released Status in “compiz” source package in Quantal: Fix Released Status in “unity” source package in Quantal: Fix Released Bug description: You have landed here because you encountered some heap corruption causing your compiz to crash. Arguably your bug is different to this one, however as most heap corruption is untraceable with regular crash reports and stack traces, it is probably better to leave you bug as a duplicate of this. We will endeavour to fix all possible sources of such heap corruption leading to such a crash over time. Thanks for you understanding. ORIGINAL DESCRIPTION: Binary package hint: compiz Here's an image link: http://img543.imageshack.us/i/screenshotdeesktop.png/ If I deactivate the driver it goes back to normal. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: compiz-core 1:0.9.4git20110322-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 NonfreeKernelModules: wl fglrx Architecture: amd64 Date: Mon Apr 4 11:26:19 2011 DistroCodename: natty DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110329.1) InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110329.1) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature_: Ubuntu 2.6.38-7.39-generic 2.6.38 Signal: 6 SourcePackage: compiz StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 free () from /lib/x86_64-linux-gnu/libc.so.6 Title: compiz crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (:1537): libindicator-WARNING **: Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'. (nautilus:1546): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed (:2026): libindicator-WARNING **: Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'. version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/750386/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service
** Changed in: systemd-shim (Debian) Status: Fix Committed => New -- 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/1359439 Title: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service Status in “systemd-shim” package in Ubuntu: In Progress Status in “systemd-shim” package in Debian: New Bug description: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [ 12.677122] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 12.683912] systemd-logind[1057]: Failed to start user service: Unknown unit: user@1000.service [ 12.685157] systemd-logind[1057]: New session c2 of user caravena. [ 12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope [ 234.494478] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 235.514349] systemd-logind[1057]: New session c3 of user lightdm. [ 244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope [ 244.245923] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-7ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 20 18:26:06 2014 InstallationDate: Installed on 2014-04-27 (115 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1359439/+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 1310356] Re: Grey trace beside the scrollbar
I am also seeing this bug (since Trusty), and it's quite annoying! The duplicated bug describes it better. When the application loses focus, the scrollbars turn gray, sometimes. When it regains focus, sometimes the scrollbars stay gray. This is a big usability issue, because a gray scrollbar on a white background is hard to see. It's even worse when the background is also gray (like in the Software Center). It's also ugly. Could someone look into this? This report seems forgotten (the last message was in April). -- You received this bug notification because you are a member of DX Packages, which is subscribed to overlay-scrollbar in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1310356 Title: Grey trace beside the scrollbar Status in Overlay Scrollbar: New Status in “overlay-scrollbar” package in Ubuntu: Triaged Bug description: Some times appears grey traces beside orange. It is reproduced in many ways, for example after minimizing app. This cosmetic bug appears since Trusty. To manage notifications about this bug go to: https://bugs.launchpad.net/overlay-scrollbar/+bug/1310356/+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 1378462] Re: [TOPBLOCKER] cannot reply to second notification
This bug was fixed in the package unity8 - 8.01.1+14.10.20141105.2~rtm- 0ubuntu1 --- unity8 (8.01.1+14.10.20141105.2~rtm-0ubuntu1) 14.09; urgency=medium [ Albert Astals ] * Fix i18n (LP: #1389165) [ Michael Zanetti ] * Fix DBusVariant conversion for launcher emblems (LP: #1387261) * Fix desktop file encoding in launcher (LP: #1387083) [ Alberto Aguirre ] * Add audioRole to QtMultimedia mock * Add a plugin to take screenshots on vol up + vol down [ Nick Dedekind ] * Reset current item selection on deleted. (LP: #1378462) * Added timer to re-assert server value after indicator menu item activation. (LP: #1336715) [ Mirco Müller ] * Added dedicated swipe-to-act button for snap-decisions, which avoids accidental taps/button-presses. (LP: #1358343) [ Michael Terry ] * Don't lock phone if user tries to switch back to an active call. (LP: #1388156) [ Daniel d'Andrada ] * TouchDispatcher: synthesize MouseButtonDblClick events (LP: #1388359) [ Michał Sawicz ] * Bump the version above the version synced from vivid, otherwise train will generate a lower-than-archive version number. * fix positive/negative answer order on the new swipe notification [ Ubuntu daily release ] * New rebuild forced unity8 (8.01+15.04.20141030-0ubuntu1) vivid; urgency=medium [ Michael Terry ] * Provide 'passphrase' as a field of Components.Lockscreen * Fix a race between Qml loading and DBus registration that caused problems when jenkins tried to unlock the phone. * Set domain explicitly for the Dialogs component because the welcome wizard wants to import it. (LP: #1381731) * When greeter or lockscreen has focus, show active call panel. (LP: #1378872) [ Ted Gould ] * Set the default OOM score for the dash (LP: #1379786) [ Michał Sawicz ] * Revert lp:~unity-team/unity8/flickables-speed-workaround to avoid risk in RTM. * Updated behaviour for zoomable image, workaround for sourcesize (LP: #1333187) [ Michael Frey ] * Added a check for Proximity to determine if we show the lock screen. (LP: #1378012) [ Ying-Chun Liu ] * Add non-interactive code into GenericScopeView. (LP: #1384441) [ Mirco Müller ] * Also use modal nature of snap-decision notifications when greeter/lockscreen is shown. This fixes LP: #1378827. (LP: #1378827) [ Michael Zanetti ] * Make the launcher update on dconf changes (LP: #1376707) * exit spread on background tap (LP: #1368261) * Use an index instead of a scope id in DashCommunicator (LP: #1376044) [ Andrea Cimitan ] * Updated behaviour for zoomable image, workaround for sourcesize (LP: #1333187) [ Daniel d'Andrada ] * Make TouchGate synthesize QMouseEvents for mouse-based target items * Don't specify a distanceThreshold as it conflicts with hintDisplacment -- Ubuntu daily releaseWed, 05 Nov 2014 14:39:41 + ** Changed in: unity8 (Ubuntu RTM) Status: In Progress => Fix Released -- 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/1378462 Title: [TOPBLOCKER] cannot reply to second notification Status in “indicator-messages” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: build 88, rtm on krillin - unlock the phone - make sure messaging-app is not running - send two sms messages to the phone - once they appear, open the messaging-menu - reply to the first message by clicking the message which makes it expand to reveal the send field - this works - attempt to reply to the second message by clicking the message to make it expand Expected results: the item should expand and allow you to send a message Actual results: the item cannot be expanded and you can't reply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1378462/+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 1389888] Re: unity not shown only desktop with new nvida 970 card
Thank you for your fast feedback. I was not able to execute dconf reset -f /org/compiz/ at tty7 because i was not able to open a shell and on tty1 i got the error "cannot autolaunch d-bus without x11 display". So I did the work myself as good as i could on tty1. sudo rm -rf ~/.config/dconf/user sudo rm -rf ~/.cache/compizconfig-1 sudo apt-get install --reinstall compiz-core compiz After a reboot the unity desktop was working again. Thank you guys. I don't know if there is be a better and cleaner solution. Your unity_support_test returns now OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 970/PCIe/SSE2 OpenGL version string: 4.4.0 NVIDIA 343.22 Not software rendered:yes Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program:yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object:yes GL version is 1.4+: yes Unity 3D supported: yes -- 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/1389888 Title: unity not shown only desktop with new nvida 970 card Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Hi I have a new Nvidia 970 card. This card is supported starting nvidia-343, so I installed them using ppa:xorg-edgers/ppa . After a reboot I see the login screen, I'm able to login but the top-right menu and the unity bar on the left side is missing. But I'm able to see my mouse and on a right-click I get a pop-menu. What I've done so far: - reinstalled ubuntu-desktop unity compizconfig-settings-manager I'm added my log files to help you. Can I do anything else to help you? I hope you can help me. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1389888/+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 1368101] Re: Stopped apps don't restart when launched from another app
** Changed in: qtmir Status: Fix Committed => Fix Released ** Changed in: qtmir (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1368101 Title: Stopped apps don't restart when launched from another app Status in Qt integration with the Mir display server: Fix Released Status in “qtmir” package in Ubuntu: Fix Released Status in “url-dispatcher” package in Ubuntu: Opinion Bug description: Steps to reproduce:- 1) Open twitter webapp and sign in 2) Open browser 3) Open some other apps to ensure browser gets cleaned up by app lifecycle 4) Switch to twitter 5) Click on a link in a tweet Expected behaviour:- * Clicked link opens in browser Actual behaviour:- * Nothing Note, you can swipe back to browser to "wake" it up from suspend, then back to twitter, click the link and it _will_ switch back to browser and open the link. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1368101/+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 1379152] Re: Needs building dependency on libmtdev-dev (or making QPlatformSupport public)
** Changed in: qtmir 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/1379152 Title: Needs building dependency on libmtdev-dev (or making QPlatformSupport public) Status in Application menu for Qt5: New Status in Qt integration with the Mir display server: Fix Released Status in QT Ubuntu: New Status in “appmenu-qt5” package in Ubuntu: New Status in “maliit-framework” package in Ubuntu: New Status in “qtmir” package in Ubuntu: Fix Released Status in “qtubuntu” package in Ubuntu: New Status in Debian GNU/Linux: Won't Fix Status in “qtmir” package in Ubuntu RTM: Fix Released Bug description: Because of packaging changes in Qt Base in Qt 5.3.2, packages using qplatformsupport from private headers will need to add an additional dependency to compile against it. From Debian bug report: --- This comes from QPlatformSupport stuff which creates a static library that needs this linking. It also happens that QPlatformSupport is private stuff, so there is really no way to solve this but either stop using private stuff or helping upstream to make QPlatformSupport public (which would be really helpful). This will in turn mean that it will become a dynamic lib and this bug can be fixed. --- So: A) someone works in qtbase upstream to make the QPlatformSupport public, or B) workaround with adding libmtdev-dev build dependencies This bug refers more to the B) option to get Qt 5.3.2 packages move forward. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1379152/+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 1386714] Re: Window Spread's type-to-search conflicts in maximization of open windows
*** This bug is a duplicate of bug 1316265 *** https://bugs.launchpad.net/bugs/1316265 ** Summary changed: - Window Spread search conflicts in maximization of open windows + Window Spread's type-to-search conflicts in maximization of open windows -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1386714 Title: Window Spread's type-to-search conflicts in maximization of open windows Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: To reproduce the bug: 1. open multiple windows; 2. open Window Spread/Scale (Super+W); 3. search for a window and select it; 4. now switch to another window without using Window Spread again; 5. try to maximize/unmaximize window. You will see the maximized window is expanded horizontally and vertically, but there are two title bars i.e. the window keeps its title bar separate from the top indicator bar even after maximization. This bug doesn't affect windows opened after window spread search. Opening Window Spread again without searching will fix the bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 Uname: Linux 3.16.0-031600-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: Tue Oct 28 17:28:34 2014 InstallationDate: Installed on 2014-10-02 (25 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386714/+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 1386714] Re: Window Spread's type-to-search conflicts in maximization of open windows
*** This bug is a duplicate of bug 1316265 *** https://bugs.launchpad.net/bugs/1316265 This is NOT a duplicate of bug #1316265. This is different and ONLY occurs when you search for a window by TYPING. A workaround for this will be opening and closing the Window Spread (for exmple by pressing Super+W twice). ** Description changed: To reproduce the bug: 1. open multiple windows; 2. open Window Spread/Scale (Super+W); - 3. search for a window and select it; + 3. search for a window by typing and select it; 4. now switch to another window without using Window Spread again; 5. try to maximize/unmaximize window. You will see the maximized window is expanded horizontally and vertically, but there are two title bars i.e. the window keeps its title bar separate from the top indicator bar even after maximization. This bug doesn't affect windows opened after window spread search. Opening Window Spread again without searching will fix the bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 Uname: Linux 3.16.0-031600-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: Tue Oct 28 17:28:34 2014 InstallationDate: Installed on 2014-10-02 (25 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1386714 Title: Window Spread's type-to-search conflicts in maximization of open windows Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: To reproduce the bug: 1. open multiple windows; 2. open Window Spread/Scale (Super+W); 3. search for a window by typing and select it; 4. now switch to another window without using Window Spread again; 5. try to maximize/unmaximize window. You will see the maximized window is expanded horizontally and vertically, but there are two title bars i.e. the window keeps its title bar separate from the top indicator bar even after maximization. This bug doesn't affect windows opened after window spread search. Opening Window Spread again without searching will fix the bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 Uname: Linux 3.16.0-031600-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: Tue Oct 28 17:28:34 2014 InstallationDate: Installed on 2014-10-02 (25 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386714/+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 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering
Comments #7 and #9 are describing a different bug related to using keyboard on window spread: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1386714 This bug occurs for me when I disabled and re-enabled window spread in Unity Tweak Tool. I could solve the problem in a strange way: 1. selected Restore Settings of window spread on Unity Tweak Tool; 2. disabled and re-enabled the window spread on Unity Tweak Tool; Suddenly Ubuntu Unity Plugin got disabled and I lost window decorations and indicators. 3. I opened a Terminal, enter `ccsm` to open CompizConfig Settings Manager; 4. noticed "Gnome Compatibility" and "Window Decorations" are enabled, both of which conflict with Unity Plugin; 5. enabled Unity Plugin and resolve conflicts with those two. Now I can use window spread without problem except the type-to-search which I've described in lp: 1386714. -- 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/1316265 Title: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: A maximized application's title bar does not merge into the menu bar once a user has performed Super + W (window slide). Note that if one does not do Super+E, then the bars to merge together. However, once Super+E has been performed, this bug persists for the lifetime of the windowed application. If the application is restarted after doing Super+E, then the bug is gone. Thus, it seems like Super+E introduces this bug for the lifetime of the windowed application. Expected behavior: Maximized window's title bar is merged into menu bar. Observed: Does not occur after Super+W is performed. Try this out using Terminal. ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon May 5 14:48:01 2014 InstallationDate: Installed on 2013-09-08 (239 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1316265/+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
Will try to generate another bug. Meanwhile here's the printout from the gdb commands: similar to above Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `compiz'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f4ebcc67439 in unity::UnityScreen::paintDisplay ( this=this@entry=0xb0f000) at /build/buildd/unity-7.3.1+14.10.20141016/plugins/unityshell/src/unityshell.cpp:837 837 /build/buildd/unity-7.3.1+14.10.20141016/plugins/unityshell/src/unityshell.cpp: No such file or directory. (gdb) print gpu_deviceUsing host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `compiz'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f4ebcc67439 in unity::UnityScreen::paintDisplay ( this=this@entry=0xb0f000) at /build/buildd/unity-7.3.1+14.10.20141016/plugins/unityshell/src/unityshell.cpp:837 837 /build/buildd/unity-7.3.1+14.10.20141016/plugins/unityshell/src/unityshell.cpp: No such file or directory. (gdb) print gpu_device $1 = (gdb) print *gpu_device value has been optimized out (gdb) print gpu_device->backup_texture0_ value has been optimized out (gdb) print *(gpu_device->backup_texture0_) value has been optimized out (gdb) print gpu_device->backup_texture0_->_NumMipLevel value has been optimized out (gdb) print gpu_device->backup_texture0_->_SurfaceArray value has been optimized out (gdb) $1 = (gdb) print *gpu_device value has been optimized out (gdb) print gpu_device->backup_texture0_ value has been optimized out (gdb) print *(gpu_device->backup_texture0_) value has been optimized out (gdb) print gpu_device->backup_texture0_->_NumMipLevel value has been optimized out (gdb) print gpu_device->backup_texture0_->_SurfaceArray value has been optimized out (gdb) ? BTW, zsync daily build on 11/06, iso booted to same symptoms. -- 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= LANG=en_US.UTF-8 XDG_RUNTIME_DIR= 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.
[Dx-packages] [Bug 1366351] Re: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings-daemon goes away
Tried sudo ubuntu-bug /var/crash/_usr_bin_compiz.1000.crash get a drop down message that ubuntu has experienced an internal error. Nothing else. Tried removing the *upload and *uploaded files, same thing. Nothing past the first drop down... Any ideas? Maybe install the new .iso and try ubuntu-bug on that one. Too late tonight. 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/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= LANG=en_US.UTF-8 XDG_RUNTIME_DIR= 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,
