UI freeze when doing import from 'Music' folder on first run

Bug #1268197 reported by Phil Wyett
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
Expired
Undecided
Unassigned
rhythmbox (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

UI freeze when doing import from 'Music' folder on first run.

See attached screenshot.

The importing progress bar just stops mid run and requires the app to be restarted to clear.

The status bar is correct that all 185 tracks have been imported.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rhythmbox 3.0.1-1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7
Uname: Linux 3.13.0-2-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Jan 11 20:28:10 2014
InstallationDate: Installed on 2014-01-11 (0 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140110)
SourcePackage: rhythmbox
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Phil Wyett (aura-yoda) wrote :
Revision history for this message
Ville Ranki (ville-ranki) wrote :

I think i can confirm this. I'm updating a large collection mounted on a sftp share. Importing
progresses quite long, but after a while (1 hour or so ) ui becomes unresponsive. This happens every time.

Here's a backtrace of the issue. The cause may also be in libgio.

(gdb) bt full
#0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
No locals.
#1 0x00007f6319380192 in _L_lock_1142 () from /lib/x86_64-linux-gnu/libpthread.so.0
No symbol table info available.
#2 0x00007f6319380110 in __GI___pthread_mutex_lock (mutex=0x1e62af0)
    at pthread_mutex_lock.c:104
        max_cnt = -1
        __PRETTY_FUNCTION__ = "__pthread_mutex_lock"
        type = 4294966784
#3 0x00007f631961b3a1 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x00007f63142a73a0 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
No symbol table info available.
#5 0x00007f63142a7986 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
No symbol table info available.
#6 0x00007f63198a9074 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#7 0x00007f63198ab294 in g_object_new_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#8 0x00007f63198ab674 in g_object_new ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#9 0x00007f6319ecd243 in ?? () from /usr/lib/librhythmbox-core.so.7
No symbol table info available.
#10 0x00007f6319ecd2fd in ?? () from /usr/lib/librhythmbox-core.so.7
No symbol table info available.
#11 0x00007f6319eef56d in ?? () from /usr/lib/librhythmbox-core.so.7
No symbol table info available.
#12 0x00007f63195db3b6 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#13 0x00007f63195db708 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#14 0x00007f63195db7ac in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#15 0x00007f6314257a8c in g_application_run ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
No symbol table info available.
#16 0x00007f6319e55e82 in rb_application_run () from /usr/lib/librhythmbox-core.so.7
No symbol table info available.
#17 0x0000000000400d22 in main ()
No symbol table info available.

Revision history for this message
Ville Ranki (ville-ranki) wrote :

And btw i'm running Ubuntu Saucy and rhythmbox version is 2.99.1-0ubuntu.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in rhythmbox (Ubuntu):
status: New → Confirmed
tags: added: saucy
Revision history for this message
Javier López (javier-lopez) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report.

This will greatly help a developer to track down your problem.

The attached backtrace even when could refer to the same problem has no symbols and therefore cannot be used for a developer to discover what failed and how to create a fix.

Changed in rhythmbox (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Ville Ranki (ville-ranki) wrote :

Here's a stack trace of the situation. UI is completely frozen.

Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue using a maintained version of Ubuntu please let us know otherwise this report can be left to expire in approximately 60 days time.

Paul White
[Ubuntu Bug Squad]

Changed in ubuntu-gnome:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu GNOME because there has been no activity for 60 days.]

Changed in ubuntu-gnome:
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]

Changed in rhythmbox (Ubuntu):
status: Incomplete → Expired
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.