[Ubuntu-x-swat] [Bug 754565] Re: Regression: shift+click on a launcher icon to open a new application instance gone

2011-04-28 Thread David Planella
I'm reopening the bug, after auto-expiration. Timo, I'm not sure I understand the information you need here, could you please elaborate? As per the question whether I was able to shift+click launch after Fri, 28 Jan, the answer is yes: bug 724865 with this feature request was filed on 2011-02-25

[Ubuntu-x-swat] [Bug 754565] Re: Regression: shift+click on a launcher icon to open a new application instance gone

2011-04-28 Thread Timo Aaltonen
Right, so it's not due to middlemouse emulation being disabled by default, but something else. Tossing back to unity :) ** Changed in: xorg-server Status: Triaged = Invalid ** Package changed: xorg (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member

[Ubuntu-x-swat] [Bug 754565] Re: Regression: shift+click on a launcher icon to open a new application instance gone

2011-04-27 Thread bugbot
We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this

[Ubuntu-x-swat] [Bug 754565] Re: Regression: shift+click on a launcher icon to open a new application instance gone

2011-04-08 Thread Didier Roche
** Project changed: unity = xorg-server ** Changed in: xorg-server Milestone: 3.8.6 = None ** Changed in: xorg-server Assignee: Didier Roche (didrocks) = (unassigned) ** Package changed: unity (Ubuntu) = xorg (Ubuntu) -- You received this bug notification because you are a member of

[Ubuntu-x-swat] [Bug 754565] Re: Regression: shift+click on a launcher icon to open a new application instance gone

2011-04-08 Thread Timo Aaltonen
First of all, middlemouse emulation has been off by default since evdev 2.6.0 was uploaded on Fri, 28 Jan. So if you were able to shift+click launch after that, the bug is somewhere else. Second, I can't understand how it could even be due to the current defaults, since you're using a modifier and