RE: rygel-0.4.2 will not start
- From: John Frankish <j-frankish slb com>
- To: GNOME UPnP/DLNA services <rygel-list gnome org>
- Subject: RE: rygel-0.4.2 will not start
- Date: Tue, 20 Oct 2009 09:04:41 +0200
Thanks - see below
-----Original Message-----
From: rygel-list-bounces gnome org [mailto:rygel-list-bounces gnome org] On Behalf Of Jens Georg
Sent: Monday, 19 October, 2009 16:25
To: GNOME UPnP/DLNA services
Subject: RE: rygel-0.4.2 will not start
Wow. Tinycore is a nasty distribution to do development on...
Not really - you start from a very small, well-known base. You are very sure what you add and so you avoid the maze of inter-related dependencies common to most large distros...
> $ gdb rygel
> GNU gdb 6.8
> ...
> This GDB was configured as "i686-pc-linux-gnu"...
> (gdb) run
> Starting program: /usr/local/bin/rygel
> [Thread debugging using libthread_db enabled]
> [New Thread 0xb78656f0 (LWP 2888)]
> [New Thread 0xb7859b90 (LWP 2893)]
> ** (rygel:2888): DEBUG: rygel-main.vala:110: new network context lo (127.0.0.1) available.
> ** (rygel:2888): DEBUG: rygel-main.vala:110: new network context eth0 (163.183.3.38) available.
> [Thread 0xb7859b90 (LWP 2893) exited]
> ^C
> Program received signal SIGINT, Interrupt.
> [Switching to Thread 0xb78656f0 (LWP 2888)]
> 0xb7fb2430 in __kernel_vsyscall ()
This is rygel idling because it cannot find its plugins. I found that
the solution is to install shared-mime-info-locales (which depends on
shared-mime-info, maybe this is enough). If you then run into the
problem of
So, rygel installs its own plug-ins and then cannot find them :) I added shared-mime-info and shared-mime-info-locales and this problem disappeared.
undefined symbol: gee_abstract_map_remove, find the two places in the
media-export plugin source C files and replace remove with unset.
I patched gee_abstract_map_remove -> gee_abstract_map_unset in:
rygel-0.4.2/src/plugins/media-export/rygel-media-export-recursive-file-monitor.c
rygel-0.4.2/src/plugins/media-export/rygel-media-export-root-container.c
..but then I got this:
$ gdb rygel
GNU gdb 6.8
...
(gdb) run
Starting program: /usr/local/bin/rygel
[Thread debugging using libthread_db enabled]
[New Thread 0xb77ae6f0 (LWP 12287)]
[New Thread 0xb77a2b90 (LWP 12292)]
** (rygel:12287): DEBUG: rygel-main.vala:110: new network context lo (127.0.0.1) available.
** (rygel:12287): DEBUG: rygel-main.vala:110: new network context eth0 (163.183.3.38) available.
** (rygel:12287): DEBUG: rygel-plugin-loader.vala:168: Loaded module source: '/usr/local/lib/rygel-1.0/librygel-external.so'
** (rygel:12287): DEBUG: rygel-plugin-loader.vala:59: New plugin 'MediaExport' available
** (rygel:12287): DEBUG: rygel-root-device-factory.vala:218: No icon provided by MediaExport.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb77ae6f0 (LWP 12287)]
0xb7827fcb in strlen () from /lib/libc.so.6
(gdb) t a a bt
Thread 2 (Thread 0xb77a2b90 (LWP 12292)):
#0 0xb7efb430 in __kernel_vsyscall ()
#1 0xb7918282 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2 0xb7db1f97 in g_cond_timed_wait_posix_impl () from /usr/local/lib/libgthread-2.0.so.0
#3 0xb799b3c1 in g_async_queue_pop_intern_unlocked () from /usr/local/lib/libglib-2.0.so.0
#4 0xb79eaf72 in g_thread_pool_thread_proxy () from /usr/local/lib/libglib-2.0.so.0
#5 0xb79e925f in g_thread_create_proxy () from /usr/local/lib/libglib-2.0.so.0
#6 0xb7913863 in start_thread () from /lib/libpthread.so.0
Thread 1 (Thread 0xb77ae6f0 (LWP 12287)):
#0 0xb7827fcb in strlen () from /lib/libc.so.6
#1 0xb79d4aa8 in match_info_new () from /usr/local/lib/libglib-2.0.so.0
#2 0xb79d611a in g_regex_match_full () from /usr/local/lib/libglib-2.0.so.0
#3 0xb79d6ab8 in g_regex_match_simple () from /usr/local/lib/libglib-2.0.so.0
#4 0xb7ec6264 in ?? () from /usr/local/lib/libgssdp-1.0.so.2
#5 0xb7ec7f92 in ?? () from /usr/local/lib/libgss
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]