Comment 2 for bug 350511

Hi all!

I'm the brave ( dumb ) fool who went ahead and packaged up the 0.3.999
release of lxpanel and its two dependencies. So far the recurring issues on
my 64 bit #! have been occasional, but irritating instances of the panel
just up and vanishing/it's process terminating. A quick "lxpanel &" in a
terminal will of course bring it right back -- only for it to die a few
hours later. When I edited the "rules" file for the packages, I followed the
lxpanel authors' recommendations for config options, per each program's
README and INSTALL files.

Looking over the bug tracker for lxpanel on Sourceforge, there do seem to be
some general stability issues/quirks with the 0.3.999 release. Users of Arch
Linux and OpenSUSE have reported these sorts of stability issues.

I've bounced back and forth between tint2 and lxpanel, not sure which I
found more annoying -- tint2's garbled rendering of system tray icons, or
lxpanel's random crashes.

Maybe the stable release of lxpanel, even with it's lack of taskbar icons
for 64bit, is simply the better way to go right now.

Sorry, all.

On Sun, Mar 29, 2009 at 1:09 AM, Philip Newborough <
<email address hidden>> wrote:

> Confirmed. I have also been experiencing a few issues with the 64bit
> build, not sure of the cause at the moment.
>
> ** Changed in: crunchbang
> Status: New => Confirmed
>
> ** Changed in: crunchbang
> Assignee: (unassigned) => CrunchBangers (crunchbangers)
>
> ** Changed in: crunchbang
> Assignee: CrunchBangers (crunchbangers) => Cory Flick (flicck)
>
> ** Changed in: crunchbang
> Assignee: Cory Flick (flicck) => (unassigned)
>
> --
> menu entry missing for lxpanel - crunchbangers ppa
> https://bugs.launchpad.net/bugs/350511
> You received this bug notification because you are a bug assignee.
>
> Status in CrunchBang Linux: Confirmed
>
> Bug description:
> menu panel item is missing from lxpanel 0.3.999-1 build in crunchbangers
> ppa. i.e. It is not in list of options when you click the 'Add' button. Have
> tried deleting lxpanel configs in .config to allow it to regenerate to new
> defaults without success.
>