After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 706470 - No files are imported
No files are imported
Status: RESOLVED FIXED
Product: rhythmbox
Classification: Other
Component: Importing
2.99.x
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
: 708002 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-08-21 08:30 UTC by Peter
Modified: 2013-09-13 20:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
rhythmbox.png (64.01 KB, image/png)
2013-08-22 18:54 UTC, Peter
Details
rhythmbox --debug output (236.11 KB, text/plain)
2013-08-22 18:54 UTC, Peter
Details
list of files in /media/music (9.63 KB, application/octet-stream)
2013-08-22 18:54 UTC, Peter
Details

Description Peter 2013-08-21 08:30:34 UTC
Hi, I have an .mp3 files in /media/music, and every time I'm trying to import it nothing is imported. Rhythmbox-2.99.1 shows small progress that never finishes and zero tracks is imported. I've started rhythmbox with --debug (see attachment) but I don't see anything relevant there. 

Gstreamer plays fine music:
 $ gst-launch-1.0 filesrc location= "/media/music/Deva Premal/2002 - Embrace/01 Deva Premal – Om Tare Tuttare.mp3" ! mad ! alsasinkt
 $ gst-typefind-1.0 './Deva Premal/2002 - Embrace/01 Deva Premal – Om Tare Tuttare.mp3'./Deva Premal/2002 - Embrace/01 Deva Premal – Om Tare Tuttare.mp3 - application/x-id3

Please, help me to understand what's going on here. TIA.
Comment 1 Jonathan Matthew 2013-08-21 09:49:43 UTC
So, what happens here is you select /media/music/ using the file browser button, and nothing appears in the track list? How many files are there in /media/music? How many of them are already in your library?

