Full screen right click causes black screen with compiz

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
11 years ago
8 years ago

People

(Reporter: jctosu, Unassigned)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2011-1-30])

Attachments

(1 attachment)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b2) Gecko/2007121016 Firefox/3.0b2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b2) Gecko/2007121016 Firefox/3.0b2

When I right click on any web page the screen turns black except for a box around the right click menu, the screen returns to its normal state after a few seconds.  This doesn't occur in other applications that go to full screen.  It only occurs when I am running the compiz desktop, not when I am using the regular Gnome display manager.

Reproducible: Always

Steps to Reproduce:
1. Go to any website
2. Go into fullscreen (F11 -or- View->Full Screen
3. Right Click
Actual Results:  
When I right click the screen turns black except for a rectangular box around the right click menu that pops as a result of me right clicking, this occurs for a few seconds before the screen is returned to normal.

Expected Results:  
The right click menu pops up and the screen doesn't turn black.

Ubuntu 7.10 with Gnome compiz display manager running on Dell Inspirion e1505 with ATI x1400 graphics.

This has something to do with compiz integration

about:buildconfig

Build platform
target
i686-pc-linux-gnu

Build tools
Compiler 	Version 	Compiler flags
/tools/gcc/bin/gcc 	gcc version 4.1.2 20061011 (Red Hat 4.1.1-29) 	-Wall -W -Wno-unused -Wpointer-arith -Wcast-align -Wno-long-long -pedantic -pthread -pipe
/tools/gcc/bin/g++ 	gcc version 4.1.2 20061011 (Red Hat 4.1.1-29) 	-fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith -Wcast-align -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wno-long-long -pedantic -fshort-wchar -pthread -pipe

Configure arguments
--enable-application=browser --enable-update-channel=beta --enable-update-packaging '--enable-optimize=-Os -freorder-blocks -fno-reorder-functions -gstabs+' --disable-debug --disable-tests --enable-official-branding
(Reporter)

Updated

11 years ago
Version: unspecified → Trunk

Comment 1

11 years ago
Created attachment 301030 [details]
Shutnik’s screenshot (Ubuntu 7.10, Compiz, NVIDIA card)

Comment 2

10 years ago
I can't reproduce it.  Try safe mode, then if that doesn't work try a new profile.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/en-US/kb/Profiles

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1a1pre) Gecko/2008071802 Minefield/3.1a1pre ID:2008071802
Can't reproduce it either. Only thing that happens is: screen turns black for about half a second (yes, it shouldn't. Maybe that's related / the point at which yours crashes?) and when I get back out of fullscreen mode I see 2 times:

(firefox-bin:19796): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed

Using: firefox 3.5.2-1, compiz-core 0.8.2-1, nvidia 185.18.31-1
arch: x86_64
Shell integration has nothing to do with full screen, etc. Moving to general though there is likely a better component for this.
Component: Shell Integration → General
QA Contact: shell.integration → general
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

You may also wish to try with the latest Firefox 4 beta, http://www.mozilla.com/en-US/firefox/all-beta.html.
Whiteboard: [CLOSEME 2011-1-30]
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.