[Compiz] [Bug 1087193] Re: Windows don't respond to input (mouse clicks) if XShape is disabled or unavailable
Ugh, High now. It seems some other recent change has made the code so fragile that reverting this fix makes windows unclickable even with XShape. ** Changed in: compiz Importance: Medium => High ** Changed in: compiz (Ubuntu) Importance: Medium => High ** Changed in: compiz/0.9.8 Milestone: 0.9.8.8 => 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/1087193 Title: Windows don't respond to input (mouse clicks) if XShape is disabled or unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1087193/+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 1089279] Re: Restored windows' contents are offset from (not aligned with) their frames
Tested reverting r3513. It did not fix the bug. In fact reverting it made things worse (bug 1087193 even when XShape is in use). -- 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/1089279 Title: Restored windows' contents are offset from (not aligned with) their frames To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1089279/+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 1085581] Re: Windows open below panel and launcher, grid does not work at all, window animations missing, and general plugin chaos if built on raring (cmake >= 2.8.10)
** 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 ** Changed in: compiz/0.9.8 Milestone: None => 0.9.8.8 -- 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/1085581 Title: Windows open below panel and launcher, grid does not work at all, window animations missing, and general plugin chaos if built on raring (cmake >= 2.8.10) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1085581/+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 960084] Re: changing font size in gnome-terminal changes terminal dimensions
** Changed in: compiz-core Status: Invalid => Confirmed ** Project changed: unity => compiz ** Changed in: compiz (Ubuntu) Status: Invalid => Confirmed ** Changed in: compiz Milestone: None => 0.9.9.0 ** Changed in: compiz Status: Confirmed => Triaged ** Changed in: compiz-core Status: Confirmed => Triaged ** Changed in: compiz (Ubuntu) Status: Confirmed => Triaged -- 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/960084 Title: changing font size in gnome-terminal changes terminal dimensions To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/960084/+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 1089251] Re: [clang] Multiple segfaults in test: SetSemantics
** Changed in: compiz (Ubuntu) Status: In Progress => Fix Committed -- 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/1089251 Title: [clang] Multiple segfaults in test: SetSemantics To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1089251/+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 1089250] Re: [clang] lp:compiz r3523 FTBFS: unused function 'ListValueToSettingValueList' [-Werror, -Wunused-function]
** Changed in: compiz (Ubuntu) Status: In Progress => Fix Committed -- 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/1089250 Title: [clang] lp:compiz r3523 FTBFS: unused function 'ListValueToSettingValueList' [-Werror,-Wunused-function] To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1089250/+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 1089246] Re: Add support for blacklisting some drivers from using unredirected fullscreen windows
** Changed in: compiz (Ubuntu) Status: In Progress => Fix Committed -- 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/1089246 Title: Add support for blacklisting some drivers from using unredirected fullscreen windows To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1089246/+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 1088996] Re: FTBFS after python2.7 upgrade - missing pyconfig.h
** Also affects: compiz (Ubuntu) Importance: Undecided Status: New ** Changed in: compiz Milestone: None => 0.9.9.0 ** Changed in: compiz (Ubuntu) Assignee: (unassigned) => Łukasz Zemczak (sil2100) ** Changed in: compiz (Ubuntu) Importance: Undecided => High ** Changed in: compiz (Ubuntu) Status: New => Fix Committed -- 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/1088996 Title: FTBFS after python2.7 upgrade - missing pyconfig.h To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1088996/+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 1027211] Re: [nvidia] Moving or resizing windows freezes and stutters on nvidia (especially if some other window is redrawing).
Yeah the fixes are not driver-specific. Everyone will benefit. We're just using nvidia as the test platform because it has the biggest problem with move/resize performance. -- 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/1027211 Title: [nvidia] Moving or resizing windows freezes and stutters on nvidia (especially if some other window is redrawing). To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1027211/+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 1063617] Re: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values
** Changed in: compiz Status: Fix Committed => 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/1063617 Title: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1063617/+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 1088414] Re: On ARM lp:compiz defaults to GL instead of GLES and FTBFS unless you -DBUILD_GLES=ON
** Summary changed: - On ARM lp:compiz defaults to GL instead of GLES and FTBFS unless you -DBUILD_GLESS=ON + On ARM lp:compiz defaults to GL instead of GLES and FTBFS unless you -DBUILD_GLES=ON -- 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/1088414 Title: On ARM lp:compiz defaults to GL instead of GLES and FTBFS unless you -DBUILD_GLES=ON To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1088414/+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 820639] Re: No bindings for scale > 'Initiate window picker for window group' can be set
** Tags added: raring -- 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/820639 Title: No bindings for scale > 'Initiate window picker for window group' can be set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/820639/+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 1089689] Re: clicking on gnome-terminal icon in unity panel moves terminal into current workspace instead of switching to next workspace
Screenshot 1: gnome-terminal created Screenshot 2: View of gnome-terminal over 4 workspaces Screenshot 3: gnome-terminal shifted from workspace 4 to workspace 1 when clicking on gnome-terminal icon in unity panel (should have only shifted me to workspace 4 instead). Screenshot 4: position of gnome-terminal after clicking on unity panel icon in workspace 1 ** Attachment added: "Screenshots of what's happening." https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1089689/+attachment/3458792/+files/screenshots.tar.gz -- 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/1089689 Title: clicking on gnome-terminal icon in unity panel moves terminal into current workspace instead of switching to next workspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1089689/+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 1089689] [NEW] clicking on gnome-terminal icon in unity panel moves terminal into current workspace instead of switching to next workspace
Public bug reported: Description:Ubuntu 12.04.1 LTS Release:12.04 compiz: Installed: 1:0.9.7.8+bzr3121-0ubuntu1 Candidate: 1:0.9.7.8+bzr3121-0ubuntu1 Version table: *** 1:0.9.7.8+bzr3121-0ubuntu1 0 500 http://ubuntu.mirror.rafal.ca/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.7.6-0ubuntu1 0 500 http://ubuntu.mirror.rafal.ca/ubuntu/ precise/main amd64 Packages Expected behavior: If I launch the gnome-terminal in say "workspace 4" and I move back to "workspace 1"; The expected behavior when clicking on the gnome-terminal icon using the unity panel is that I'm switched to "workspace 4". What happened instead. Instead the gnome-terminal window is moved to the current workspace and the window itself is physically moved to the upper left corner of the screen. ** 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/1089689 Title: clicking on gnome-terminal icon in unity panel moves terminal into current workspace instead of switching to next workspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1089689/+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
Re: [Compiz] [Bug 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
@zzecool I think you are having another bug. My shortcuts settings has been kept in every update, even with Bruno's great ppa (again many thanks Bruno, you are awesome). -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
@seb128: argh. I meant "this fixeD everything" (for 12.10 that is). I know it's only one issue per bug report. But the underlying problem is a single commit and many bugs are connected to fixing this bug correctly (which has been done for 12.10). This bug produces issues for people who don't even use "scale all". Most corporte users don't use scale all but they do see the flying windows. @mc3man: the problem fixing this bug is that if you fix it the default behavior changes and you can't change the user settings on upgrade. The only way to do that is ask for user interaction through a notification (the way it happens when you install Dropbox). That would work but bothering the user with notifications is unwanted, so it won't happen. The way I see it this bug is unfixable with the only acceptable solution apparently being the introduction of a second hack that will (I think) introduce even more problems for the next dist-upgrade. -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
I guess I'm missing something here & as I don't use 12.04 should likely shut up Anyway what's the downside to applying the 0.9.7 commit in precise & also adjusting scale.xml.in to get desired results. Did so here on a 12.04 install still hanging around & when creating a new user the bindings & actions seemed fine Super+w picks on current ws Shift+Alt+up picks on all ws's As in - --- compiz-0.9.7.8+bzr3121.orig/plugins/scale/scale.xml.in +++ compiz-0.9.7.8+bzr3121/plugins/scale/scale.xml.in @@ -127,7 +127,7 @@ <_short>Initiate Window Picker <_long>Layout and start transforming windows -Up + w <_short>Initiate Window Picker @@ -145,7 +145,7 @@ <_short>Initiate Window Picker For All Windows <_long>Layout and start transforming all windows - w + Up <_short>Initiate Window Picker For Window Group -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
The thing you seem to forget, Sebastien, is that the core issue is this: A hack was introduced that not only changed the default behavior for all users, but -- more importantly -- also made it impossible to switch back to the desired behavior. In other words, mucking around with people's configs has already been done. How about we own up to the mistake and fix it? The only reasonable way is to revert the ugly hack, and repair the functionality of 'show windows from all workspaces'. Users will have to update their key bindings if they don't like that it's working again. It won't take them more than a minute. I can also add that I work in a corporate environment and everyone I know who uses Ubuntu here is -not- happy about the hack. -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 1027211] Re: [nvidia] Moving or resizing windows freezes and stutters on nvidia (especially if some other window is redrawing).
I know this is tagged as a NVIDIA bug but I have drastically improved window movement performance with fglrx here on Ubuntu 12.10 and the newest builds of the unity-team/staging PPA. I also had stutter/freezing when moving windows after I already opened some other windows. It was the worst when I had Steam open, but it's all smooth now! Great news for Ubuntu 13.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/1027211 Title: [nvidia] Moving or resizing windows freezes and stutters on nvidia (especially if some other window is redrawing). To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1027211/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
@zzecool: what you mention is a bug in compiz itself, it should not be happening and is being worked on... -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
Sorry Seb but your statement about the user data is not valid. I know that in every compiz update i have to reassign all of my modifications in compiz config settings manager because every small compiz update reset them to the default. Hot Corners Modified shortcuts etc . -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
@zzecool: > So while you undo the "hack" why don't you just change - fix the shortcut in the compiz config settings to correspond to the fix ? ( Assign super-W to initiate window picker ) So noone will notice the fix. you can find the reason in comment #158 I wrote a bit earlier, the configuration is user-owned and there is no way we can change user config behind that back for several reasons: - the user config belongs to the user, it would feel wrong to change user settings behind their back, the package management tools don't touch user datas ... - I'm sure you can understand some users would feel uneasy knowing that their datas might be changed by the system behind their back ... how to know which ones, what if something was set the way it was for a reason - the user directory might not be accessible, it might be protected or unmounted -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
zzecool sayd: -I still can't understand .. seb - -You say that if you are going to undo the "hack" the super-W would change the behaviour back to the "for all windows" when it is -documented to be for the current workspace. - -So while you undo the "hack" why don't you just change - fix the shortcut in the compiz config settings to correspond to the fix ? -( Assign super-W to initiate window picker ) So noone will notice the fix. - -I really don't get it , it looks so dead simple. I say::+1000 -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
@mniess: > This fixes everything (tm). that would change the behaviour of super-W for users upgrading though no? > will still leave all the other bugs that would be fixed by reverting the > offending commit (flying windows, ...) that's a different issue from the one this bug is about, this bug is ""Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.". There is no discussion that we should fix other bugs if they exist but: - the number of comments "complaining" that things are broken make it hard to find where the informations are in the bug - one bug report should describe one issue, that bug is about the picker acting on one workspace when it's supposed to include others ones. if you have other issues I would be happy to find resources in the desktop team to look at them and to help to get them resolved but please open a new bug with a short and explanatory description (better if users don't come to turn that one is a flood of comments as well so we can keep the discussion focussed on resolving that issue) > I don't know what feedback you get from corporate users (employees won't come here to report bugs) but I know several small businesses (50-150 employees) that suffer from this bug. We didn't get customers complains about that issue and nobody at Canonical has been complaining about it either. Most people running unity just use the unity-launcher and click on the icons and get what they want, or they use the documented super-W which acts as documented. In all the years I've been using GNOME/compiz or unity I never felt the need to use an "overview of all the wins open over all desktops" ... that would be a lot of things displayed and my workspaces are often organized by activity so the overview makes more sense to me when it's restricted to the workspace/context I'm working with. That's just to say that different people have different workflow and what might seem an end of the world issue is a no issue for others... ( note that I mention unity there because it's the desktop we ship and provide support for ... I do understand that some of you run compiz in other context though and that's fine and should work without bug as well) In any case your users seem to have a workflow built around that feature and it would be good to fix the issue so let's focus on that -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 960084] Re: changing font size in gnome-terminal changes terminal dimensions
Attempting to clarify again. To reproduce the problem: 1.) $ echo $LINES $COLUMNS 24 80 $ 2.) increase font size + + 3.) $ echo $LINES $COLUMNS 20 62 $ 4.) decrease font size - - 5.) $ echo $LINES $COLUMNS 27 92 $ The terminal size in lines and columns should remain the same, while the x window changes size to accommodate. -- 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/960084 Title: changing font size in gnome-terminal changes terminal dimensions To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/960084/+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 1089573] [NEW] clusterssh tiling places windows outside of display on multi-monitor
Public bug reported: I'm running 12.10 with Unity on 2 monitors, the built in laptop display and a larger external monitor. clusterssh automatically tiles the xterm windows it launches, and appears to be using the total width and height of both displays when placing them, resulting in some windows being placed outside the viewable area of the 2 monitors. ** 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/1089573 Title: clusterssh tiling places windows outside of display on multi-monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1089573/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
I still can't understand .. seb You say that if you are going to undo the "hack" the super-W would change the behaviour back to the "for all windows" when it is documented to be for the current workspace. So while you undo the "hack" why don't you just change - fix the shortcut in the compiz config settings to correspond to the fix ? ( Assign super-W to initiate window picker ) So noone will notice the fix. I really don't get it , it looks so dead simple. -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
@seb128: the problem goes much deeper than the "show all windows" thing. As far as I can see the offending commit is just reverted in 12.10 and the shortcuts are set correctly. This fixes everything (tm). *Only* offering an option to show all windows will still leave all the other bugs that would be fixed by reverting the offending commit (flying windows, ...). Just as another incentive to really fix this instead of adding another hack to the first one that causes all the problems. I don't know what feedback you get from corporate users (employees won't come here to report bugs) but I know several small businesses (50-150 employees) that suffer from this bug. We keep many users at 10.04 and the rest uses 12.10 (which we hate because it means a lot of extra work). -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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
Re: [Compiz] [Bug 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
Sebastian, how about switching the behaviours around for 12.04? Maintain the current one as is and change the other to behave like this did. Those who want to have the correct behaviour change the key bindings, and current users are unaffected. Does it make sense? No dia 12 de Dez de 2012 17:48, "Sebastien Bacher" escreveu: > hey everyone, thanks for the interest to Ubuntu/compiz/that issue and > sorry it's taking time to get resolved but comments are turning to > heated tone and insults at this point and that's often non > constructive... > > quite the contrary it might finish by demotivating the people who are on > your side and want to see the issue fixed but are just overworked and > didn't find the time to get to work on that yet > > So could you move the chit-chat to some mailing list or user forum? > > > That said for those who want to help to get the issue resolved we welcome > help on finding a solution which restore the option without changing the > existing behaviour for users: > > Summary of the issue/precise situation: > > - super-W is binded to "show wins from all workspaces" > - "show for all workspaces" has been wrongly hacked to do "show only from > current workspace" > - "show from current workspace" is not used > > * the issue with undoing the hack is that it would change the behaviour > of super-W for all existing user to work over all workspace when it's > documented to be for the current workspace and how it behaves at the > moment ... > > * we can't "fix" those user configuration from the distribution side, > the packages are not supposed to temper user configs and even if we > could we have no garanty that the user directory is available (it could > be password protected or on a nfs server and non mounted at the time of > the upgrade) > > > @mniess did some suggestions in comment #136, thanks for that. > > I don't think the "prompt user about the configuration" is something we > wil do, that bug has 236 followers and some of you do care strongly > about the topic, but in practice the question would be in-appropriate > for 99% of Ubuntu users who don't care about that setting/don't use > it/don't know about it/like it the way it is at the moment/don't want to > be asked questions they don't understand on upgrade ... we believe that > the tradeoff would be in disfavor of the majority of Ubuntu users, you > might disagree but it's the calling we are making and we are discarting > that option > > That let us with the "add yet another option to "really show all wins > for other workspaces included" or "find a better option that the ones > suggested" ... we would really appreciate if somebody can help and come > with a smart idea to solve the issue without breaking existing users or > bothering them on upgrade > > thanks for reading > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/933776 > > Title: > [regression] scale/spread: "Initiate Window Picker for All Windows" > does not show all windows. It shows only windows from curent > workspace. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ayatana-design/+bug/933776/+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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 980766] Re: Remmina fullscreen jumps between workspaces
Someone please fix this. This bug is driving me crazy! -- 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/980766 Title: Remmina fullscreen jumps between workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/980766/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
one other way would be to "break" "show wins from the current workspace" to make it show wins from all workspace, e.g have both actions reverse and not matching that description ... it's not "right" but it would make the action possible for the tweakers that want it without breaking behaviour on upgrade -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
hey everyone, thanks for the interest to Ubuntu/compiz/that issue and sorry it's taking time to get resolved but comments are turning to heated tone and insults at this point and that's often non constructive... quite the contrary it might finish by demotivating the people who are on your side and want to see the issue fixed but are just overworked and didn't find the time to get to work on that yet So could you move the chit-chat to some mailing list or user forum? That said for those who want to help to get the issue resolved we welcome help on finding a solution which restore the option without changing the existing behaviour for users: Summary of the issue/precise situation: - super-W is binded to "show wins from all workspaces" - "show for all workspaces" has been wrongly hacked to do "show only from current workspace" - "show from current workspace" is not used * the issue with undoing the hack is that it would change the behaviour of super-W for all existing user to work over all workspace when it's documented to be for the current workspace and how it behaves at the moment ... * we can't "fix" those user configuration from the distribution side, the packages are not supposed to temper user configs and even if we could we have no garanty that the user directory is available (it could be password protected or on a nfs server and non mounted at the time of the upgrade) @mniess did some suggestions in comment #136, thanks for that. I don't think the "prompt user about the configuration" is something we wil do, that bug has 236 followers and some of you do care strongly about the topic, but in practice the question would be in-appropriate for 99% of Ubuntu users who don't care about that setting/don't use it/don't know about it/like it the way it is at the moment/don't want to be asked questions they don't understand on upgrade ... we believe that the tradeoff would be in disfavor of the majority of Ubuntu users, you might disagree but it's the calling we are making and we are discarting that option That let us with the "add yet another option to "really show all wins for other workspaces included" or "find a better option that the ones suggested" ... we would really appreciate if somebody can help and come with a smart idea to solve the issue without breaking existing users or bothering them on upgrade thanks for reading -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 1063617] Re: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values
** Changed in: compiz Status: In Progress => Fix Committed -- 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/1063617 Title: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1063617/+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 1089251] Re: [clang] Multiple segfaults in test: SetSemantics
** Changed in: compiz Status: In Progress => Fix Committed -- 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/1089251 Title: [clang] Multiple segfaults in test: SetSemantics To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1089251/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
+1 for common sense -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 1089250] Re: [clang] lp:compiz r3523 FTBFS: unused function 'ListValueToSettingValueList' [-Werror, -Wunused-function]
** Changed in: compiz Status: In Progress => Fix Committed -- 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/1089250 Title: [clang] lp:compiz r3523 FTBFS: unused function 'ListValueToSettingValueList' [-Werror,-Wunused-function] To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1089250/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
^^ zzecool hit the nail on the head. They had the chance to fix this before whatever deadline that made impossible to change default behaviour. But instead, they dicided to hack compiz to shit to bend it to thier will. Really stupid when you consider all they had to do was bind the action in bug #689733 to THE OTHER KEYBINDING THAT WAS MEANT FOR THE TASK. Now The only reason I can see this isn't fixed is stubborn pigheadedness. Soon Suttleworth himself will be here to ironically tell us this is the way its supposed to be like it or lump it or fix it yourself. I will never lift a finger for Ubuntu development again, I've seen this treatment too many times now. This attitude that the release is set in stone, fix it in the next one is just lazy. -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
We have a very nice expression here in Greece .. "Πνίγεσαι σε μια κουταλιά νερό" in free translation "drowning in a teaspoon of water" And this is what is really happening with this bug. The whole situation is a joke. This is a bug and a regression , if it is to hunt and file a report about a so serious bug at 16/2/2012 during the Precise "Alpha 2" ! to find out that the bug is still here with so much attention , not even after beta1 beta2 but 8 months after the Final LTS release ... then i don't really know why i have to file a bug report again than pray and hope for a 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 1089246] Re: Add support for blacklisting some drivers from using unredirected fullscreen windows
** Changed in: compiz Status: In Progress => Fix Committed -- 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/1089246 Title: Add support for blacklisting some drivers from using unredirected fullscreen windows To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1089246/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
Sorry, but for me, this is definitely a bug exists only in 12.04: with ccsm (Window Management / Scale / Assignments) it is possible to set 'Start selector windows for all windows': -> It works until 10.04 with 12.04 it does not work ==> BUG! ! ! -> From 13.04, it works again - google translate from french - Désolé, mais pour moi, cela reste définitivement un bug existant uniquement dans 12.04: avec ccsm (Gestion des fenêtres/Echelle/Assignations), il est possible de paramétrer 'Lancer le sélecteur de fenêtres pour toutes les fenêtres' : --> jusque 10.04 cela fonctionne avec 12.04 cela ne fonctionne pas==>BUG ! ! ! --> depuis 13.04, cela refonctionne -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
@johnlea: I proposed a solution in #122 and #136. If I understand correctly bug #689733 was just an incorrectly set shortcut (super+w was set to "scale all viewports" instead of "scale current viewport"). The solution (again, if I understand correctly) was to hack "scale all viewports" to display only the windows on the current viewport (which is an ugly hack and introduced a ton of other bugs). Introducing a new option to compiz and keeping "scale all viewports" as it is would cause problems with with the upgrade path to 14.04, wouldn't it? Having to change a keycombo is such a minor annoyance compared to having this bug (and all that come with it, flying windows, etc.). And as proposed in #122 we could even do it automatically. -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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
Re: [Compiz] [Bug 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
@John Lea, I think that exposing this option in 'System Settings / Keyboard / Shortcuts' is a great solution that could be landed in 12.04. Don't you agree? -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
@desgua; that's because it is the current implementation, and people generally don't comment if they are happy with the status quo. We had *a lot* of requests from the community to make the change described in bug #689733, so this debate is really is 6 of one, half a dozen of another. If we were to change the behaviour around to what it was before bug #689733 was implemented I guarantee we will have an equal number of people complaining that "I use workspaces to segment tasks/areas of life/contexts, for example I have one workspace for personal stuff I use in my lunch break, another workspace I use for work, and another workspace dedicated to the report I am working on. I use workspaces so that I can focus on the task at hand, please don't always display windows from other workspaces that I am not currently using." The issue is that there are several valid different ways of using workspaces, and we don't want to make a change that will inconvenience all the users who requested that we make the change described in bug #689733 in the first place. This is why this bug requests that this behaviour is made configurable in System Settings: -- "- In the short term what we can do is expose this option in 'System Settings / Keyboard / Shortcuts'. We can add two new actions to this panel: 'Spread all windows on the current workspace' (default setting: Super+W) and 'Spread all windows on all workspaces' (default setting: Disabled) and then it will be easy for users to choose the behaviour that suites them best." -- Can you see any alternative means of making all classes of workspace users happy without introducing this configuration option? -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
The bug 689733 has now a "heat" of 184 while this has "1090". So which behavior is more critical from a user point of view? -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 933776] Re: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace.
If policy prevents fixing broken behavior it seems to me said policy needs to be amended. -- 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/933776 Title: [regression] scale/spread: "Initiate Window Picker for All Windows" does not show all windows. It shows only windows from curent workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/933776/+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 1089279] Re: Restored windows' contents are offset from (not aligned with) their frames
There has been a suggestion that reverting r3513 might fix this. But even if it does, that would be technically wrong as a fix. Because it would regress bug 1087193. -- 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/1089279 Title: Restored windows' contents are offset from (not aligned with) their frames To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1089279/+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 1089279] [NEW] Restored windows' contents are offset from (not aligned with) their frames
Public bug reported: Restored windows' contents are offset from (not aligned with) their frames. Using the latest lp:compiz ... 1. Minimize a window. 2. Restore it. ** Affects: compiz Importance: Critical Assignee: Sam Spilsbury (smspillaz) Status: Triaged ** Affects: compiz (Ubuntu) Importance: Critical Assignee: Sam Spilsbury (smspillaz) Status: Triaged ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New ** Changed in: compiz (Ubuntu) Status: New => Triaged ** Changed in: compiz (Ubuntu) Importance: Undecided => Critical ** Changed in: compiz (Ubuntu) Assignee: (unassigned) => Sam Spilsbury (smspillaz) -- 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/1089279 Title: Restored windows' contents are offset from (not aligned with) their frames To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1089279/+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 1002246] Re: Window management - When a monitor is disconnected, the windows do not move to the remaining monitor and the Launcher pips do not update
** No longer affects: unity ** No longer affects: unity (Ubuntu) -- 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/1002246 Title: Window management - When a monitor is disconnected, the windows do not move to the remaining monitor and the Launcher pips do not update To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1002246/+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 878516] Re: Window management - Restoring a grid-placed window by dragging the title bar downwards does not restore the original window width
** Changed in: compiz Assignee: Sam Spilsbury (smspillaz) => Andrea Azzarone (andyrock) ** Changed in: compiz (Ubuntu) Assignee: Sam Spilsbury (smspillaz) => Andrea Azzarone (andyrock) ** Changed in: compiz Status: Triaged => In Progress ** Changed in: compiz (Ubuntu) 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/878516 Title: Window management - Restoring a grid-placed window by dragging the title bar downwards does not restore the original window width To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/878516/+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 1051802] Re: "Unredirect Fullscreen Windows" can cause significant tearing on fullscreen windows (especially playing video)
** Also affects: compiz (Ubuntu Quantal) 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/1051802 Title: "Unredirect Fullscreen Windows" can cause significant tearing on fullscreen windows (especially playing video) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1051802/+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 1086337] Re: HTML5 video in Firefox continues to tear
** Also affects: compiz (Ubuntu Quantal) 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/1086337 Title: HTML5 video in Firefox continues to tear To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1086337/+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 1071689] Re: Grid: Window management - resize preview does not show when moving a window from the semi-maximised state to the maximised state in a single action
** Also affects: compiz (Ubuntu Quantal) 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/1071689 Title: Grid: Window management - resize preview does not show when moving a window from the semi-maximised state to the maximised state in a single action To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1071689/+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 1048855] Re: [grid] Gedit, Nautilus will not snap/semi-maximize with the mouse
** Also affects: compiz (Ubuntu Quantal) 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/1048855 Title: [grid] Gedit, Nautilus will not snap/semi-maximize with the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1048855/+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 1067812] Re: Gedit, blocked window at the corners with compiz grid plugin
** Also affects: compiz (Ubuntu Quantal) 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/1067812 Title: Gedit, blocked window at the corners with compiz grid plugin To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1067812/+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 1063690] Re: Unredirect fullscreen windows should be the default for optimal performance
** Also affects: compiz (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: compiz (Ubuntu Quantal) 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/1063690 Title: Unredirect fullscreen windows should be the default for optimal performance To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1063690/+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 1084401] Re: Unredirected fullscreen windows freeze and stay on top when wall sliding (Ctrl+Alt+Left/Right)
** Also affects: compiz (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: compiz (Ubuntu Quantal) 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/1084401 Title: Unredirected fullscreen windows freeze and stay on top when wall sliding (Ctrl+Alt+Left/Right) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1084401/+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 1089251] Re: [clang] Multiple segfaults in test: SetSemantics/SettingDefaulImplSetFailure.
Only High severity now. The segfaults seem to be caused by bugs in the test cases only. ** Changed in: compiz Importance: Critical => High ** Changed in: compiz (Ubuntu) Importance: Critical => High ** Changed in: compiz Status: Triaged => In Progress ** Changed in: compiz (Ubuntu) Status: Triaged => In Progress ** Summary changed: - [clang] Multiple segfaults in test: SetSemantics/SettingDefaulImplSetFailure. + [clang] Multiple segfaults in test: SetSemantics -- 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/1089251 Title: [clang] Multiple segfaults in test: SetSemantics To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1089251/+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 1063617] Re: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values
I've got this bug on every restart in Quantal. System Settings > Keyboard > Shortcuts keeps showing the custom values but they are not effective. -- 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/1063617 Title: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1063617/+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 1063617] Re: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values
Linked the fix for bug 1089251 too. That's a crash caused by one of the fixes for this bug. ** Branch linked: lp:~vanvugt/compiz/fix-1089251 -- 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/1063617 Title: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1063617/+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 1089251] Re: [clang] Multiple segfaults in test: SetSemantics/SettingDefaulImplSetFailure.
** Changed in: compiz Assignee: Sam Spilsbury (smspillaz) => Daniel van Vugt (vanvugt) ** Changed in: compiz (Ubuntu) Assignee: Sam Spilsbury (smspillaz) => Daniel van Vugt (vanvugt) ** Branch linked: lp:~vanvugt/compiz/fix-1089251 -- 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/1089251 Title: [clang] Multiple segfaults in test: SetSemantics/SettingDefaulImplSetFailure. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1089251/+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 1089251] Re: [clang] Multiple segfaults in test: SetSemantics/SettingDefaulImplSetFailure.
valgrind compizconfig/libcompizconfig/tests/compizconfig_test_ccs_setting ==11525== Memcheck, a memory error detector ==11525== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==11525== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==11525== Command: compizconfig/libcompizconfig/tests/compizconfig_test_ccs_setting ==11525== Running main() from gtest_main.cc [==] Running 126 tests from 4 test cases. [--] Global test environment set-up. [--] 1 test from CCSSettingTest [ RUN ] CCSSettingTest.TestMock [ OK ] CCSSettingTest.TestMock (585 ms) [--] 1 test from CCSSettingTest (593 ms total) [--] 1 test from CCSSettingDefaultImplTest [ RUN ] CCSSettingDefaultImplTest.Construction [ OK ] CCSSettingDefaultImplTest.Construction (77 ms) [--] 1 test from CCSSettingDefaultImplTest (78 ms total) [--] 120 tests from SetSemantics/SettingDefaultImplSet [ RUN ] SetSemantics/SettingDefaultImplSet.Construction/0 [ OK ] SetSemantics/SettingDefaultImplSet.Construction/0 (47 ms) [ RUN ] SetSemantics/SettingDefaultImplSet.Construction/1 [ OK ] SetSemantics/SettingDefaultImplSet.Construction/1 (8 ms) [ RUN ] SetSemantics/SettingDefaultImplSet.Construction/2 [ OK ] SetSemantics/SettingDefaultImplSet.Construction/2 (5 ms) [ RUN ] SetSemantics/SettingDefaultImplSet.Construction/3 ==11525== Invalid read of size 1 ==11525==at 0x4C2BD02: __GI_strlen (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==11525==by 0x5D9CD65: strdup (strdup.c:42) ==11525==by 0x4872A6: (anonymous namespace)::NormalValueContainer::getContainedValue(_CCSSettingType, boost::shared_ptr<_CCSSettingInfo> const&) (compizconfig_test_ccs_setting.cpp:501) ==11525==by 0x487598: (anonymous namespace)::TypedSetParam::SetUpSetting(boost::function const&) (compizconfig_test_ccs_setting.cpp:1021) ==11525==by 0x47F442: (anonymous namespace)::SettingDefaultImplSet::SetUp() (compizconfig_test_ccs_setting.cpp:1272) ==11525==by 0x4C741A: void testing::internal::HandleExceptionsInMethodIfSupported(testing::Test*, void (testing::Test::*)(), char const*) (gtest.cc:2090) ==11525==by 0x4B6DA3: testing::Test::Run() (gtest.cc:2157) ==11525==by 0x4B7B3F: testing::TestInfo::Run() (gtest.cc:2338) ==11525==by 0x4B8168: testing::TestCase::Run() (gtest.cc:2445) ==11525==by 0x4BD0C4: testing::internal::UnitTestImpl::RunAllTests() (gtest.cc:4243) ==11525==by 0x4C7D0A: bool testing::internal::HandleExceptionsInMethodIfSupported(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) (gtest.cc:2090) ==11525==by 0x4BCD9D: testing::UnitTest::Run() (gtest.cc:3878) ==11525== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==11525== ==11525== ==11525== Process terminating with default action of signal 11 (SIGSEGV) ==11525== Access not within mapped region at address 0x0 ==11525==at 0x4C2BD02: __GI_strlen (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==11525==by 0x5D9CD65: strdup (strdup.c:42) ==11525==by 0x4872A6: (anonymous namespace)::NormalValueContainer::getContainedValue(_CCSSettingType, boost::shared_ptr<_CCSSettingInfo> const&) (compizconfig_test_ccs_setting.cpp:501) ==11525==by 0x487598: (anonymous namespace)::TypedSetParam::SetUpSetting(boost::function const&) (compizconfig_test_ccs_setting.cpp:1021) ==11525==by 0x47F442: (anonymous namespace)::SettingDefaultImplSet::SetUp() (compizconfig_test_ccs_setting.cpp:1272) ==11525==by 0x4C741A: void testing::internal::HandleExceptionsInMethodIfSupported(testing::Test*, void (testing::Test::*)(), char const*) (gtest.cc:2090) ==11525==by 0x4B6DA3: testing::Test::Run() (gtest.cc:2157) ==11525==by 0x4B7B3F: testing::TestInfo::Run() (gtest.cc:2338) ==11525==by 0x4B8168: testing::TestCase::Run() (gtest.cc:2445) ==11525==by 0x4BD0C4: testing::internal::UnitTestImpl::RunAllTests() (gtest.cc:4243) ==11525==by 0x4C7D0A: bool testing::internal::HandleExceptionsInMethodIfSupported(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) (gtest.cc:2090) ==11525==by 0x4BCD9D: testing::UnitTest::Run() (gtest.cc:3878) ==11525== If you believe this happened as a result of a stack ==11525== overflow in your program's main thread (unlikely but ==11525== possible), you can try to increase the size of the ==11525== main thread stack using the --main-stacksize= flag. ==11525== The main thread stack size used in this run was 8388608. ==11525== ==11525== HEAP SUMMARY: ==11525== in use at exit: 141,873 bytes in 2,060 blocks ==11525== total heap usage: 8,184 allocs, 6,124 frees, 845,361 bytes allocated ==11525== ==11525== LEAK SUMMARY: ==11525==definitely lost: 0 bytes in 0 blocks ==11525==indirectly lost: 0 bytes in 0 blocks ==11525== possibly lost: 20,779 bytes in 459 blocks ==11525==
[Compiz] [Bug 1054257] Re: [fglrx] Compiz (opengl) - Fatal: glXQueryExtensionsString is NULL for screen 0
Same to me on NVIDIA Geforce GTX 660M. Background image appears, and Unity fails. Ubuntu 12.10. cashy -- 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/1054257 Title: [fglrx] Compiz (opengl) - Fatal: glXQueryExtensionsString is NULL for screen 0 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1054257/+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 1063690] Re: Unredirect fullscreen windows should be the default for optimal performance
For precise (compiz 0.9.7), this is blocked pending the resolution of bug 1089246 and it being backported to 0.9.7. -- 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/1063690 Title: Unredirect fullscreen windows should be the default for optimal performance To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1063690/+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 1089251] [NEW] [clang] Multiple segfaults in test: SetSemantics/SettingDefaulImplSetFailure.
Public bug reported: [clang] Multiple segfaults in test: SetSemantics/SettingDefaulImplSetFailure NOTE: You need the fix for bug 1089250 before you can reproduce it. The following tests FAILED: 196 - SetSemantics/SettingDefaulImplSetFailure.ToFailValue/2 (SEGFAULT) 197 - SetSemantics/SettingDefaulImplSetFailure.ToFailValue/3 (SEGFAULT) 201 - SetSemantics/SettingDefaultImplSet.Construction/3 (SEGFAULT) 202 - SetSemantics/SettingDefaultImplSet.Construction/4 (SEGFAULT) 211 - SetSemantics/SettingDefaultImplSet.Construction/13 (SEGFAULT) 212 - SetSemantics/SettingDefaultImplSet.Construction/14 (SEGFAULT) 221 - SetSemantics/SettingDefaultImplSet.WithInvalidType/3 (SEGFAULT) 222 - SetSemantics/SettingDefaultImplSet.WithInvalidType/4 (SEGFAULT) 231 - SetSemantics/SettingDefaultImplSet.WithInvalidType/13 (SEGFAULT) 232 - SetSemantics/SettingDefaultImplSet.WithInvalidType/14 (SEGFAULT) 241 - SetSemantics/SettingDefaultImplSet.ToNewValue/3 (SEGFAULT) 242 - SetSemantics/SettingDefaultImplSet.ToNewValue/4 (SEGFAULT) 251 - SetSemantics/SettingDefaultImplSet.ToNewValue/13 (SEGFAULT) 252 - SetSemantics/SettingDefaultImplSet.ToNewValue/14 (SEGFAULT) 261 - SetSemantics/SettingDefaultImplSet.ToSameValue/3 (SEGFAULT) 262 - SetSemantics/SettingDefaultImplSet.ToSameValue/4 (SEGFAULT) 271 - SetSemantics/SettingDefaultImplSet.ToSameValue/13 (SEGFAULT) 272 - SetSemantics/SettingDefaultImplSet.ToSameValue/14 (SEGFAULT) 281 - SetSemantics/SettingDefaultImplSet.ToDefaultValue/3 (SEGFAULT) 282 - SetSemantics/SettingDefaultImplSet.ToDefaultValue/4 (SEGFAULT) 291 - SetSemantics/SettingDefaultImplSet.ToDefaultValue/13 (SEGFAULT) 292 - SetSemantics/SettingDefaultImplSet.ToDefaultValue/14 (SEGFAULT) 301 - SetSemantics/SettingDefaultImplSet.IsDefaultValue/3 (SEGFAULT) 302 - SetSemantics/SettingDefaultImplSet.IsDefaultValue/4 (SEGFAULT) 311 - SetSemantics/SettingDefaultImplSet.IsDefaultValue/13 (SEGFAULT) 312 - SetSemantics/SettingDefaultImplSet.IsDefaultValue/14 (SEGFAULT) Errors while running CTest ** Affects: compiz Importance: Critical Assignee: Sam Spilsbury (smspillaz) Status: Triaged ** Affects: compiz (Ubuntu) Importance: Critical Assignee: Sam Spilsbury (smspillaz) Status: Triaged ** Also affects: compiz Importance: Undecided Status: New ** Changed in: compiz Status: New => Triaged ** Changed in: compiz Importance: Undecided => Critical ** Changed in: compiz Assignee: (unassigned) => Sam Spilsbury (smspillaz) ** Description changed: [clang] Multiple segfaults in test: SetSemantics/SettingDefaulImplSetFailure + NOTE: You need the fix for bug 1089250 before you can reproduce it. + The following tests FAILED: - 196 - SetSemantics/SettingDefaulImplSetFailure.ToFailValue/2 (SEGFAULT) - 197 - SetSemantics/SettingDefaulImplSetFailure.ToFailValue/3 (SEGFAULT) - 201 - SetSemantics/SettingDefaultImplSet.Construction/3 (SEGFAULT) - 202 - SetSemantics/SettingDefaultImplSet.Construction/4 (SEGFAULT) - 211 - SetSemantics/SettingDefaultImplSet.Construction/13 (SEGFAULT) - 212 - SetSemantics/SettingDefaultImplSet.Construction/14 (SEGFAULT) - 221 - SetSemantics/SettingDefaultImplSet.WithInvalidType/3 (SEGFAULT) - 222 - SetSemantics/SettingDefaultImplSet.WithInvalidType/4 (SEGFAULT) - 231 - SetSemantics/SettingDefaultImplSet.WithInvalidType/13 (SEGFAULT) - 232 - SetSemantics/SettingDefaultImplSet.WithInvalidType/14 (SEGFAULT) - 241 - SetSemantics/SettingDefaultImplSet.ToNewValue/3 (SEGFAULT) - 242 - SetSemantics/SettingDefaultImplSet.ToNewValue/4 (SEGFAULT) - 251 - SetSemantics/SettingDefaultImplSet.ToNewValue/13 (SEGFAULT) - 252 - SetSemantics/SettingDefaultImplSet.ToNewValue/14 (SEGFAULT) - 261 - SetSemantics/SettingDefaultImplSet.ToSameValue/3 (SEGFAULT) - 262 - SetSemantics/SettingDefaultImplSet.ToSameValue/4 (SEGFAULT) - 271 - SetSemantics/SettingDefaultImplSet.ToSameValue/13 (SEGFAULT) - 272 - SetSemantics/SettingDefaultImplSet.ToSameValue/14 (SEGFAULT) - 281 - SetSemantics/SettingDefaultImplSet.ToDefaultValue/3 (SEGFAULT) - 282 - SetSemantics/SettingDefaultImplSet.ToDefaultValue/4 (SEGFAULT) - 291 - SetSemantics/SettingDefaultImplSet.ToDefaultValue/13 (SEGFAULT) - 292 - SetSemantics/SettingDefaultImplSet.ToDefaultValue/14 (SEGFAULT) - 301 - SetSemantics/SettingDefaultImplSet.IsDefaultValue/3 (SEGFAULT) - 302 - SetSemantics/SettingDefaultImplSet.IsDefaultValue/4 (SEGFAULT) - 311 - SetSemantics/SettingDefaultImplSet.IsDefaultValue/13 (SEGFAULT) - 312 - SetSemantics/SettingDefaultImplSet.IsDefaultValue/14 (SEGFAULT) + 196 - SetSemantics/SettingDefaulImplSetFailure.ToFailValue/2 (SEGFAULT) + 197 - SetSemantics/SettingDefaulImplSetFailure.ToFailValue/3 (SEGFAULT) + 201 - SetSemantics/SettingDefaultImplSet.Construction/3 (SEGFAULT) + 202 - SetSemantics/SettingDefaultImplSet.Construct
[Compiz] [Bug 1089250] Re: [clang] lp:compiz r3523 FTBFS: unused function 'ListValueToSettingValueList' [-Werror, -Wunused-function]
** Also affects: compiz (Ubuntu) Importance: Undecided Status: New ** Changed in: compiz (Ubuntu) Status: New => In Progress ** Changed in: compiz (Ubuntu) Importance: Undecided => Low ** Changed in: compiz (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: compiz (Ubuntu) Importance: Low => 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/1089250 Title: [clang] lp:compiz r3523 FTBFS: unused function 'ListValueToSettingValueList' [-Werror,-Wunused-function] To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1089250/+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 1089246] [NEW] Add support for blacklisting some drivers from using unredirected fullscreen windows
Public bug reported: Add support for blacklisting some drivers from using unredirected fullscreen windows. This is a prerequisite before we can resolve bug 1063690 on precise. ** Affects: compiz Importance: Wishlist Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Affects: compiz/0.9.8 Importance: Wishlist Status: Triaged ** Affects: compiz-core Importance: High Status: Triaged ** Affects: compiz (Ubuntu) Importance: Wishlist Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags: unredirect ** 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 => Wishlist ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New ** Changed in: compiz (Ubuntu) Status: New => In Progress ** Changed in: compiz (Ubuntu) Importance: Undecided => Wishlist ** Changed in: compiz (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Also affects: compiz-core Importance: Undecided Status: New ** Changed in: compiz-core Importance: Undecided => High ** Changed in: compiz-core Status: New => Triaged ** Changed in: compiz-core Milestone: None => 0.9.7.12 ** Branch linked: lp:~vanvugt/compiz/blacklist -- 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/1089246 Title: Add support for blacklisting some drivers from using unredirected fullscreen windows To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1089246/+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
