Changing monitor configurations after changing lowgfx mode could lead to a HudControl crash
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
Fix Released
|
Medium
|
Marco Trevisan (Treviño) | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
When changing monitor settings unity might crash with this backtrace:
#0 0x00007f90dae11428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/
#1 0x00007f90dae1302a in __GI_abort () at abort.c:89
#2 0x00007f90db44b84d in __gnu_cxx:
#3 0x00007f90db4496b6 in __cxxabiv1:
at ../../.
#4 0x00007f90db449701 in std::terminate() () at ../../.
#5 0x00007f90db449919 in __cxxabiv1:
at ../../.
#6 0x00007f90db4728b2 in std::__
#7 0x00007f90b9a9d2cc in unity::
#8 0x00007f90b9a9d2cc in unity::
at /build/
#9 0x00007f90b9a9effc in unity::
at /build/
#10 0x00007f90b9aa00e4 in unity::
at /build/
#11 0x00007f90b9c4d350 in unity::
at /usr/include/
#12 0x00007f90b9c4d350 in unity::
at /usr/include/
#13 0x00007f90b9c4d350 in unity::
at /build/
#14 0x00007f90b9c4df9c in std::_Function_
#15 0x00007f90b9c4df9c in std::_Function_
#16 0x00007f90b62878ca in unity::
#17 0x00007f90d970604a in g_main_
#18 0x00007f90d970604a in g_main_
at /build/
#19 0x00007f90d97063f0 in g_main_
#20 0x00007f90d9706712 in g_main_loop_run (loop=0x6cb010) at /build/
#21 0x00007f90db79c31f in compiz:
at /usr/lib/
#22 0x00000000004017c1 in main ()
[ Test case ]
- Change gsetting lowgfx mode
* gsettings set com.canonical.Unity lowgfx false
* gsettings set com.canonical.Unity lowgfx true
- In unity-control-
- Open HUD
- Unity should not crash
[ Regression potential ]
UI doesn't adapt properly to monitor changes.
Related branches
- Andrea Azzarone (community): Approve
-
Diff: 149 lines (+27/-45)4 files modifiedhud/HudController.cpp (+1/-1)
launcher/EdgeBarrierController.cpp (+21/-36)
launcher/EdgeBarrierControllerPrivate.h (+1/-4)
plugins/unityshell/src/unityshell.cpp (+4/-4)
- Andrea Azzarone (community): Approve
-
Diff: 233 lines (+50/-51)8 files modifieddebian/changelog (+10/-0)
decorations/DecoratedWindow.cpp (+3/-1)
hud/HudController.cpp (+1/-1)
launcher/CairoBaseWindow.cpp (+8/-3)
launcher/EdgeBarrierController.cpp (+21/-36)
launcher/EdgeBarrierControllerPrivate.h (+1/-4)
plugins/unity-mt-grab-handles/src/unity-mt-grab-handles.cpp (+1/-1)
plugins/unityshell/src/unityshell.cpp (+5/-5)
- Unity Team: Pending requested
-
Diff: 9045 lines (+6157/-2465) (has conflicts)25 files modifiedAUTHORS (+2/-0)
CMakeLists.txt (+5/-0)
ChangeLog (+5502/-2418)
UnityCore/GLibSignal.h (+4/-0)
dash/ResultRendererTile.cpp (+6/-0)
data/CMakeLists.txt (+40/-0)
debian/changelog (+250/-0)
debian/control (+4/-0)
debian/libunity-core-6.0-9.install (+5/-0)
debian/rules (+6/-0)
debian/unity-services.install (+4/-0)
debian/unity.install (+7/-0)
debian/unity.migrations (+4/-0)
hud/HudController.cpp (+1/-1)
launcher/EdgeBarrierController.cpp (+21/-36)
launcher/EdgeBarrierControllerPrivate.h (+1/-4)
lockscreen/LockScreenController.cpp (+8/-0)
lockscreen/LockScreenController.h (+4/-0)
plugins/unityshell/src/unityshell.cpp (+7/-3)
services/unity-panel-service-lockscreen.service.in (+10/-0)
tests/CMakeLists.txt (+157/-0)
tests/test_lockscreen_controller.cpp (+12/-0)
tools/CMakeLists.txt (+35/-0)
unity-shared/UnitySettings.cpp (+51/-3)
unity-shared/UpstartWrapper.cpp (+11/-0)
Changed in unity (Ubuntu): | |
status: | In Progress → Fix Released |
description: | updated |
summary: |
Changing monitor configurations after changing lowgfx mode could lead to - a crash + a HudControl crash |
Hello Marco, or anyone else affected,
Accepted unity into xenial-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ unity/7. 4.5+16. 04.20180221- 0ubuntu1 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 on 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- xenial to verification- done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- xenial. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!