Re: [Compiz] [Bug 751605] Re: Multi-monitor - Windows maximize on the wrong monitor
Here is a way to reproduce it 100% of the time. 1. Have the bigger monitor on the left, and have a window there that is bigger in at least one dimension than the second monitor on the right. 2. Drag the window to the second monitor, and either first drop it there, and then maximize it (by pushing the window border against the panel (a correct maximize outline is shown), and let go, or by still dragging the window push it against the panel (still showing the right maximize outline. 3. Release the mouse button. The window should now be maximized on the smaller right monitor, but in fact it maximized on the larger left monitor instead. On 13 Nov 2012 07:47, Daniel van Vugt daniel.van.v...@canonical.com wrote: OK, it took me a surprisingly long time to reproduce the problem but now I can reproduce it in some unnatural cases: (a) The centre of the window is below the bottom of the bottom-most monitor (or right of the right-most); or (b) The height of the window is greater than the height of the monitor it's mostly on (and probably applies to width too). I still cannot reproduce the bug in any natural case where (c) a window smaller than the monitor it's on (and centred) fails to maximize on that monitor. That's the main case reported at the top of the bug and the main case that worries me. I can't reproduce it. Can anyone reproduce (c) any more or is it just (a) and (b) that are a problem? -- You received this bug notification because you are subscribed to a duplicate bug report (966547). https://bugs.launchpad.net/bugs/751605 Title: Multi-monitor - Windows maximize on the wrong monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/751605/+subscriptions -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/751605 Title: Multi-monitor - Windows maximize on the wrong monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/751605/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 751605] Re: Multi-monitor - Windows maximize on the wrong monitor
wacked_up: That's case (b) I described above and can already reproduce. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/751605 Title: Multi-monitor - Windows maximize on the wrong monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/751605/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 751605] Re: Multi-monitor - Windows maximize on the wrong monitor
I don't remember ever encountering case (a), and I use Ubuntu 10 hours every day. I've been using Unity only since 12.04 though. Maybe case (a) has been already fixed since the original report (from 2011-04). -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/751605 Title: Multi-monitor - Windows maximize on the wrong monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/751605/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 751605] Re: Multi-monitor - Windows maximize on the wrong monitor
No, cases (a) and (b) I have reproduced with the latest compiz 0.9.9 source. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/751605 Title: Multi-monitor - Windows maximize on the wrong monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/751605/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 751605] Re: Multi-monitor - Windows maximize on the wrong monitor
Sorry Daniel, in my comment I meant case (c)! I can also reproduce cases (a) and (b) here :-) -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/751605 Title: Multi-monitor - Windows maximize on the wrong monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/751605/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 751605] Re: Multi-monitor - Windows maximize on the wrong monitor
Daniel: Case (c) works for me, meaning small windows maximize correctly - it's *not* buggy here. Regarding (b), it's not just the height that triggers the bug, it's also the width: If any current window dimension doesn't fit onto the selected monitor, it maximizes to the other (larger) one instead. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/751605 Title: Multi-monitor - Windows maximize on the wrong monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/751605/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1078226] Re: fails to load background picture in raring daily
Thank you for your bug report, can you add your xsession-errors to the bug? ** Package changed: compiz (Ubuntu) = nautilus (Ubuntu) ** Changed in: nautilus (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1078226 Title: fails to load background picture in raring daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1078226/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1078226] Re: fails to load background picture in raring daily
** Attachment added: gray-boxes.png https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1078226/+attachment/3431964/+files/gray-boxes.png ** Changed in: compiz (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1078226 Title: fails to load background picture in raring daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1078226/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 751605] Re: Multi-monitor - Windows maximize on the wrong monitor
** Changed in: compiz Status: Triaged = In Progress -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/751605 Title: Multi-monitor - Windows maximize on the wrong monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/751605/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 751605] Re: Multi-monitor - Windows maximize on the wrong monitor
Daniel: my understanding is that case (b) is what we're seeing - I don't think I've seen (c). With two monitors of different size, it's very easy to get a window slightly larger than the smaller one. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/751605 Title: Multi-monitor - Windows maximize on the wrong monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/751605/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 770515] Re: The keybind of Unity's launcher conflicts with Magnifier plugin of Compiz
When I activate the Compz-Magnifier with the Shortcut Super+m it also take effect to the Alt+Enter - shortcut. And this is a very important shortcut in cause of the file and folder properties. That means: when the magnifier is activ and I want to change the properties (e.g. the rights-management) of a file the magnifier will get activ... I try to eradicate this problem with dconf, gconf - even with the .xml-Files they used, but I can't solve this. And it is quite annoying to deactivate the magnifier whenever I wanna change the access rights of an element, because Alt+Enter is much more comfortable then do a rightclick and choose properties. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/770515 Title: The keybind of Unity's launcher conflicts with Magnifier plugin of Compiz To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/770515/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 994841] Re: 'make test' fails lots of test cases if you don't have Xvfb installed
** Changed in: compiz-core Milestone: 0.9.7.10 = None -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/994841 Title: 'make test' fails lots of test cases if you don't have Xvfb installed To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/994841/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 956986] Re: compiz crashed with SIGSEGV when imgsvg is loaded, in getCompPluginVTable20090315_imgsvg() from dlloaderLoadPlugin() from CompPlugin::load()
** Description changed: + == Impact == + + Crash when disabling a plugin. + + == Test case == + using ccsm, after disabling session management, got this error. + + == Regression potential == + + Very low, the commit is an additional dependency to a makefile. + ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: compiz-core 1:0.9.7.0+bzr3035-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 .tmp.unity.support.test.0: - + ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 CompizPlugins: [core,composite,opengl,notification,maximumize,imgjpeg,compiztoolbox,decor,move,gnomecompat,wobbly,imgsvg,text,imgpng,workarounds,resize,kdecompat,cube,rotate,resizeinfo,unityshell,unitymtgrabhandles] CompositorRunning: compiz CrashCounter: 1 Date: Fri Mar 16 10:53:28 2012 Disassembly: = 0x75a6: Cannot access memory at address 0x75a6 DistUpgraded: Log time: 2012-03-03 15:54:54.478616 DistroCodename: precise DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: - Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Device [1043:8340] -Subsystem: ASUSTeK Computer Inc. Device [1043:8340] + Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Device [1043:8340] + Subsystem: ASUSTeK Computer Inc. Device [1043:8340] InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386 (20100429.4) MachineType: ASUSTeK Computer INC. 1000H ProcCmdline: compiz ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae root=UUID=c214beb7-4177-4333-ace3-7e5d86fd3c91 ro splash vga=788 quiet splash security=selinux selinux=1 vt.handoff=7 SegvAnalysis: - Segfault happened at: 0x75a6:Cannot access memory at address 0x75a6 - PC (0x75a6) not located in a known VMA region (needed executable region)! + Segfault happened at: 0x75a6:Cannot access memory at address 0x75a6 + PC (0x75a6) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: - ?? () - getCompPluginVTable20090315_imgsvg () from /usr/lib/compiz/libimgsvg.so - ?? () from /usr/lib/libcompiz_core.so.ABI-20120228 - CompPlugin::load(char const*) () from /usr/lib/libcompiz_core.so.ABI-20120228 - compiz::private_screen::PluginManager::updatePlugins() () from /usr/lib/libcompiz_core.so.ABI-20120228 + ?? () + getCompPluginVTable20090315_imgsvg () from /usr/lib/compiz/libimgsvg.so + ?? () from /usr/lib/libcompiz_core.so.ABI-20120228 + CompPlugin::load(char const*) () from /usr/lib/libcompiz_core.so.ABI-20120228 + compiz::private_screen::PluginManager::updatePlugins() () from /usr/lib/libcompiz_core.so.ABI-20120228 Title: compiz crashed with SIGSEGV in getCompPluginVTable20090315_imgsvg() UpgradeStatus: Upgraded to precise on 2012-03-05 (10 days ago) UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 02/18/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000H dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1701:bd02/18/2009:svnASUSTeKComputerINC.:pn1000H:pvrx.x:rvnASUSTeKComputerINC.:rn1000H:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000H dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.7.0+bzr3035-0ubuntu1 version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Description changed: - == Impact == + [Impact] Crash when disabling a plugin. - == Test case == + [Test Case] using ccsm, after disabling session management, got this error. - == Regression potential == + [Regression Potential] Very low, the commit is an additional dependency to a makefile. - ProblemType: Crash DistroRelease: Ubuntu
[Compiz] [Bug 976032] Re: Place plugin problem with panel in fullscreen and gnome classic
Fix Released in this bug's compiz(Ubuntu) means it's fixed for the newest Ubuntu release at the time of marking it fixed. It has now also been nominated for 12.04 as per SRU process, and the fix is testable in https://launchpad.net/~unity-team/+archive/sru (ppa:unity-team/sru). There will be additional verification needed when the stable release upgrade hits precise-proposed. ** Description changed: + [Impact] + + Flash video fullscreen problem with GNOME panel. + + [Test Case] + In precise, when I want watch a flash video in fullscreen (like youtube or other flash site), the gnome panel doesn't dissapear. If I disable the place plugin with CCSM it works well. I use the last version of compiz : 1:0.9.7.4-0ubuntu3. + + [Regression Potential] + + Window placement in general, should be tested by manual/checkbox tests. + The same commit has been well tested in Ubuntu 12.10. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/976032 Title: Place plugin problem with panel in fullscreen and gnome classic To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/976032/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 974242] Re: Compiz is moving windows against my will
** Description changed: + [Impact] + + Regression in window handling when using Gnome Classic. + + [Test case] + + 1. (multi-monitor) Place a window between first and second monitor. The + window should not be forced back. + + 2. Place a window half-off the bottom of the screen. The window should + not snap back up and there should always be a way to detach it from the + bottom of the screen. + + [Regression potential] + + Window placement in general, should be tested by manual/checkbox tests. + The same commit has been well tested in Ubuntu 12.10. + + + -- original bug report -- + My screen is Nvidia Twinview setup and I'm using Gnome Classic with Compiz. I have found that since updating to 12.04 windows have two detrimental regressions. 1. If I place a window between the first and second monitor (so it overlaps both), the window is forced back over. I can understand this for off-screen windows but between-monitors is silly. And there should be an option for turning this off if there isn't one already. 2. If I place a window half-off the bottom of the screen, all hell breaks loose. Firstly it snaps back up so it's all on the screen (makes sense if you like that sort of thing), but after that, there's no way to detach it from the bottom of the screen. As soon as you do (and then click anywhere) it snaps back down so the bottom of the window is back at the bottom of the screen. -The same is true with the top (if you move a window too high up (say + The same is true with the top (if you move a window too high up (say holding alt and left-click-dragging the bottom up). I've found no way to work around this other than to close the window and start again, or restart compiz. The first is a dual-screen issue, the second might affect everybody; but they definitely seem related. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: compiz 1:0.9.7.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .tmp.unity.support.test.0: ApportVersion: 2.0-0ubuntu4 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,move,commands,gnomecompat,mousepoll,workarounds,compiztoolbox,resize,place,resizeinfo,ezoom] CompositorRunning: compiz Date: Thu Apr 5 13:26:27 2012 DistUpgraded: 2012-04-03 15:47:41,715 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF110 [GeForce GTX 580] [10de:1080] (rev a1) (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Gigabyte Technology Co., Ltd. X58A-UD7 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic root=UUID=1b66bb9e-5b02-49f1-8cf9-bc3f649d70a6 ro nomodeset pcie_aspm=force SourcePackage: compiz UpgradeStatus: Upgraded to precise on 2012-04-03 (1 days ago) dmi.bios.date: 08/24/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: X58A-UD7 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd08/24/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD7:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD7:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD7 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.7.4-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/974242 Title: Compiz is moving windows against my will To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/974242/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More
[Compiz] [Bug 1057263] Re: gtk-window-decorator leaks large numbers of pixmaps and pixmap memory
** Description changed: + [Impact] + + Memory leak when resizing window in normal mode. + + [Test Case] + Test case: 1. Install xrestop (sudo apt-get install xrestop) 2. Run xrestop and look for the gtk-window-decorator row 3. Note the values for Pxms and Pxm mem. 4. Resize a window rapidly (make sure you have Normal resize mode, not Rectangle) Expected: No significant change in Pxm metrics. Observed: Hundreds of pixmaps leaked and Pxm mem grows by several megabytes per second. + + [Regrsesion Potential] + + Low, used in Ubuntu 12.10 as well without regressions. ** Description changed: [Impact] Memory leak when resizing window in normal mode. [Test Case] Test case: 1. Install xrestop (sudo apt-get install xrestop) 2. Run xrestop and look for the gtk-window-decorator row 3. Note the values for Pxms and Pxm mem. 4. Resize a window rapidly (make sure you have Normal resize mode, not Rectangle) Expected: No significant change in Pxm metrics. Observed: Hundreds of pixmaps leaked and Pxm mem grows by several megabytes per second. - [Regrsesion Potential] + [Regression Potential] Low, used in Ubuntu 12.10 as well without regressions. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1057263 Title: gtk-window-decorator leaks large numbers of pixmaps and pixmap memory To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1057263/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1050610] Re: gtk-window-decorator leaking window handles. Window operations become sluggish after a few days of usage
** Description changed:
+ [Impact]
+
+ Memory leaking causing user visible problems like performance
+ degradation.
+
+ [Test Case]
+
+ GTK-Window-Decorator Resource Usage
+ ===
+ Sam Spilsbury sam.spilsb...@canonical.com
+
+ XRestop usage
+ -
+ #. Install xrestop (sudo apt-get install xrestop)
+ #. Run xrestop (eg, $ xrestop )
+ #. Note the number in the Wns column for gtk-window-decorator
+ #. Open a window
+ #. Close that window
+ #. The number should be the same
+
+ [Regression Potential]
+
+ Low, has been well tested in Ubuntu 12.10.
+
+ --- original bug report ---
+
gtk-window-decorator appears to be leaking window handles when windows
are opened. The leak(s) correspond with performance degradation over
time, especially on systems with relatively low amounts of VRAM (I have
256MB).
User-visible symptoms include:
* Performance degradation over time
* Sluggish animations, such as when using Super-W and Super-S
* When switching windows, window contents briefly drawn as black rectangles
before being rendered correctly
* Window decorations not drawn on new windows
To reproduce:
1) install xrestop (apt-get install xrestop)
2) In a terminal, launch xrestop. Keep it running, and observe the number of
'Wins' and amount of pixmam memory ('Pxm mem') associated with the
gtk-window-decorator process
3) Open a new terminal (or any other) window. Observe that the number of
windows had gone up by some amount. Opening a terminal window reliably results
in exactly 19 extra window handles on my system.
- 4) Close the window
+ 4) Close the window
Expected results:
Per xrestop, the number of window handles goes down when you close the
window. (Are some of the handles are related to window-open animation? In that
case I'd expect them to be disposed of when the animation is complete)
Actual results:
Per xrestop, the number of window handles remains the same when you close the
window.
I also observed that the total pixmap memory used by gtk-window-
decorator steadily climbs over time. While closing a window does appear
to release some pixmap memory, it does not seem to release all of it.
Performace on my system with 256MB VRAM got really bad when the number
of window handles in gtk-window-decorator climbed above 7000 and the
total pixmap memory used by gtk-window-decorator was about 75MB.
Killing + restarting gtk-window-decorator temporarily solves the
problem.
-
xrestop output:
xrestop - Display: localhost
- Monitoring 32 clients. XErrors: 7
- Pixmaps: 169216K total, Other: 672K total, All: 169889K total
+ Monitoring 32 clients. XErrors: 7
+ Pixmaps: 169216K total, Other: 672K total, All: 169889K total
- res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier
+ res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier
260 7176 671 495 72478983K187K 79171K 2359
gtk-window-dec
0c0 129221 112 1536457130K391K 57521K ? Compiz
-
top output:
- PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
- 1306 root 20 0 573m 461m 6364 R 105.5 11.7 357:52.15 Xorg
+ PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
+ 1306 root 20 0 573m 461m 6364 R 105.5 11.7 357:52.15 Xorg
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: compiz-gnome 1:0.9.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary:
.proc.driver.nvidia.version:
- NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.43 Sun Aug 19 20:14:03
PDT 2012
- GCC version: gcc version 4.7.1 20120908 (prerelease) (Ubuntu/Linaro
4.7.1-8ubuntu1)
+ NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.43 Sun Aug 19 20:14:03
PDT 2012
+ GCC version: gcc version 4.7.1 20120908 (prerelease) (Ubuntu/Linaro
4.7.1-8ubuntu1)
.proc.driver.nvidia.warnings.fbdev:
- Your system is not currently configured to drive a VGA console
- on the primary VGA device. The NVIDIA Linux graphics driver
- requires the use of a text-mode VGA console. Use of other console
- drivers including, but not limited to, vesafb, may result in
- corruption and stability problems, and is not supported.
+ Your system is not currently configured to drive a VGA console
+ on the primary VGA device. The NVIDIA Linux graphics driver
+ requires the use of a text-mode VGA console. Use of other console
+ drivers including, but not limited to, vesafb, may result in
+ corruption and stability problems, and is not supported.
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for
[Compiz] [Bug 1077802] Re: Compiz 0.9.7 branch currently failing to build on ARM in Ubuntu 12.04 packaging
** Description changed: + [Impact] + + ARM build failure] + + [Test Case] + + Check that ARM builds succeed. + + [Regression Potential] + + Low and ARM-specific (only a patch applied to ARM builds modified). A + similar change to other fixes to not use GL paths when using GLES. The + other part of the fix is just removing a NEWS file change. + + + --- original bug report --- + Latest bzr3121 of Compiz Core 0.9.7 branch seems to be failing. A buildlog at https://launchpadlibrarian.net/122486781/buildlog_ubuntu- precise- armhf.compiz_1%3A0.9.7.8%2Bbzr3121-0ubuntu1~test1_FAILEDTOBUILD.txt.gz Since ARM support in 12.04 is achieved via a distro patch, this is technically a Ubuntu package problem, not upstream Compiz Core problem. ---cut--- [ 53%] Building CXX object plugins/copytex/CMakeFiles/copytex.dir/src/copytex.cpp.o cd /build/buildd/compiz-0.9.7.8+bzr3121/obj-arm-linux-gnueabihf/plugins/copytex /usr/bin/c++ -Dcopytex_EXPORTS -DHAVE_SCANDIR_POSIX -DHAVE_SCANDIR_POSIX -DHAVE_SCANDIR_POSIX -DHAVE_CONFIG_H -DHAVE_SCANDIR_POSIX -DCOPYTEX_DEFSADD -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -fPIC -Wall -Wno-deprecated-declarations -Werror -fPIC -Wall -Wno-deprecated-declarations -Werror -fPIC -Wall -Wno-deprecated-declarations -Werror -fPIC -Wall -Wno-deprecated-declarations -Werror -O2 -g -DQT_NO_DEBUG -fPIC -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/../include -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/../src -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/../src/timer/include -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/../src/string/include -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/../src/pluginclasshandler/include -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/../src/point/include -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/../src/rect/include -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/../src/window/geometry/include -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/../src/window/geometry-saver/include -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/../src/window/extents/include -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/../src/window/constrainment/include -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/../logmessage/include -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/copytex/src -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/copytex/include -I/build/buildd/compiz-0.9.7.8+bzr3121/obj-arm-linux-gnueabihf/generated -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/copytex/../composite/include -I/build/buildd/compiz-0.9.7.8+bzr3121/plugins/copytex/../opengl/include -I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/glibmm-2.4 -I/usr/lib/arm-linux-gnueabihf/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/arm-linux-gnueabihf/sigc++-2.0/include -I/usr/include/startup-notification-1.0 -I/build/buildd/compiz-0.9.7.8+bzr3121/include -I/build/buildd/compiz-0.9.7.8+bzr3121/obj-arm-linux-gnueabihf -DPREFIX='/usr' -o CMakeFiles/copytex.dir/src/copytex.cpp.o -c /build/buildd/compiz-0.9.7.8+bzr3121/plugins/copytex/src/copytex.cpp In file included from /build/buildd/compiz-0.9.7.8+bzr3121/plugins/copytex/src/copytex.h:28:0, from /build/buildd/compiz-0.9.7.8+bzr3121/plugins/copytex/src/copytex.cpp:25: /build/buildd/compiz-0.9.7.8+bzr3121/plugins/copytex/../opengl/include/opengl/opengl.h:31:19: fatal error: GL/gl.h: No such file or directory compilation terminated. --cut--- -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1077802 Title: Compiz 0.9.7 branch currently failing to build on ARM in Ubuntu 12.04 packaging To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/1077802/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 944653] Re: compiz crashed on startup with SIGSEGV in strstr() from GLScreen::GLScreen()
The fix is now testable at https://launchpad.net/~unity- team/+archive/sru (ppa:unity-team/sru). Actual verification action will be required when the new SRU hits precise-proposed. ** Description changed: - Ubuntu 12.04 beta1 + [Impact] + + A frequent crasher. + + [Test Case] + + Ensure no crashes happen with the same stack trace, but there is no one + clear test case. + + [Regression Potential] + + Low, the commit is a simple NULL check to prevent a crash and show a + warning in log instead. + + --- original bug report --- + + Ubuntu 12.04 beta1 unity 5.4.0-0ubuntu2 compiz 1:0.9.7.0~bzr2995-0ubuntu5 compiz crashes frequently after boot into system. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: compiz-core 1:0.9.7.0~bzr2995-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 295.20 Mon Feb 6 21:07:30 PST 2012 - GCC version: gcc version 4.6.2 (Ubuntu/Linaro 4.6.2-16ubuntu1) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 295.20 Mon Feb 6 21:07:30 PST 2012 + GCC version: gcc version 4.6.2 (Ubuntu/Linaro 4.6.2-16ubuntu1) .tmp.unity.support.test.0: - + ApportVersion: 1.93-0ubuntu2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,mousepoll,resize,imgpng,place,session,snap,move,grid,vpswitch,unitymtgrabhandles,wall,animation,expo,fade,workarounds,ezoom,scale,unityshell] CompositorRunning: compiz CurrentDmesg: - [ 44.441706] type=1400 audit(1330680576.805:24): apparmor=DENIED operation=open parent=2141 profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2142 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 - [ 50.880026] eth2: no IPv6 routers present + [ 44.441706] type=1400 audit(1330680576.805:24): apparmor=DENIED operation=open parent=2141 profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2142 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 + [ 50.880026] eth2: no IPv6 routers present Date: Fri Mar 2 17:27:29 2012 DistUpgraded: Log time: 2012-03-02 14:48:08.811970 DistroCodename: precise DistroVariant: ubuntu DkmsStatus: - bcmwl, 5.100.82.38+bdcom, 3.2.0-17-generic, x86_64: installed - nvidia-current, 295.20, 3.2.0-17-generic, x86_64: installed + bcmwl, 5.100.82.38+bdcom, 3.2.0-17-generic, x86_64: installed + nvidia-current, 295.20, 3.2.0-17-generic, x86_64: installed ExecutablePath: /usr/bin/compiz GraphicsCard: - NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) -Subsystem: Apple Inc. Device [106b:00b9] + NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) + Subsystem: Apple Inc. Device [106b:00b9] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) JockeyStatus: - kmod:wl - Broadcom STA wireless driver (Proprietary, Enabled, In use) [auto-install] - xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) - xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) + kmod:wl - Broadcom STA wireless driver (Proprietary, Enabled, In use) [auto-install] + xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) + xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: Apple Inc. MacBookPro5,5 ProcCmdline: Compiz ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=7b317aa3-857b-4076-888b-7d3602de212a ro quiet splash vt.handoff=7 SegvAnalysis: - Segfault happened at: 0x7f56f26a6d74:movzbl (%rdi),%eax - PC (0x7f56f26a6d74) ok - source (%rdi) (0x) not located in a known VMA region (needed readable region)! - destination %eax ok + Segfault happened at: 0x7f56f26a6d74:movzbl (%rdi),%eax + PC (0x7f56f26a6d74) ok + source (%rdi) (0x) not located in a known VMA region (needed readable region)! + destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: - ?? () from /lib/x86_64-linux-gnu/libc.so.6 - GLScreen::GLScreen(CompScreen*) () from /usr/lib/compiz/libopengl.so - PluginClassHandlerGLScreen, CompScreen, 4::get(CompScreen*) () from /usr/lib/compiz/libopengl.so - CompPlugin::VTableForScreenAndWindowGLScreen, GLWindow::initScreen(CompScreen*) () from /usr/lib/compiz/libopengl.so - CompManager::initPlugin(CompPlugin*) () from /usr/lib/libcompiz_core.so.ABI-20120216 + ?? ()
[Compiz] [Bug 751605] Re: Multi-monitor - Windows maximize on the wrong monitor
I am experiencing b). Like the original reporter, I have a laptop with an external monitor. To reproduce this, all I have to do is drag a window that was sized for the external monitor to the laptop monitor and maximize it. It's not an unnatural thing to do. I have to work around this bug multiple times a day. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/751605 Title: Multi-monitor - Windows maximize on the wrong monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/751605/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 751605] Re: Multi-monitor - Windows maximize on the wrong monitor
Sorry for the noise, but I figured praise-noise is worth it: It's great to finally see some fixing activity on this bug. Thanks a lot! 3 -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/751605 Title: Multi-monitor - Windows maximize on the wrong monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/751605/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1078309] [NEW] multi-monitor, placement: attempt to satisfy size request by opening on the monitor where it fits
Public bug reported: Description:Ubuntu 12.10 Release:12.10 compiz 1:0.9.8.4-0ubuntu3 I have two monitors of different sizes (laptop and external). I have emacs configured for a default frame size that makes efficient use of my external monitor. However, emacs opens with its default-default window size, then changes when it reads my init file. “Smart” placement will more or less randomly place it in either monitor, depending on the apps I have open at the moment, where my mouse cursor is, the day of the week, and direction of the wind. It's fine when it places it on the external, but when it's placed on the laptop, it then tries to resize to larger than would fit on the screen. Expected: the window would be moved to the large monitor, where it fits. What happens instead: it gets maximized; unmaximizing it and then moving it doesn't make it the right size. I have to “Open new frame...” from the emacs menu, then close the old one. This of course happens with other apps too, it's just easier to reproduce with emacs due to the fact that it reads its init file after the window has already been drawn. ** Affects: compiz (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1078309 Title: multi-monitor, placement: attempt to satisfy size request by opening on the monitor where it fits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1078309/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1064602] Re: compiz crashed with SIGSEGV in CompositeScreen::compositingActive() from PrivateCompositeWindow::PrivateCompositeWindow() from CompositeWindow::CompositeWindow()
Problem arises when I launch a second VNC server. Ubuntu 12.04. Did not have this issue with 10.04 or 11.10. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1064602 Title: compiz crashed with SIGSEGV in CompositeScreen::compositingActive() from PrivateCompositeWindow::PrivateCompositeWindow() from CompositeWindow::CompositeWindow() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1064602/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1078309] Re: multi-monitor, placement: attempt to satisfy size request by opening on the monitor where it fits
Trying to understand the exact problem... can I retitle this to: Window opens maximized on a smaller monitor instead of opening on a larger monitor where it would fit ? ** Also affects: compiz Importance: Undecided Status: New ** Changed in: compiz Status: New = Incomplete ** Changed in: compiz (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1078309 Title: multi-monitor, placement: attempt to satisfy size request by opening on the monitor where it fits To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1078309/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 994841] Re: 'make test' fails lots of test cases if you don't have Xvfb installed
Won't Fix. Distro has rejected and reverted the fix in lp:compiz- core/0.9.7 r3123. ** Changed in: compiz-core Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/994841 Title: 'make test' fails lots of test cases if you don't have Xvfb installed To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/994841/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 927168] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpTexture::en
** Changed in: compiz-core Milestone: 0.9.7.10 = 0.9.7.12 -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/927168 Title: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpTexture::enable() from enableFragmentOperationsAndDrawGeometry() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/927168/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 950160] Re: Unity blocks other programs from binding globally to Super+* (* = any key)
** Changed in: compiz-core Milestone: 0.9.7.10 = 0.9.7.12 -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/950160 Title: Unity blocks other programs from binding globally to Super+* (* = any key) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/950160/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1077802] Re: Compiz 0.9.7 branch currently failing to build on ARM in Ubuntu 12.04 packaging
** Changed in: compiz (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1077802 Title: Compiz 0.9.7 branch currently failing to build on ARM in Ubuntu 12.04 packaging To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/1077802/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 754508] Re: Modal dialogs don't appear on the same workspace/monitor as their parent window
Dual-screens in U12.04 is not well implemented. As many have reported, either popups appear on the other screen to the application that launched them, or new applications launched by clicking on images, files etc, all seem to open in the left-most-screen. Somehow, at least on Thinkpad using NVIDIA, the left-most screen seems to always launch new application windows when the app is launched indirectly, say from Nautilus actions like open or edit. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/754508 Title: Modal dialogs don't appear on the same workspace/monitor as their parent window To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/754508/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 944653] Re: compiz crashed on startup with SIGSEGV in strstr() from GLScreen::GLScreen()
Thanks Timo! I tried the ppa and updated compiz; indeed the crash is fixed however the decorator doesn't seem to work when I run kernel 3.2.0-30 or newer. I don't think this is any worse that the previous version of compiz though, in which case I got a crash with the same kernels (with kernel 3.2.0-29 both the old and the new compiz work fine for me by the way). So I have to ask, what changed between kernel 3.2.0-29 and 3.2.0-30 that causes compiz to either crash, or after this fix, causes the decorator to not do anything? I even tried compiz-decorator --replace, it finds and says it starts /usr/bin/gtk-window-decorator but to no effect, all windows I launch are still borderless and the desktop cube is not rotating (I can't switch to other workspaces). Am I hitting some other bug? Any pointers welcome! -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/944653 Title: compiz crashed on startup with SIGSEGV in strstr() from GLScreen::GLScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/944653/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 944653] Re: compiz crashed on startup with SIGSEGV in strstr() from GLScreen::GLScreen()
sordna: Sounds like compiz is crashing or failing to start for some other reason. Hence you won't have window decorations or cube rotation etc. Please try to find a .crash file for it in /var/crash and log a new bug. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/944653 Title: compiz crashed on startup with SIGSEGV in strstr() from GLScreen::GLScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/944653/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 944653] Re: compiz crashed on startup with SIGSEGV in strstr() from GLScreen::GLScreen()
Ok, false alarm, for some reason my nvidia kernel module wasn't being built... I fixed it with 'dpkg-reconfigure nvidia-current' (found this out by running 'compiz --replace ccp' and seeing messages GLX extension missing). Sorry for the noise, but at least I can verify that I did consistently get a compiz crash that was resolved only after upgrading to version 0.9.7.8+bzr3121-0ubuntu1~test6 from ppa:unity-team/sru So the fix is good, thanks to all who made it happen and hope to see it soon in the regular repository for 12.04 LTS. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/944653 Title: compiz crashed on startup with SIGSEGV in strstr() from GLScreen::GLScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/944653/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1050776] [NEW] kde4-window-decorator crashes when starting up with oxygen theme
You have been subscribed to a public bug: I'm using compiz with KDE 4.9.1, and kde4-window-decorator always crashes when launching. Kwin can be started with no problem. The crash report generated by KDE crash handler is attached. ** Affects: compiz Importance: Medium Assignee: Iven Hsu (ivenvd) Status: Fix Committed ** Affects: compiz (Ubuntu) Importance: Undecided Status: Invalid -- kde4-window-decorator crashes when starting up with oxygen theme https://bugs.launchpad.net/bugs/1050776 You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1050776] Re: kde4-window-decorator crashes when starting up with oxygen theme
Fix committed into lp:compiz at revision 3468 ** Package changed: kde-workspace (Ubuntu) = compiz (Ubuntu) ** Changed in: compiz (Ubuntu) Importance: Undecided = Medium ** Also affects: compiz/0.9.8 Importance: Undecided Status: New ** Changed in: compiz/0.9.8 Status: New = Triaged ** Changed in: compiz/0.9.8 Importance: Undecided = Medium -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1050776 Title: kde4-window-decorator crashes when starting up with oxygen theme To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1050776/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 986208] Re: Compiz does not remember user preferences upon system restart
Here's a backtrace from when the options get reset, but I can't quite make sense of it. It looks like compiz gets notified that the gsettings key 'org.compiz.core close-window-key' (which I can't find in dconf- editor!) got changed. As a response to that it sets 'org.gnome.desktop.wm.keybindings close' to the new value (which happens to be the default value), thereby overwriting the user-set value. Which I think would be a terrible idea even if the user had intentionally changed close-window-key. ** Attachment added: backtrace https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/986208/+attachment/3432896/+files/compiz.log -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/986208 Title: Compiz does not remember user preferences upon system restart To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/986208/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
