For testing Midori against Wayland, I use "./configure --enable-gtk3 --disable-unique". But at present there hasn't been a WebkitGTK+ release that has proper wayland support. I've been using GTK3 master and the webkit patch from <https://bugs.webkit.org/show_bug.cgi?id=81456>, rebased against WebkitGTK+ 2.0.0; some weeks ago I asked #webkitgtk+ IRC what the status of that bug was and didn't hear anything, but I haven't had time to look into it since. They may be waiting on subsurfaces so that Webkit2 (which does out-of-process rendering) can be supported more easily.
So technically nothing has changed recently from Midori's perspective; we're still just waiting on released versions of dependencies to lose their internal Xlib calls. On 26 de abril de 2013 at 3:56 AM, "Chang Liu" <[email protected]> wrote: > >Sorry I CC'ed wayland-devel-request. I have to resend the mail. > >I tried this morning. Midori crashed on start. Both midori and >libunique are latest git version. > >Backtrace: >Launching command: '/usr/bin/gdb' --batch -ex 'set print thread- >events >off' -ex run -ex 'set logging on /run/user/1000/midori/gdb.bt' -ex >'bt' --return-child-result --args midori >[Thread debugging using libthread_db enabled] >Using host libthread_db library "/usr/lib/libthread_db.so.1". > >Program received signal SIGSEGV, Segmentation fault. >slowly_and_stupidly_obtain_ >timestamp (display=display@entry=0x71a060) >at ./uniqueapp.c:129 >129 xwindow = XCreateWindow (xdisplay, RootWindow (xdisplay, >0), >#0 slowly_and_stupidly_obtain_timestamp >(display=display@entry=0x71a060) at ./uniqueapp.c:129 >#1 0x00007ffff73870b8 in set_startup_id (startup_id=<optimized >out>, >backend=0x71b4c0) at ./uniqueapp.c:198 >#2 unique_app_set_property (gobject=0x7142d0, prop_id=<optimized >out>, value=0x7fffffffdd60, pspec=0x78bcf0) at ./uniqueapp.c:300 >#3 0x00007ffff7ba10d2 in ?? () from /usr/lib/libgobject-2.0.so.0 >#4 0x00007ffff73870f8 in unique_app_constructor (gtype=7863568, >n_params=3, params=0x77fd80) at ./uniqueapp.c:271 >#5 0x00007ffff7ba2509 in g_object_newv () from >/usr/lib/libgobject-2.0.so.0 >#6 0x00007ffff7ba2cd6 in g_object_new_valist () from >/usr/lib/libgobject-2.0.so.0 >#7 0x00007ffff7ba3044 in g_object_new () from /usr/lib/libgobject- >2.0.so.0 >#8 0x000000000042ccfc in midori_app_instance_is_running () >#9 0x000000000043ffa5 in midori_normal_app_new () >#10 0x000000000042924c in main () > >Looks like libunique still has reference to Xlib functions. Or am I >doing things wrong? (Is there a build-time switch for libunique to >change this?) > > >2013/4/25 <[email protected]>: >> >> I just noticed the bug for preliminary wayland support was just >closed. I >> haven't tried it. >> >> http://twotoasts.de/index.php/midori/ >> http://en.wikipedia.org/wiki/Midori_%28web_browser%29 >> Bug: https://bugs.launchpad.net/midori/+bug/975355 >> >> It's based on WebKitGTK+, so maybe that should work now as well? >> >> ----- Forwarded message ----- >> >> Date: Thu, 25 Apr 2013 22:16:49 -0000 >> Subject: [Bug 975355] Re: Preliminary Wayland support >> >> ** Summary changed: >> >> - Wayland support >> + Preliminary Wayland support >> >> ** Changed in: midori >> Status: In Progress => Fix Released >> >> ** Changed in: midori >> Importance: Undecided => Low >> >> -- >> You received this bug notification because you are subscribed to >the bug >> report. >> https://bugs.launchpad.net/bugs/975355 >> >> Title: >> Preliminary Wayland support >> >> Status in Midori: Webkit Web browser: >> Fix Released >> >> Bug description: >> To work with wayland, gdk_x11_ calls and Xlib calls need to be >wrapped >> in build-time and run-time backend checks: >> http://developer.gnome.org/gtk3/3.3/ch24s02.html#id1502079 >> >> $ grep -r gdk_x11 . >> ./midori/sokoke.c: Atom save_mode_atom = >gdk_x11_get_xatom_by_name_for_display ( >> ./midori/midori-browser.c: >gdk_x11_xatom_to_atom (XA_INTEGER), >> >> $ grep -r Xlib . >> ./midori/main.c: #include <X11/Xlib.h> >> >> http://wayland.freedesktop.org/gtk.html >> >> The wayland backend in GTK+ 3.4 works, so as soon as these are >done >> midori should be usable with wayland. >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/midori/+bug/975355/+subscriptions >> >> >> ----- End forwarded message ----- >> >> -- >> "Will I ever learn? I hope not, I'm having too much fun." >> - Brent "Minime" Avis, motorcycle.com >> http://www.ChaosReigns.com >> _______________________________________________ >> wayland-devel mailing list >> [email protected] >> http://lists.freedesktop.org/mailman/listinfo/wayland-devel >_______________________________________________ >wayland-devel mailing list >[email protected] >http://lists.freedesktop.org/mailman/listinfo/wayland-devel _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
