After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 546348 - crash in Terminal: Again, I simply try maki...
crash in Terminal: Again, I simply try maki...
Status: RESOLVED OBSOLETE
Product: gnome-terminal
Classification: Core
Component: BugBuddyBugs
2.22.x
Other All
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
: 562889 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-08-05 01:59 UTC by Richard Schwarting
Modified: 2008-12-11 20:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Richard Schwarting 2008-08-05 01:59:57 UTC
Version: 2.22.2

What were you doing when the application crashed?
Again, I simply try making a terminal window transparent, and GNOME Terminal crashes on me.  

I'm not sure how useful these crash reports could be, with the Crash Details claiming most/all values have been "optimised out".  If there's anything I can do to get those values into the Crash Details, please, let me know.


Distribution: Fedora release 9 (Sulphur)
Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.11-97.fc9.i686 #1 SMP Mon Jul 21 01:31:09 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10499905
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: HighContrast-SVG

Memory status: size: 127127552 vsize: 127127552 resident: 23560192 share: 11018240 rss: 23560192 rss_rlim: 4294967295
CPU usage: start_time: 1217696040 rtime: 16492 utime: 13491 stime: 3001 cutime:231760 cstime: 26495 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-terminal'

[Thread debugging using libthread_db enabled]
[New Thread 0xb809c760 (LWP 4144)]
[New Thread 0xb5868b90 (LWP 4152)]
0x00110416 in __kernel_vsyscall ()


----------- .xsession-errors ---------------------
(npviewer.bin:12099): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
(npviewer.bin:12099): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x58001fc (*Unsaved 1); these messages lack timestamps and therefore suck.
Could not find the frame base for "IA__g_spawn_command_line_sync".
Could not find the frame base for "IA__g_cclosure_marshal_VOID__POINTER".
Could not find the frame base for "IA__g_signal_emit".
Could not find the frame base for "notify_listeners_callback".
Could not find the frame base for "gconf_listeners_notify".
Could not find the frame base for "g_idle_dispatch".
Could not find the frame base for "g_main_context_iterate".
Cannot access memory at address 0x4
Could not find the frame base for "child_watch_helper_thread".
Could not find the frame base for "child_watch_helper_thread".
Could not find the frame base for "IA__g_spawn_sync".
--------------------------------------------------
Comment 1 Christian Persch 2008-08-05 10:44:54 UTC
Fixed in 2.23.x.

This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.
Comment 2 palfrey 2008-12-01 17:57:24 UTC
*** Bug 562889 has been marked as a duplicate of this bug. ***
Comment 3 Sam Morris 2008-12-01 20:46:21 UTC
Could you please point me to the commit that fixes this bug? I'd like to make sure that the patch ends up in the next Debian release.
Comment 4 Christian Persch 2008-12-11 20:08:25 UTC
There is no single commit; this was fixed in the complete refactoring that g-t went through in 2.23.