New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #32886 (closed defect: invalid)

Opened 16 months ago

Last modified 16 months ago

[zenity] [@2.32.1_2] causing X11 to crash on Leopard

Reported by: medintux@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc: devans@…, suv-sf@…
Port: zenity

Description

On Leopard, launching zenity (for instance zenity --info --text "test") causes an X11 crash.

Process: X11.bin
Version: 2.1.6
Build info: X11server-480700-2
OS Version: Mac OS X 10.5.8 (9L31a)
Exception Type: EXC_BAD_ACCESS (SIGBUS)
X.Org X Server 1.4.2-apple33 Build Date: 20090226

With same DISPLAY environment /usr/bin/X11/xterm is working fine, as well as port abclock @1.0d_2.

Change History

comment:1 Changed 16 months ago by medintux@…

  • Cc medintux@… added

Cc Me!

comment:2 Changed 16 months ago by medintux@…

Sorry for inconvenience : solved by reinstalling X11-2.6.3.dmg from xquartz.macosforge.org

Problem was coming from an Xcode upgrade (RTFM ;-)

comment:3 Changed 16 months ago by ryandesign@…

  • Status changed from new to closed
  • Cc devans@… added; medintux@… removed
  • Resolution set to invalid
  • Port set to zenity

comment:4 Changed 16 months ago by suv-sf@…

AFAIU this crash is due to having xcb fully enabled in cairo 1.10.2 in MacPorts (note: the xcb-backend and xlib over xcb is not considered stable in cairo yet (on the roadmap for cairo 1.12) and is not enabled by default. Yet in the cairo port it was not added as variant but is now enabled by default and cannot be turned off by a variant (e.g. -x11_xcb). The result of this cairo configuration is that e.g. GTK+ apps compiled with a current MacPorts tree can no longer be run with the default X11 version installed on Leopard (no xcb support in X11 2.1.6 - this was only added in later Xquartz releases ≥ 2.5.1).

Related:
#23483 (awesome dependency cairo-xcb)
#31869 (X (gtk2 using?) ports crash OS X 10.5.8 X11.bin)

Another side-effect of enabling this unstable feature (xlib over xcb) in the stable cairo port (1.10.2) are rendering errors (text overflowing the container, missing or incorrect gradient shadings/highlights e.g. for buttons and scrollbars when using gtk theme engines like clearlooks and murrine).

comment:5 Changed 16 months ago by suv-sf@…

  • Cc suv-sf@… added

Cc Me!

Note: See TracTickets for help on using tickets.