Well, as I said, I think the crash was during a "Failsafe Gnome Session". When the session started, The system offered some "recovery options" for me, and I choose something like "See X Server Errors Log". I think this option tried to open the error log with gedit, and it crashed, because after a while I didn't see any error log, and switched to console 1 to restart gnome. After I've restarted Gnome, the same options appeared, and the same happened, switched again... and finnaly I decided to start gnome wihout seeing any log file. Then, just after gnome started, I've seen the crash report of gedit.
So... in few words, start gnome in failsafe mode(set a wrong/broken graphics driver in xorg.conf...), and try to see the X Server error log from the menu, and see what happens. Hope this helps, I'm not in my machine on theese days... Greetings, Felipe. On Tue, Sep 16, 2008 at 5:09 AM, Sebastien Bacher <[EMAIL PROTECTED]> wrote: > thank you for your bug report. did you get the issue only once? could > you describe how to trigger it? > > ** Visibility changed to: Public > > ** Changed in: gedit (Ubuntu) > Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs) > Status: New => Incomplete > > -- > gedit crashed with SIGSEGV in PyObject_GetAttrString() > https://bugs.launchpad.net/bugs/269447 > You received this bug notification because you are a direct subscriber > of the bug. > -- ATTE: Hernán Felipe De la Puente Christen Móvil : 93199807 ICQ : 58547127 MSN/Google Talk : [EMAIL PROTECTED] -- gedit crashed with SIGSEGV in PyObject_GetAttrString() https://bugs.launchpad.net/bugs/269447 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
