When filing a bug report, you need to provide as much relevant detail as you possibly can. In this case, you should explain at least how you installed wayland/weston and what you did to get this error message.

Since desktop-shell protocol is a special case, not just anything can bind to it. In fact, the compositor only allows the instance of desktop-shell that it initiated to bind. This means that you cannot start desktop-shell manually, you must let the compositor start it.

Thanks for your reply.
I'm very sorry to the shore description 
1.weston,wayland build complete
2.the example of weston run ok
3.when weston server running,
desktop-shell is runned

4.when I'want to run the desktop-shell client under weston client ,
error message is printed

[3586982.176] wl_display@1.global(1, "wl_display", 1)
[3586982.276] wl_display@1.global(2, "wl_compositor", 1)
[3586982.312]  -> wl_display@1.bind(2, "wl_compositor", 1, new id 2)
[3586982.345] wl_display@1.global(3, "wl_shm", 1)
[3586982.381]  -> wl_display@1.bind(3, "wl_shm", 1, new id 3)
[3586982.437] wl_display@1.global(4, "wl_drm", 1)
[3586982.629] wl_display@1.global(5, "screenshooter", 1)
[3586982.668] wl_display@1.global(6, "wl_data_device_manager", 1)
[3586982.705]  -> wl_display@1.bind(6, "wl_data_device_manager", 1, new id 4)
[3586982.739] wl_display@1.global(7, "wl_output", 1)
[3586982.775]  -> wl_display@1.bind(7, "wl_output", 1, new id 5)
[3586982.826] wl_display@1.global(8, "wl_input_device", 1)
[3586982.856]  -> wl_display@1.bind(8, "wl_input_device", 1, new id 6)
[3586982.894]  -> wl_data_device_manager@4.get_data_device(new id 7, wl_input_device@6)
[3586982.916] wl_display@1.global(9, "wl_shell", 1)
[3586982.944]  -> wl_display@1.bind(9, "wl_shell", 1, new id 8)
[3586982.976] wl_display@1.global(10, "desktop_shell", 1)
[3586983.003] wl_display@1.global(11, "screensaver", 1)
[3586983.968]  -> wl_display@1.bind(4, "wl_drm", 1, new id 9)
[3586984.052]  -> wl_display@1.sync(new id 10)
[3586984.695] wl_output@5.geometry(0, 0, 1024, 640, 0, "(null)", "(null)")
[3586984.752] wl_output@5.mode(3, 1024, 640, 60)
[3586984.783] wl_drm@9.device("/dev/dri/card0")
[3586984.872]  -> wl_drm@9.authenticate(152)
[3586984.892] wl_drm@9.format(875713089)
[3586984.908] wl_drm@9.format(875713112)
[3586984.923] wl_callback@10.done(0)
[3586984.945] wl_display@1.delete_id(10)
[3586984.963]  -> wl_display@1.sync(new id 10)
[3586986.923] wl_drm@9.authenticated()
[3586986.947] wl_callback@10.done(0)
[3586986.964] wl_display@1.delete_id(10)
[3587063.757]  -> wl_drm@9.create_buffer(new id 10, 1769497248, 32, 32, 128, 875713089)
[3587067.164]  -> wl_drm@9.create_buffer(new id 11, 1662543360, 32, 32, 128, 875713089)
[3587068.626]  -> wl_drm@9.create_buffer(new id 12, 421027840, 32, 32, 128, 875713089)
[3587069.578]  -> wl_drm@9.create_buffer(new id 13, 278422656, 32, 32, 128, 875713089)
[3587070.445]  -> wl_drm@9.create_buffer(new id 14, 1774287040, 32, 32, 128, 875713089)
[3587071.582]  -> wl_drm@9.create_buffer(new id 15, 1082226688, 32, 32, 128, 875713089)
[3587073.097]  -> wl_drm@9.create_buffer(new id 16, 975272800, 32, 32, 128, 875713089)
[3587073.940]  -> wl_drm@9.create_buffer(new id 17, 939621504, 32, 32, 128, 875713089)
[3587075.007]  -> wl_drm@9.create_buffer(new id 18, 241543456, 32, 32, 128, 875713089)
[3587075.819]  -> wl_drm@9.create_buffer(new id 19, 790998624, 32, 32, 128, 875713089)
[3587076.704]  -> wl_drm@9.create_buffer(new id 20, 98938272, 32, 32, 128, 875713089)
[3587078.498]  -> wl_drm@9.create_buffer(new id 21, 1748498912, 32, 32, 128, 875713089)
[3587153.440]  -> wl_display@1.bind(7, "wl_output", 1, new id 22)
[3587153.466]  -> wl_display@1.bind(10, "desktop_shell", 1, new id 23)
fopen path /home/tte/.config/weston-desktop-shell.ini
fgets path /home/tte/.config/weston-desktop-shell.ini
display_run start
[3587153.984] wl_display@1.error(desktop_shell@23, 0, "permission to bind desktop_shell denied")
desktop_shell@23: error 0: permission to bind desktop_shell denied



(In reply to comment #1)
> When filing a bug report, you need to provide as much relevant detail as you
> possibly can. In this case, you should explain at least how you installed
> wayland/weston and what you did to get this error message.

Since
> desktop-shell protocol is a special case, not just anything can bind to it.
> In fact, the compositor only allows the instance of desktop-shell that it
> initiated to bind. This means that you cannot start desktop-shell manually,
> you must let the compositor start it.

(In reply to comment #2)
> Thanks for your reply.
> I'm very sorry to the shore description 
> 1.weston,wayland build complete

Is there a reason you're using 0.85 instead of wayland/weston git master?

> 2.the example of weston run ok
> 3.when weston server running,
> desktop-shell is runned
> 
> 4.when I'want to run the desktop-shell client under weston client ,
> error message is printed

Desktop shell is the client that draws the panel and background surfaces. It doesn't make sense to start a new instance of desktop-shell. Perhaps what you want to do is run weston nested? (i.e. run weston in weston as a wayland client)

(In reply to comment #2)
> 3.when weston server running,
> desktop-shell is runned
> 
> 4.when I'want to run the desktop-shell client under weston client ,
> error message is printed

That's intended behavior, not a bug.  desktop-shell is launched automatically by weston, and you're not allowed to run it manually:
http://lists.freedesktop.org/archives/wayland-devel/2011-November/001541.html

Please do not close bugs where other people are actively conversing. Thanks.