On Fri, Jun 25, 2010 at 06:03:59PM +0200, Joachim Ott wrote: > On 25 June 2010 14:09, Martin Jansa <[email protected]> wrote: > >> Some work-in-progress stuff was accidentaly rsynced to public feeds > >> yesterday.. > >> > >> so if you want working Xorg, don't opkg upgrade now, I'll reply here as > >> soon as I finish my changes and rsync it to working and tested state. > >> > >> Sorry for inconvenience ( I guess that everybody will read this only > >> _after_ failed opkg upgrade ;/ - so I'll remove feeds for today..) > >> > >> Regards, > > > > There is workaround for those who opkg upgraded between 23:00 CEST > > yesterday and today morning when I renamed ipk dir.. > > > > You can install any kernel from > > http://build.shr-project.org/shr-kms/ > > and follow the instructions there. 2.6.32 are known to work (except that > > some people see white screen on some occassions). > > I haven't got any 2.6.32 kernel to work, the X-server always crashes. > This is with the latest 2.6.32.13 from the above page just some > minutes ago (full logfile attached):
You're not affected by today's upgrade right (because you have old xserver and its drivers). Can you try to run Xorg -verbose 3 in gdb after installing -dbg packages (from tests/shr-unstable.29) and get some backtrace from this segmentation fault (I have never seen this one it if it's really from adding keyboard). And make sure that you're starting only Xorg not whole Xsession, because ie enlightenment fails to start when there is wrong mouse device node in xorg.conf and exiting enlightenment as last process of Xsession kills the Xorg then.. Regards, -- Jansa 'JaMa' Martin jabber: [email protected] _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
