The crash just happened randomly. I ran it with gdb previously for
many times, but no useful information was got. It kept crash randomly
and causes random flickers without known cause. The notification area
spec is just too complicated to understand. Since gnome-panel's
systray works flawlessly, th
Hi,
For such incompatible changes, you need to bump the SONAME of
libmenu-cache library, to mark the fact that reverse-depends need to be
ported.
Also, I think lxlauncher which use also menu-cache, need to be ported to
the new API.
Regards,
Julien Lavergne
Le lundi 15 février 2010 à 09:16 +0800
I have to admit I take exception to characterizing the systray as "buggy".
Could someone summarize what the problems with it are and why haven't I been
presented with a backtrace that proves it did something wrong so it can be
fixed, or for that matter a backtrace of any panel crash. I did fix
Am Montag, den 15.02.2010, 11:25 +0100 schrieb Andrea Florio:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> please release new lxpanel NOW or retire menu-cache release...
>
> having menu-cache 0.3.0 and lxpanel 0.5.4.1 made the second one to
> crasch immediatly:
Did you rebuild the panel
Am Montag, den 15.02.2010, 11:16 +0100 schrieb Andrea Florio:
> attached you can find gdb output
The backtrace was not very fruitful, you don't have the debug symbols
installed. Please compile both menu-cache and pcmanfm2 with CFLAGS="-g
-O0". Instead of "bt" you might want to use "thread apply al
Hello,
I just ported the 'notification area' applet of gnome-panel to lxpanel
as systray2 plugin.
Now all the old problems are solved and I think this new one can
replace the old buggy systray.
The source code is in lxpanel-plugins/systray2.
I also implemented a new container class named LxGrid.
Th
Hi
Pootle is back online again. I have tried to restore all the privileges
and stuff but might have missed yours. Drop me a note (include user name)
via e-mail or IRC and I'll look into it if something is wrong for you.
Pootle is now fully on git, missing is the push ability because I haven't
g
I don't know what happened either, but you might need to make sure
that old menu-cached is not running.
The IPC mechnism inside menu-cache has been changed a bit.
Let me explain what are changed:
1. menu-cache:
* now the menu cache is loaded asynchronously. After calling
menu_cache_lookup you get
With lxsession 0.4.1, menu-cache 0.2.6, lxpanel GIT Head, I am finding that
selecting Logout from the menu dims the screen and gets stuck without putting
up the logout dialog. Manually running lxsession-logout from a terminal works
properly. With lxsession 0.4.1, menu-cache 0.3.0, lxpanel GIT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
please release new lxpanel NOW or retire menu-cache release...
having menu-cache 0.3.0 and lxpanel 0.5.4.1 made the second one to
crasch immediatly:
(gdb) r
Starting program: /usr/bin/lxpanel
[Thread debugging using libthread_db enabled]
Program
attached you can find gdb output
i see some differences now after upgrading menu-cache to verson 0.3.0
--
--
Andrea Florio
QSI International School of Brindisi Sys Admin
CISCO CCNA Certified
openSUSE-Education Administrator
openSUSE Official Member (anubis
11 matches
Mail list logo