Re: Xlib: extension "Generic Event Extension" missing on display ":0.0"

[Da Rock]

On Thu, 2009-02-05 at 08:53 +0100, Alain G. Fabry wrote:
> I'm using the radeonhd driver and am getting the message also.
> 
> Video card is the ati mobility radeon x1600.
> 
> 
> On Wed, Feb 04, 2009 at 06:48:40PM -0500, Robert Huff wrote:
> > 
> > Da Rock writes:
> > 
> > >  > X is working fine here on a Radeon X1650 on 7.1-RELEASE with rnoland's
> > >  > last patch to update the kernel direct rendering support (which should
> > >  > be in 7-STABLE by now). Accellerated X works, 2D and 3D. Xv also works.
> > >  
> > >  This is getting very interesting now. Based On your comments as
> > >  well as others this could be related to intel. So far all good
> > >  reports are from radeon video drivers, but I happen to be running
> > >  onboard intel videos.
> > 
> > I'm getting this.
> > It appears harmless.
> > The machine in question has a Matrox G450.
> > 
> > 
> > 
> > Robert Huff
> > 
Ok, got that sorted - I'd like to fill in exactly how, but I can't quite
remember what was the trick :( (I think it might have had something to
do EXA and XAA, don't hold me to it though). The error message is still
showing, but I can watch something now on xine and/or mplayer now.

Having said that, I'm still having some crashes- but thats for my new
thread... (seems appropriate)

Thanks again guys.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[O. Hartmann]

Ulrich Spörlein wrote:

On Fri, 30.01.2009 at 23:19:41 +0100, O. Hartmann wrote:

After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4
and having done hurting recompiling nearly everything/package twice now
firefox3 still doesn't work properly and hits me when starting with this
error message:

Xlib:  extension "Generic Event Extension" missing on display ":0.0".

Then firefox3 freezes forever, showing something like the background or
pixel remnants of windows/picograms moving over its window.


This should be unrelated to Xorg 7.4, as it happens to my 7.1 box,
running Xorg 7.3 and the latest firefox3. Please try backing down
firefox3 or some other related libraries that were updated in the last
month (when this started to show up)

Cheers,
Ulrich Spörlein


Hello.
As I reported earlier in this thread, I recompiled everything/package on 
my boxes at least three times and the specified problem still remained. 
But after the update of libGL/libGLUT the last three days everything 
seems to run all right now. Weird ...


Greetings,
Oliver

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[cwt]

Ulrich Spörlein wrote:

On Fri, 30.01.2009 at 23:19:41 +0100, O. Hartmann wrote:
  

After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4
and having done hurting recompiling nearly everything/package twice now
firefox3 still doesn't work properly and hits me when starting with this
error message:

Xlib:  extension "Generic Event Extension" missing on display ":0.0".

Then firefox3 freezes forever, showing something like the background or
pixel remnants of windows/picograms moving over its window.



This should be unrelated to Xorg 7.4, as it happens to my 7.1 box,
running Xorg 7.3 and the latest firefox3. Please try backing down
firefox3 or some other related libraries that were updated in the last
month (when this started to show up)

Cheers,
Ulrich Spörlein
  
hey, sorry to barge in, but have you ppl by any chance seen a related 
post about this?
i saw this (am still getting it) after 7.4 upgrade, but when someone 
else reported it, the person who i think committed xorg updates i 
believe said this warning is harmless and only showing because some new 
functionality in the lib is not yet being used, something to that effect?


i think he explained that he just overlooked disabling the warning.

are you aware of this or are you having stability problems still? my 
system spits this warning, but just noise, and all working ok otherwise.
if you are aware of the post, but still having problems, then disregard 
this, and sorry if i missed something

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xlib: extension "Generic Event Extension" missing on display ":0.0"

[Alain G. Fabry]

I'm using the radeonhd driver and am getting the message also.

Video card is the ati mobility radeon x1600.


On Wed, Feb 04, 2009 at 06:48:40PM -0500, Robert Huff wrote:
> 
> Da Rock writes:
> 
> >  > X is working fine here on a Radeon X1650 on 7.1-RELEASE with rnoland's
> >  > last patch to update the kernel direct rendering support (which should
> >  > be in 7-STABLE by now). Accellerated X works, 2D and 3D. Xv also works.
> >  
> >  This is getting very interesting now. Based On your comments as
> >  well as others this could be related to intel. So far all good
> >  reports are from radeon video drivers, but I happen to be running
> >  onboard intel videos.
> 
>   I'm getting this.
>   It appears harmless.
>   The machine in question has a Matrox G450.
> 
> 
> 
>   Robert Huff
> 
> 
> 
> 
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[Ulrich Spörlein]

On Fri, 30.01.2009 at 23:19:41 +0100, O. Hartmann wrote:
> After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4
> and having done hurting recompiling nearly everything/package twice now
> firefox3 still doesn't work properly and hits me when starting with this
> error message:
> 
> Xlib:  extension "Generic Event Extension" missing on display ":0.0".
> 
> Then firefox3 freezes forever, showing something like the background or
> pixel remnants of windows/picograms moving over its window.

This should be unrelated to Xorg 7.4, as it happens to my 7.1 box,
running Xorg 7.3 and the latest firefox3. Please try backing down
firefox3 or some other related libraries that were updated in the last
month (when this started to show up)

Cheers,
Ulrich Spörlein
-- 
None are more hopelessly enslaved than those who falsely believe they are free
-- Johann Wolfgang von Goethe
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xlib: extension "Generic Event Extension" missing on display ":0.0"

[Robert Huff]

Da Rock writes:

>  > X is working fine here on a Radeon X1650 on 7.1-RELEASE with rnoland's
>  > last patch to update the kernel direct rendering support (which should
>  > be in 7-STABLE by now). Accellerated X works, 2D and 3D. Xv also works.
>  
>  This is getting very interesting now. Based On your comments as
>  well as others this could be related to intel. So far all good
>  reports are from radeon video drivers, but I happen to be running
>  onboard intel videos.

I'm getting this.
It appears harmless.
The machine in question has a Matrox G450.



Robert Huff





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xlib: extension "Generic Event Extension" missing on display ":0.0"

[Da Rock]

On Wed, 2009-02-04 at 18:56 +0100, Roland Smith wrote:
> On Thu, Feb 05, 2009 at 12:10:30AM +1000, Da Rock wrote:
> > Ok, I give up... wtf am I missing here? 
> 
> The Xext library has the extension, but the server hasn't yet. It should
> be harmless. I don't notice any problems with it. (7.1-RELEASE amd64
> with Xorg 7.4)
> 
> > I can now confirm this problem in several ways:
> > 1) I just ran xine, mplayer, and file-roller and the error came up
> > causing all programs bar file-roller to crash.
> 
> I've got mplayer playing fine with this message.
> 
> > Logs don't show anything, this error is just on screen (wierd?). Another
> > clarification to this is that it only happens in media players after
> > content is attempted to load.
> 
> What driver are you using in X? And what kind of video output driver are
> you using in mplayer?
> 
> X is working fine here on a Radeon X1650 on 7.1-RELEASE with rnoland's
> last patch to update the kernel direct rendering support (which should
> be in 7-STABLE by now). Accellerated X works, 2D and 3D. Xv also works.

