[Bug 908718] Re: gedit crashed with SIGSEGV

2016-06-12 Thread Bug Watch Updater
** Changed in: gedit Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908718 Title: gedit crashed with SIGSEGV To manage notifications about this bug go to: https://bug

[Bug 908718] Re: gedit crashed with SIGSEGV

2013-11-10 Thread Bug Watch Updater
** Changed in: gedit Importance: Critical => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908718 Title: gedit crashed with SIGSEGV To manage notifications about this bug go to: https:/

[Bug 908718] Re: gedit crashed with SIGSEGV

2012-02-14 Thread Bug Watch Updater
** Changed in: gedit Status: Unknown => New ** Changed in: gedit Importance: Unknown => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908718 Title: gedit crashed with SIGSEGV To

[Bug 908718] Re: gedit crashed with SIGSEGV

2012-02-14 Thread Vadim Rutkovsky
** Changed in: gedit (Ubuntu) Status: New => Confirmed ** Bug watch added: GNOME Bug Tracker #670064 https://bugzilla.gnome.org/show_bug.cgi?id=670064 ** Also affects: gedit via https://bugzilla.gnome.org/show_bug.cgi?id=670064 Importance: Unknown Status: Unknown -- You r

[Bug 908718] Re: gedit crashed with SIGSEGV

2012-02-02 Thread Daniel Winzen
Now I got a third version of valgrind log. ** Attachment added: "Version 3 of valgrind log" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/908718/+attachment/2708192/+files/valgrind.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed t

[Bug 908718] Re: gedit crashed with SIGSEGV

2012-02-01 Thread Sebastien Bacher
thanks, that new log has no similar error though ... could you try again and see if you have some gtk_text_view_set_buffer mention in the log for example? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/

[Bug 908718] Re: gedit crashed with SIGSEGV

2012-02-01 Thread Daniel Winzen
Now I installed the debug packages and got again a valgrid log. ** Attachment added: "New valgrid log after installation of debug packages." https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/908718/+attachment/2705792/+files/valgrind.log -- You received this bug notification because you a

[Bug 908718] Re: gedit crashed with SIGSEGV

2012-02-01 Thread Sebastien Bacher
or and gedit-dbgsym as well -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908718 Title: gedit crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+s

[Bug 908718] Re: gedit crashed with SIGSEGV

2012-02-01 Thread Sebastien Bacher
the issue is "==5940== Invalid write of size 4 ==5940==at 0x4B5B5E7: g_nullify_pointer (in /lib/i386-linux-gnu/libglib-2.0.so.0.3115.0) ==5940==by 0x4AA779A: ??? (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.3115.0) ==5940==by 0x4B0FD35: g_datalist_id_set_data_full (in /lib/i386-l

[Bug 908718] Re: gedit crashed with SIGSEGV

2012-02-01 Thread Daniel Winzen
PS: A few days ago I made an update of gedit, now there is no crash anymore, it just takes about 10 minutes to load the file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908718 Title: gedit crashe

[Bug 908718] Re: gedit crashed with SIGSEGV

2012-02-01 Thread Daniel Winzen
Now I got a valgrind log for the issue. ** Attachment added: "valgrind log" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/908718/+attachment/2705371/+files/valgrind.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https:

[Bug 908718] Re: gedit crashed with SIGSEGV

2012-02-01 Thread Sebastien Bacher
Could you try to follow https://wiki.ubuntu.com/Valgrind and get a valgrind log for the issue? ** Changed in: gedit (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/b

[Bug 908718] Re: gedit crashed with SIGSEGV

2012-02-01 Thread Daniel Winzen
Yes, it happens every time I try to open that file or files with the same size. I have to stop gedit manual with gnome-system-monitor after it crashed. I don't know how to use gdb, so I can't get a stacktrace. -- You received this bug notification because you are a member of Ubuntu Bugs, which i

[Bug 908718] Re: gedit crashed with SIGSEGV

2012-02-01 Thread Sebastien Bacher
Thank you for your bug report, does it happen every time you try to open that file? It seems a bit similar to https://bugzilla.gnome.org/show_bug.cgi?id=317800 Could you get a stacktrace using gdb when it happens? ** Bug watch added: GNOME Bug Tracker #317800 https://bugzilla.gnome.org/show_bu

[Bug 908718] Re: gedit crashed with SIGSEGV

2012-01-05 Thread Sebastien Bacher
** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/908718/+attachment/2647225/+files/CoreDump.gz ** Changed in: gedit (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscr

[Bug 908718] Re: gedit crashed with SIGSEGV

2011-12-26 Thread Daniel Winzen
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908718 Title: gedit crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubun