** Changed in: gtk
Importance: Unknown = Medium
--
libgtk2.0 upgrade broke things in gtk apps such as mousepad and gedit
https://bugs.launchpad.net/bugs/78665
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
** Changed in: gtk (upstream)
Status: Rejected = Fix Released
--
libgtk2.0 upgrade broke things in gtk apps such as mousepad and gedit
https://launchpad.net/bugs/78665
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Bug watch removed: GNOME Bug Tracker #396826
http://bugzilla.gnome.org/show_bug.cgi?id=396826
** Bug watch added: GNOME Bug Tracker #393813
http://bugzilla.gnome.org/show_bug.cgi?id=393813
--
libgtk2.0 upgrade broke things in gtk apps such as mousepad and gedit
** Changed in: gtk (upstream)
Status: Unknown = Rejected
--
libgtk2.0 upgrade broke things in gtk apps such as mousepad and gedit
https://launchpad.net/bugs/78665
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
From the duplicate:
If I start gedit from the terminal and select settings/add line numbers
gedit crashes. If I restart it the line numbers are active. It crashes
again if I remove the line numbers and select them again.
I get this error in the terminal Segmentation fault (core dumped)
I've
It was already known as http://bugzilla.gnome.org/show_bug.cgi?id=393813
--
libgtk2.0 upgrade broke things in gtk apps such as mousepad and gedit
https://launchpad.net/bugs/78665
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Thank you for the comment didier
Fixed with this upload:
gtk+2.0 (2.10.7-0ubuntu2) feisty; urgency=low
.
* debian/patches/090_from_svn_fix_textview_window_crasher.patch:
- patch from SVN, fix GtkTextView crasher (Ubuntu: #78665)
** Changed in: gtk+2.0 (Ubuntu)
Status:
The upstream of version 2.10.7-0ubuntu2 fixed the problem running
mousepad as a normal user. Mousepad now runs properly as a normal user,
however the bug with gedit/mousepad when clicking open file still
remains unfixed.
To reproduce this bug just run sudo gedit and hit open on the
toolbar,
Thank you for your bug. Could you get a backtrace with libgtk2.0-0-dbg
installed?
** Summary changed:
- FEISTY: libgtk2.0 upgrade broke things in gtk apps such as mousepad and gedit
+ libgtk2.0 upgrade broke things in gtk apps such as mousepad and gedit
** Changed in: gtk+2.0 (Ubuntu)
Yep I got a backtrace with the debug package installed
Here are the results:
Starting program: /usr/bin/mousepad
(no debugging symbols found)
Failed to read a valid object file image from memory.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no
sorry for the split post.. i forgot the important part :)
(gdb) backtrace
#0 0xb7b8fd5f in IA__gdk_drawable_get_screen (drawable=0x4c4c)
at gdkdraw.c:202
#1 0xb7bd3178 in IA__gdk_window_new (parent=0x4c4c, attributes=0xbf9e9bb4,
attributes_mask=108) at gdkwindow-x11.c:673
#2
** Description changed:
Binary package hint: libgtk2.0-0
- I received some updates tonight for feisty. One of which was libc6-i686
- as well as just the libc6 package. I was trying to edit some files in
- mousepad and noticed when I clicked the Open option from the file menu
- it froze
Can you try entering 'thread apply all bt full' instead of 'bt'? It'd be
nice if you'd follow the instructions on
https://wiki.ubuntu.com/DebuggingProgramCrash to get debug symbols for
mousepad and libglib2.0-0
--
libgtk2.0 upgrade broke things in gtk apps such as mousepad and gedit
$ cat /tmp/gdb-mousepad.txt
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
I have a new logfile I generated with how mousepad works if ran by root,
until you try to open a file from the menu. Here is the command I ran
with valgrind
sudo valgrind -v --tool=memcheck --leak-check=full --num-callers=12
--log-file=valgrind2.log mousepad
Attached is the output
Thanks in
Here is some more debugging information from gdb i got.
$ gdb mousepad 21 | tee /tmp/gdb-mousepad-open.txt
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute
16 matches
Mail list logo
