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 89049 - transparent background causes x error/crash regularly
transparent background causes x error/crash regularly
Status: RESOLVED FIXED
Product: vte
Classification: Core
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: VTE Maintainers
Nalin Dahyabhai
: 89098 89835 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-07-25 14:26 UTC by Luis Villa
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Description Luis Villa 2002-07-25 14:27:09 UTC 
Package: vte
Severity: critical
Version: 2.0.0
Synopsis: use 'su -' with transparent background causes x error/crash
Bugzilla-Product: vte
Bugzilla-Component: VteTerminal
BugBuddy-GnomeVersion: 2.0 (2.0.1)

Description:
Description of Problem:
I run vte/terminal with the 'monotype.com' font and a transparent
background. In the second tab, I did 'su -' and it crashed.

Not sure if it is reproduceable yet.



Debugging Information:

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

[New Thread 1024 (LWP 2911)]
0x408d44b9 in wait4 () from /lib/libc.so.6

+ Trace 25453

Thread 1 (Thread 1024 (LWP 2911))

  • #0 wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.0
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 620
  • #4 pthread_sighandler
    from /lib/libpthread.so.0
  • #5 <signal handler called>
  • #6 g_logv
  • #7 g_log
    at gmessages.c line 526
  • #8 gdk_x_error
    at gdkmain-x11.c line 854
  • #9 bonobo_x_error_handler
    at bonobo-ui-main.c line 50
  • #10 _XError
    from /usr/X11R6/lib/libX11.so.6
  • #11 _XReply
    from /usr/X11R6/lib/libX11.so.6
  • #12 XTranslateCoordinates
    from /usr/X11R6/lib/libX11.so.6
  • #13 gdk_window_get_origin
    at gdkwindow-x11.c line 2196
  • #14 vte_terminal_setup_background
    at vte.c line 11527 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-07-25 10:27 -------

Reassigning to the default owner of the component, nalin@redhat.com.
Comment 1 Ben FrantzDale 2002-07-25 17:47:36 UTC 

*** This bug has been marked as a duplicate of 75340 ***
Comment 2 Luis Villa 2002-07-26 01:39:58 UTC 
Whoa, there, Ben... two different codebases :)
Comment 3 Luis Villa 2002-07-26 01:40:46 UTC 
*** Bug 89098 has been marked as a duplicate of this bug. ***
Comment 4 Luis Villa 2002-07-26 16:24:51 UTC 
Argh. Forgot to mark new/high.

FWIW, MTBF on this is 3-4 minutes for me, and it's not always
happening when I'm using the terminal- mostly it just spontaneously
combusts while I'm on another desktop. zvt had basically the same
problem a few months ago. I'll try to get a --sync trace soon.
Comment 5 Luis Villa 2002-07-29 16:20:03 UTC 
OK, so, I've run for hours with --sync with no crashes. Run without
--sync and it happens regularly, literally so often it's unusable. So
I've not got any clue where to go from here- any suggestions on
debugging welcome.
Comment 6 Havoc Pennington 2002-07-29 16:32:17 UTC 
I'd suggest just carefully going through the vte get-the-background
code and ensuring there's an error trap anytime we're touching the 
untrusted pixmap.
Comment 7 Luis Villa 2002-08-03 17:03:49 UTC 
Re-titling, and noting that if you guys ship with this bug I'll get
literally thousands of reports of it. And that will suck, a lot.
Please either fix this bug or disable transparency in the 7.3.93 g-t.
Comment 8 Havoc Pennington 2002-08-03 18:01:22 UTC 
I put in a gdk_flush() that might help (but I doubt it is the entire fix).

If --sync makes it go away that does indicate that gdk_flush() could
be the fix, though. Maybe try the latest vte cvs out.
Comment 9 Luis Villa 2002-08-03 18:14:10 UTC 
I assume this was this morning, since my copy of Changelog doesn't
include and checkins by hp in some time. I'll certainly grab a new
build from our snaps tomorrow and 'pound' it. [Where pound in this
case means 'leave open while doing other things.' :)]
Comment 10 Ben FrantzDale 2002-08-04 16:24:11 UTC 
*** Bug 89835 has been marked as a duplicate of this bug. ***
Comment 11 Luis Villa 2002-08-05 19:39:08 UTC 
Hrm. Haven't seen this since I updated yesterday morning, which makes
me think Havoc's patch fixed it. I'll be sure to reopen if that's not
actually the case.