gnome-panel killed

Thank you for your bug. Do you have any error if you run it from a command line?

Yes, it had problems with the gnome-session. I've tried to run sessions properties.. it "thinks" a bit then nothing!
$ sudo gnome-session-properties
could not connect to the session manager

Tried reinstalling gnome-sessions gnome-panel and gnome-core, didn't help. I assume it is a problem of beryl-manager, as it's one of the unstable applications I have.

I've formatted the / root partition today, removed with --purge the above named packages and reinstalled them, and I must say it hasn't helped either. I'm on failsafe right now, trying to figure out what's wrong.

It was gnome-session! This is the /home/forger/.gnome2/session:
[Default]
0,id=117f000101000117528882300000076030000
0,RestartStyleHint=1
0,Program=update-notifier
0,CurrentDirectory=/home/forger
0,CloneCommand=update-notifier
0,RestartCommand=update-notifier --sm-client-id 117f000101000117528882300000076030000 --screen 0
1,id=117f000101000117528882300000076030001
1,Program=gnome-power-manager
1,CurrentDirectory=/home/forger
1,CloneCommand=gnome-power-manager
1,RestartCommand=gnome-power-manager --sm-client-id 117f000101000117528882300000076030001 --screen 0
2,id=117f000101000117536632300000122270000
2,RestartStyleHint=0
2,Program=evolution-alarm-notify
2,CurrentDirectory=/home/forger
2,CloneCommand=evolution-alarm-notify
2,RestartCommand=evolution-alarm-notify --sm-client-id 117f000101000117536632300000122270000 --screen 0
3,id=117f000101000117536632400000122270001
3,Program=evolution-exchange
3,CurrentDirectory=/
3,CloneCommand=evolution-exchange
3,RestartCommand=evolution-exchange --sm-client-id 117f000101000117536632400000122270001 --screen 0
4,RestartCommand=/usr/lib/control-center/gnome-settings-daemon
5,RestartCommand=gnome-volume-manager --sm-disable
6,RestartCommand=restricted-manager --check
7,RestartCommand=/usr/lib/evolution/2.10/evolution-alarm-notify
8,RestartCommand=nm-applet --sm-disable
num_clients=9

[Failsafe]
0,id=117f000101000117536636500000124050000
0,RestartStyleHint=2
0,Priority=40
0,Program=nautilus
0,CurrentDirectory=/home/forger
0,CloneCommand=nautilus
0,RestartCommand=nautilus --sm-client-id 117f000101000117536636500000124050000 --screen 0
1,id=117f000101000117536636500000124050001
1,RestartStyleHint=1
1,Priority=40
1,Program=gnome-volume-manager
1,CurrentDirectory=/home/forger
1,CloneCommand=gnome-volume-manager
1,RestartCommand=gnome-volume-manager --sm-client-id 117f000101000117536636500000124050001 --screen 0
2,id=117f000101000117536636500000124050002
2,RestartStyleHint=2
2,Priority=40
2,Program=gnome-panel
2,CurrentDirectory=/home/forger
2,CloneCommand=gnome-panel
2,RestartCommand=gnome-panel --sm-client-id 117f000101000117536636500000124050002 --screen 0
3,id=117f000101000117536636700000124050003
3,RestartStyleHint=2
3,Priority=20
3,Program=metacity
3,CurrentDirectory=/home/forger
3,DiscardCommand=rm -f /home/forger/.metacity/sessions/1175366375-12444-1202444034.ms
3,CloneCommand=metacity
3,RestartCommand=metacity --sm-save-file 1175366375-12444-1202444034.ms
4,id=117f000101000117536637400000124050004
4,RestartStyleHint=0
4,Program=evolution-alarm-notify
4,CurrentDirectory=/home/forger
4,CloneCommand=evolution-alarm-notify
4,RestartCommand=evolution-alarm-notify --sm-client-id 117f000101000117536637400000124050004 --screen 0
5,id=117f000101000117536637400000124050005
5,RestartStyleHint=2
5,Priority=50
5,Program=gnome-cups-icon
5,CurrentDirectory=/home/forger
5,CloneCommand=gnome-cups-icon
5,RestartCommand=gnome-cups-icon --sm-client-id 117f000101000117536637400000124050005 --screen 0
6,id=117f000101000117536637400000124050006
6,Program=gnome-power-manager
6,CurrentDirectory=/home/forger
6,CloneCommand=gnome-power-manager
6,RestartCommand=gnome-power-manager --sm-client-id 117f000101...

Does using the config you described again trigger the bug? Could you try to remove items and note which one is causing the bug?

Yes, the config under [Default] made the normal (by normal I mean GNOME, not Safe GNOME) login, and I could recreate the bug by readding those values. I'm really sorry though, I don't have that info anymore, since the problem got fixed by clearing the values under [Default], as I've previously mentioned.

You copied the config on launchpad, could you try to use it and note if that triggers the bug again now?

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.