This is getting very interesting now. Based On your comments as well as
others this could be related to intel. So far all good reports are from
radeon video drivers, but I happen to be running onboard intel videos.

xorg.conf (Let me know if there could be any security risk in posting
this verbatim, I couldn't see how myself.):

Section "ServerLayout"
Identifier "X.org Configured"
Screen  0  "Screen0" 0 0
InputDevice"Mouse0" "CorePointer"
InputDevice"Keyboard0" "CoreKeyboard"
Option "AIGLX" "True"
EndSection

Section "Files"
#   RgbPath  "/usr/local/share/X11/rgb"
ModulePath   "/usr/local/lib/xorg/modules"
FontPath "/usr/local/lib/X11/fonts/misc/"
FontPath "/usr/local/lib/X11/fonts/TTF/"
FontPath "/usr/local/lib/X11/fonts/OTF"
FontPath "/usr/local/lib/X11/fonts/Type1/"
FontPath "/usr/local/lib/X11/fonts/100dpi/"
FontPath "/usr/local/lib/X11/fonts/75dpi/"
EndSection

Section "Module"
Load  "extmod"
Load  "record"
Load  "dbe"
Load  "glx"
Load  "GLcore"
Load  "xtrap"
Load  "dri"
Load  "freetype"
Load  "type1"
EndSection

Section "InputDevice"
Identifier  "Keyboard0"
Driver  "kbd"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option  "Protocol" "auto"
Option  "Device" "/dev/sysmouse"
Option  "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
#DisplaySize  330   210 # mm
Identifier   "Monitor0"
VendorName   "SEC"
ModelName"4945"
EndSection

Section "Device"
### Available Driver options are:-
### Values: : integer, : float, : "True"/"False",
### : "String", : " Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel"   # []
#Option "SWcursor"  # []
#Option "ColorKey"  # 
#Option "CacheLines"# 
#Option "Dac6Bit"   # []
#Option "DRI"   # []
#Option "NoDDC" # []
#Option "ShowCache" # []
#Option "XvMCSurfaces"  # 
#Option "PageFlip"  # []
Identifier  "Card0"
Driver  "intel"
VendorName  "Intel Corporation"
BoardName   "Mobile GM965/GL960 Integrated Graphics Controller"
BusID   "PCI:0:2:0"
#Option  "LVDS24Bit""True"
Option  "AddARGBGLXVisuals" "True"
Option  "DRI"   "True"
Option  "AccelMethod"   "EXA"
Option  "XAANoOffscreenPixmaps" "True"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor"Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport   0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 24
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

Section "DRI"
Mode0666
EndSection

This is just on my laptop, I set this up in my testing compiz-fusion,
the

Re: Xlib: extension "Generic Event Extension" missing on display ":0.0"

[matt donovan]

On Wed, Feb 4, 2009 at 12:56 PM, Roland Smith  wrote:

> On Thu, Feb 05, 2009 at 12:10:30AM +1000, Da Rock wrote:
> > Ok, I give up... wtf am I missing here?
>
> The Xext library has the extension, but the server hasn't yet. It should
> be harmless. I don't notice any problems with it. (7.1-RELEASE amd64
> with Xorg 7.4)
>
> > I can now confirm this problem in several ways:
> > 1) I just ran xine, mplayer, and file-roller and the error came up
> > causing all programs bar file-roller to crash.
>
> I've got mplayer playing fine with this message.
>
> > Logs don't show anything, this error is just on screen (wierd?). Another
> > clarification to this is that it only happens in media players after
> > content is attempted to load.
>
> What driver are you using in X? And what kind of video output driver are
> you using in mplayer?
>
> X is working fine here on a Radeon X1650 on 7.1-RELEASE with rnoland's
> last patch to update the kernel direct rendering support (which should
> be in 7-STABLE by now). Accellerated X works, 2D and 3D. Xv also works.
>
> > Can someone clarify why? Also how do I kill this extension (I don't
> > think that ever came out- correct me if I'm wrong)?
>
> The upcoming server 1.6.0 has this extension. As soon as that is rolled
> out, the messages should disappear, I think.
>
> You yould try to roll-back the Xext library...
>
> Roland
> --
> R.F.Smith   
> http://www.xs4all.nl/~rsmith/
> [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
> pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


/usr/ports/UPDATING is already updated about this message and to say just
ignore it
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xlib: extension "Generic Event Extension" missing on display ":0.0"

[Roland Smith]

On Thu, Feb 05, 2009 at 12:10:30AM +1000, Da Rock wrote:
> Ok, I give up... wtf am I missing here? 

The Xext library has the extension, but the server hasn't yet. It should
be harmless. I don't notice any problems with it. (7.1-RELEASE amd64
with Xorg 7.4)

> I can now confirm this problem in several ways:
> 1) I just ran xine, mplayer, and file-roller and the error came up
> causing all programs bar file-roller to crash.

I've got mplayer playing fine with this message.

