Le vendredi 28 septembre 2012 à 15:18 +0000, FFADO a écrit :
#362: ffado-dbus-server crashes when launching ffado-mixer
----------------------------+-----------------------------------------------
   Reporter:  andreeecz     |       Owner:  arnonym          
       Type:  bug           |      Status:  new              
   Priority:  major         |   Milestone:  FFADO 2.x        
  Component:  ffado-mixer   |     Version:  FFADO SVN (trunk)
 Resolution:                |    Keywords:                   
Device_name:  SaffirePro40  |  
----------------------------+-----------------------------------------------
Comment (by andreeecz):

 I have caught the bull by the horns!


 {{{
 Thread 1 (Thread 0xb74d4700 (LWP 4188)):
 #0  0xb7fdd424 in __kernel_vsyscall ()
 #1  0xb76165df in raise () from /usr/lib/libc.so.6
 #2  0xb7617ec3 in abort () from /usr/lib/libc.so.6
 #3  0xb7c45f35 in ?? () from /usr/lib/libdbus-1.so.3
 #4  0xb7c3b271 in ?? () from /usr/lib/libdbus-1.so.3
 #5  0xb7c2ba74 in dbus_message_iter_append_basic () from
 /usr/lib/libdbus-1.so.3
 #6  0xb7c7623b in ?? () from /usr/lib/libdbus-c++-1.so.0
 #7  0xb7c766af in DBus::MessageIter::append_string(char const*) ()
 ---Type <return> to continue, or q <return> to quit---
    from /usr/lib/libdbus-c++-1.so.0
 #8  0x08057813 in operator<< (iter=..., val=
 "SaffirePro40arry\267l$\r\b@\355\372\267l$\r\btR\357\377\277\350\061\b\b\002\310\361\267N\310\361\267\063")
 at /usr/include/dbus-c++-1/dbus-c++/types.h:382
 #9  0x0805b450 in
 org::ffado::Control::Element::Text_adaptor::_getValue_stub (this=
     0x80b1240, call=...) at support/dbus/controlserver-glue.h:929
 #10 0x08069c73 in
 DBus::Callback<org::ffado::Control::Element::Text_adaptor, DBus::Message,
 DBus::CallMessage const&>::call (this=0x80b1150, param=...)
     at /usr/include/dbus-c++-1/dbus-c++/util.h:283
 #11 0xb7c87ff4 in ?? () from /usr/lib/libdbus-c++-1.so.0
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
 }}}

 This is a gdb output on ffado-dbus-server crash. From here, it is pretty
 clear whats happening: Former name of the device was
 <something>ScarryBarry, which can be seen from the leftovers in the call.
 I have set the nickname to SaffirePro40. Now ffado doesnt seem to be able
 to handle this, as the nickname clearly contains lots of non-utf stuff! :)

Strange, since getnickname (at least for Focusrite) returns no more than 16 characters; and ffado-dbus-server effectively returns a 16 characters nickname (your previous report). Which way did you use to change the nickname at first ?

Phil

--
Philippe Carriere <la-page-web-of-phil.contact@orange.fr>