On Sat, Dec 31, 2011 at 6:17 AM, mh <[email protected]> wrote: > On Dec 30, 2011, at 10:54 PM, mh wrote: >> On Dec 30, 2011, at 10:39 PM, mh wrote: >>> On Dec 30, 2011, at 10:25 PM, P Purkayastha wrote: >>>> On Saturday, December 31, 2011 9:33:43 AM UTC+8, mh wrote: >>>>> On Dec 30, 2011, at 8:28 PM, mh wrote: >>>>>> On Dec 30, 2011, at 6:04 PM, Cedric BAIL wrote: >>>>>>> On Fri, Dec 30, 2011 at 11:51 PM, Jeff Hoogland <[email protected]> >>>>> wrote: >>>>>>>> What theme is it? A good deal of older themes no longer work with >>>>> current >>>>>>>> Enlightenment revisions. They need to be manually updated to the new >>>>>>>> formatting. >>>>>>> >>>>>>> They should never crash E like that. If it's due to a theme, please >>>>>>> send it to me. >>>>>> >>>>>> I'll try downloading and importing a theme that I have working already. >>>>>> >>>>>>> >>>>>>>> On Fri, Dec 30, 2011 at 4:24 PM, mh <[email protected]> wrote: >>>>>>>> >>>>>>>>> This is what I'm seeing now: from E, go to the themes setting box. I >>>>> have >>>>>>>>> several themes there, can pick and change them without problem. >>>>>>>>> >>>>>>>>> But if I click on "Import" to import a theme I've downloaded, all the >>>>>>>>> windows freeze. The cursor can still move, but can't select anything. >>>>> There >>>>>>>>> are many, many errors in the vt that I ran startx from. Caught as >>>>> many as I >>>>>>>>> could in the attachment. If I ctl-c in the vt I ran startx from, the >>>>> one >>>>>>>>> with the error messages, it kills X with the message at the bottom of >>>>> the >>>>>>>>> attachment. >>>>>>>>> >>>>>>>>> This is v.666703. Any ideas? >>>>>>> >>>>>>> When E froze could you connect gdb to it and give us the backtrace ? >>>>>>> >>>>>>> Thanks, >>>>>>> -- >>>>>>> Cedric BAIL >>>>>> >>>>>> I'll look at that and see if I can get a bt. It's a very repeatable >>>>> process to failure. >>>>>> >>>>>> mike >>>>> >>>>> Question: Do I just need to compile e with debug symbols, or all the EFLs? >>>>> >>>>> >>>>> All of EFL and e. >>> >>> Ok, got everything recompiled with debugging symbols, started X, exported >>> E_START and DISPLAY, gdb enlightenment, run. Changed to X session and tried >>> to import a theme and it froze as I expected. Back to vt2 where gdb is >>> running. I tried to capture what was on vt2 with cat /dev/vcs2 > e-crash, >>> but that only captured part of the backtrace. How do I capture all the >>> output from the gdb session? >>> >> >> oh never mind, I got it. I should look before I speak :( >> >> (gdb) record > > > no, I think it's (gdb) set logging file file-name, and then (gdb) set logging > on. > > I'm stuck. I think I should be able to get the backtrace for this with, doing > everything as root: > > Xorg -ac :1 & > export E_START=1 > export DISPLAY=:1 > gdb enlightenment - no breakpoints? > > then, in the gdb session, > > set logging file log-file.txt > set logging on > r > > But this doesn't start enlightenment. I'm doing something wrong, don't know > what.
You need to run enlightenment_start instead. -- Cedric BAIL ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
