Logging in with UBUNTU_MENUPROXY=0 makes unity-panel-services crash continuously

[Martijn vdS]

I created /etc/X11/Xsession.d/85local with one line of content: "export UBUNTU_MENUPROXY=0".

This turned the global menus off correctly, but it also made all the indicators disappear (sometimes they'd show for a fraction of a second).

Looking in my logs, I found unity-panel-service was crashing, being restarted, etc.:

[ 59.259569] unity-panel-ser[4531]: segfault at 20 ip 00007f210aff5b92 sp 00007fff70648258 error 4 in libglib-2.0.so.0.3120.0[7f210af7b000+f2000]
[ 59.492952] unity-panel-ser[4556]: segfault at 20 ip 00007f005427ab92 sp 00007fff53c8b428 error 4 in libglib-2.0.so.0.3120.0[7f0054200000+f2000]

However, I never got an apport dialog for this.

Removing the UBUNTU_MENUPROXY line from /etc/X11/Xsession.d/85local makes everything work correctly again.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity-services 5.6.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,imgpng,resize,place,grid,session,move,vpswitch,regex,mousepoll,gnomecompat,snap,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell]
Date: Thu Mar 15 10:08:15 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803)
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: Upgraded to precise on 2011-12-03 (102 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[captbunzo (captbunzo)]

Btw. I accomplished the same thing with:

      apt-get remove indicator-appmenu

(i.e. putting menus back where they should be!!! WITH the application!)

[Christian MATHIEU (kikito63)]

I have almost the same problem: Bug # 958067

[Alex Baggott (alex-baggott)]

Thank you for taking the time to report this bug. We have tried to recreate this on the latest release of Ubuntu and cannot reproduce it. This bug is being marked as Invalid. If you believe the problem to still exist in the latest version of Ubuntu, please comment on why that is the case and change the bug status to NEW.