rygel crashed with SIGSEGV in rygel_media_export_media_cache_get_object_from_statement()

Bug #1162279 reported by Sebastian Wendowski
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
rygel (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Wanted to stream videofile, but got a crach.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: rygel 0.18.0-1
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Sat Mar 30 17:59:02 2013
ExecutablePath: /usr/bin/rygel
InstallationDate: Installed on 2013-03-05 (25 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130301)
MarkForUpload: True
ProcCmdline: /usr/bin/rygel
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f7fbdb52d96: mov %rax,0x48(%r13)
 PC (0x7f7fbdb52d96) ok
 source "%rax" ok
 destination "0x48(%r13)" (0x00000048) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: rygel
StacktraceTop:
 ?? () from /usr/lib/rygel-2.0/plugins/librygel-media-export.so
 rygel_media_export_media_cache_get_children () from /usr/lib/rygel-2.0/plugins/librygel-media-export.so
 ?? () from /usr/lib/rygel-2.0/plugins/librygel-media-export.so
 ?? () from /usr/lib/librygel-server-2.0.so.1
 ?? () from /usr/lib/librygel-server-2.0.so.1
Title: rygel crashed with SIGSEGV in rygel_media_export_media_cache_get_children()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Sebastian Wendowski (sebwen-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 rygel_media_export_media_cache_get_object_from_statement (self=self@entry=0x172fa00, parent=parent@entry=0x1c0a8e0, statement=0x196ac78) at rygel-media-export-media-cache.c:3896
 rygel_media_export_media_cache_get_children (self=0x172fa00, container=0x1c0a8e0, sort_criteria=<optimized out>, offset=<optimized out>, max_count=<optimized out>, error=error@entry=0x1c14070) at rygel-media-export-media-cache.c:1475
 rygel_media_export_db_container_real_get_children_co (_data_=0x1c14000) at rygel-media-export-db-container.c:388
 rygel_media_export_db_container_real_get_children (base=<optimized out>, offset=0, max_count=1, sort_criteria=0x1d0b3f0 "+upnp:class,+dc:title", cancellable=0x7f7fb00014f0, _callback_=0x7f7fc82ced20 <rygel_browse_handle_children_request_ready>, _user_data_=0x1c10080) at rygel-media-export-db-container.c:358
 rygel_browse_handle_children_request_co (_data_=0x1c10080) at rygel-browse.c:699

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in rygel (Ubuntu):
importance: Undecided → Medium
summary: rygel crashed with SIGSEGV in
- rygel_media_export_media_cache_get_children()
+ rygel_media_export_media_cache_get_object_from_statement()
tags: removed: need-amd64-retrace
information type: Private → Private Security
information type: Private Security → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in rygel (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in rygel (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.