Announcement

Collapse
No announcement yet.

X.Org Applications On Wayland Are Working

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    Originally posted by Obscene_CNN View Post
    Of course this does nothing to to fix the problem of people writing wayland native apps that you can't run remotely.
    Which presumes that is actually a problem, and isn't already being fixed.

    Comment


    • #12
      Originally posted by ChrisXY View Post
      in the wayland-terminal the letters e,z,s,j,y, etc. cannot be typed. At this point I couldn't test further keys because something got changed so everything got remapped, for example a mapped to enter or something.
      this was a bug in libxkbcommon, which is now fixed.

      Comment


      • #13
        Originally posted by daniels View Post
        this was a bug in libxkbcommon, which is now fixed.
        Thanks, I don't always remember updating it too.

        After updating everything weston-desktop-shell keeps dieing like
        Code:
        [18:07:50.233] weston-desktop-shell died, respawning...
        read error from connection 0x981e80: Connection reset by peer (104)
        [18:07:50.410] libwayland: disconnect from client 0x980220
        [18:07:50.410] weston-desktop-shell died, respawning..
        as soon as I move the mouse in wayland in x and in a tty.

        I believe this is a (probably too incomplete) backtrace of the desktop shell I got in gdb when running a weston-terminal and moving the mouse in wayland which made the weston-terminal crash.
        Code:
        Program received signal SIGSEGV, Segmentation fault.
        0x00007fffef4e34ff in ?? () from /usr/lib/weston/desktop-shell.so
        (gdb) bt
        #0  0x00007fffef4e34ff in ?? () from /usr/lib/weston/desktop-shell.so
        #1  0x00007fffef4e35b8 in ?? () from /usr/lib/weston/desktop-shell.so
        #2  0x00007ffff6b71553 in ?? () from /usr/lib/libwayland-server.so.0
        #3  0x00007ffff6b71c5b in wl_event_loop_dispatch () from /usr/lib/libwayland-server.so.0
        #4  0x00007ffff6b6fe3d in wl_display_run () from /usr/lib/libwayland-server.so.0
        #5  0x00000000004062d8 in ?? ()
        #6  0x00007ffff408e455 in __libc_start_main () from /lib/libc.so.6
        #7  0x00000000004063b9 in _start ()
        Is it still buggy? I'd say yes.

        edit: luckily wayland is small enaugh:
        weston-desktop-shell crash:
        Code:
        Program received signal SIGSEGV, Segmentation fault.
        0x00007fffef4e34ff in set_busy_cursor (shsurf=shsurf@entry=0x97b250, pointer=0x7c75c0) at shell.c:860
        860             shell->busy_surface->output = sprite->output;
        (gdb) bt
        #0  0x00007fffef4e34ff in set_busy_cursor (shsurf=shsurf@entry=0x97b250, pointer=0x7c75c0) at shell.c:860
        #1  0x00007fffef4e35b8 in ping_timeout_handler (data=0x97b250) at shell.c:899
        #2  0x00007ffff6b71553 in wl_event_source_timer_dispatch (source=0x8f82a0, ep=<optimized out>) at event-loop.c:173
        #3  0x00007ffff6b71c5b in wl_event_loop_dispatch (loop=0x6169a0, timeout=timeout@entry=-1) at event-loop.c:410
        #4  0x00007ffff6b6fe3d in wl_display_run (display=display@entry=0x616950) at wayland-server.c:1027
        #5  0x00000000004062d8 in main (argc=1, argv=0x7fffffffdb48) at compositor.c:3426
        weston-terminal crash:
        Code:
        Program received signal SIGSEGV, Segmentation fault.
        pointer_surface_frame_callback (data=0x61d510, callback=<optimized out>, time=<optimized out>) at window.c:2342
        2342            if (cursor->image_count == 1)
        (gdb) bt
        #0  pointer_surface_frame_callback (data=0x61d510, callback=<optimized out>, time=<optimized out>) at window.c:2342
        #1  0x00007ffff495ee48 in ffi_call_unix64 () from /usr/lib/libffi.so.6
        #2  0x00007ffff495e850 in ffi_call () from /usr/lib/libffi.so.6
        #3  0x00007ffff4b6744f in wl_closure_invoke (closure=closure@entry=0x6b63f0, target=target@entry=0x65ff20, func=<optimized out>, data=0x61d510) at connection.c:773
        #4  0x00007ffff4b65be2 in handle_event (size=24, opcode=<optimized out>, id=<optimized out>, display=0x6189d0) at wayland-client.c:495
        #5  wl_display_iterate (display=0x6189d0, mask=<optimized out>) at wayland-client.c:528
        #6  0x000000000040ddf7 in display_run (display=display@entry=0x6188b0) at window.c:3669
        #7  0x0000000000404faf in main (argc=<optimized out>, argv=<optimized out>) at terminal.c:2405
        Last edited by ChrisXY; 06-15-2012, 12:24 PM.

        Comment


        • #14
          Originally posted by smitty3268 View Post
          Which presumes that is actually a problem, and isn't already being fixed.
          If it wasn't a problem then why are people trying to fix it?

          Comment


          • #15
            Originally posted by Obscene_CNN View Post
            If it wasn't a problem then why are people trying to fix it?
            It's only a problem if people are actually creating Wayland-only apps before it gets fixed.

            The point is, it will be fixed soon, and for the forseeable future no one is going to stop their apps from running over X anyway. Why would you want to artificially limit your app to only work on brand-new linux distros, and fail on all the BSD's, etc. It's not a problem because no one will do that.

            Apps that gain Wayland support will still fallback to X when necessary.

            Comment


            • #16
              [quote]Why would you want to artificially limit your app to only work on brand-new linux distros, and fail on all the BSD's, etc. It's not a problem because no one will do that.[/quote[

              You sir, have clearly not heard about Lennart.

              Comment


              • #17
                Originally posted by smitty3268 View Post
                It's only a problem if people are actually creating Wayland-only apps before it gets fixed.
                Hey, maybe X gets "fixed" before wayland is at a point where it doesn't break all the time.


                I'm just a little bit sarcstic because people think wayland is nearly ready to take over from X. I do think it's an important and awesome project but let's face it: Unless mature software like X.org, the linux kernel or mesa where you can use git builds with hardly any problem ever wayland and weston are constantly in a state where it's not working for end users. I'm just amazed the developers themselves sometimes get it to a demo-able state where they can make videos of new features.

                So you people who worry about it not being feature complete: It doesn't matter because apart from tech demos you won't use it in the near future anyway. You won't run or need xwayland because wayland and weston first need to be stable...

                Comment

                Working...
                X