> Logs don't show anything, this error is just on screen (wierd?). Another
> clarification to this is that it only happens in media players after
> content is attempted to load.

What driver are you using in X? And what kind of video output driver are
you using in mplayer?

X is working fine here on a Radeon X1650 on 7.1-RELEASE with rnoland's
last patch to update the kernel direct rendering support (which should
be in 7-STABLE by now). Accellerated X works, 2D and 3D. Xv also works.

> Can someone clarify why? Also how do I kill this extension (I don't
> think that ever came out- correct me if I'm wrong)?

The upcoming server 1.6.0 has this extension. As soon as that is rolled
out, the messages should disappear, I think.

You yould try to roll-back the Xext library...

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgphOYzjnsRHA.pgp
Description: PGP signature

Re: Xlib: extension "Generic Event Extension" missing on display ":0.0"

[Warren Block]

On Thu, 5 Feb 2009, Da Rock wrote:


Ok, I give up... wtf am I missing here? As per the Xorg upgrade disaster
discussion, I commented that this error IS causing issues; namely
mplayer, file-roller. After that I read nothing in reply.


The extension message is probably not the problem.  mplayer runs fine 
here; in fact, it's running as I type this, and two of the Generic Event 
Extension messages are visible before mplayer text output in the console 
window.



I can now confirm this problem in several ways:
1) I just ran xine, mplayer, and file-roller and the error came up
causing all programs bar file-roller to crash.
2) New install of 7.1 on a desktop has the same problem. Tested with
xine and xine crashed.


Maybe video driver?  I'm using a radeon driver with EXA enabled.

-Warren Block * Rapid City, South Dakota USA
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Xlib: extension "Generic Event Extension" missing on display ":0.0"

[Da Rock]

Ok, I give up... wtf am I missing here? As per the Xorg upgrade disaster
discussion, I commented that this error IS causing issues; namely
mplayer, file-roller. After that I read nothing in reply.

I can now confirm this problem in several ways:
1) I just ran xine, mplayer, and file-roller and the error came up
causing all programs bar file-roller to crash.
2) New install of 7.1 on a desktop has the same problem. Tested with
xine and xine crashed.

Logs don't show anything, this error is just on screen (wierd?). Another
clarification to this is that it only happens in media players after
content is attempted to load.

