touch-packages team mailing list archive

[Thomas Hellström <1370386@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When starting up a mir 7 client on vmware (Ubuntu 14.04) it hangs in the
following location:

    at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
185	../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such file or directory.
(gdb) bt
#0  pthread_cond_wait@@GLIBC_2.3.2 ()
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007ffff679266c in std::condition_variable::wait(std::unique_lock<std::mutex>&) ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#2  0x00007ffff7b92e9b in MirWaitHandle::wait_for_all() ()
   from /usr/lib/x86_64-linux-gnu/libmirclient.so.7
#3  0x0000000000401027 in demo_client ()
#4  0x0000000000400e97 in main ()

(This is mir_demo_client_basic from the mir_demos package)

The mir_demo_standalone_* applications seem to work fine, and the
mir_demo_server_* applications seem to be running nicely with a visible
mouse cursor.

This also happens with XMir, which is the most annoying part.

It appears to be a regression, since I'm sure I had this running on an
earlier update snapshot of Ubuntu 14.04

Thanks,
Thomas

** Affects: mir (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1370386

Title:
  libmirclient7 hang on client startup

Status in “mir” package in Ubuntu:
  New

Bug description:
  When starting up a mir 7 client on vmware (Ubuntu 14.04) it hangs in
  the following location:

      at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  185	../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such file or directory.
  (gdb) bt
  #0  pthread_cond_wait@@GLIBC_2.3.2 ()
      at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x00007ffff679266c in std::condition_variable::wait(std::unique_lock<std::mutex>&) ()
     from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #2  0x00007ffff7b92e9b in MirWaitHandle::wait_for_all() ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.7
  #3  0x0000000000401027 in demo_client ()
  #4  0x0000000000400e97 in main ()

  (This is mir_demo_client_basic from the mir_demos package)

  The mir_demo_standalone_* applications seem to work fine, and the
  mir_demo_server_* applications seem to be running nicely with a
  visible mouse cursor.

  This also happens with XMir, which is the most annoying part.

  It appears to be a regression, since I'm sure I had this running on an
  earlier update snapshot of Ubuntu 14.04

  Thanks,
  Thomas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1370386/+subscriptions