[SRU] OpenGL backend is wrongly blocked and menus are over the dock
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cairo-dock (Ubuntu) |
Fix Released
|
High
|
Matthieu Baerts | ||
Trusty |
Fix Released
|
High
|
Unassigned | ||
Utopic |
Fix Released
|
High
|
Matthieu Baerts |
Bug Description
Hello,
== 1st Bug: Wrong blacklisting ==
It seems that the patch 'bzr1719_
But this patch wrongly removes the blacklist and then it's possible that you'll need to force the OpenGL backend (with the '-o' option) to use it even if you don't have this Intel 4000HD video card and you choose to use it.
== 2nd Bug: Menus are not correctly positioned ==
There is also a bug with the menus: It seems that the behaviour of menus with a custom position has changed since using GTK 3.10: https:/
We now have to use the 'natural' size instead of the 'minimum' size:
- gtk_widget_
+ gtk_widget_
A branch has been linked to this bug report and it fixes these 2 bugs: lp:~cairo-dock-team/ubuntu/trusty/cairo-dock/1329090
[Test Case]
For the first bug: You should be able to reproduce this bug when using Free and Open Source video drivers. Simply launch the dock for the first time from a terminal:
$ cairo-dock
(or if it's not the first time: $ cairo-dock -A)
You should see a window to confirm that you want to use the OpenGL backend: click on this "Yes" button. Then you should see on the terminal that you're not using the OpenGL backend: "Running with OpenGL: 0"
For the second bug: simply do a right click on the dock and you should see that the menu is over the dock instead of on top of it. Cairo-Dock's menus should not overlap the dock.
[Regression Potential]
The only possible regression that I see is that this OpenGL backend could maybe be accidentally blocked for some users which have an old, exotic and badly supported video card. If these users enable this OpenGL backend, the dock can look strange but this is why there is a message the first time you launch the dock ;-)
But in other words, it seems there is no regression, just a correct behaviour (if the user wants to use the hardware acceleration, he will be able to use it as requested)
Note that these two patches have been tested and added in our unstable and stable PPAs and in the official Utopic repositories one month ago.
Related branches
description: | updated |
Changed in cairo-dock (Ubuntu Utopic): | |
status: | New → Fix Released |
importance: | Undecided → High |
Changed in cairo-dock (Ubuntu Trusty): | |
importance: | Undecided → High |
Changed in cairo-dock (Ubuntu Utopic): | |
assignee: | nobody → Matthieu Baerts (matttbe) |
milestone: | none → ubuntu-14.05 |
Changed in cairo-dock (Ubuntu Trusty): | |
milestone: | none → ubuntu-14.04.1 |
Changed in cairo-dock (Ubuntu Trusty): | |
status: | New → In Progress |
Changed in cairo-dock (Ubuntu Utopic): | |
milestone: | ubuntu-14.05 → none |
Hello Matthieu, or anyone else affected,
Accepted cairo-dock into trusty-proposed. The package will build now and be available at http:// launchpad. net/ubuntu/ +source/ cairo-dock/ 3.3.99. beta1.2. really. 3.3.2-0ubuntu2. 1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!