From: Marty J. <mar...@co...> - 2010-02-15 13:54:52
|
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 Head, I am finding that logging in leaves me with a black screen. Does anyone else see this or have an idea what changed. |
From: PCMan <pcm...@gm...> - 2010-02-15 14:22:02
|
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 an empty menu and this function call doesn't block the execution. Later, a reload notification will be sent, and that means the menu cache is loaded and is ready for use. * The IPC mechanism inside menu-cache is changed. * no other parts are changed. 2. lxpanel: * I modify menu.c and launcherbar.c to adopt this new behavior of menu-cache. * no other parts are changed. So, why the logout screen is affected is very weird. The blank screen after login might be caused by lxpanel crash. Manual start of lxpanel with gdb might be needed for testing. On Mon, Feb 15, 2010 at 9:49 PM, Marty Jack <mar...@co...> wrote: > 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 Head, I am finding that logging in leaves me with a black screen. > > Does anyone else see this or have an idea what changed. > > ------------------------------------------------------------------------------ > SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW > http://p.sf.net/sfu/solaris-dev2dev > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list > |
From: PCMan <pcm...@gm...> - 2010-02-17 04:10:18
|
I've researched this a bit previously. Current situation: 1. IIRC, Shutdown and reboot are handled by ConsoleKit. 2. Suspend is now handled by DevKit/Power, but later it will become upower. 3. HAL still works in some places where devkit is not available. 4. The gdm support can be dropped as gdm no more uses that old IPC mechanism. 5. The condition of kdm is unknown. investigation is needed. 6. Though gdm doesn't work as before, we still need user-switching facilities when its available. As we use dbus and didn't bind to any one of the preceding methods, it's possible to support all of them at the same time. Just check for availability of devkit and consolekit at runtime. If they're not available, check if HAL works. This should work for FreeBSD where HAL is available and devkit is not. (Actually DevKit is Linux only) This approach should keep backward compatibility. Since things are linked at runtime, we don't have additional dependencies, either. The last issue to solve would be what to do if all of preceding mechanisms are not availble? Is calling 'reboot' and 'shutdown' with sudo or something similar as fallback an option? If it is, how to do it correctly? On Wed, Feb 17, 2010 at 11:33 AM, Marty Jack <mar...@co...> wrote: > Good progress today. I have the screen display up and running. The way I do it is to have a single toplevel fullscreen window and a box with the controls in it surrounded by four drawing areas into which I draw the root window screenshot in the foreground. This is the only way I could think of to do it that leaves the box with the controls having the correct background. > > The part that is left is layering in the mechanism. Logout is easy and is finished. > > The actual critical issue for us is that the mechanisms are very close to changing away from HAL. We don't have support for the new mechanism, DeviceKit/power, and if this isn't adjusted we will lose the ability to do everything except Logout. Probably we will need the HAL mechanism also for a good while until the distro releases that are HAL based are sufficiently old. Also, it currently has support for the extremely old GDM mechanism with the socket. I think this went over to DBUS in 2.20 and this would be a good opportunity to remove it. > > After I do some more research I'll make a proposal on the mailing list. > |
From: L. A. G. <agi...@sy...> - 2010-02-17 21:31:30
|
Hi, First thing, how is that I can't see the original Marty's message in the list? was it a private message for PCMan? Second, I've found lxsession-logout (Debian version 0.3.8+svn20090521-1) a little bit weird in the sense that it just seems to kill -9 my desktop. I mean, when I log off (or reboot, or shut down), it just halts the machine (i don't see the init scripts running down). Moreover, when I re-login, all the programs that were started don't start automatically (as it's suposed in a session), and programs like, for example, firefox, wake as if they were killed (i.e. the window with the "it's embarrassing, it seems that firefox crashed"). The OS itself seems to be halted properly (as in ACPI power button pressed). I'd like to see that fixed, since I'm starting to give a shot to lxde as my second desktop environment, and I'm willing to help if it's needed. I have a good C knowledge, but no Desktop infrastructure (X internals, freedesktop.org specs, etc) and my notions of GTK are somewhat basic, but I would have no problem in learning. I just need some initial point, guidelines, whatever. Best regards, -- L. Alberto Giménez GnuPG key ID 0x3BAABDE1 |