myDSL Extensions (deprecated) :: NOTICE!! New GTK2-0705.dsl file replaces gtk2.dsl



I've noticed a problem with firefox 1.04 and I'm not sure if it happened in the old GTK2

The titlebar always displays Unnamed instead of Firefox + the webpage, this then appears in the toolbar as unnamed

Have I messed up something or are other people getting this, Im using the new GTK2 mentionned in this thread and the newest firefox 1.04 UCI

The firefox included in DSL doesn't have this problem so I don't think it's a firefox preference

Any ideas,

ps I'm also starting GTK2 as suggested here, excellent as I can go straight into firefox and others without having to load them.

I've noticed this is also happening for me in GFTP, how can I make GTK2 apps show correctly in the toolbar and in their menu bar ?????
I've seen the same thing in a Rox 2.x extension I've been working on. Since window titles are actually handled by the WM, I'm guessing that GTK+ 2.x is using a newer window manager API that the DSL version of Fluxbox doesn't support. However this is just pure speculation on my part. Are there any window manager experts here that could lend some insight?
I'm just guessing here, but follow my logic...

DSL recently changed default shells, from rxvt to aterm.
Most of the gtk2 apps I have contributed, I start with a
wrapper, something similar to start_gimp or start_gftp,
tucked inside /usr/bin.

The wrapper allows you to execute a process,
rather than open a shell, then run a process from that shell,
essentially leaving 2 shells open during the use of the app.

Also, a wrapper gives you environment options,
like exporting PATH and LD_LIBRARY_PATH to direct
the seek of dependancies to certain directories.

I'm thinking here that the wrappers might need more
than just #!/bin/bash to startup the apps..
Or , perhaps the aterm opens as "Unnamed" by default?

Not an answer, I know, but food for thought.

Maybe change to something like this in the wrapper
" exec aterm -tr -T "gFTP" -e /usr/bin/gftp "  ???

73
ke4nt

Quote (ke4nt1 @ Aug. 01 2005,12:17)
I'm thinking here that the wrappers might need more
than just #!/bin/bash to startup the apps..
Or , perhaps the aterm opens as "Unnamed" by default?

I don't think it's the wrapper that's causing the problem since my ROX 2 extension doesn't use a wrapper to launch and exhibits the same "Unnamed" behavior.

Keep in mind that Aterm is a terminal emulator and not a shell. If you exec a shell via #!/bin/bash its process will run as a child of the process that launched it. In the case of launching from a Fluxbox menu or icon, the wrapper script will run as a child of Fluxbox and will never be associated with an Aterm window. You can confirm this by closing all your Aterm windows, launch a GTK+2 app, drop to the console (CTRL-ALT-F1), then "ps agx". You'll see no aterm processes running.

The fact is that any GTK+2 application is going to create it's own top level window in the X11 heirarchy using calls to GTK+ which in turn make calls into xlib. The window title and other WM hints are defined by the app through these APIs and are not inherited from the parent app the way environment variables and such are. So I'm still convinced that somehow we have a disconnect between GTK+2, xlib, and Fluxbox.

Next Page...
original here.