(In reply to comment #0)
> I've started rhythmbox with --debug (see attachment) but I don't see anything relevant there. 

you didn't attach anything.
Comment 2 Peter 2013-08-22 18:54:06 UTC
Created attachment 252784 [details]
rhythmbox.png

Sorry, looks like attachment somehow was lost. So you could better understood situation here is a screenshot of what I see - everything looks like "hang of import process". I can press buttons, select other dirs with music, but nothing is imported.
Comment 3 Peter 2013-08-22 18:54:26 UTC
Created attachment 252785 [details]
rhythmbox --debug output
Comment 4 Peter 2013-08-22 18:54:49 UTC
Created attachment 252786 [details]
list of files in /media/music
Comment 5 Peter 2013-08-22 18:56:46 UTC
Reopening as attachment are in place now.
Comment 6 Jonathan Matthew 2013-08-22 23:03:32 UTC
Looks like the dbus connection to the metadata service isn't working. A couple of things you could do to investigate:

Build rhythmbox from source, use the test program built as metadata/test-metadata to try reading a few files. './test-metadata --debug /path/to/file.mp3' should produce some useful output.

export G_DBUS_DEBUG=transport,message (and LANG=C while we're at it) and run rhythmbox --debug again.
Comment 7 Yanko Kaneti 2013-09-10 16:06:36 UTC
I am having the same problem here on rawhide.
What seems to be failing is the getSaveableTypes call when done from rhythmbox, it just times-out

..
(18:55:53) [0x2426ca0] [start_metadata_service] rb-metadata-dbus-client.c:308: Metadata process 24587 started
(18:55:53) [0x1433e60] [new_connection_cb] rb-metadata-dbus-service.c:229: new connection to metadata service
========================================================================
GDBus-debug:Transport:
  >>>> WROTE 176 bytes of message with serial 1 and
       size 176 from offset 0 on a GSocketOutputStream
========================================================================
GDBus-debug:Message:
  >>>> SENT D-Bus message (176 bytes)
  Type:    method-call
  Flags:   none
  Version: 0
  Serial:  1
  Headers:
    path -> objectpath '/org/gnome/Rhythmbox3/MetadataService'
    interface -> 'org.gnome.Rhythmbox3.Metadata'
    member -> 'getSaveableTypes'
    destination -> 'org.gnome.Rhythmbox3.Metadata'
  Body: ()
  UNIX File Descriptors:
    (none)
(18:56:08) [0x1433e60] [electromagnetic_shotgun] rb-metadata-dbus-service.c:176: shutting down (1378828568s idle)
(18:56:08) [0x2426ca0] [start_metadata_service] rb-metadata-dbus-client.c:327: saveable type query failed: The connection is closed
...


The same call but from test-metadata succeeds
...
(18:56:45) [0x1be0e00] [start_metadata_service] rb-metadata-dbus-client.c:308: Metadata process 24676 started
========================================================================
GDBus-debug:Transport:
  >>>> WROTE 176 bytes of message with serial 1 and
       size 176 from offset 0 on a GSocketOutputStream
========================================================================
GDBus-debug:Message:
  >>>> SENT D-Bus message (176 bytes)
  Type:    method-call
  Flags:   none
  Version: 0
  Serial:  1
  Headers:
    path -> objectpath '/org/gnome/Rhythmbox3/MetadataService'
    interface -> 'org.gnome.Rhythmbox3.Metadata'
    member -> 'getSaveableTypes'
    destination -> 'org.gnome.Rhythmbox3.Metadata'
  Body: ()
  UNIX File Descriptors:
    (none)
(18:56:45) [0x23cee60] [new_connection_cb] rb-metadata-dbus-service.c:229: new connection to metadata service
(18:56:45) [0x23cee60] [handle_method_call] rb-metadata-dbus-service.c:193: handling metadata service message: org.gnome.Rhythmbox3.Metadata.getSaveableTypes
========================================================================
GDBus-debug:Transport:
  <<<< READ 16 bytes of message with serial 1 and
       size 105 to offset 0 from a GSocketInputStream
========================================================================
GDBus-debug:Transport:
  <<<< READ 89 bytes of message with serial 1 and
       size 105 to offset 16 from a GSocketInputStream
========================================================================
GDBus-debug:Message:
  <<<< RECEIVED D-Bus message (105 bytes)
  Type:    method-return
  Flags:   no-reply-expected
  Version: 0
  Serial:  1
  Headers:
    reply-serial -> uint32 1
    signature -> signature 'as'
  Body: (['audio/x-vorbis', 'audio/x-aac', 'audio/mpeg', 'audio/x-flac'],)
  UNIX File Descriptors:
    (none)
(18:56:45) [0x1be0e00] [start_metadata_service] rb-metadata-dbus-client.c:334: saveable types from metadata helper: audio/x-vorbis, audio/x-aac, audio/mpeg, audio/x-flac
....

What gives?
Comment 8 Yanko Kaneti 2013-09-10 21:30:51 UTC
Did some more digging.
Don't know if this makes any sense but it seems here I can reliably avoid the bug by building rhythmbox _without_ the default Fedora -fstack-protector-strong

CFLAGS="`echo $RPM_OPT_FLAGS | sed -e 's/-fstack-protector-strong//'`"
before %configure
Comment 9 Elad Alfassa 2013-09-10 22:05:50 UTC
Found a FESCO ticket explaining fedora's move to fstack-protector-strong in F20, https://fedorahosted.org/fesco/ticket/1128

We have two possible courses of action here: 
1) removing fstack-protector-strong from the fedora package and closing this bug as NOTGNOME
2) Finding why having this option causes rhythmbox to fail
Comment 10 Jonathan Matthew 2013-09-13 02:46:24 UTC
*** Bug 708002 has been marked as a duplicate of this bug. ***
Comment 11 Dhiru Kholia 2013-09-13 09:36:58 UTC
(In reply to comment #9)
> We have two possible courses of action here: 
> 1) removing fstack-protector-strong from the fedora package and closing this
> bug as NOTGNOME
> 2) Finding why having this option causes rhythmbox to fail

"-fstack-protector-strong" has already found multiple REAL bugs in applications.

e.g. https://bugzilla.gnome.org/show_bug.cgi?id=703991

So, for now at least, I will "vote" for option 2.
Comment 12 Jonathan Matthew 2013-09-13 12:23:40 UTC
fixed in commit 76540fd

it was just a missing return value from a signal handler.
Comment 13 Kalev Lember 2013-09-13 13:14:40 UTC
Thanks, I've backported this to Fedora rhythmbox-3.0-2.fc20 package as well.
Comment 14 Peter 2013-09-13 20:11:10 UTC
Finally it works for me! Thank you, guys.