Ubuntu

[Regression] Panel shadow dropped on full screen windows after notification

Reported by Alfred Neumayer on 2013-04-20
330
This bug affects 68 people
Affects Status Importance Assigned to Milestone
Unity
7.0
Medium
Marco Trevisan (Treviño)
7.1
Medium
Marco Trevisan (Treviño)
unity (Ubuntu)
Undecided
Marco Trevisan (Treviño)
Raring
Undecided
Marco Trevisan (Treviño)

Bug Description

[Impact]

Panel shadow drawn on a full screen window.

[Test Case]

1) Open Totem
2) make it full-screen pressing F11
3) Change the main volume using the multimedia keyboards

Expected behavior:
4) The volume notification is drawn above it, and the panel shadow is not

Actual behavior
4) The panel shadow is drawn below the notification bubble.

[Regression Potential]

No regression potential.

------

When having a full screen window focused and getting a notification, the Unity panel shadow gets drawn on top of the full screen window as well.
Screenshot attached.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Apr 20 16:33:38 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0713]
 NVIDIA Corporation GK107M [GeForce GT 640M LE] [10de:0fd3] (rev ff) (prog-if ff)
MachineType: Acer Aspire M5-481TG
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-19-generic root=UUID=d67047dc-d9af-4097-8c13-0c46dc017014 ro quiet splash i915_enable_rc6=1 i915.i915_enable_fbc=1 pcie_aspm=force acpi_osi=Linux pciehp.pciehp_force=1 acpi_backlight=vendor vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf:
 Section "InputClass"
         Identifier "Disable clickpad buttons on Apple touchpads"
         MatchDriver "synaptics"
         Option "SoftButtonAreas" "0 0 0 0 0 0 0 0"
 EndSection
dmi.bios.date: 11/13/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.12
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: MA40_HX
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd11/13/2012:svnAcer:pnAspireM5-481TG:pvrV1.12:rvnAcer:rnMA40_HX:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire M5-481TG
dmi.product.version: V1.12
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.43-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1
xserver.bootTime: Sat Apr 20 12:36:26 2013
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.13.3-0ubuntu6
xserver.video_driver: intel

Related branches

lp:~3v1n0/unity/panel-shadow-fullscreen-fix
Merged into lp:unity/7.0 at revision 3311
PS Jenkins bot: Approve (continuous-integration) on 2013-04-24
Andrea Azzarone: Approve on 2013-04-23
Merged into lp:unity at revision 3313
PS Jenkins bot: Approve (continuous-integration) on 2013-04-23
Andrea Azzarone: Approve on 2013-04-23
Alfred Neumayer (beidl) wrote :
description: updated
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity (Ubuntu):
status: New → Confirmed
Petro (petrochemicals) wrote :

I am seeing this as well. Four days till release Canonical, this should not be a problem so close to release.

bwat47 (bwat47) wrote :

I've been seeing panel shadow being drawn over fullscreen video in 13.04 as well. Not sure if it happened due to a notifiaction or not. i had one machine where it just seemed to happen at all times no matter what in smplayer or totem. I ended up doing: dpkg-divert --local --rename --divert /usr/share/unity/6/panel-shadow.png_disabled --add /usr/share/unity/6/panel-shadow.png

to just get rid of the panel shadow completely.

