Jump to content
ElementaryOS France

Voodoonice

Membres
 View Profile  See their activity

  • Posts

    40

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Posts posted by Voodoonice

    Crash Midori

    in Un problème ?

    Posted

    Bonsoir à tous;

     

    Je rencontre un problème assez bizarre avec Midori depuis quelques semaines, c'est d'autant plus étrange qu'il n’apparaît que sur ma session. Lorsque je lance Midori il crash immédiatement. J'ai tenté de le lancé avec le terminal et voici ce qu'il sort 

     

     

    emmanuel@Voodoonux:~$ midori

     
    ** (midori:2321): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-DlB1fzSvVf: Connexion refusée
     
    (midori4:2321): Gtk-CRITICAL **: gtk_action_set_action_group: assertion 'action_group == NULL' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    ** (midori4:2321): CRITICAL **: midori_view_get_display_uri: assertion 'MIDORI_IS_VIEW (view)' failed
     
    (midori4:2321): Gdk-ERROR **: The program 'midori4' received an X Window System error.
    This probably reflects a bug in the program.
    The error was 'BadAlloc (insufficient resources for operation)'.
      (Details: serial 646 error_code 11 request_code 53 (core protocol) minor_code 0)
      (Note to programmers: normally, X errors are reported asynchronously;
       that is, you will receive the error a while after causing it.
       To debug your program, run it with the GDK_SYNCHRONIZE environment
       variable to change this behavior. You can then get a meaningful
       backtrace from your debugger if you break on the gdk_x_error() function.)
    Trappe pour point d'arrêt et de trace (core dumped)
    emmanuel@Voodoonux:~$ 
     

     

    Je suis allez fouillé dans /tmp mais aucune trace de dbus-DlB1fzSvVf  :unsure:  :blink:  :wacko:

     

    Merci d'avance pour votre aide  ;)

    Joyeux anniversaire Linux

    in Le bar des amis

    Posted

    Et oui, il y a 24 ans Linus Torvalds annocé la naissance de Linux par mail  :wub: 

    Le message d'origine est archivé ici

     

     

    Path: gmdzi!unido!fauern!ira.uka.de!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!wupost!uunet!mcsun!news.funet.fi!hydra!klaava!torvalds

    From: torv...@klaava.Helsinki.FI (Linus Benedict Torvalds)
    Newsgroups: comp.os.minix
    Subject: What would you like to see most in minix?
    Summary: small poll for my new operating system
    Keywords: 386, preferences
    Message-ID: <1991Aug25.205708.9541@klaava.Helsinki.FI>
    Date: 25 Aug 91 20:57:08 GMT
    Organization: University of Helsinki
    Lines: 20


    Hello everybody out there using minix -

    I'm doing a (free) operating system (just a hobby, won't be big and
    professional like gnu) for 386(486) AT clones. This has been brewing
    since april, and is starting to get ready. I'd like any feedback on
    things people like/dislike in minix, as my OS resembles it somewhat
    (same physical layout of the file-system (due to practical reasons)
    among other things).

    I've currently ported bash(1.08) and gcc(1.40), and things seem to work.
    This implies that I'll get something practical within a few months, and
    I'd like to know what features most people would want. Any suggestions
    are welcome, but I won't promise I'll implement them :-)

            Linus (torv...@kruuna.helsinki.fi)

    PS. Yes - it's free of any minix code, and it has a multi-threaded fs.
    It is NOT protable (uses 386 task switching etc), and it probably never
    will support anything other than AT-harddisks, as that's all I have :-(.
     

     

×
×
  • Create New...