marionnet-dev team mailing list archive

[Gianluca Guidi <gminded@xxxxxxxxx>]

I actually found out that the problem is solved by resetting nautilus configuration, so I guess that marionnet is not to blame.
Sorry, I really believed that it was a bug.

** Changed in: marionnet
       Status: New => Invalid

-- 
You received this bug notification because you are a member of
marionnet-dev, which is subscribed to marionnet.
https://bugs.launchpad.net/bugs/1320692

Title:
  Can't create new project

Status in Marionnet - A virtual network laboratory:
  Invalid

Bug description:
  When I click Project > New the file manager opens up as expected, but after typing the project name and clicking OK, nothing happens.
  I tried with nautilus and thunar file managers, but the effect is the same: nothing happens when the confirmation button is pressed.
  This is the complete output:

  =======================================================
   Welcome to marionnet
   Version              : 0.90.6
   Source revision      : 318 - 2011-02-02 19:27:57 +0100
   Ocamlbricks revision : 229 - 2010-11-23 10:55:39 +0100

   Built in date 2014-04-06 15:57:25 +0200 on system:
   
          Linux 3.2.0-4-amd64 #1 SMP Debian
          3.2.54-2 x86_64 GNU/Linux
   
   For bug reporting, please get a launchpad account and
   either:
    - report bugs at https://bugs.launchpad.net/marionnet
   or do *all* the following:
    - add yourself to the marionnet-dev team
    - add yourself to the marionnet-dev mailing list
    - write to marionnet-dev@xxxxxxxxxxxxxxxxxxx
  =======================================================

  (marionnet:9174): Gtk-WARNING **: Unable to locate theme engine in
  module_path: "pixmap",

  (marionnet:9174): Gtk-WARNING **: Unable to locate theme engine in
  module_path: "pixmap",

  (marionnet:9174): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
  [0]: Menu entry with label "New" selected by user
  [0]: --- Dialog result: NOTHING TO DO (CANCELED)
  [0]: Menu entry with label "Quit" selected by user
  [0]: --- Dialog result:
  answer = no
  ------------------
  [0]: is_there_something_on_or_sleeping: no
  [0]: Killing the death monitor thread...
  [0]: Stopping the infinite polling loop (locked).
  [0]: If the program hangs at this point then you are probably using the
  [0]: locked version within a callback. See the comment in death_monitor.ml .
  [0]: destroy_process_before_quitting: BEGIN
  [0]: destroy_process_before_quitting: END (success)
  [0]: Main thread: quit has been scheduled.
  [8]: task_runner: Executing the task "close_project_sync"
  [8]: state#close_project_sync: starting...
  [8]: state#close_project_sync: no project opened.
  [8]: state#close_project_sync: done.
  [8]: task_runner: The task "close_project_sync" succeeded.
  [8]: task_runner: I'm ready for the next task...
  [8]: task_runner: Executing the task "quit"
  [8]: Starting the last job...
  [8]: destroy_process_before_quitting: BEGIN
  [8]: destroy_process_before_quitting: END (success)
  [8]: Killing the blinker thread...
  [8]: Sending the message "please-die" to the blinker thread...
  [8]:   Ok.
  [8]: Ok, the blinker thread has exited now.
  [7]: Warning: can't understand the message ''
  [8]: Ok, the blinker thread was killed.
  [8]: Synced.
  [8]: state#quit: done.
  [8]: task_runner: The task "quit" succeeded.
  [8]: task_runner: I'm ready for the next task...

  After a few tries I canceled the dialog and closed the process, of
  course.

To manage notifications about this bug go to:
https://bugs.launchpad.net/marionnet/+bug/1320692/+subscriptions