Performed a normal update today (7/27/01) and upon completion and reboot, startx at the console failed to start Reproducible: Always Steps to Reproduce: 1.emerge -uD @world 2.restart computer 3.check that lxsession-0.4.6 is included Actual Results: error starting X Expected Results: No difference prior to lxsession update - normal starting of X From dmesg: [ 1.761902] pci 0000:00:1f.0: rerouting interrupts for [8086:2670] [ 47.341347] lxsession[4472]: segfault at 0 ip 00007f7ed8602e29 sp 00007fff912e22b0 error 4 in libc-2.13.so[7f7ed858b000+183000] [ 337.646347] lxsession[5841]: segfault at 0 ip 00007fc9870bde29 sp 00007ffff4d802e0 error 4 in libc-2.13.so[7fc987046000+183000] Temporary resolution: I masked lxde-base/lxsession-0.4.6 and re-emerged to version 0.4.5 and X started normally.
Did lxsession-0.4.6 work ok before updating the rest of the system? Or is this a regression over 0.4.5? You should also try to get a better backtrace: http://www.gentoo.org/proj/en/qa/backtraces.xml
Pacho, These are the packages that were included in the upgrade. It was after this upgrade X didn't start and dmesg contained the segfault error message. I added lxde-base/lxsession-0.4.6-r1 to package.mask, issued emerge -uD @world again and only lxsession version 0.4.5 was pulled in. Upon completion, startx at the console started everything normally. net-libs/miniupnpc-1.6 [1.5] dev-python/numpy-1.6.1 [1.6.0] lxde-base/lxmenu-data-0.1.2 [0.1.1] lxde-base/lxterminal-0.1.10 [0.1.9] lxde-base/lxrandr-0.1.2 [0.1.1] lxde-base/lxshortcut-0.1.2 [0.1.1] lxde-base/lxpanel-0.5.7-r1 [0.5.6] lxde-base/lxsession-0.4.6-r1 [0.4.5] lxde-base/lxsession-edit-0.2.0 [0.1.1] lxde-base/lxde-meta-0.5.0-r7 [0.5.0-r6] If you need a backtrace I will set it up and and provide the output this afternoon. Just let me know if you still require that information. In the interim, I hope this useful.
Pacho, An update arrived to lxsession today (07/28/11): Calculating dependencies... done! [ebuild U ] x11-wm/twm-1.0.7 [1.0.6] [ebuild U ] app-portage/gentoolkit-0.3.0.4-r1 [0.3.0.4] [ebuild U ] sys-kernel/genkernel-3.4.18 [3.4.17] [ebuild U ] lxde-base/lxsession-0.4.6.1 [0.4.5] [ebuild U ] x11-drivers/nvidia-drivers-275.21 [275.19] After performing the update and rebooting, everything was fine. Apparently, this problem must have been identified internally and quickly rectified. Therefore I do not see a need to pursue this any further. In any event, I'm going to configure the backtrace feature for reporting future issues. Thanks for your quick response. Given that this has been resolved with lxsession-0.4.6.1 I will close this issue. Regards, Bill
