rhythmbox won't start, loop over [rb_audioscrobbler_should_handshake]

Bug #547121 reported by Boris MARECHAL
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: rhythmbox

Rhytmbox process start, don't crash but no window opens...

In debug (rhythmbox -d) I can see in loop:

(18:58:00) [0x9506028] [rb_audioscrobbler_should_handshake] rb-audioscrobbler.c:758: No username set
(18:58:15) [0x9506028] [rb_audioscrobbler_should_handshake] rb-audioscrobbler.c:758: No username set
(18:58:30) [0x9506028] [rb_audioscrobbler_should_handshake] rb-audioscrobbler.c:758: No username set
(18:58:45) [0x9506028] [rb_audioscrobbler_should_handshake] rb-audioscrobbler.c:758: No username set
(18:58:46) [0x9506028] [rhythmdb_read_enter] rhythmdb.c:1223: counter: 1
(18:58:46) [0x9506028] [rhythmdb_read_enter] rhythmdb.c:1223: counter: 2
(18:58:46) [0xa231bf0] [query_thread_main] rhythmdb.c:4098: entering query thread
(18:58:46) [0xa231bf0] [rhythmdb_query_internal] rhythmdb.c:4075: doing query
(18:58:46) [0xa231bf0] [do_query_recurse] rhythmdb-tree.c:2243: doing recursive query, 1 conjunctions
(18:58:46) [0xa262948] [query_thread_main] rhythmdb.c:4098: entering query thread
(18:58:46) [0xa262948] [rhythmdb_query_internal] rhythmdb.c:4075: doing query
(18:58:46) [0xa262948] [do_query_recurse] rhythmdb-tree.c:2243: doing recursive query, 1 conjunctions
(18:58:46) [0xa231bf0] [rhythmdb_query_model_add_results] rhythmdb-query-model.c:2023: adding 0 entries
(18:58:46) [0xa231bf0] [rhythmdb_query_internal] rhythmdb.c:4081: completed
(18:58:46) [0x9506028] [idle_process_update] rhythmdb-query-model.c:1065: inserting 0 rows
(18:58:46) [0x9506028] [rhythmdb_process_one_event] rhythmdb.c:2637: processing RHYTHMDB_EVENT_QUERY_COMPLETE
(18:58:46) [0x9506028] [rhythmdb_read_leave] rhythmdb.c:1237: counter: 1
(18:58:46) [0x9506028] [rhythmdb_process_one_event] rhythmdb.c:2630: processing RHYTHMDB_EVENT_THREAD_EXITED
(18:58:46) [0xa262948] [rhythmdb_query_model_add_results] rhythmdb-query-model.c:2023: adding 0 entries
(18:58:46) [0xa262948] [rhythmdb_query_internal] rhythmdb.c:4081: completed
(18:58:46) [0x9506028] [idle_process_update] rhythmdb-query-model.c:1065: inserting 0 rows
(18:58:46) [0x9506028] [rhythmdb_process_one_event] rhythmdb.c:2637: processing RHYTHMDB_EVENT_QUERY_COMPLETE
(18:58:46) [0x9506028] [rhythmdb_read_leave] rhythmdb.c:1237: counter: 0
(18:58:46) [0x9506028] [rhythmdb_process_one_event] rhythmdb.c:2630: processing RHYTHMDB_EVENT_THREAD_EXITED
(18:59:00) [0x9506028] [rb_audioscrobbler_should_handshake] rb-audioscrobbler.c:758: No username set
(18:59:15) [0x9506028] [rb_audioscrobbler_should_handshake] rb-audioscrobbler.c:758: No username set
(18:59:30) [0x9506028] [rb_audioscrobbler_should_handshake] rb-audioscrobbler.c:758: No username set
(18:59:45) [0x9506028] [rb_audioscrobbler_should_handshake] rb-audioscrobbler.c:758: No username set

ProblemType: Bug
Architecture: i386
Date: Thu Mar 25 19:06:16 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: fglrx
Package: rhythmbox 0.12.5-0ubuntu5.2
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_FR.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic-pae
SourcePackage: rhythmbox
Uname: Linux 2.6.31-20-generic-pae i686

Revision history for this message
Boris MARECHAL (boris-marechal) wrote :
Revision history for this message
Boris MARECHAL (boris-marechal) wrote :

Sorry for the noise, I'm a litle dump...

That's just config, rhythmbox is only in systray (got this strange config after a crappy exit ?)

Note that's really not user friendly to start an application just in systray... Perhaps add a notification ?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

the start minimized is a known issue, thanks for reporting.

Changed in rhythmbox (Ubuntu):
importance: Undecided → Low
status: New → Invalid
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.