Can someone clarify why? Also how do I kill this extension (I don't
think that ever came out- correct me if I'm wrong)?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade disaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[Da Rock]

On Sun, 2009-02-01 at 21:49 +0100, Marcin Cieslak wrote:
> O. Hartmann wrote:
> > After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4
> > and having done hurting recompiling nearly everything/package twice now
> > firefox3 still doesn't work properly and hits me when starting with this
> > error message:
> > 
> > Xlib:  extension "Generic Event Extension" missing on display ":0.0".
> 
> 
> Looks like libraries (Xext among others) already support the XGE extension:
> 
> http://thread.gmane.org/gmane.comp.freedesktop.xorg/36483
> 
> but the current the 1.5 Xorg server does not support and the 1.6 release 
> is behind schedule a bit:
> 
> http://www.phoronix.com/scan.php?page=news_item&px=Njg4OA
> 
> I keep getting this error after upgrade of X today but everything works 
> as usual.
> 

Except for me: I have mplayer not working as well as other misc X progs.
Same error...

> > Then firefox3 freezes forever, showing something like the background or
> > pixel remnants of windows/picograms moving over its window.
> 
> The firefox problem is unrelated I think to the message above (as 
> demonstrated later in the thred)
> 
> --Marcin
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade disaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[Marcin Cieslak]

O. Hartmann wrote:

After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4
and having done hurting recompiling nearly everything/package twice now
firefox3 still doesn't work properly and hits me when starting with this
error message:

Xlib:  extension "Generic Event Extension" missing on display ":0.0".



Looks like libraries (Xext among others) already support the XGE extension:

http://thread.gmane.org/gmane.comp.freedesktop.xorg/36483

but the current the 1.5 Xorg server does not support and the 1.6 release 
is behind schedule a bit:


http://www.phoronix.com/scan.php?page=news_item&px=Njg4OA

I keep getting this error after upgrade of X today but everything works 
as usual.



Then firefox3 freezes forever, showing something like the background or
pixel remnants of windows/picograms moving over its window.


The firefox problem is unrelated I think to the message above (as 
demonstrated later in the thred)


--Marcin

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[Scot Hetzel]

On Sun, Feb 1, 2009 at 5:28 AM, O. Hartmann
 wrote:
> Scot Hetzel wrote:
>> On Sat, Jan 31, 2009 at 6:39 PM, O. Hartmann
>>  wrote:
>>
>>> build-process, but I doubt this. I did a 'ldd' on the Firefox3 binary
>>> and  I got the attached dump of the linked shared objects.
>>> Interestingly, the first three entries show up something missing -
>>> therefore I deinstalled Firefox and rebuild the browser after an
>>> additional rebuild of libxcb (via portupgrade -rf). Previously, all Xorg
>>>
>>
>>
>>> thor# ldd firefox-bin
>>> firefox-bin:
>>>libxul.so => not found (0x0)
>>>libmozjs.so => not found (0x0)
>>>libxpcom.so => not found (0x0)
>>>libplds4.so.1 => /usr/local/lib/libplds4.so.1 (0x80063e000)
>>>libplc4.so.1 => /usr/local/lib/libplc4.so.1 (0x80076f000)
>>>
>>
>> When firefox3 was first added to the ports collection, I had noticed
>> this problem with firefox3 (after using sysutils/libchk), but I didn't
>> have this problem with the firefox 2.  A look at the difference
>> between the www/firefox and www/firefox3 Makefiles showed that
>> firefox3 was missing this:
>>
>> LDFLAGS+= -Wl,-rpath,${PREFIX}/lib/${MOZ_RPATH}
>>
>> After adding this line to the ports Makefile, and rebuilding the port,
>> these libraries are now showing as found in the ldd output.
>>
>> Scot
>>
> Isn't that worth a PR?
>
>
Submitted and rejected:

http://www.freebsd.org/cgi/query-pr.cgi?pr=131237

As it doesn't affect the operation of Firefox3's firefox-bin program.

Scot
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension " missing on display ":0.0".

[Garrett Cooper]

On Jan 31, 2009, at 9:05 PM, Mel wrote:


On Saturday 31 January 2009 15:39:03 O. Hartmann wrote:

Mel wrote:

On Friday 30 January 2009 13:19:41 O. Hartmann wrote:
After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new  
xorg-7.4
and having done hurting recompiling nearly everything/package  
twice now
firefox3 still doesn't work properly and hits me when starting  
with this

error message:

Xlib:  extension "Generic Event Extension" missing on display ": 
0.0".


Then firefox3 freezes forever, showing something like the  
background or

pixel remnants of windows/picograms moving over its window.


http://lists.freedesktop.org/archives/xorg/2008-October/039134.html


Well, that doesn't help very much. As R. Noland wrote, the error  
coming

up isn't of any harm.

I still have Firefox3 not working on a FreeBSD 8.0-CURRENT/AMD64 UP  
box,

running the most recent FreeBSD 8.0-CURRENT and having now recompiled
three time EVERYTHING, Firefox3 inclusive. Firefox3 is still stuck  
when
it comes to pulldown menus or requester for download destination,  
eating

up 100% CPU time and slowing down the box incredible. I pretty sure I
have all the stuff of the X11 suite in the right place and the right
revision number, as I said, I recompiled everything three times and I
did several attempts upgrading the whole Xorg since sunday last week.


You have 2 choices:
- revert to known working xorg-server-1.4 (xorg 7.3)
- try to debug this using the send-pr system, given the ammount of  
problems
people are posting with this xorg-server, more datapoints are not a  
bad

thing.

As a sidenote, it would be nice if xorg-server14 port would be  
created till

the dust has settled.


	I don't have an issue with any cairo related ports after upgrading to  
xorg 7.4. Of course I had to rebuild everything dependent on libxcb,  
but that took no more than one iteration to complete (apart from  
xchat2, which took 4 iterations to finish because of some wonky  
library mucking up the works). Yay for statically linked library code - 
_-...

-Garrett
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[Alex Goncharov]

,--- I/Alex (Sun, 01 Feb 2009 07:56:40 -0500) *
| All I was saying was that your ldd experiment was... hmm... not
| correct (if you agree with mine, of course). 
,--- You/O. (Sun, 01 Feb 2009 14:50:47 +0100) *
| Saying, it was stupid? You're correct. It was stupid and, of course, it
| doesn't matter if the libs show up or not.

Not stupid -- you tried various things in desperation and hurry, and
reported your observations and thoughts.  It's normal :-)

| I thought, at the first shot, firefox3 binary needs to have a
| complete reference to all of its libraries, but thinking so leads
| the advantage of having dynamical loadable objects ad absurdum.

Glad this is cleared now!

-- Alex -- alex-goncha...@comcast.net --

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[O. Hartmann]

Alex Goncharov wrote:
> ,--- You/O. (Sun, 01 Feb 2009 12:07:32 +0100) *
> | Alex Goncharov wrote:
> | > ,--- You/O. (Sun, 01 Feb 2009 01:39:03 +0100) *
> | > | I did a 'ldd' on the Firefox3 binary
> | > | and  I got the attached dump of the linked shared objects.
> | > | Interestingly, the first three entries show up something missing -
> | >
> | > LD_LIBRARY_PATH=/usr/local/lib/firefox3 ldd 
> /usr/local/lib/firefox3/firefox-bin | head -n 5
> | > /usr/local/lib/firefox3/firefox-bin:
> | > libxul.so => /usr/local/lib/firefox3/libxul.so (0x28087000)
> | > libmozjs.so => /usr/local/lib/firefox3/libmozjs.so (0x28e8f000)
> | > libxpcom.so => /usr/local/lib/firefox3/libxpcom.so (0x28f1f000)
> | >
> | > firefox3 sets LD_LIBRARY_PATH for you :-)
> | >   
> | It does not!
>
> --
>
> $ grep run-mozilla.sh  /usr/local/bin/firefox3 
> # Use run-mozilla.sh in the current dir if it exists
> # If not, then start resolving symlinks until we find run-mozilla.sh
> run_moz="$curdir/run-mozilla.sh"
> run_moz="$curdir/run-mozilla.sh"
>   run_moz="$dist_bin/run-mozilla.sh"
>   if [ -x "$moz_libdir/run-mozilla.sh" ]; then
>   echo $dist_bin/run-mozilla.sh $script_args $dist_bin/$MOZILLA_BIN "$@"
> "$dist_bin/run-mozilla.sh" $script_args "$dist_bin/$MOZILLA_BIN" "$@"
>
>
> $ grep  LD_LIBRARY_PATH /usr/local/lib/firefox3/run-mozilla.sh
> ## Set LD_LIBRARY_PATH
> ## On Solaris we use $ORIGIN (set in RUNPATH) instead of LD_LIBRARY_PATH 
> ## under dist/bin. To solve the problem, we should rely on LD_LIBRARY_PATH
> 
> LD_LIBRARY_PATH=${MOZ_DIST_BIN}:${MOZ_DIST_BIN}/plugins:${MRE_HOME}${LD_LIBRARY_PATH+":$LD_LIBRARY_PATH"}
> if [ -n "$LD_LIBRARY_PATH_64" ]; then
> 
> LD_LIBRARY_PATH_64=${MOZ_DIST_BIN}:${MOZ_DIST_BIN}/plugins:${MRE_HOME}${LD_LIBRARY_PATH_64+":$LD_LIBRARY_PATH_64"}
> ## Set DYLD_LIBRARY_PATH for Mac OS X (Darwin)
> DYLD_LIBRARY_PATH=${MOZ_DIST_BIN}:${MRE_HOME}${DYLD_LIBRARY_PATH+":$DYLD_LIBRARY_PATH"}
>   echo "  LD_LIBRARY_PATH=$LD_LIBRARY_PATH"
>   if [ -n "$LD_LIBRARY_PATH_64" ]; then
> echo "LD_LIBRARY_PATH_64=$LD_LIBRARY_PATH_64"
>   echo "DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH"
> export MOZILLA_FIVE_HOME LD_LIBRARY_PATH
> export SHLIB_PATH LIBPATH LIBRARY_PATH ADDON_PATH DYLD_LIBRARY_PATH
>
> --
>
> No, it doesn't?
>
> | ... on all of my boxes (amd64), it does not ... even on those
> | machines where Firefox3 is running, these libs are empty. But I
> | realized that those boxes are capable running firefox3 after the
> | 'great Xorg-update-catastrophy' have still installed firefox2 ... I
> | will check tomorrow at the lab if this do have an influence of the
> | proper work abilities of firefox3 when removing the old firefox2.
> | 
> | When setting LD_LIBRARY_PATH manually, adding /usr/lib/firefox3/, it
> | doesn't change the bad situation on the failing CURRENT amd64 box.
>
> All I was saying was that your ldd experiment was... hmm... not
> correct (if you agree with mine, of course). 
>   

