Banshee freezes on start trying to look for network share on previous network

Bug #512994 reported by Kory Hauser on 2010-01-26
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: banshee

I use my laptop at work (Ubuntu 9.10) and Banshee (1.5.1-1) detects one of my boss' daughter's network share. It doesn't connect to the share. I shut the computer down and will connect to a different network elsewhere. When I start up Banshee again, it freezes and the process needs to be killed manually. This only ever happens after I've been on that network with the share.

On Wednesday 27,January,2010 06:03 AM, Kory Hauser wrote:
> Public bug reported:
>
> Binary package hint: banshee
>
> I use my laptop at work (Ubuntu 9.10) and Banshee (1.5.1-1) detects one
> of my boss' daughter's network share. It doesn't connect to the share. I
> shut the computer down and will connect to a different network
> elsewhere. When I start up Banshee again, it freezes and the process
> needs to be killed manually. This only ever happens after I've been on
> that network with the share.
>
> ** Affects: banshee (Ubuntu)
> Importance: Undecided
> Status: New
>
Could you post the output of `banshee --debug`? And when it hangs try running
`killall -SIGQUIT banshee-1` in a different terminal. It should dump a
stacktrace to the `banshee --debug` output which should be useful for debugging.

--
Kind regards,
Chow Loong Jin (GPG: 0x8F02A411)
Ubuntu Contributing Developer

Vish (vish) wrote :

Any news on this bug?
Could you provide the information as requested on comment #1?

Changed in banshee (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Jeff (jdorenbush) wrote :

I think I'm having the same or a similar problem, and I think the problem might lie within the user's privileges.

When running "banshee --debug" I caught it hanging at the following:

[1 Debug 23:10:38.735] Delayed Initializating Banshee.Daap.DaapService
[3 Warn 23:10:38.741] Failed to load media-player-info file for
** (Banshee:7925): CRITICAL **: itdb_get_control_dir: assertion `mountpoint' failed
[4 Debug 23:10:38.909] DAAP Proxy listening for connections on port 8089

After having to force quit Banshee, I decided, out of pure curiosity, to try and run "sudo banshee --debug" -- Banshee started up just fine.

Jeff (jdorenbush) wrote :

After removing the DAAP service I determined there were other services causing it to hang. Through process of elimination I determined the services causing my lock ups were:
/usr/lib/banshee-1/Extensions/Banshee.Daap.dll
/usr/lib/banshee-1/Extensions/Banshee.Dap.dll
/usr/lib/banshee-1/Extensions/Banshee.Podcasting.dll

After removing them the problem stopped.

matze (matzex) wrote :

The bug also affects me.
When I start banshee in the terminal, the following error occures:

[Warn [...]] Failed to load media-player-info file for
 ** (Banshee: [...]): CRITICAL **: itdb_get_control_dir: assertion `mountpoint' failed #

After this I deactivate the daap support and delete the
Banshee.Daap.dll Banshee.Dap.dll Banshee.Podcasting.dll
data, like Jeff above me wrote.
So, banshee is running!
But I need the Pdcasting support in Banshee, which I can't use at the moment.

This bug can be a duplicate of Bug #646482, but there they wrote about media device support, which doesn't affect this here.
See: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/646482

I user Banshee 1.7.6 on Ubuntu 10.10!

Launchpad Janitor (janitor) wrote :

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

Changed in banshee (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers