I’ve been playing around with this one for awhile now. Two or three times I have installed and re-installed Banshee but I keep getting the same results. It tries to start and after about 30 seconds or so it just stops trying to launch. I went into the repositories to see if there were any other files I may need for it to work on my system, but no luck there. I get no error codes and no notifications that I am missing any kind of file or plug-ins. Anyone got an idea? :\
On 01/26/2012 01:56 PM, roguehorse wrote:
>
> I’ve been playing around with this one for awhile now. Two or three
> times I have installed and re-installed Banshee but I keep getting the
> same results. It tries to start and after about 30 seconds or so it just
> stops trying to launch. I went into the repositories to see if there
> were any other files I may need for it to work on my system, but no luck
> there. I get no error codes and no notifications that I am missing any
> kind of file or plug-ins. Anyone got an idea? :\
If you are trying to launch it from the GUI, you get very little in the way of
diagnostics. Open a terminal and start it from there. That way you will find
what shared library is missing. From the terminal, the full path is
/usr/bin/banshee.
FWIW, it works fine on my 64-bit KDE system.
Thank you,
I will try this then get back to you.
I tried Banshee again this morning from terminal and it came back with the following error:
[Info 06:43:54.397] Running Banshee 2.2.1: [openSUSE 12.1 (linux-gnu, x86_64) @ 2011-11-23 16:24:41 UTC]
[Warn 06:43:54.613] Cannot connect to NetworkManager or Wicd - An available, working network connection will be assumed
The program ‘Banshee’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadAccess (attempt to access private resource denied)’.
(Details: serial 466 error_code 10 request_code 152 minor_code 1)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
On 01/27/2012 09:16 AM, roguehorse wrote:
>
> I tried Banshee again this morning from terminal and it came back with
> the following error:
>
> [Info 06:43:54.397] Running Banshee 2.2.1: [openSUSE 12.1 (linux-gnu,
> x86_64) @ 2011-11-23 16:24:41 UTC]
> [Warn 06:43:54.613] Cannot connect to NetworkManager or Wicd - An
> available, working network connection will be assumed
> The program ‘Banshee’ received an X Window System error.
> This probably reflects a bug in the program.
> The error was ‘BadAccess (attempt to access private resource denied)’.
> (Details: serial 466 error_code 10 request_code 152 minor_code 1)
> (Note to programmers: normally, X errors are reported asynchronously;
> that is, you will receive the error a while after causing it.
> To debug your program, run it with the --sync command line
> option to change this behavior. You can then get a meaningful
> backtrace from your debugger if you break on the gdk_x_error()
> function.)
The network warning can be ignored.
On the off chance that something in your user configuration is causing the
problem, create a new user using YaST, and log in as that user. If the problem
persists, you need to file a bug report and list the above info as some part of
X in your system has been corrupted. I doubt that anyone reading this list knows
what it is, or how to find it.
Ok, Thanks!
I’ll post results after.
Well I finally got around to creating that guest user profile and pretty much got the same results from both ways of trying to initialize Banshee, desktop and terminal
user@linux-aaws:~> banshee
[Info 21:43:35.325] Running Banshee 2.2.1: [openSUSE 12.1 (linux-gnu, x86_64) @ 2012-01-18 17:02:47 UTC]
[Warn 21:43:35.539] Cannot connect to NetworkManager or Wicd - An available, working network connection will be assumed
The program ‘Banshee’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadAccess (attempt to access private resource denied)’.
(Details: serial 466 error_code 10 request_code 152 minor_code 1)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
user@linux-aaws:~>
Hi,
You have to change the GTK widget style. Go to System Settings>Common Appearance and Behavior> Application Appearance> Gtk Styles and Fonts> Use style (and select which style suits you, the Ubuntu guys suggested Raleigh, but see what works for you). A restart might be needed for the settings to take effect.
Cool thanks, I’ll try that now and report back.
YOU ROCK!! That was the fix!
Can we go a step further and ask why this change was necessary to initialize Banshee? receiving the answer is always nice, but understanding why is even more fun.
It is supposed to be a KDE bug - a function which should handle the appearance of programs like Banshee, based on GTK, does not get along well with them, so you get the error 
That is a bug on gtk-oxygen which is responsible to make GTK+ applications look like the Oxygen. It’s not a problem with Banshee, it’s a Feature of KDE