Saying, it was stupid? You're correct. It was stupid and, of course, it
doesn't matter if the libs show up or not.
 I thought, at the first shot, firefox3 binary needs to have a complete
reference to all of its
libraries, but thinking so leads  the advantage of having dynamical
loadable objects ad absurdum.

Greetings,
Oliver
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension " missing on display ":0.0".

[Alex Goncharov]

,--- You/Mel (Sat, 31 Jan 2009 20:05:50 -0900) *
| As a sidenote, it would be nice if xorg-server14 port would be created till 
| the dust has settled.

Very, very nice.

Almost as nice as xorg-server being the old, working xorg-server and
xorg-server-devel the new, broken one.

-- Alex -- alex-goncha...@comcast.net --
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[Alex Goncharov]

,--- You/O. (Sun, 01 Feb 2009 12:07:32 +0100) *
| Alex Goncharov wrote:
| > ,--- You/O. (Sun, 01 Feb 2009 01:39:03 +0100) *
| > | I did a 'ldd' on the Firefox3 binary
| > | and  I got the attached dump of the linked shared objects.
| > | Interestingly, the first three entries show up something missing -
| >
| > LD_LIBRARY_PATH=/usr/local/lib/firefox3 ldd 
/usr/local/lib/firefox3/firefox-bin | head -n 5
| > /usr/local/lib/firefox3/firefox-bin:
| > libxul.so => /usr/local/lib/firefox3/libxul.so (0x28087000)
| > libmozjs.so => /usr/local/lib/firefox3/libmozjs.so (0x28e8f000)
| > libxpcom.so => /usr/local/lib/firefox3/libxpcom.so (0x28f1f000)
| >
| > firefox3 sets LD_LIBRARY_PATH for you :-)
| >   
| It does not!

--

$ grep run-mozilla.sh  /usr/local/bin/firefox3 
# Use run-mozilla.sh in the current dir if it exists
# If not, then start resolving symlinks until we find run-mozilla.sh
run_moz="$curdir/run-mozilla.sh"
run_moz="$curdir/run-mozilla.sh"
  run_moz="$dist_bin/run-mozilla.sh"
  if [ -x "$moz_libdir/run-mozilla.sh" ]; then
  echo $dist_bin/run-mozilla.sh $script_args $dist_bin/$MOZILLA_BIN "$@"
"$dist_bin/run-mozilla.sh" $script_args "$dist_bin/$MOZILLA_BIN" "$@"


$ grep  LD_LIBRARY_PATH /usr/local/lib/firefox3/run-mozilla.sh
## Set LD_LIBRARY_PATH
## On Solaris we use $ORIGIN (set in RUNPATH) instead of LD_LIBRARY_PATH 
## under dist/bin. To solve the problem, we should rely on LD_LIBRARY_PATH

LD_LIBRARY_PATH=${MOZ_DIST_BIN}:${MOZ_DIST_BIN}/plugins:${MRE_HOME}${LD_LIBRARY_PATH+":$LD_LIBRARY_PATH"}
if [ -n "$LD_LIBRARY_PATH_64" ]; then

LD_LIBRARY_PATH_64=${MOZ_DIST_BIN}:${MOZ_DIST_BIN}/plugins:${MRE_HOME}${LD_LIBRARY_PATH_64+":$LD_LIBRARY_PATH_64"}
## Set DYLD_LIBRARY_PATH for Mac OS X (Darwin)
DYLD_LIBRARY_PATH=${MOZ_DIST_BIN}:${MRE_HOME}${DYLD_LIBRARY_PATH+":$DYLD_LIBRARY_PATH"}
  echo "  LD_LIBRARY_PATH=$LD_LIBRARY_PATH"
  if [ -n "$LD_LIBRARY_PATH_64" ]; then
echo "LD_LIBRARY_PATH_64=$LD_LIBRARY_PATH_64"
  echo "DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH"
export MOZILLA_FIVE_HOME LD_LIBRARY_PATH
export SHLIB_PATH LIBPATH LIBRARY_PATH ADDON_PATH DYLD_LIBRARY_PATH

--

No, it doesn't?

| ... on all of my boxes (amd64), it does not ... even on those
| machines where Firefox3 is running, these libs are empty. But I
| realized that those boxes are capable running firefox3 after the
| 'great Xorg-update-catastrophy' have still installed firefox2 ... I
| will check tomorrow at the lab if this do have an influence of the
| proper work abilities of firefox3 when removing the old firefox2.
| 
| When setting LD_LIBRARY_PATH manually, adding /usr/lib/firefox3/, it
| doesn't change the bad situation on the failing CURRENT amd64 box.

All I was saying was that your ldd experiment was... hmm... not
correct (if you agree with mine, of course). 

-- Alex -- alex-goncha...@comcast.net --

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[O. Hartmann]

Scot Hetzel wrote:
> On Sat, Jan 31, 2009 at 6:39 PM, O. Hartmann
>  wrote:
>   
>> build-process, but I doubt this. I did a 'ldd' on the Firefox3 binary
>> and  I got the attached dump of the linked shared objects.
>> Interestingly, the first three entries show up something missing -
>> therefore I deinstalled Firefox and rebuild the browser after an
>> additional rebuild of libxcb (via portupgrade -rf). Previously, all Xorg
>> 
>
>   
>> thor# ldd firefox-bin
>> firefox-bin:
>>libxul.so => not found (0x0)
>>libmozjs.so => not found (0x0)
>>libxpcom.so => not found (0x0)
>>libplds4.so.1 => /usr/local/lib/libplds4.so.1 (0x80063e000)
>>libplc4.so.1 => /usr/local/lib/libplc4.so.1 (0x80076f000)
>> 
>
> When firefox3 was first added to the ports collection, I had noticed
> this problem with firefox3 (after using sysutils/libchk), but I didn't
> have this problem with the firefox 2.  A look at the difference
> between the www/firefox and www/firefox3 Makefiles showed that
> firefox3 was missing this:
>
> LDFLAGS+= -Wl,-rpath,${PREFIX}/lib/${MOZ_RPATH}
>
> After adding this line to the ports Makefile, and rebuilding the port,
> these libraries are now showing as found in the ldd output.
>
> Scot
>   
Isn't that worth a PR?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[O. Hartmann]

Alex Goncharov wrote:
> ,--- You/O. (Sun, 01 Feb 2009 01:39:03 +0100) *
> | I did a 'ldd' on the Firefox3 binary
> | and  I got the attached dump of the linked shared objects.
> | Interestingly, the first three entries show up something missing -
>
> LD_LIBRARY_PATH=/usr/local/lib/firefox3 ldd 
> /usr/local/lib/firefox3/firefox-bin | head -n 5
> /usr/local/lib/firefox3/firefox-bin:
> libxul.so => /usr/local/lib/firefox3/libxul.so (0x28087000)
> libmozjs.so => /usr/local/lib/firefox3/libmozjs.so (0x28e8f000)
> libxpcom.so => /usr/local/lib/firefox3/libxpcom.so (0x28f1f000)
>
> firefox3 sets LD_LIBRARY_PATH for you :-)
>   
It does not!

... on all of my boxes (amd64), it does not ... even on those machines
where Firefox3 is running, these libs are empty. But I realized that those
boxes are capable running firefox3 after the 'great
Xorg-update-catastrophy' have still installed firefox2 ... I will check
tomorrow at the lab if
this do have an influence of the proper work abilities of firefox3 when
removing the old firefox2.

When setting LD_LIBRARY_PATH manually, adding /usr/lib/firefox3/, it
doesn't change the bad situation on the failing CURRENT amd64 box.
> | thor# ldd firefox-bin
> | firefox-bin:
> | libxul.so => not found (0x0)
> | libmozjs.so => not found (0x0)
> | libxpcom.so => not found (0x0)
> | libplds4.so.1 => /usr/local/lib/libplds4.so.1 (0x80063e000)
>
> -- Alex -- alex-goncha...@comcast.net --
>
>   

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension " missing on display ":0.0".

[Mel]

On Saturday 31 January 2009 15:39:03 O. Hartmann wrote:
> Mel wrote:
> > On Friday 30 January 2009 13:19:41 O. Hartmann wrote:
> >> After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4
> >> and having done hurting recompiling nearly everything/package twice now
> >> firefox3 still doesn't work properly and hits me when starting with this
> >> error message:
> >>
> >> Xlib:  extension "Generic Event Extension" missing on display ":0.0".
> >>
> >> Then firefox3 freezes forever, showing something like the background or
> >> pixel remnants of windows/picograms moving over its window.
> >
> > http://lists.freedesktop.org/archives/xorg/2008-October/039134.html
>
> Well, that doesn't help very much. As R. Noland wrote, the error coming
> up isn't of any harm.
>
> I still have Firefox3 not working on a FreeBSD 8.0-CURRENT/AMD64 UP box,
> running the most recent FreeBSD 8.0-CURRENT and having now recompiled
> three time EVERYTHING, Firefox3 inclusive. Firefox3 is still stuck when
> it comes to pulldown menus or requester for download destination, eating
> up 100% CPU time and slowing down the box incredible. I pretty sure I
> have all the stuff of the X11 suite in the right place and the right
> revision number, as I said, I recompiled everything three times and I
> did several attempts upgrading the whole Xorg since sunday last week.

You have 2 choices:
- revert to known working xorg-server-1.4 (xorg 7.3)
- try to debug this using the send-pr system, given the ammount of problems 
people are posting with this xorg-server, more datapoints are not a bad 
thing.

As a sidenote, it would be nice if xorg-server14 port would be created till 
the dust has settled.
-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[Alex Goncharov]

,--- You/O. (Sun, 01 Feb 2009 01:39:03 +0100) *
| I did a 'ldd' on the Firefox3 binary
| and  I got the attached dump of the linked shared objects.
| Interestingly, the first three entries show up something missing -

LD_LIBRARY_PATH=/usr/local/lib/firefox3 ldd /usr/local/lib/firefox3/firefox-bin 
| head -n 5
/usr/local/lib/firefox3/firefox-bin:
libxul.so => /usr/local/lib/firefox3/libxul.so (0x28087000)
libmozjs.so => /usr/local/lib/firefox3/libmozjs.so (0x28e8f000)
libxpcom.so => /usr/local/lib/firefox3/libxpcom.so (0x28f1f000)

firefox3 sets LD_LIBRARY_PATH for you :-)

| thor# ldd firefox-bin
| firefox-bin:
| libxul.so => not found (0x0)
| libmozjs.so => not found (0x0)
| libxpcom.so => not found (0x0)
| libplds4.so.1 => /usr/local/lib/libplds4.so.1 (0x80063e000)

-- Alex -- alex-goncha...@comcast.net --

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[Scot Hetzel]

On Sat, Jan 31, 2009 at 6:39 PM, O. Hartmann
 wrote:
> build-process, but I doubt this. I did a 'ldd' on the Firefox3 binary
> and  I got the attached dump of the linked shared objects.
> Interestingly, the first three entries show up something missing -
> therefore I deinstalled Firefox and rebuild the browser after an
> additional rebuild of libxcb (via portupgrade -rf). Previously, all Xorg

