Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#556276: Gnome Nautilus and Panel error when attempting to register with bonobo on gnome startup

17 views
Skip to first unread message

Manish Mohania

unread,
Nov 15, 2009, 3:30:02 AM11/15/09
to
Package: gnome
Version: 1:2.22.2~5

When I login to GNOME, I get this error :

1) Nautilus

Package: nautilus
Version: 2.20.0-7

Error:
Nautilus can't be used now, due to an unexpected error.

Details:
Nautilus can't be used now, due to an unexpected error from Bonobo
when attempting to register the file manager view server

2) Panel

Package: gnome-panel
Version: 2.20.3-5

Error:
The panel has encountered a fatal error.
The panel could not register with the bonobo-activation server (error
code: 3) and will exit.
It may be automatically restarted.

My system was working fine till I shutdown/restarted my system and
tried to login to GNOME. The only thing that I did before logging
out/shutdown was to connect to ftp site using :

Places -> Connect to Server

menu option in nautilus.

After I connect to server, an icon with connection name as label
appeared on my desktop. I didnot unmount the connection before logging
out.

I am a complete novice and I do not know if this is the real issue.

I am not able to use GNOME due to these 2 errors. please, help me get
my good system back to working state :-) . Also, please let me know if
you need to know anything else.

Thanks and Regards

Manish Mohania

System Information - Output of "uname -a"

Linux debian 2.6.26-2-686 #1 SMP Wed Nov 4 20:45:37 UTC 2009 i686 GNU/Linux

Debian Lenny/stable - 5.0.3

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Josselin Mouette

unread,
Nov 16, 2009, 4:50:02 AM11/16/09
to
Le dimanche 15 novembre 2009 à 13:41 +0530, Manish Mohania a écrit :
> Nautilus can't be used now, due to an unexpected error from Bonobo
> when attempting to register the file manager view server
>
> The panel has encountered a fatal error.
> The panel could not register with the bonobo-activation server (error
> code: 3) and will exit.
> It may be automatically restarted.

What if you kill any bonobo-activation-server that might be left on your
system?

Also, are there any relevant errors in ~/.xsession-errors ?

Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling

signature.asc

Manish Mohania

unread,
Nov 16, 2009, 10:20:02 AM11/16/09
to
Thank you, for addressing my problem.

Here is what I did as per your suggestion.

When I run the following command from terminal (CTRL + ALT + F1) :

ps aux | grep bonobo

I do not see any process with name bonobo-ativation-server.

Also, when I do :

killall bonobo-activation-server

It gives the following output :

bonobo-activation-server: no process killed

I do not understand what bonobo-activation-server is, but I have read
the man page. I think it is some important application :(

There as no errors in ~/.xsession-errors but two warnings. I am
providing the contents of ~/.xsession-errors:

------- File: ~/.xsession-errors ---------

/etc/gdm/Xsession: Beginning session setup...
SESSION_MANAGER=local/debian:/tmp/.ICE-unix/2902

** (gnome-settings-daemon:2960): WARNING **: Failed to open file
'/etc/gnome/config/General.ad': No such file or directory
Window manager warning: Failed to read saved session file
/home/manish/.metacity/sessions/default0.ms: Failed to open file
'/home/manish/.metacity/sessions/default0.ms': No such file or
directory

--------- End File: ~/.xsession-errors -------------

As far as I believe my gnome is running since, I can see the
background and I am able to run application from terminal (CTRL + ALT
+ F1) as :

iceweasel --display=:0.0
gedit --display=:0.0

This problem is very unpredictable, today I was able to login two
times in my gnome with these steps.

1. First I rebooted in single user mode.
2. After login as root, I run the "init 5" command.
3. Then, I login as normal user "manish" from graphical display.

But when I rebooted in single user mode again, I was not able to login
using above mentioned steps :(

Also,
1) sometimes when I boot my system, I get the following error:

RAMDISK: incomplete write (-28 != 32768) 8388608
crc error
Kernel Panic - not syncing: VFS : Unable to mount root fs on unknown-block (0)

2) sometimes I get this error:

Probing EDD (edd=off to disable)
Decompressing Linux .... ok
crc error

Do you think I should file a seperate bug report for this error. ??

Thank you for your patience and time to read this bug report.

Regards

Manish Mohania

2009/11/16 Josselin Mouette <jo...@debian.org>:


> What if you kill any bonobo-activation-server that might be left on your
> system?
>
> Also, are there any relevant errors in ~/.xsession-errors ?
>

--

Josselin Mouette

unread,
Nov 16, 2009, 10:50:02 AM11/16/09
to
Le lundi 16 novembre 2009 à 20:31 +0530, Manish Mohania a écrit :
> 1) sometimes when I boot my system, I get the following error:
>
> RAMDISK: incomplete write (-28 != 32768) 8388608
> crc error
> Kernel Panic - not syncing: VFS : Unable to mount root fs on unknown-block (0)
>
> 2) sometimes I get this error:
>
> Probing EDD (edd=off to disable)
> Decompressing Linux .... ok
> crc error
>
> Do you think I should file a seperate bug report for this error. ??

This is a hardware issue. You should test your RAM with the memtest86
program.

It is very likely that the issues you are experiencing are caused by
that.

signature.asc

Manish Mohania

unread,
Nov 16, 2009, 11:10:02 AM11/16/09
to
Thanks again, for a quick reply and suggestion ..

Ok ... Let me check it with memtest86. I will also try to check it
with a new/different RAM, if I can arrange one.

Will get back to you soon ... :-)

Regards

Manish Mohania

2009/11/16 Josselin Mouette <jo...@debian.org>:

--

Manish Mohania

unread,
Nov 18, 2009, 6:00:01 AM11/18/09
to
Hi,

As per your suggestions:

I have run memtest86+ on my system, and I did not find any errors through it.

I also tested it through a new RAM, but I am having the same error:

Decompressing Linux ..
crc error
System halted

Let me know what do you suggest ?

Can it be a hardisk problem ? I have run e2fsck on my hard disk -
/dev/sda1 and I did not find any errors.

Right now I am running my system using gNewSense Live CD. It is
running fine. I am mailing you using gmail through this Live CD.

Thanks & Regards

Manish Mohania

0 new messages