| 2007-01-10 09:25:01 |
Lance Poore |
bug |
|
|
added bug |
| 2007-01-10 09:53:22 |
Sebastien Bacher |
title |
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 |
|
| 2007-01-10 09:54:20 |
Sebastien Bacher |
gtk+2.0: status |
Unconfirmed |
Needs Info |
|
| 2007-01-10 09:54:20 |
Sebastien Bacher |
gtk+2.0: assignee |
|
desktop-bugs |
|
| 2007-01-10 09:54:20 |
Sebastien Bacher |
gtk+2.0: statusexplanation |
|
Thank you for your bug. Could you get a backtrace with libgtk2.0-0-dbg installed? |
|
| 2007-01-10 10:35:20 |
Lance Poore |
description |
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 mousepad, I restarted X and tried again, same issue. I fired up gedit and got the same problem. I was running both as root. However if i ran gedit as a normal user it worked fine. When i tried running mousepad as a normal user I got a segfault, so I decided to debug mousepad with gdb. This is the results:
$ gdb mousepad
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.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) run
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 debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1219246400 (LWP 627)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1219246400 (LWP 627)]
0xb7aacd5f in gdk_drawable_get_screen () from /usr/lib/libgdk-x11-2.0.so.0
As you can see it refers to the file /usr/lib/libgdk-x11-2.0.so.0
dpkg says these files are part of libgtk2.0-0
$ dpkg --search libgdk-x11-2.0.so.0
libgtk2.0-0: /usr/lib/libgdk-x11-2.0.so.0.1000.7
libgtk2.0-0: /usr/lib/libgdk-x11-2.0.so.0
Hopefully this is enough information for anyone to regenerate the issue and confirm it is a major bug.
thanks
Lance Poore |
Binary package hint: libgtk2.0-0
I received some updates tonight for feisty. One of which was libgtk2.0-0. I was trying to edit some files in mousepad and noticed when I clicked the Open option from the file menu it froze mousepad, I restarted X and tried again, same issue. I fired up gedit and got the same problem. I was running both as root. However if i ran gedit as a normal user it worked fine. When i tried running mousepad as a normal user I got a segfault, so I decided to debug mousepad with gdb. This is the results:
$ gdb mousepad
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.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) run
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 debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1219246400 (LWP 627)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1219246400 (LWP 627)]
0xb7aacd5f in gdk_drawable_get_screen () from /usr/lib/libgdk-x11-2.0.so.0
As you can see it refers to the file /usr/lib/libgdk-x11-2.0.so.0
dpkg says these files are part of libgtk2.0-0
$ dpkg --search libgdk-x11-2.0.so.0
libgtk2.0-0: /usr/lib/libgdk-x11-2.0.so.0.1000.7
libgtk2.0-0: /usr/lib/libgdk-x11-2.0.so.0
Hopefully this is enough information for anyone to regenerate the issue and confirm it is a major bug.
thanks
Lance Poore |
|
| 2007-01-10 19:14:38 |
Lance Poore |
bug |
|
|
added attachment 'valgrind.log.18418' (Valgrind log of Mousepad) |
| 2007-01-10 21:27:23 |
Lance Poore |
bug |
|
|
added attachment 'valgrind2.log.24295' (valgrind log of Mousepad ran as root) |
| 2007-01-15 11:26:07 |
Sebastien Bacher |
gtk+2.0: status |
Needs Info |
Confirmed |
|
| 2007-01-15 11:26:07 |
Sebastien Bacher |
gtk+2.0: importance |
Undecided |
High |
|
| 2007-01-15 11:26:07 |
Sebastien Bacher |
gtk+2.0: statusexplanation |
Thank you for your bug. Could you get a backtrace with libgtk2.0-0-dbg installed? |
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 forwarded that upstream: http://bugzilla.gnome.org/show_bug.cgi?id=396826 |
|
| 2007-01-15 11:26:21 |
Sebastien Bacher |
bug |
|
|
assigned to gtk (upstream) |
| 2007-01-15 17:29:23 |
Sebastien Bacher |
gtk+2.0: status |
Confirmed |
Fix Released |
|
| 2007-01-15 17:29:23 |
Sebastien Bacher |
gtk+2.0: statusexplanation |
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 forwarded that upstream: http://bugzilla.gnome.org/show_bug.cgi?id=396826 |
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)
|
|
| 2007-01-17 05:16:10 |
Bug Watch Updater |
gtk: status |
Unknown |
Rejected |
|
| 2007-01-24 21:40:39 |
Bug Watch Updater |
gtk: status |
Rejected |
Fix Released |
|
| 2010-09-16 02:16:44 |
Bug Watch Updater |
gtk: importance |
Unknown |
Medium |
|