> thor# ldd firefox-bin
> firefox-bin:
>libxul.so => not found (0x0)
>libmozjs.so => not found (0x0)
>libxpcom.so => not found (0x0)
>libplds4.so.1 => /usr/local/lib/libplds4.so.1 (0x80063e000)
>libplc4.so.1 => /usr/local/lib/libplc4.so.1 (0x80076f000)

When firefox3 was first added to the ports collection, I had noticed
this problem with firefox3 (after using sysutils/libchk), but I didn't
have this problem with the firefox 2.  A look at the difference
between the www/firefox and www/firefox3 Makefiles showed that
firefox3 was missing this:

LDFLAGS+= -Wl,-rpath,${PREFIX}/lib/${MOZ_RPATH}

After adding this line to the ports Makefile, and rebuilding the port,
these libraries are now showing as found in the ldd output.

Scot
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[O. Hartmann]

Mel wrote:
> On Friday 30 January 2009 13:19:41 O. Hartmann wrote:
>   
>> After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4
>> and having done hurting recompiling nearly everything/package twice now
>> firefox3 still doesn't work properly and hits me when starting with this
>> error message:
>>
>> Xlib:  extension "Generic Event Extension" missing on display ":0.0".
>>
>> Then firefox3 freezes forever, showing something like the background or
>> pixel remnants of windows/picograms moving over its window.
>> 
>
> http://lists.freedesktop.org/archives/xorg/2008-October/039134.html
>
>   
Well, that doesn't help very much. As R. Noland wrote, the error coming
up isn't of any harm.

I still have Firefox3 not working on a FreeBSD 8.0-CURRENT/AMD64 UP box,
running the most recent FreeBSD 8.0-CURRENT and having now recompiled
three time EVERYTHING, Firefox3 inclusive. Firefox3 is still stuck when
it comes to pulldown menus or requester for download destination, eating
up 100% CPU time and slowing down the box incredible. I pretty sure I
have all the stuff of the X11 suite in the right place and the right
revision number, as I said, I recompiled everything three times and I
did several attempts upgrading the whole Xorg since sunday last week.
Also a deletion of the ports has been performed and then reinstalled. I
can not asure that there is any zomby-library out there disturbing the
build-process, but I doubt this. I did a 'ldd' on the Firefox3 binary
and  I got the attached dump of the linked shared objects.
Interestingly, the first three entries show up something missing -
therefore I deinstalled Firefox and rebuild the browser after an
additional rebuild of libxcb (via portupgrade -rf). Previously, all Xorg
stuff has been rebuild and by the numbers it seems to be up to date.
I double checked if /usr/local/lib/firefox3 has been completely removed
and for the user's stuff, I deleted the entire ~/.mozilla folder and
started Firefox3 from scratch - everytime with the same result.

Firefox3 did not show these symptomes on a FreeBSD 7.1-STABLE/AMD64 SMP
box, also with most recent sources and undergone the same three time
recompilation of everything procedure. Unlucklily, I do not have another
UP box running FreeBSD 8.0/amd64 for double check this behaviour. Bevor
filing a PR, I would like to ask the list ...

Thanks in advance,

Oliver

thor# ldd firefox-bin
firefox-bin:
libxul.so => not found (0x0)
libmozjs.so => not found (0x0)
libxpcom.so => not found (0x0)
libplds4.so.1 => /usr/local/lib/libplds4.so.1 (0x80063e000)
libplc4.so.1 => /usr/local/lib/libplc4.so.1 (0x80076f000)
libnspr4.so.1 => /usr/local/lib/libnspr4.so.1 (0x8008a1000)
libgtk-x11-2.0.so.0 => /usr/local/lib/libgtk-x11-2.0.so.0
(0x8009d9000)
libatk-1.0.so.0 => /usr/local/lib/libatk-1.0.so.0 (0x800e92000)
libgdk-x11-2.0.so.0 => /usr/local/lib/libgdk-x11-2.0.so.0
(0x800fb1000)
libgdk_pixbuf-2.0.so.0 => /usr/local/lib/libgdk_pixbuf-2.0.so.0
(0x80114d000)
libpangocairo-1.0.so.0 => /usr/local/lib/libpangocairo-1.0.so.0
(0x801267000)
libgio-2.0.so.0 => /usr/local/lib/libgio-2.0.so.0 (0x801372000)
libXext.so.6 => /usr/local/lib/libXext.so.6 (0x8014de000)
libXrender.so.1 => /usr/local/lib/libXrender.so.1 (0x8015ef000)
libXinerama.so.1 => /usr/local/lib/libXinerama.so.1 (0x8016f8000)
libXi.so.6 => /usr/local/lib/libXi.so.6 (0x8017fa000)
libXrandr.so.2 => /usr/local/lib/libXrandr.so.2 (0x801903000)
libXcursor.so.1 => /usr/local/lib/libXcursor.so.1 (0x801a0a000)
libXcomposite.so.1 => /usr/local/lib/libXcomposite.so.1
(0x801b14000)
libXdamage.so.1 => /usr/local/lib/libXdamage.so.1 (0x801c17000)
libcairo.so.2 => /usr/local/lib/libcairo.so.2 (0x801d19000)
libpangoft2-1.0.so.0 => /usr/local/lib/libpangoft2-1.0.so.0
(0x801e96000)
libpango-1.0.so.0 => /usr/local/lib/libpango-1.0.so.0 (0x801fc3000)
libfreetype.so.9 => /usr/local/lib/libfreetype.so.9 (0x80210a000)
libz.so.4 => /lib/libz.so.4 (0x802287000)
libfontconfig.so.1 => /usr/local/lib/libfontconfig.so.1
(0x80239b000)
libgmodule-2.0.so.0 => /usr/local/lib/libgmodule-2.0.so.0
(0x8024ca000)
libX11.so.6 => /usr/local/lib/libX11.so.6 (0x8025cd000)
libXfixes.so.3 => /usr/local/lib/libXfixes.so.3 (0x8027cb000)
libgobject-2.0.so.0 => /usr/local/lib/libgobject-2.0.so.0
(0x8028d)
libglib-2.0.so.0 => /usr/local/lib/libglib-2.0.so.0 (0x802a12000)
libm.so.5 => /lib/libm.so.5 (0x802bcb000)
libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x802cea000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x802ecd0

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[Robert Noland]