Changed in unity:
status: New → In Progress
Changed in unity (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
Changed in unity:
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
milestone: none → 7.0.1
importance: Undecided → Medium
Changed in unity:
status: In Progress → Fix Committed
Changed in unity (Ubuntu):
status: In Progress → Fix Committed
Alfred Neumayer (beidl) wrote :

The fix works, please package it up for release ASAP!

Kay (ksthiele) wrote :

pressing SUPER-Button removes the panel, but it should be fixed asap

Mathieu Cossette (mcossette) wrote :

Also affects even with no Unity notification by the way on Raring and Saucy, when going fullscreen with Totem

See picture

See the top bar showing in a transparent manner when full screen

Petro (petrochemicals) wrote :

Jesus christ, is this fix still not released? What a fucking joke.

Hello,

This issue has been identified and has been fixed in the Unity code base. We have certain protocols that need to be followed in order to get an updated Unity package out. Please be patient. This will be released.

Thanks!

Petro (petrochemicals) wrote :

@ Christopher Townsend

Okay, so there are strict protocols to release bug fixes that take a very long tome to release to the users but where are these strict protocols when it comes to releasing so called "stable" versions of your OS? Doesn't look like you or any one else at Canonical cared when all of you knew you were releasing the bug ridden mess of 13.04 to us and now that we want it fixed you want to spout off about "protocols" where the hell where these "protocols" BEFORE 13.04 was released with this and many other bugs?

Hi Petro,

I appreciate your passion that you want bugs fixed, especially ones that really annoy you. I care very much about Ubuntu and ideally would love it to be bug free. I work on Unity and I am very proud of the work we did for 13.04. That said, there are bugs. It's an unfortunate fact of life. For this particular bug, a fix is identified and is merged in the Unity source code. A Stable Release Update (SRU) will come out to fix this . I don't have any control of when this SRU comes out, so I can't give a timeframe of when it will be available.

description: updated
Petro (petrochemicals) wrote :

@ Christopher

You say we are waiting for an SRU but what does stable even mean coming from you people? This release (13.04) was supposed to be "stable" but is filled with bugs. So now we are waiting for a "stable" update for Unity to fix this regression, why? The fix works, and has been comiited, why are we being made to wait for our supposed stable sytems to work correctly? With the dropped time of support from non LTS releases there is only now 9 months to get these many bugs fixed, including this one. So how does sitting on a fix help the users when there is now such a short time span that this release is even going to be usable? Are we just supposed to use non stable systems for half of this releases life just because of some bullshit rule about SRU's ?

@Petro: this is not really the place to discuss about distro policies.

This bug has been promptly fixed (as it's slightly annoying despite it has a *very low inpact*), it had only to be packaged in distro (you could have added the ubuntu unity daily ppa if really you needed this before), and distro needs to follow rules in order to deliver a good product.

If you want to discuss about more general topics, please refer to the proper channels.

Petro (petrochemicals) wrote :

"despite it has a *very low inpact*"

Says who, you? Frankly it has a very large impact on me as my OS is incapable of playing videos without part of the OS overlaying it. Think hard about when the last time Windows or OSX released a "stable" release with their default video player ruining every video they play. Actually I can't even think of a Windows beta that had a bug this big in it.

"it had only to be packaged in distro"

Exactly, kind of useless unless you actually release the damn fix to the USERS!

"you could have added the ubuntu unity daily ppa if really you needed this before"

So instead of Ubuntu fixing their mistakes your saying it's my fault for not fixing my broken OS by installing unstable and experimental software that should have been released already but was pushed back because of Canonicals incompetence. Wow, what a great option, thanks guy.

"distro needs to follow rules in order to deliver a good product"

This is what I am saying! Where are the rules that prevent Canonical from releasing stable OS's that are filled with known bugs? It's only after you release unstable software under the name of stable that we all now need to follow these very important rules. Frankly not a single user could care about your dumb rules, what they do care about is an OS that works.

"If you want to discuss about more general topics, please refer to the proper channels."

Thanks for pointing out what exactly those channels are and where they can be found, very helpful indeed.

Daniel van Vugt (vanvugt) wrote :

It's not just occurring when notifications are visible, but all the time. It's only the Unredirected Fullscreen Windows option (which is now enabled in raring) that's hiding the bug until notifications appear...

1. CCSM > Composite > Unredirect Fullscreen Windows = OFF
2. Fullscreen Firefox
Expected: Just Firefox is visible.
Observed: The panel shadow is always drawn over Firefox.

tags: added: regression-release
pirast (pirast) wrote :

Well, Canonical is too busy with its vision of Ubuntu on TVs, tablets and phones - they obviously have no time for proper quality assurance for the desktop Ubuntu (that is actually being used by quite a large user base).

Stephen M. Webb (bregma) wrote :

The Ubuntu Desktop is a very very large project with many millions of lines of code. From time to time a change to fix a bug will introduce altered functionality or even another bug that slips through the rigorous testing processes that we subject all of our software to, so once in a while such bugs get released unnoticed. This is true for all software projects.

The fact is this particular problem has been fixed in the code, and is propagating into Ubuntu following the normal well-documented processes established to ensure a high quality product and the best experience for all involved. These rules will not be bent or disregarded. Any discussion of these processes is not germane to the resolution of this bug.

The kind of bitter vitriol recently being expressed as comments related to this bug are neither constructive to solving the problem described nor contributing positively to anybody's experience, and are best kept to weblogs, informal chats, ranting emails, and other venues more appropriate to that discussions of that nature. Please keep such comments there.

description: updated
Petro (petrochemicals) wrote :

"The Ubuntu Desktop is a very very large project with many millions of lines of code."

Is the work too hard for Canonical? Is it too difficult to keep up with such bugs and fix them? Well then maybe Canonical should not be falsely representing itself as a competitor to Windows with slogans such as "avoid the pain of Windows 8". Either Ubuntu is on the same playing field of it's stated competitor OS's and thus held to the same scrutiny of not releasing with huge visual bugs in STABLE releases, or it is a hobby OS created by an understaffed and underfunded company and it's users and thus allowed the shortcomings that come along with that. But it certainly can not be both. Frankly if you don't like the flak you are receiving maybe you should tell your marketing department to stop lying to it's user base about being an actual option to replace production environment OS's such as Windows or OSX because as it stands, you are no where near that level of professionalism and stability.

"From time to time a change to fix a bug will introduce altered functionality or even another bug that slips through the rigorous testing processes that we subject all of our software to, so once in a while such bugs get released unnoticed."

You are using incorrect phrasing here. From "time to time", "once n a while" are both flat out preposterous. It's not like this is just some one time occurrence. EVERY SINGLE RELEASE has major bugs and regressions in it. This very bug was also released in 12.04, except it was the whole panel and not just the shadow. So it was fixed and yet again it is back. This of course is very representative of how unprofessional and cobbled together Ubuntu really is.

"The fact is this particular problem has been fixed in the code, and is propagating into Ubuntu following the normal well-documented processes established to ensure a high quality product and the best experience for all involved."

No, the fact is that Canonical is willfully holding out on releasing a working fix to it's users on an OS that has a very limited lifespan of 9 months (now 8). If you want to talk about high quality and best experiences than maybe Canonical should test their product more and not release bug filled software under the name of stable. Like I said before, where in the hell was all of this quality insurance BEFORE you release?

"The kind of bitter vitriol recently being expressed as comments related to this bug are neither constructive to solving the problem described nor contributing positively to anybody's experience"

Hey you know what doesn't contribute positively to my experience? A FUCKING BROKEN OS!

Viol (violent23) wrote :

Petro has a point. There are laptops being sold that come with Ubuntu 13.04. Imagine plunking down your hard earned money for a brand new laptop come to find out that your OS has a huge amount of bugs and can't even play video correctly. No wonder there are not many manufacturers that offer Ubuntu. I would imagine Dell get's a lot of returns on those laptops that do have Ubuntu. No one wants a broken OS with such poor support as whats being shown in this bug report. If this is how you take care of your PC users, how bad is the support going to be for your phones?

I too have been experiencing this bug since before release. Why has this fix not been sent out to the users yet? Eight months left to go, shall I expect this fix to sit in limbo for that long or is someone going to get off their ass and put user experience before some arbitrary rules?

pirast (pirast) wrote :

You both definitly have a point there.
I bought an expensive Dell system shipping with Ubuntu, and it was the most frustrating IT experience that I had for a long time due to it being covered by lots of bugs (and shipping with a really old version of Ubuntu) (see https://answers.launchpad.net/ubuntu-certification/+question/216889 , even made suggestions for improvement at the bottom, but did not get a reply on that).
The out-of-box experience was by far not comparable to when you buy a device shipping with Windows or Mac OS X (both because of bugs and missing hardware support).
The marketing of Ubuntu is saying that Windows is a pain. But sooner or later you realize it's the other way around. Which is sad, because once Ubuntu really looked promising.

Petro (petrochemicals) wrote :

Because of Canonical's ineptitude and poor support there is now an article on this very bug on one of the most popular Ubuntu websites. I would assume it was written as every 13.04 user is tired of waiting on Canonical to fix bugs that should have never shown up in a stable release in the first place.

http://www.webupd8.org/2013/05/fix-shadow-displayed-on-top-of-full.html

 It list two workarounds to try and mitigate the issue, but alas neither are really that great of an option. Yet again showing how important it is for Canonical to fix bugs like this sooner rather than later.

Here is a very good quote from a comment on that article.

"If ubuntu really wants to become mainstream, and 'not another linux distro" they need to take more steps not to release a stable ubuntu with obvious stability and/or visual bugs like this. It really gives me the feeling that I'm using beta software, and not a stable and polished release."

Which I have to agree. There are laptops being sold with this OS, there is no excuse at this point to have these kind of bugs in so called stable releases.

Doug McMahon (mc3man) wrote :

Fix may take care of the panel shadow when in fullscreen but doesn't address the flashing thru of panel & or the launcher when using keyboard or moving mouse

'cause that's another bug ;-)

Max Bowsher (maxb) wrote :

Should the Ubuntu bugtask really be marked "Fix Committed" when it looks like the fix has only landed into Unity upstream branches at present?

Also, when might this reach raring-proposed?

Mathias Dietrich (theghost) wrote :

Yet another workaround is to enable the workspace switcher icon in Unity.

To my mind it is logical to release error fixes as fast as possible after they went to QA. But instead every user has to wait until the whole Unity 7.0.1 version is ready. Why don't you release error fixes ASAP and bring new features / refactories in a minor version (like 7.0.x) ?

I can understand that a lot of users are angry about this. They see these issues every day in production / daily use, while the fix is already available.

Is there at least a schedule when this fix lands in Proposed ?

Salem (salemsaberhagen) wrote :

In my humble opinion if you release a stable OS that is not able to properly play videos, and fail to correct that after all this time something is very wrong with your QA process. Releasing something with bugs is acceptable, taking this long to deliver a fix (which is already available) to a release with only 9 months lifetime is just WTF?!!!

I understand this is not the best place to express my opinion, but I really hope anyone who defines how things are released understands how frustrating this is.

Also if anyone could point out the address of the "unity daily ppa" would be nice.
http://askubuntu.com/questions/244287/official-daily-ppa-for-unity

Benjamin Drung (bdrung) wrote :

I can understand your frustration and I wonder, why the Unity SRU takes so long this time.

The AskUbuntu answer points to [1]. There you find unity 7.0.0daily13.05.31~13.04-0ubuntu1, which should contain the fix (the version number suggest it).

[1] https://launchpad.net/~unity-team/+archive/sru

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity (Ubuntu Raring):
status: New → Confirmed
Petro (petrochemicals) wrote :

Still not fixed I see. Well, you devs should really be proud, such a quality product you are offering here.

Vincent Thiele (vincentthiele) wrote :

They work on Mir... Compiz based Unity isn't important anymore... :/

Petro (petrochemicals) wrote :

@ Vincent Thiele

How many years have they been working on Compiz based Unity, and it is still horse shit. Let's just say my confidence in what Mir and Unity are going to be is not very high.

You just gotta love a supposed "stable" OS that is in a constant flux of being broken in one way or another. It just blows my mind that this crap is being installed on OEM devices and sold. I just feel sorry for the people that are fooled by Dell and the like that Ubuntu is in any way comparable to real OS.

wow! You guys are doing a bang up job of releasing a stable OS.

Petro (petrochemicals) wrote :

Another two weeks since my last comment, still no fix given to the users.

How about you developers explain to us lowly users as to why you are still sitting on this fix?

Better yet how about you explain it to the unfortunate souls that went out of their way to purchased brand new and expensive laptops with your broken OS installed on them. Tell them why you feel that they don't need working video players on their new laptops, explain how it is that you are helping them by not pushing out a fix that already exists.

Casonade (damystica) wrote :

Is this some kind of trends on Linux land--a trend to break something and then fix something else? Every fucking release breaks one thing after another, even the tiniest sh!t. Great job, Ubuntu devs! Now my external NTFS hard drive can no longer be mounted on Ubuntu 13.04. I'll stay in Linux land until 14.04, if not by then, I will switch back to either Windows or Mac.

Daniel van Vugt (vanvugt) wrote :

It appears the developers are working on fixing bugs like this in raring and you can monitor the progress here:
https://launchpad.net/unity/+milestone/7.0.1

However the developers have no control over when the 7.0.1 update gets released.

This bug should be fixed in Unity that is currently in raring-proposed. For some reason, the SRU team is using bug #1171934 (which is a duplicate of this bug) as the base bug for this.

Anyone who is affected by this bug, please see bug #1171934 and verify this is fixed so we can move forward on getting Unity promoted to raring-updates.

Thanks!

tags: added: verification-needed
Changed in unity (Ubuntu):
status: Fix Committed → Fix Released
Changed in unity (Ubuntu Raring):
status: Confirmed → In Progress
Petro (petrochemicals) wrote :

@ Christopher Townsend

This bug is not fixed in raring-proposed, it is just different. Three months sitting on this fix and it doesn't even fix the problem. Maybe if you people had released this supposed fix three months ago like everyone asked you to do in this thread we would have all known it doesn't really work and a real fix would have been found by now. But of course idiotic rules are supposed to be followed to provide "stability", as we can see that works really well.

I have attatched a video of what this "fix" accomplishes. Now instead of drawing the panel shadow above fullscreen videos the top panel and Unity panel flash above the fullscreen video when the mouse is moved.

Great job devs, you sat on this for 1/3 of the lifespan of this release all for nothing. How much longer can we expect to wait for an actual fix to the broken fix? I would assume it won't make it into 13.04. What amazes me even more is that crap like this will still not stop Canonical from calling 13.10 "stable" just like 13.04 is supposed to be.

tags: added: verification-failed
removed: verification-needed

I did confirm the behavior that Petro sees in the movie. However, this behavior is present in Unity version 7.0.0daily13.04.18~13.04-0ubuntu1 (the version in main) and is a completely different bug than this one. Hence, there is no SRU regression here.

Since Petro has confirmed the Panel shadow is indeed gone, this bug is verification-done.

I will create a new bug with the behavior seen in the movie as it still occurs in Unity trunk in Saucy.

tags: added: verification-done
removed: verification-failed

@Petro,

Thanks for pointing out the new bug. I have created bug #1196724 for this newly discovered behavior.

Changed in unity (Ubuntu Raring):
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
Changed in unity (Ubuntu Raring):
status: In Progress → Fix Committed
Stephen M. Webb (bregma) on 2013-08-09
no longer affects: unity
senyorita (bdoojin) wrote :

When I move a mouse cursor in fullscreen video players, unity flickers for a short time on top.

I found a workaround for this issue.

1) Install and execute "CompizConfig Settings Manager"(execute ccsm on the shell)
2) Visit general>compositing and remove !(class=Vlc) from "unredirect match" to solve the issue for VLC only
Or set "unredirect match" to "(all)" to solve the issue for every application.

To post a comment you must log in.