Version-Release number of selected component: dleyna-renderer-0.4.0-3.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/dleyna-renderer-service crash_function: gupnp_context_manager_manage_control_point executable: /usr/libexec/dleyna-renderer-service kernel: 3.17.1-302.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gupnp_context_manager_manage_control_point at gupnp-context-manager.c:647 #1 prv_on_context_available at upnp.c:359 #5 g_signal_emit_by_name at gsignal.c:3405 #6 create_context_for_device at gupnp-network-manager.c:265 #7 on_device_activated at gupnp-network-manager.c:336 #8 use_new_device at gupnp-network-manager.c:404 #9 device_proxy_new_cb at gupnp-network-manager.c:485 #10 g_simple_async_result_complete at gsimpleasyncresult.c:763 #11 complete_in_idle_cb at gsimpleasyncresult.c:775 #16 dleyna_main_loop_start at libdleyna/core/main-loop.c:155 Potential duplicate: bug 1083856
Created attachment 948661 [details] File: backtrace
Created attachment 948662 [details] File: cgroup
Created attachment 948663 [details] File: core_backtrace
Created attachment 948664 [details] File: dso_list
Created attachment 948665 [details] File: environ
Created attachment 948666 [details] File: exploitable
Created attachment 948667 [details] File: limits
Created attachment 948668 [details] File: maps
Created attachment 948669 [details] File: open_fds
Created attachment 948670 [details] File: proc_pid_status
Created attachment 948671 [details] File: var_log_messages
I'm experiencing this bug every day. I'd also like to note that it's in the top ten on the list of bugs on the ABRT retrace server.
Same here, every day bug. Hardware : Dell E6530 * PCI devices (lspci): 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) 00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 (rev c4) 00:1c.5 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 6 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation QM77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04) 01:00.0 VGA compatible controller: NVIDIA Corporation GF108GLM [NVS 5200M] (rev ff) 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34) 0c:00.0 SD Host controller: O2 Micro, Inc. OZ600FJ0/OZ900FJ0/OZ600FJS SD/MMC Card Reader Controller (rev 05) * USB devices (lsusb): Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 0c45:643f Microdia Dell Integrated HD Webcam Bus 001 Device 004: ID 413c:8197 Dell Computer Corp. Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Debarshi, is there any information that we can provide that would make this easier to track down?
(In reply to Stephen Gallagher from comment #14) > Debarshi, is there any information that we can provide that would make this > easier to track down? I don't think I need any further info. I have encountered dleyna-renderer crashes on my system, so I think I should be able to reproduce it. It is just a matter of me working through my pile of bugs. I will get to these dleyna-renderer crashes tomorrow and hope to have a fix by next week.
*** Bug 1102408 has been marked as a duplicate of this bug. ***
*** Bug 1083856 has been marked as a duplicate of this bug. ***
These are all crashes caused by a client immediately exiting after spawning dleyna-renderer. One way to reproduce that is to spawn the service using something like this, when you have a DLNA Renderer on your network (eg., a TV or a GNOME computer): $ gdbus call \ --session \ --dest com.intel.dleyna-renderer \ --object-path /com/intel/dLeynaRenderer \ --method com.intel.dLeynaRenderer.Manager.Release This generally occurs in Fedora when a user has gnome-photos installed and tries to search for something from gnome-shell's overview. This triggers gnome-photos' search provider which in turn spawns dleyna-renderer and immediately exits. I sent a few fixes upstream: https://lists.01.org/pipermail/dleyna/2015-January/thread.html Ideally, we should also fix gnome-photos to not poke dleyna-renderer when the search provider is being used.
*** Bug 1140871 has been marked as a duplicate of this bug. ***
*** Bug 1150223 has been marked as a duplicate of this bug. ***
*** Bug 1154330 has been marked as a duplicate of this bug. ***
*** Bug 1182117 has been marked as a duplicate of this bug. ***
*** Bug 1144774 has been marked as a duplicate of this bug. ***
dleyna-renderer-0.4.0-4.fc21,dleyna-connector-dbus-0.2.0-4.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/dleyna-renderer-0.4.0-4.fc21,dleyna-connector-dbus-0.2.0-4.fc21
Package dleyna-renderer-0.4.0-4.fc21, dleyna-connector-dbus-0.2.0-4.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dleyna-renderer-0.4.0-4.fc21 dleyna-connector-dbus-0.2.0-4.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-1011/dleyna-renderer-0.4.0-4.fc21,dleyna-connector-dbus-0.2.0-4.fc21 then log in and leave karma (feedback).
dleyna-renderer-0.4.0-4.fc21, dleyna-connector-dbus-0.2.0-4.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
This issue still occurs with 0.4.0.4.fc21.x86_64 , just ABRT now refers to this existing report: https://bugzilla.redhat.com/show_bug.cgi?id=1154330 instead of submitting stuff.