On Fri, 2009-01-30 at 18:23 -0500, Alex Goncharov wrote:
> ,--- You/O. (Fri, 30 Jan 2009 23:19:41 +0100) *
> | After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4
> | and having done hurting recompiling nearly everything/package twice now
> | firefox3 still doesn't work properly and hits me when starting with this
> | error message:
> | 
> | Xlib:  extension "Generic Event Extension" missing on display ":0.0".
> 
> Interesting -- I just did my comprehensive upgrade, as a part of which
> xorg-server went from 1.5.3_1,1 to 1.5.3_2,1.
> 
> And this is what I see now, for the first time, and consistently:
> 
> ----
> $ xterm&
> [3] 12585
> 
> $ emacs &   
> [4] 12644
> Xlib:  extension "Generic Event Extension" missing on display ":0.0".
> Xlib:  extension "Generic Event Extension" missing on display ":0.0".
> Xlib:  extension "Generic Event Extension" missing on display ":0.0".
> Xlib:  extension "Generic Event Extension" missing on display ":0.0".
> Xlib:  extension "Generic Event Extension" missing on display ":0.0".
> Xlib:  extension "Generic Event Extension" missing on display ":0.0".

This is harmless, it indicates that libXext has support for generic
events, but the server does not yet.

robert.

> 
> 
> The garbage still pollutes my windows periodically, so, I guess, my
> next xorg-server will be 1.4.
> 
> For reference, my system is:
> 
>i386 FreeBSD 7.1-STABLE Sun Jan 25 06:28:38 EST 2009
> 
> It not being CURRENT, I took the liberty of cc: freebsd-po...@freebsd.org.
> 
> -- Alex -- alex-goncha...@comcast.net --
> ___
> freebsd-po...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
-- 
Robert Noland 
FreeBSD


signature.asc
Description: This is a digitally signed message part

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[Alex Goncharov]

,--- You/O. (Fri, 30 Jan 2009 23:19:41 +0100) *
| After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4
| and having done hurting recompiling nearly everything/package twice now
| firefox3 still doesn't work properly and hits me when starting with this
| error message:
| 
| Xlib:  extension "Generic Event Extension" missing on display ":0.0".

Interesting -- I just did my comprehensive upgrade, as a part of which
xorg-server went from 1.5.3_1,1 to 1.5.3_2,1.

And this is what I see now, for the first time, and consistently:


$ xterm&
[3] 12585

$ emacs &   
[4] 12644
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".


The garbage still pollutes my windows periodically, so, I guess, my
next xorg-server will be 1.4.

For reference, my system is:

   i386 FreeBSD 7.1-STABLE Sun Jan 25 06:28:38 EST 2009

It not being CURRENT, I took the liberty of cc: freebsd-po...@freebsd.org.

-- Alex -- alex-goncha...@comcast.net --
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[Mel]

On Friday 30 January 2009 13:19:41 O. Hartmann wrote:
> After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4
> and having done hurting recompiling nearly everything/package twice now
> firefox3 still doesn't work properly and hits me when starting with this
> error message:
>
> Xlib:  extension "Generic Event Extension" missing on display ":0.0".
>
> Then firefox3 freezes forever, showing something like the background or
> pixel remnants of windows/picograms moving over its window.

http://lists.freedesktop.org/archives/xorg/2008-October/039134.html

-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[Daniel Eischen]

On Fri, 30 Jan 2009, O. Hartmann wrote:


After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4
and having done hurting recompiling nearly everything/package twice now
firefox3 still doesn't work properly and hits me when starting with this
error message:

Xlib:  extension "Generic Event Extension" missing on display ":0.0".

Then firefox3 freezes forever, showing something like the background or
pixel remnants of windows/picograms moving over its window.

I recompiled three times libxcb and its dependencies, two times
Xlib/Xserver/xf86-input-* to be sure having compiled everything and then
I recompiled everything again what's necessary to build Firefox3. No
effect. I now recompile everything needed to build Xlib to get rid of
the above shown error message because I suspect this causing my firefox3
not working.

On another box, also amd64, but FreeBSD 7.1-STABLE (SMP) I had to do the
same procedure and firefox3 is working properly. Bot boxes do have ATI
graphics (driver radeon).

I also tried deleting my personal .mozille directory and started firefox
from scratch. But after some download-save-requester opened (when trying
to download a file from a location in the web) firefox freezes also
eating up 100% cpu. In all cases Firefox3 can be killed.

Any help is appreciated.


Perhaps it's a little overkill, but what I usually do when I
perform upgrades like this, is to move /usr/local out of the
way (along with /var/db/pkg), and remove any X/KDE/QT stuff
in /tmp, /var/.., etc.  Then I install (portupdate -NR) everything
from scratch.  If something goes wrong, I just have to move the
original /usr/local back until I work out the problems.

--
DE
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".

[O. Hartmann]

After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4
and having done hurting recompiling nearly everything/package twice now
firefox3 still doesn't work properly and hits me when starting with this
error message:

Xlib:  extension "Generic Event Extension" missing on display ":0.0".

Then firefox3 freezes forever, showing something like the background or
pixel remnants of windows/picograms moving over its window.

I recompiled three times libxcb and its dependencies, two times
Xlib/Xserver/xf86-input-* to be sure having compiled everything and then
I recompiled everything again what's necessary to build Firefox3. No
effect. I now recompile everything needed to build Xlib to get rid of
the above shown error message because I suspect this causing my firefox3
not working.

On another box, also amd64, but FreeBSD 7.1-STABLE (SMP) I had to do the
same procedure and firefox3 is working properly. Bot boxes do have ATI
graphics (driver radeon).

I also tried deleting my personal .mozille directory and started firefox
from scratch. But after some download-save-requester opened (when trying
to download a file from a location in the web) firefox freezes also
eating up 100% cpu. In all cases Firefox3 can be killed.

Any help is appreciated.

Oliver

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"