From mstaszyszyn at heiler.com  Mon Aug  5 13:00:34 2002
From: mstaszyszyn at heiler.com (Staszyszyn, Marcin)
Date: Mon, 5 Aug 2002 13:00:34 +0200
Subject: Possible inconsistency with TaskBar
References: <1028071408.8634.225.camel@emperor>
Message-ID: <001301c23c6f$532bc8d0$6a1e0a0a@ipheiler.pl>

'Unsorted' means none sort function is applied to windows. New window
appears at the end of  list (righthmost side of taskbar area) but previous
state of existing windows is not changes
Have a nice day
Marcin

----- Original Message -----
From: "Joe Klemmer" <klemmerj at webtrek.com>
To: <xfce-dev at moongroup.com>
Cc: <xfce at moongroup.com>
Sent: Wednesday, July 31, 2002 1:23 AM
Subject: Possible inconsistency with TaskBar

 I just noticed a possible inconsistency with TaskBar.  The options
available when you right click the little bar on the left of the taskbar
gives you some options where you can set the sort order.  Normally I
have things sorted by desk.  It seems that choosing unsorted and by
desktop sort the same.   Sort by name and sort by window ID work as
expected.

 Just thought someone would like to know.





From d726f6e at SDF.LONESTAR.ORG  Sat Aug 17 23:34:01 2002
From: d726f6e at SDF.LONESTAR.ORG (Dmitry DELTA Malykhanov)
Date: Sat, 17 Aug 2002 21:34:01 +0000 (UTC)
Subject: xfpager, and general observations
In-Reply-To: <m3ptwhb6no.fsf@newsguy.com>
Message-ID: <Pine.NEB.4.44.0208172125130.13234-100000@otaku.freeshell.org>

Harry,

probably the best way will be to move the discussion to the xfce-dev list.
And if we will solve this mystery, we will post a summary to the general
xfce list. I'm sending this message to both lists, and I suggest you to
reply to xfce-dev list only (unless you and/or other xfce users feeling
that we should stay here).

I'll send detailed instructions how to set up your environment to the
xfce-dev list later. Is it ok?

On Sat, 17 Aug 2002, Harry Putnam wrote:
>
> [NOTE:  If people think this should be taken off list, please say
> so.  My feeling was that it might be of general interest to newer
> users -ed HP]
>
> Dmitry writes:
> > I'd say it's a real mystery. Do you normally have gradient background,
> > backdrop image or plain color on the root window? Anyway, XFCE shouldn't
> > change it if you're not switching workspaces.
>
> Harry Writes:
> I tinkered with lots of settings, but really have only run xfce for
> a day at this point so don't really have any settings that would
> qualify as normal.
>
> > Maybe there is something else broken there? Maybe it's not XFCE problem at
> > all? I think we should start from the beginning. But maybe tomorrow. It's
> > midnight in California. :)
>
> This seems very likely, since I'm far from competent and may well
> have other things screwed up. One thing is that this is all happening
> on an intall of `beta' Redhat.  Known as `limbo' and is the developer
> version that is being tested since last major release of 7.3.  Not
> considered ready for showtime.
>
> The macine with xfce installed is a machine I use to experiment on.
> It has several OS's on it.
>
> > I you have enough time and would like to continue, could you please
> > describe your system (like CPU, distro, gcc version, libraries
> > installed)? Maybe we should meet on IRC channel...
>
> My xfce setup is on an Athlon t-bird 1.2ghz, with 2 Maxtor IDE HDD.
> It has the beta release of redhat (limbo2) on Second HDD, jumpered as
> 2nd master, It begans at /dev/hdc2,current release (3.1) of openBSD,
> is on /dev/hdc1 (in linux speak) and the lastest intel release of
> Solaris (Media kit 2/02), occupies the first disk (/dev/hda1)leaving
> several gbyte unused on that disk.
>
> Dual booting with lilo.  Xfce is installed on the Redhat `limbo'
> installation.
>
> kernel 2.4.18-5
> gcc-2.96
> glibc-2.2.5-39
>
> I downloaded Xfce from the cvs server, but when I noticed the
> developer version couldn't be built with simple
> ./configure
> make
> make install
>
> That is, there are no Makefile.in in the various directories.
> I didn't know how to build them so tried the `stable' version that
> was part of the cvs download.
>
> Not sure how to tell exactly what version it is, but the last entry
> in the change log says:
>    2002-04-28
> The *lsm file is named:
>     xfce-3.8.18.lsm
>
> I built it with simple:
> ./configure --prefix=/usr/local (wasn't sure if that was default)
> make
> make install
>
> I didn't encounter any errors but some warnings flew by.  I have a
> complete record of the output of above commands if you want it.
> I ran them thru tee into an accumulative file.
>
> This is my first encounter with `xfce' but I did run `fvwm2' for
> probably 2 years, its been a couple years ago now.  Maybe some
> 3-4.
>
> It seems there are some similarities to fvwm2.
>
> I've been using gnome/sawfish for something like 2-3 years, but it is
> getting really heavy and complicated, requiring more and more
> horsepower just to start it.  I notice a standard (with gnome)
> install now has dozens of gnome related packaged required just to run
> at all.
>
> Can you suggest an outline to arrive at a known state.  And then
> conduct experiments from that point?
>
> Probably start by removing ~/.xfce and let all new files be
> generated. Then maybe instead of copying the example xfwmrc to
> ~/.xfce, maybe build it with one entry at a time.
>
> Maybe just the *xfpager.geometry  line, and nothing else.
>
> ====
> Since the above message, I've done what is suggested there.
> rm -rf ~/.xfce
> mkdir .xfce
>
> Ran make distclean in top directory.
> Using all unedited src files now.
>
> ./configure --prefix=/usr/local
> make
> make install
>
> No errors
>
> startx  Making sure xfce would come up
> I have one simple line in ~/.Xclients-default
>   exec /usr/local/bin/xfwm
>
> It started and seems normal.  closing down X
>
> echo -e "*xfpager.geometry +600+700\n*xfpager.smallfont 5x8" \
>  > ~/.xfce/fwmrc
>
>    startx
> xfce comes up but no pager is visible.
> _______________________________________________
> Xfce mailing list
> Xfce at moongroup.com
> http://moongroup.com/mailman/listinfo/xfce
>

--
It's me -- Delta at SDF Public Access UNIX System - http://sdf.lonestar.org

"I don't advise it, citizen, mn-e-eh... I don't advise it. You'll be eaten."



From reader at newsguy.com  Sun Aug 18 00:46:00 2002
From: reader at newsguy.com (Harry Putnam)
Date: Sat, 17 Aug 2002 15:46:00 -0700
Subject: xfpager, and general observations
In-Reply-To: <Pine.NEB.4.44.0208172125130.13234-100000@otaku.freeshell.org> (Dmitry
 DELTA Malykhanov's message of "Sat, 17 Aug 2002 21:34:01 +0000 (UTC)")
References: <Pine.NEB.4.44.0208172125130.13234-100000@otaku.freeshell.org>
Message-ID: <m3sn1d9k9j.fsf@newsguy.com>

> Harry,
>
> probably the best way will be to move the discussion to the xfce-dev list.
> And if we will solve this mystery, we will post a summary to the general
> xfce list. I'm sending this message to both lists, and I suggest you to
> reply to xfce-dev list only (unless you and/or other xfce users feeling
> that we should stay here).
>
> I'll send detailed instructions how to set up your environment to the
> xfce-dev list later. Is it ok?

Deferring to your judgement on this.  And I'll look for you post here
on xfce-dev.


From d726f6e at SDF.LONESTAR.ORG  Sun Aug 18 02:41:03 2002
From: d726f6e at SDF.LONESTAR.ORG (Dmitry DELTA Malykhanov)
Date: Sun, 18 Aug 2002 00:41:03 +0000 (UTC)
Subject: xfpager, and general observations
In-Reply-To: <m3sn1d9k9j.fsf@newsguy.com>
Message-ID: <Pine.NEB.4.44.0208180009010.1376-100000@otaku.freeshell.org>

Harry,

Here is the description of my own environment, where I'm testing new
window managers, desktop environments and things like this. It's not an
easy thing to configure and use, but it's completely separate from you own
environment and you will not have to restart your X session anymore! IMHO
it's worth the time you'll spend setting it up. Here is the description:

NOTE: I'm running Red Hat 7.3, so package versions on your machine
will be different, packages _names_ should be the same

1. make sure you have the following packages: openssh-server,
openssh-clients and XFree86-Xnest

$ rpm -qa | egrep 'openssh-server|openssh-clients|Xnest'
openssh-server-3.1p1-6
openssh-clients-3.1p1-6
XFree86-Xnest-4.2.0-8


2. make sure sshd is running:
bigtux(dmitry)dmitry>/sbin/service sshd status
sshd (pid 886) is running...

if it's not -- start it (as root)
# /sbin/services sshd start


3. create test user (so any experiments will not affect your real
environment), as root user:
# /usr/sbin/useradd -d /home/xfce -s /bin/bash -c 'XFCE test user' -m xfce

assign valid password (as root user):
# passwd xfce
Changing password for user xfce.
New password: <typing password here>
Retype new password: <typing again>
passwd: all authentication tokens updated successfully.


4. do the following (you must have X11 session running!), in the
xterm (or your favorite termnial under X):

bigtux(dmitry)dmitry>ssh xfce at localhost
The authenticity of host 'localhost (127.0.0.1)' can't be established.
RSA key fingerprint is 6c:10:bb:30:65:3f:77:ff:f0:25:f7:d2:80:6b:d9:f3.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'localhost' (RSA) to the list of known hosts.
xfce at localhost's password:
/usr/X11R6/bin/xauth:  creating new authority file /home/xfce/.Xauthority
[xfce at bigtux xfce]$

NOTE: key fingerprint on you machine will be different. 'bigtux' is my
hostname.


5. make sure that X11 forwarding is working:

[xfce at bigtux xfce]$ xterm

the new xterm should appear, you can close it

Congratulations! Now you have separate environment for experiments.


6. check PATH environment var, to make sure xfce user has access to
your xfce installation:

[xfce at bigtux xfce]$ echo $PATH
/opt/bin:/opt/java/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/xfce/bin

in my case xfce installed under /usr and /usr/bin is in the PATH, so
I'm ok here. On your machine /usr/local/bin must be there


7. as 'xfce' user start Xnest X server (don't forget to put it into
background with '&'):

[xfce at bigtux xfce]$ Xnest :1 &
[1] 2477
[xfce at bigtux xfce]$


8. as 'xfce' user start xterm which will use Xnest server:
[xfce at bigtux xfce]$ xterm -display :1

xterm will appear in the Xnest window ("display"). Note: on the Xnest
"display" there is no window manager yet! That's ok.


9. start your favorite window manager (which is of course xfwm :)) from
the xterm running under Xnest control and you will see WM running into the
Xnest window, under different account and completely isolated from _your_
environment!

[xfce at bigtux xfce]$ xfwm
xfwm message (type main):  Xinerama extension disabled

xfwm message (type SessionInit):  X Session Manager not available
Using builtin session management instead

/home/xfce/.xfce/xfbdrc File not found.
Loading GNOME menus
Loading KDE menus

Now you don't even have to restart Xnest, just exit XFCE (the xterm still
be running) and start it again. And either way, your experiments will not
affect _your_ X11 session, since everything will be running in the
"virtual" X server under different user account. (trick with ssh'ing to
the same host is just an easy way to solve X11 authenticaion issues)

Note: you may wish to run xfce_setup script, before starting xfce
as 'xfce' user under the Xnest control. I didn't, that's why
"/home/xfce/.xfce/xfbdrc File not found." is there and when I'm clicking
on "exit" button on xfce panel it shown dialog window "can't create file".

Note: if you have session management enabled (and by default it is
enabled) xfwm will always start an extra xterm (because it will consider
the already running xterm as a part of current session), just close this
extra xterm.

========================================================================

OK, I hope you will be able to setup such environment, so here goes the
test case for you:

remove everything from /home/xfce/.xfce dir and /home/xfce/.xfwmrc if
there is one. Then try to start xfwm _without_ xfce panel. In order to get
xfpager running, you have to add the following lines to the ~/.xfce/xfwmrc
file:

AddToFunc "InitFunction"
+ "I" Module xfpager
AddToFunc "RestartFunction"
+ "I" Module xfpager

that's because normally xfce panel is starting xfpager for you, but we
don't want to start panel this time. Thus we have to tell xfwm to start
xfpager. Of course, add '*xfpager.geometry +100+300' to the xfwmrc too.

Now start xfwm _without_ xfce panel:

[xfce at bigtux xfce]$ xfwm -noxfce

and tell us what will happen

P.S. And just another crazy idea. You may wish to try my build:

http://d726f6e.freeshell.org/xfce/xfce-3.8.16-2_intl.i386.rpm

actually, it's for Red Hat 7.2, but it should work on your machine.

On Sat, 17 Aug 2002, Harry Putnam wrote:
> > Dmitry Malykhanov wrote:
> > I'll send detailed instructions how to set up your environment to the
> > xfce-dev list later. Is it ok?
>
> Deferring to your judgement on this.  And I'll look for you post here
> on xfce-dev.

--
It's me -- Delta at SDF Public Access UNIX System - http://sdf.lonestar.org

"I don't advise it, citizen, mn-e-eh... I don't advise it. You'll be eaten."



From reader at newsguy.com  Sun Aug 18 04:09:08 2002
From: reader at newsguy.com (Harry Putnam)
Date: Sat, 17 Aug 2002 19:09:08 -0700
Subject: xfpager, and general observations
In-Reply-To: <Pine.NEB.4.44.0208180009010.1376-100000@otaku.freeshell.org> (Dmitry
 DELTA Malykhanov's message of "Sun, 18 Aug 2002 00:41:03 +0000 (UTC)")
References: <Pine.NEB.4.44.0208180009010.1376-100000@otaku.freeshell.org>
Message-ID: <m31y8w9axu.fsf@newsguy.com>

Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:

Got the directions and am proceeding with the setup.  Looks like a
pretty cool way to setup a sand box.

In the meantime, I've been tinkering here and have discovered
something that explains some of the confusion we were discussing
yesterday.

There is an item on pallette (setup tool) on `startup' menu:
[] xfpager
If that isn't checked, no amount of stuff in xfwmrc will make it move
according to geometry settings there.  In fact it seems it will not
even be displayed.  (However, yesterday it was getting displayed but
not moving according to geometry...)

I rm -rf .xfce, rebuilt xfce src package after `make distclean' Using
the original unedited XfwmPager.c src file.

Did mkdir .xfce  and `startx'  Worked good.

So, copied the xfwmrc and started tinkering with xfpager, after [x] in
pallette/startup [x] xfpager.

Now I can shuffle the pager around all I want with geometry settings.
Also I don't see the odd background changing behavior when clicking
[one] window on panel as I did yesterday.

Tail of xfwmrc  (that is all that is changed from the example)
[...]
  ## ==================
  Key e   A CS Exec emacs -geometry +500+300 . 
  Key t   A CS Exec xterm -geometry +600+400
  Key b   A CS Exec netscape -no-about-splash -geometry +400+300
  Key t   A CM xterm -bg midnightblue -fg antiquewhite -title "     SSH SESSION" 
  Key k   A CS Exec xterm -geometry +700+500 -e vim +'/xfpager\.geom' ~/.xfce/xfwmrc
  Key v   A CS Exec gvim -fn 9x15 -geometry +660+460 .xfce
  Key r   A CM Restart
  Key q   A CSM Quit
  Key m   A CS Exec xterm -geometry +500+500 -e mutt
  Key c   A CS Exec xfclock
  Key 1   A CS Exec xterm -geometry +300+350 -bg darkslategrey -fg wheat -e ssh root at localhost
  # Options for xfpager :
  #
  *xfpager.geometry 170x120+1141+1050
  # [HP 08/17/02 17:42  Changing the font seems to have no effect]
  *xfpager.font 9x15

I'm starting work on the setup you describe and will get back to you
when I have it running.


From d726f6e at SDF.LONESTAR.ORG  Sun Aug 18 04:58:23 2002
From: d726f6e at SDF.LONESTAR.ORG (Dmitry DELTA Malykhanov)
Date: Sun, 18 Aug 2002 02:58:23 +0000 (UTC)
Subject: xfpager, and general observations
In-Reply-To: <m31y8w9axu.fsf@newsguy.com>
Message-ID: <Pine.NEB.4.44.0208180237050.9389-100000@otaku.freeshell.org>

Yeah, just try to run it without xfce panel. If it still will not work,
try to install my rpm package (which is the latest "official" stable
version, because 3.8.18 is not an "official" stable release yet).

Anyway, here goes the short explanation, how xfwm starts xfpager module.

xfpager is xfwm module. Which means it _must_ be started by the xfwm. Just
try to start it from the command line, and you'll see

xfpager Version 3.8.16 should only be executed by xfwm!

Somehow xfwm must know that it should start xfpager module. There are
two ways to tell xfwm to do so:
1) you can add appropriate command to the xfwmrc file (those AddToFunc
lines);
2) you can ask xfce panel to send appropriate command to xfwm.

If you have checkbox "Pager (xfpager)" checked (setup dialog, "startup"
tab), then during the startup xfce panel will send a command to xfwm to
spawn xfpager module. Another way is to use panel menu at any time (again
panel will just send a command to xfwm). You can use this if you've killed
xfpager (note: the configuration is still maintained by xfwm, so don't
expect xfpager to pick up new setting from xfwmrc file -- it won't). And
the third way (somehow equivalent to the checkbox) is to modify xfwmrc
file.

Hence, if you don't have 'AddToFunc "InitFunction" + "I" Module xfpager'
line in your xfwmrc file and the checkbox is not checked, XFCE should not
start xfpager.

And I'm sorry, maybe I've missed something. Are you're saying that
sometimes, even if the checkbox is checked or not, and you do NOT have
'AddToFunc "InitFunction" + "I" Module xfpager' in your xfwmrc, xfpager
is still appears when you starting xfce? That's weird. In this case I
would recommend you to roll back to the 3.8.16 release, because it could
be a bug in the session management code in 3.8.18.

On Sat, 17 Aug 2002, Harry Putnam wrote:
>
> In the meantime, I've been tinkering here and have discovered
> something that explains some of the confusion we were discussing
> yesterday.
>
> There is an item on pallette (setup tool) on `startup' menu:
> [] xfpager
> If that isn't checked, no amount of stuff in xfwmrc will make it move
> according to geometry settings there.  In fact it seems it will not
> even be displayed.  (However, yesterday it was getting displayed but
> not moving according to geometry...)
>

--
It's me -- Delta at SDF Public Access UNIX System - http://sdf.lonestar.org

"I don't advise it, citizen, mn-e-eh... I don't advise it. You'll be eaten."



From reader at newsguy.com  Sun Aug 18 05:12:10 2002
From: reader at newsguy.com (Harry Putnam)
Date: Sat, 17 Aug 2002 20:12:10 -0700
Subject: xfpager, and general observations
In-Reply-To: <Pine.NEB.4.44.0208180237050.9389-100000@otaku.freeshell.org> (Dmitry
 DELTA Malykhanov's message of "Sun, 18 Aug 2002 02:58:23 +0000 (UTC)")
References: <Pine.NEB.4.44.0208180237050.9389-100000@otaku.freeshell.org>
Message-ID: <m3u1lsdfn9.fsf@newsguy.com>

Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:

[...] snipped infomative explanations

> And I'm sorry, maybe I've missed something. Are you're saying that
> sometimes, even if the checkbox is checked or not, and you do NOT have
> 'AddToFunc "InitFunction" + "I" Module xfpager' in your xfwmrc, xfpager
> is still appears when you starting xfce? That's weird. In this case I
> would recommend you to roll back to the 3.8.16 release, because it could
> be a bug in the session management code in 3.8.18.

No, I don't see that.  I was suggesting it may have been happening
yesterday, somehow.  For some reason in yesterdays experiments, we
had xfpager run on startup, but would not obey geometry settings.

Unfortunately, I rm 'ed the entire .xfce directory from
yesterday, when setting up a clean start today.  I've seen no
problems today with pager.  Well, I see one, but different.  Not
about geometry.  It seems changing 
   *xfpager.smallfont 5x8
To some other size
   *xfpager.smallfont 9x15
Or even 
  *xfpager.font 9x15 

Seems to have no effect on the pager

I wanted to see if the geometry would grow by itself if the font was
bigger.

PS- Still working on creating the sand box.


From reader at newsguy.com  Sun Aug 18 16:20:55 2002
From: reader at newsguy.com (Harry Putnam)
Date: Sun, 18 Aug 2002 07:20:55 -0700
Subject: xfpager, and general observations
In-Reply-To: <Pine.NEB.4.44.0208180009010.1376-100000@otaku.freeshell.org> (Dmitry
 DELTA Malykhanov's message of "Sun, 18 Aug 2002 00:41:03 +0000 (UTC)")
References: <Pine.NEB.4.44.0208180009010.1376-100000@otaku.freeshell.org>
Message-ID: <m3lm741c54.fsf@newsguy.com>

Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:

> AddToFunc "InitFunction"
> + "I" Module xfpager
> AddToFunc "RestartFunction"
> + "I" Module xfpager
>
> that's because normally xfce panel is starting xfpager for you, but we
> don't want to start panel this time. Thus we have to tell xfwm to start
> xfpager. Of course, add '*xfpager.geometry +100+300' to the xfwmrc too.
>
> Now start xfwm _without_ xfce panel:
>
> [xfce at bigtux xfce]$ xfwm -noxfce
>
> and tell us what will happen

I got the sand box setup with your carefull instructions.  I had no
idea one could setup such a thing.  It all works as you described.

So starting `xfwm -noxfce' with the edited xfwmrc as shown above in your
instructions.  I see the pager at the top of my Xnest window a little
to the right. (and no panel)

Adding this to xfwmrc
  *xfpager.geometry +500+400

And `xfwm -noxfce' 

Brings the pager about center, so its working as it should.

I notice one phenomena.  With no panel, there is no handy way to quit
a session cleanly.  So if you had any xterms running or whatever,
when you ^ c to stop xfwm in the Xnest window.  On next startup you
begin to accumulate xterms in the Xnest sand box.

I tried adding `Key  q   A  CSM Quit' to the sandbox xfwmrc file.  
But when I press the combo, it quits not only Xnest sandbox but my
regular X sesion too!... hehe
Backs me clear out to a console prompt.

I guess one needs the panel in the Xnest sandbox to quit cleanly. 


But I have the test setup working, and ready for experiments.


From d726f6e at SDF.LONESTAR.ORG  Mon Aug 19 02:10:50 2002
From: d726f6e at SDF.LONESTAR.ORG (Dmitry DELTA Malykhanov)
Date: Mon, 19 Aug 2002 00:10:50 +0000 (UTC)
Subject: xfpager, and general observations
In-Reply-To: <m3lm741c54.fsf@newsguy.com>
Message-ID: <Pine.NEB.4.44.0208190001090.22977-100000@otaku.freeshell.org>

On Sun, 18 Aug 2002, Harry Putnam wrote:
>
> So starting `xfwm -noxfce' with the edited xfwmrc as shown above in your
> instructions.  I see the pager at the top of my Xnest window a little
> to the right. (and no panel)
>
> Adding this to xfwmrc
>   *xfpager.geometry +500+400
>
> And `xfwm -noxfce'
>
> Brings the pager about center, so its working as it should.
>

Aha! Maybe your machine is too fast for XFCE... :) And if you will remove
'AddToFunc' lines (but leave xfpager.geometry line) from xfwmrc and start
xfwm, and xfwm will start xfce panel -- just the usual session but in the
sandbox... Please try it and tell us what will happen.

> I notice one phenomena.  With no panel, there is no handy way to quit
> a session cleanly.  So if you had any xterms running or whatever,
> when you ^ c to stop xfwm in the Xnest window.  On next startup you
> begin to accumulate xterms in the Xnest sand box.
>
> I tried adding `Key  q   A  CSM Quit' to the sandbox xfwmrc file.
> But when I press the combo, it quits not only Xnest sandbox but my
> regular X sesion too!... hehe
> Backs me clear out to a console prompt.
>
> I guess one needs the panel in the Xnest sandbox to quit cleanly.

Hmm, it works as it should on my machine. I mean, when I'm choosing
"Quit XFWM" -> "Quit" from the root window pop up menu (left click on the
root window) only the xfwm in the sandbox got killed. My regular session
(which is, of course, xfwm too) is staying alive. I've just tried it.
Maybe it has something to do with startx script. I'm using xdm (no
console).

--
It's me -- Delta at SDF Public Access UNIX System - http://sdf.lonestar.org

"I don't advise it, citizen, mn-e-eh... I don't advise it. You'll be eaten."



From reader at newsguy.com  Mon Aug 19 02:30:02 2002
From: reader at newsguy.com (Harry Putnam)
Date: Sun, 18 Aug 2002 17:30:02 -0700
Subject: xfpager, and general observations
In-Reply-To: <Pine.NEB.4.44.0208190001090.22977-100000@otaku.freeshell.org> (Dmitry
 DELTA Malykhanov's message of "Mon, 19 Aug 2002 00:10:50 +0000 (UTC)")
References: <Pine.NEB.4.44.0208190001090.22977-100000@otaku.freeshell.org>
Message-ID: <m365y7y9kl.fsf@newsguy.com>

Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:

> On Sun, 18 Aug 2002, Harry Putnam wrote:
>>
>> So starting `xfwm -noxfce' with the edited xfwmrc as shown above in your
>> instructions.  I see the pager at the top of my Xnest window a little
>> to the right. (and no panel)
>>
>> Adding this to xfwmrc
>>   *xfpager.geometry +500+400
>>
>> And `xfwm -noxfce'
>>
>> Brings the pager about center, so its working as it should.
>>
>
> Aha! Maybe your machine is too fast for XFCE... :) And if you will remove

What I reported above is correct behavior... is it not?  the geometry
shown should bring pager to about center.  That is what happened.

> 'AddToFunc' lines (but leave xfpager.geometry line) from xfwmrc and start
> xfwm, and xfwm will start xfce panel -- just the usual session but in the
> sandbox... Please try it and tell us what will happen.

With the AddToFunc lines commented out, no pager is started.  panel
started as it should.  Setting the pallette/startup/[x]xfpager and a
restart.  As it should, the  pager appears at geometry specified.  My
current spec from xfwmrc

   *xfpager.geometry 170x120+1141+1050

Puts the pager level with and at the right (just touching) the panel.
And at a size I like.

I haven't been able to duplicate the problems we say previously.

>> I notice one phenomena.  With no panel, there is no handy way to quit
>> a session cleanly.  So if you had any xterms running or whatever,
>> when you ^ c to stop xfwm in the Xnest window.  On next startup you
>> begin to accumulate xterms in the Xnest sand box.
>>
>> I tried adding `Key  q   A  CSM Quit' to the sandbox xfwmrc file.
>> But when I press the combo, it quits not only Xnest sandbox but my
>> regular X sesion too!... hehe
>> Backs me clear out to a console prompt.
>>
>> I guess one needs the panel in the Xnest sandbox to quit cleanly.
>
> Hmm, it works as it should on my machine. I mean, when I'm choosing
> "Quit XFWM" -> "Quit" from the root window pop up menu (left click on the
> root window) only the xfwm in the sandbox got killed. My regular session
> (which is, of course, xfwm too) is staying alive. I've just tried it.
> Maybe it has something to do with startx script. I'm using xdm (no
> console).

Please note that in the above description I didn't use the panel
`quit' button or menu `quit' like you did.  I set a key combo, shown
above, to invoke quit.  When I use that keycombo in the sandbox.  It
quits out of Xnest, and the regular X (also xfce) session.  All
the way out to console mode.

How might I make the panel a bit larger?


From d726f6e at SDF.LONESTAR.ORG  Mon Aug 19 03:21:43 2002
From: d726f6e at SDF.LONESTAR.ORG (Dmitry DELTA Malykhanov)
Date: Mon, 19 Aug 2002 01:21:43 +0000 (UTC)
Subject: xfpager, and general observations
In-Reply-To: <m365y7y9kl.fsf@newsguy.com>
Message-ID: <Pine.NEB.4.44.0208190057500.25633-100000@otaku.freeshell.org>

Bingo! I was able to reproduce your problem on my machine! Though, I must
admit, I can not explain it. :( Maybe Olivier can help us. I have to look
closer to the way, how xfwm starts modules.

Right now I have one more question: are you using the same shell as 'xfce'
user (or whatever sandbox owner username is on your machine)? Hmm, xfwm is
using execvp function, to spawn the module... It has nothing to do with
the shell... But that's the only idea I have now. Please make sure that
your account and xfce test user account have the same shell and the same
PATH.

Here is the explanation, how I managed to reproduce the problem:

I though I may have something to do with timing during the
xfwm-xfce-xfpager communications, and I was going to suggest you to delay
xfpager startup. But when I've decided to try it on my machine, I suddely
got exactly the same behaviour: not matter, what is in the xfwmrc file,
xfwm has it's own idea of xfpager location (ignoring xfpager.geometry
settings).

What I did: I moved xfpager binary to xfpager.bin and wrote short shell
wrapper.

-- xfpager wrapper starts --
#!/bin/bin

sleep 5
exec xfpager.bin ${1:+"$@"}

# EOF
-- xfpager wrapper ends --

In fact, I can remove 'sleep 5' line, and xfpager will still ignore
geometry settings. But when I remove this wrapper script and allow xfwm to
execute xfpager binary directly everything works, and xfpager is always
taking the designated place on the screen. Very strange. I will look at
the xfwm<->module communication code.

P.S. the behaviour of the "Quit" function on your box still looks
strange. AFAIK no matter which "Exit"/"Quit" button you are clicking, the
same "Quit" command got sent to the xfwm process.

On Sun, 18 Aug 2002, Harry Putnam wrote:

> Date: Sun, 18 Aug 2002 17:30:02 -0700
> From: Harry Putnam <reader at newsguy.com>
> Reply-To: xfce-dev at moongroup.com
> To: xfce-dev at moongroup.com
> Subject: Re: xfpager, and general observations
>
> Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:
>
> > On Sun, 18 Aug 2002, Harry Putnam wrote:
> >>
> >> So starting `xfwm -noxfce' with the edited xfwmrc as shown above in your
> >> instructions.  I see the pager at the top of my Xnest window a little
> >> to the right. (and no panel)
> >>
> >> Adding this to xfwmrc
> >>   *xfpager.geometry +500+400
> >>
> >> And `xfwm -noxfce'
> >>
> >> Brings the pager about center, so its working as it should.
> >>
> >
> > Aha! Maybe your machine is too fast for XFCE... :) And if you will remove
>
> What I reported above is correct behavior... is it not?  the geometry
> shown should bring pager to about center.  That is what happened.
>
> > 'AddToFunc' lines (but leave xfpager.geometry line) from xfwmrc and start
> > xfwm, and xfwm will start xfce panel -- just the usual session but in the
> > sandbox... Please try it and tell us what will happen.
>
> With the AddToFunc lines commented out, no pager is started.  panel
> started as it should.  Setting the pallette/startup/[x]xfpager and a
> restart.  As it should, the  pager appears at geometry specified.  My
> current spec from xfwmrc
>
>    *xfpager.geometry 170x120+1141+1050
>
> Puts the pager level with and at the right (just touching) the panel.
> And at a size I like.
>
> I haven't been able to duplicate the problems we say previously.
>
> >> I notice one phenomena.  With no panel, there is no handy way to quit
> >> a session cleanly.  So if you had any xterms running or whatever,
> >> when you ^ c to stop xfwm in the Xnest window.  On next startup you
> >> begin to accumulate xterms in the Xnest sand box.
> >>
> >> I tried adding `Key  q   A  CSM Quit' to the sandbox xfwmrc file.
> >> But when I press the combo, it quits not only Xnest sandbox but my
> >> regular X sesion too!... hehe
> >> Backs me clear out to a console prompt.
> >>
> >> I guess one needs the panel in the Xnest sandbox to quit cleanly.
> >
> > Hmm, it works as it should on my machine. I mean, when I'm choosing
> > "Quit XFWM" -> "Quit" from the root window pop up menu (left click on the
> > root window) only the xfwm in the sandbox got killed. My regular session
> > (which is, of course, xfwm too) is staying alive. I've just tried it.
> > Maybe it has something to do with startx script. I'm using xdm (no
> > console).
>
> Please note that in the above description I didn't use the panel
> `quit' button or menu `quit' like you did.  I set a key combo, shown
> above, to invoke quit.  When I use that keycombo in the sandbox.  It
> quits out of Xnest, and the regular X (also xfce) session.  All
> the way out to console mode.
>
> How might I make the panel a bit larger?
> _______________________________________________
> Xfce-dev mailing list
> Xfce-dev at moongroup.com
> http://moongroup.com/mailman/listinfo/xfce-dev
>

--
It's me -- Delta at SDF Public Access UNIX System - http://sdf.lonestar.org

"I don't advise it, citizen, mn-e-eh... I don't advise it. You'll be eaten."



From d726f6e at SDF.LONESTAR.ORG  Mon Aug 19 04:13:46 2002
From: d726f6e at SDF.LONESTAR.ORG (Dmitry DELTA Malykhanov)
Date: Mon, 19 Aug 2002 02:13:46 +0000 (UTC)
Subject: xfpager, and general observations
In-Reply-To: <Pine.NEB.4.44.0208190057500.25633-100000@otaku.freeshell.org>
Message-ID: <Pine.NEB.4.44.0208190206330.25633-100000@otaku.freeshell.org>

OK, it's pretty clear, why it doesn't work. xfpager actually looking for
the string "*%s.geometry", where %s is argv[0]. Of course, in my example
argv[0] is "xfpager.bin" and xfwm sends the line "*xfpager.geometry".

Harry, could you please add one more line to the code, dumping incoming
commands to the file (just next to the existing fprintf statement):

fprintf(log, "MyName = %s\n", MyName);

use this modified binary and post output here.

On Mon, 19 Aug 2002, Dmitry DELTA Malykhanov wrote:
>
> What I did: I moved xfpager binary to xfpager.bin and wrote short shell
> wrapper.
>
> -- xfpager wrapper starts --
> #!/bin/bin
>
> sleep 5
> exec xfpager.bin ${1:+"$@"}
>
> # EOF
> -- xfpager wrapper ends --
>
> In fact, I can remove 'sleep 5' line, and xfpager will still ignore
> geometry settings. But when I remove this wrapper script and allow xfwm to
> execute xfpager binary directly everything works, and xfpager is always
> taking the designated place on the screen. Very strange. I will look at
> the xfwm<->module communication code.
>
> P.S. the behaviour of the "Quit" function on your box still looks
> strange. AFAIK no matter which "Exit"/"Quit" button you are clicking, the
> same "Quit" command got sent to the xfwm process.
>
> On Sun, 18 Aug 2002, Harry Putnam wrote:
>
> > Date: Sun, 18 Aug 2002 17:30:02 -0700
> > From: Harry Putnam <reader at newsguy.com>
> > Reply-To: xfce-dev at moongroup.com
> > To: xfce-dev at moongroup.com
> > Subject: Re: xfpager, and general observations
> >
> > Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:
> >
> > > On Sun, 18 Aug 2002, Harry Putnam wrote:
> > >>
> > >> So starting `xfwm -noxfce' with the edited xfwmrc as shown above in your
> > >> instructions.  I see the pager at the top of my Xnest window a little
> > >> to the right. (and no panel)
> > >>
> > >> Adding this to xfwmrc
> > >>   *xfpager.geometry +500+400
> > >>
> > >> And `xfwm -noxfce'
> > >>
> > >> Brings the pager about center, so its working as it should.
> > >>
> > >
> > > Aha! Maybe your machine is too fast for XFCE... :) And if you will remove
> >
> > What I reported above is correct behavior... is it not?  the geometry
> > shown should bring pager to about center.  That is what happened.
> >
> > > 'AddToFunc' lines (but leave xfpager.geometry line) from xfwmrc and start
> > > xfwm, and xfwm will start xfce panel -- just the usual session but in the
> > > sandbox... Please try it and tell us what will happen.
> >
> > With the AddToFunc lines commented out, no pager is started.  panel
> > started as it should.  Setting the pallette/startup/[x]xfpager and a
> > restart.  As it should, the  pager appears at geometry specified.  My
> > current spec from xfwmrc
> >
> >    *xfpager.geometry 170x120+1141+1050
> >
> > Puts the pager level with and at the right (just touching) the panel.
> > And at a size I like.
> >
> > I haven't been able to duplicate the problems we say previously.
> >
> > >> I notice one phenomena.  With no panel, there is no handy way to quit
> > >> a session cleanly.  So if you had any xterms running or whatever,
> > >> when you ^ c to stop xfwm in the Xnest window.  On next startup you
> > >> begin to accumulate xterms in the Xnest sand box.
> > >>
> > >> I tried adding `Key  q   A  CSM Quit' to the sandbox xfwmrc file.
> > >> But when I press the combo, it quits not only Xnest sandbox but my
> > >> regular X sesion too!... hehe
> > >> Backs me clear out to a console prompt.
> > >>
> > >> I guess one needs the panel in the Xnest sandbox to quit cleanly.
> > >
> > > Hmm, it works as it should on my machine. I mean, when I'm choosing
> > > "Quit XFWM" -> "Quit" from the root window pop up menu (left click on the
> > > root window) only the xfwm in the sandbox got killed. My regular session
> > > (which is, of course, xfwm too) is staying alive. I've just tried it.
> > > Maybe it has something to do with startx script. I'm using xdm (no
> > > console).
> >
> > Please note that in the above description I didn't use the panel
> > `quit' button or menu `quit' like you did.  I set a key combo, shown
> > above, to invoke quit.  When I use that keycombo in the sandbox.  It
> > quits out of Xnest, and the regular X (also xfce) session.  All
> > the way out to console mode.
> >
> > How might I make the panel a bit larger?
> > _______________________________________________
> > Xfce-dev mailing list
> > Xfce-dev at moongroup.com
> > http://moongroup.com/mailman/listinfo/xfce-dev
> >
>
> --
> It's me -- Delta at SDF Public Access UNIX System - http://sdf.lonestar.org
>
> "I don't advise it, citizen, mn-e-eh... I don't advise it. You'll be eaten."
>
> _______________________________________________
> Xfce-dev mailing list
> Xfce-dev at moongroup.com
> http://moongroup.com/mailman/listinfo/xfce-dev
>

--
It's me -- Delta at SDF Public Access UNIX System - http://sdf.lonestar.org

"I don't advise it, citizen, mn-e-eh... I don't advise it. You'll be eaten."



From reader at newsguy.com  Mon Aug 19 04:26:25 2002
From: reader at newsguy.com (Harry Putnam)
Date: Sun, 18 Aug 2002 19:26:25 -0700
Subject: xfpager, and general observations
In-Reply-To: <Pine.NEB.4.44.0208190057500.25633-100000@otaku.freeshell.org> (Dmitry
 DELTA Malykhanov's message of "Mon, 19 Aug 2002 01:21:43 +0000 (UTC)")
References: <Pine.NEB.4.44.0208190057500.25633-100000@otaku.freeshell.org>
Message-ID: <m3fzxbwpm6.fsf@newsguy.com>

Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:

> Bingo! I was able to reproduce your problem on my machine! Though, I must
> admit, I can not explain it. :( Maybe Olivier can help us. I have to look
> closer to the way, how xfwm starts modules.

Well at least I wasn't dreaming...

> Right now I have one more question: are you using the same shell as 'xfce'
> user (or whatever sandbox owner username is on your machine)? Hmm, xfwm is
> using execvp function, to spawn the module... It has nothing to do with
> the shell... But that's the only idea I have now. Please make sure that
> your account and xfce test user account have the same shell and the same
> PATH.

My dummy user is `wm'. It has the same shell and shell init files as me
`reader'.  I just copied .bashrc .bash_profile over.
The path is identical too.

> Here is the explanation, how I managed to reproduce the problem:
>
> I though I may have something to do with timing during the
> xfwm-xfce-xfpager communications, and I was going to suggest you to delay
> xfpager startup. But when I've decided to try it on my machine, I suddely
> got exactly the same behaviour: not matter, what is in the xfwmrc file,
> xfwm has it's own idea of xfpager location (ignoring xfpager.geometry
> settings).

Can you look at palette/Startup/[]xfpager at that point and see if it
is checked or not?  (Just a long shot)

Also, if there is something in xfwmrc that causes an error, will that
cause the geometry setting to be ignored?

> P.S. the behaviour of the "Quit" function on your box still looks
> strange. AFAIK no matter which "Exit"/"Quit" button you are clicking, the
> same "Quit" command got sent to the xfwm process.

It turned out to be something really dumb.  I had set the same key
combo in `wm' .xfce/xfwmrc   as in `reader' .xfce/xfwmrc

Key q  A CSM  In both rc files.  So pressing that combo backed me
clear out to console.

After changing the combo in the sandbox rc file.  It doesn't happen.


From reader at newsguy.com  Mon Aug 19 05:37:10 2002
From: reader at newsguy.com (Harry Putnam)
Date: Sun, 18 Aug 2002 20:37:10 -0700
Subject: xfpager, and general observations
In-Reply-To: <Pine.NEB.4.44.0208190206330.25633-100000@otaku.freeshell.org> (Dmitry
 DELTA Malykhanov's message of "Mon, 19 Aug 2002 02:13:46 +0000 (UTC)")
References: <Pine.NEB.4.44.0208190206330.25633-100000@otaku.freeshell.org>
Message-ID: <m3hehrv7w1.fsf@newsguy.com>

Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:

> Harry, could you please add one more line to the code, dumping incoming
> commands to the file (just next to the existing fprintf statement):
>
> fprintf(log, "MyName = %s\n", MyName);

Not sure what you wnat here.  Existing code looks like this:
 (beginning line 871
871 while (tline != NULL)
872   {
873     int g_x, g_y, flags;
874     unsigned width, height;
875
876 	 FILE *log;
877	 if( (log=fopen("/home/reader/XFPAGER.LOG", "a+"))!=NULL ) {
878				  fprintf(log, "%s", tline);
879				    fclose(log);
880	  }				 

Where does the new line go?  And what does it actually do?


From d726f6e at SDF.LONESTAR.ORG  Mon Aug 19 05:47:02 2002
From: d726f6e at SDF.LONESTAR.ORG (Dmitry DELTA Malykhanov)
Date: Mon, 19 Aug 2002 03:47:02 +0000 (UTC)
Subject: xfpager, and general observations
In-Reply-To: <m3hehrv7w1.fsf@newsguy.com>
Message-ID: <Pine.NEB.4.44.0208190339430.25633-100000@otaku.freeshell.org>

Just add it after the line 878 (see below)

On Sun, 18 Aug 2002, Harry Putnam wrote:
> > Harry, could you please add one more line to the code, dumping incoming
> > commands to the file (just next to the existing fprintf statement):
> >
> > fprintf(log, "MyName = %s\n", MyName);
>
> Not sure what you wnat here.  Existing code looks like this:
>  (beginning line 871
> 871 while (tline != NULL)
> 872   {
> 873     int g_x, g_y, flags;
> 874     unsigned width, height;
> 875
> 876 	 FILE *log;
> 877	 if( (log=fopen("/home/reader/XFPAGER.LOG", "a+"))!=NULL ) {
> 878				  fprintf(log, "%s", tline);
                                  fprintf(log, "MyName = %s\n", MyName);
> 879				    fclose(log);
> 880	  }
>
> Where does the new line go?  And what does it actually do?

This line will show us what the xfpager "thinks" about it's own name. When
xfpager is reading the configuration, it's looking for strings starting
from *${MyName}.PARAMETER (where MyName is something derived from the
argv[0], actually, a sort of basename() equivalent). If the name used by
the xfpager internally is not "xfpager" for same reason, it will be unable
to process it's own configuration. For example, in my case (after moving
xfpager to xfpager.bin), the pager was looking for string
"*xfpager.bin.geometry", not "*xfpager.geometry".

--
It's me -- Delta at SDF Public Access UNIX System - http://sdf.lonestar.org

"I don't advise it, citizen, mn-e-eh... I don't advise it. You'll be eaten."



From reader at newsguy.com  Mon Aug 19 06:32:46 2002
From: reader at newsguy.com (Harry Putnam)
Date: Sun, 18 Aug 2002 21:32:46 -0700
Subject: xfpager, and general observations
In-Reply-To: <Pine.NEB.4.44.0208190206330.25633-100000@otaku.freeshell.org> (Dmitry
 DELTA Malykhanov's message of "Mon, 19 Aug 2002 02:13:46 +0000 (UTC)")
References: <Pine.NEB.4.44.0208190206330.25633-100000@otaku.freeshell.org>
Message-ID: <m34rdr1n9t.fsf@newsguy.com>

Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:

> OK, it's pretty clear, why it doesn't work. xfpager actually looking for
> the string "*%s.geometry", where %s is argv[0]. Of course, in my example
> argv[0] is "xfpager.bin" and xfwm sends the line "*xfpager.geometry".
>
> Harry, could you please add one more line to the code, dumping incoming
> commands to the file (just next to the existing fprintf statement):
>
> fprintf(log, "MyName = %s\n", MyName);
>
> use this modified binary and post output here.

Not sure how you expect xfwmrc to be setup so I post first everthing
from xfwmrc about xfpager

  Style "xfpager"         Sticky
  *xfpager.geometry 170x120+1141+1050
  # [HP 08/17/02 17:42  Changing the font seems to have no effect]
  *xfpager.font 9x15

Also palette/Startup/xfpager is checked [x]

On a startup of xfwm this is reported to log.

cat XFPAGER.LOG
  ClickTime 300
  MyName = xfpager
  *xfpager.geometry 170x120+1141+1050
  MyName = xfpager
  *xfpager.font 9x15
  MyName = xfpager


From d726f6e at SDF.LONESTAR.ORG  Mon Aug 19 07:01:52 2002
From: d726f6e at SDF.LONESTAR.ORG (Dmitry DELTA Malykhanov)
Date: Mon, 19 Aug 2002 05:01:52 +0000 (UTC)
Subject: xfpager, and general observations
In-Reply-To: <m34rdr1n9t.fsf@newsguy.com>
Message-ID: <Pine.NEB.4.44.0208190443490.8677-100000@otaku.freeshell.org>

Thanks. That's exactly what I was asking for. I wish that all my customers
were like you. ;)

I assume that pager still appears at +0+0, does it? Well, in this case
that was another bad idea. :( Your xfpager thinks that it's name is
"xfpager". Hence it should be able to parse configuration.

If you are not tired yet, we can try one more thing. Please download this
tarball http://d726f6e.freeshell.org/xfce/xfpgr.tar.gz (it contains 2
files) and put those files under WHERE_YOU_KEEP_XFCE_SOURCE/xfpager/
(replacing existing XfwmPager.c and x_pager.c). There are a lot
modifications there, so it will be easier for you to download modified
files, instead of applying the diffs. Then just recompile xfpager one
more time.

Once you will have the modifed xfpager installed, just do the usual thing
-- restart xfwm/xfce (keep your xfwmrc file the same, and keep checkbox
checked), and post the XFPAGER.LOG here. NOTE: my code will create
XFPAGER.LOG file in /tmp

On Sun, 18 Aug 2002, Harry Putnam wrote:
>
> Not sure how you expect xfwmrc to be setup so I post first everthing
> from xfwmrc about xfpager
>
>   Style "xfpager"         Sticky
>   *xfpager.geometry 170x120+1141+1050
>   # [HP 08/17/02 17:42  Changing the font seems to have no effect]
>   *xfpager.font 9x15
>
> Also palette/Startup/xfpager is checked [x]
>
> On a startup of xfwm this is reported to log.
>
> cat XFPAGER.LOG
>   ClickTime 300
>   MyName = xfpager
>   *xfpager.geometry 170x120+1141+1050
>   MyName = xfpager
>   *xfpager.font 9x15
>   MyName = xfpager
>

--
It's me -- Delta at SDF Public Access UNIX System - http://sdf.lonestar.org

"I don't advise it, citizen, mn-e-eh... I don't advise it. You'll be eaten."



From reader at newsguy.com  Mon Aug 19 07:22:04 2002
From: reader at newsguy.com (Harry Putnam)
Date: Sun, 18 Aug 2002 22:22:04 -0700
Subject: xfpager, and general observations
In-Reply-To: <Pine.NEB.4.44.0208190443490.8677-100000@otaku.freeshell.org> (Dmitry
 DELTA Malykhanov's message of "Mon, 19 Aug 2002 05:01:52 +0000 (UTC)")
References: <Pine.NEB.4.44.0208190443490.8677-100000@otaku.freeshell.org>
Message-ID: <m3sn1bzamb.fsf@newsguy.com>

Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:

> I assume that pager still appears at +0+0, does it? Well, in this case
> that was another bad idea. :( Your xfpager thinks that it's name is
> "xfpager". Hence it should be able to parse configuration.

No, the pager appears where the geometry says.  I haven't seen the
geometry be ignored since yesterday.  I've reported that I am not
seeing the ignoring problem.  Haven't since the rm'ing .xfce and
starting over this morning. 


From d726f6e at SDF.LONESTAR.ORG  Mon Aug 19 07:33:25 2002
From: d726f6e at SDF.LONESTAR.ORG (Dmitry DELTA Malykhanov)
Date: Mon, 19 Aug 2002 05:33:25 +0000 (UTC)
Subject: xfpager, and general observations
In-Reply-To: <m3sn1bzamb.fsf@newsguy.com>
Message-ID: <Pine.NEB.4.44.0208190526491.8677-100000@otaku.freeshell.org>

So everything works as expected? Cool.

Unfortunately, we haven't found the root of the problem (was is a typo in
your xfwmrc or hard-to-find bug in xfce). But if it's working for you
now... Probably we should put it on hold, until you will experience it
again. What do you think?

P.S. BTW, my problem with xmms refusing to stay sticky came back, however
the xfpager is still honoring the geometry settings.

On Sun, 18 Aug 2002, Harry Putnam wrote:
> Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:
>
> > I assume that pager still appears at +0+0, does it? Well, in this case
> > that was another bad idea. :( Your xfpager thinks that it's name is
> > "xfpager". Hence it should be able to parse configuration.
>
> No, the pager appears where the geometry says.  I haven't seen the
> geometry be ignored since yesterday.  I've reported that I am not
> seeing the ignoring problem.  Haven't since the rm'ing .xfce and
> starting over this morning.
>

--
It's me -- Delta at SDF Public Access UNIX System - http://sdf.lonestar.org

"I don't advise it, citizen, mn-e-eh... I don't advise it. You'll be eaten."



From reader at newsguy.com  Mon Aug 19 07:37:51 2002
From: reader at newsguy.com (Harry Putnam)
Date: Sun, 18 Aug 2002 22:37:51 -0700
Subject: xfpager, and general observations
In-Reply-To: <Pine.NEB.4.44.0208190526491.8677-100000@otaku.freeshell.org> (Dmitry
 DELTA Malykhanov's message of "Mon, 19 Aug 2002 05:33:25 +0000 (UTC)")
References: <Pine.NEB.4.44.0208190526491.8677-100000@otaku.freeshell.org>
Message-ID: <m3n0rjz9w0.fsf@newsguy.com>

Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:

> So everything works as expected? Cool.

Yes,  Sorry I thought I had made that clear several messages back.

> Unfortunately, we haven't found the root of the problem (was is a typo in
> your xfwmrc or hard-to-find bug in xfce). But if it's working for you
> now... Probably we should put it on hold, until you will experience it
> again. What do you think?

Yes, but is there something else that needs work?


From reader at newsguy.com  Mon Aug 19 07:43:18 2002
From: reader at newsguy.com (Harry Putnam)
Date: Sun, 18 Aug 2002 22:43:18 -0700
Subject: xfpager, and general observations
In-Reply-To: <Pine.NEB.4.44.0208190443490.8677-100000@otaku.freeshell.org> (Dmitry
 DELTA Malykhanov's message of "Mon, 19 Aug 2002 05:01:52 +0000 (UTC)")
References: <Pine.NEB.4.44.0208190443490.8677-100000@otaku.freeshell.org>
Message-ID: <m3bs7zz9mx.fsf@newsguy.com>

Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:

> Once you will have the modifed xfpager installed, just do the usual thing
> -- restart xfwm/xfce (keep your xfwmrc file the same, and keep checkbox
> checked), and post the XFPAGER.LOG here. NOTE: my code will create
> XFPAGER.LOG file in /tmp

For the record.  A restart shows this in the log.
Should the prefix number be the same like that?

cat /tmp/XFPAGER.LOG

  22517: ClickTime 300
  22517: length = 14
  22517: *xfpager.geometry 170x120+1141+1050
  22517: length = 36
  22517: ParseOptions geometry spec '*xfpager.geometry 170x120+1141+1050
  '
  22517: ParseOptions() geometry '170x120+1141+1050'
  22517: *xfpager.font 9x15
  22517: length = 19
  22517: MyName = 'xfpager'
  22517: ParseOptions() window_x = 1141 window_y = 1050
  22517: initialize_pager() hasConfig = 1
  22517: initialize_pager() window_x = 1141 window_y = 1050


From d726f6e at SDF.LONESTAR.ORG  Mon Aug 19 07:45:49 2002
From: d726f6e at SDF.LONESTAR.ORG (Dmitry DELTA Malykhanov)
Date: Mon, 19 Aug 2002 05:45:49 +0000 (UTC)
Subject: xfpager, and general observations
In-Reply-To: <m3n0rjz9w0.fsf@newsguy.com>
Message-ID: <Pine.NEB.4.44.0208190542560.8677-100000@otaku.freeshell.org>

On Sun, 18 Aug 2002, Harry Putnam wrote:
> Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:
>
> > So everything works as expected? Cool.
>
> Yes,  Sorry I thought I had made that clear several messages back.

No, that's fine. I just had a crazy weekend. :) Tried to do a lot of
things as the same time.

> > Unfortunately, we haven't found the root of the problem (was is a typo in
> > your xfwmrc or hard-to-find bug in xfce). But if it's working for you
> > now... Probably we should put it on hold, until you will experience it
> > again. What do you think?
>
> Yes, but is there something else that needs work?

Well, we always can think of something... :)

--
It's me -- Delta at SDF Public Access UNIX System - http://sdf.lonestar.org

"I don't advise it, citizen, mn-e-eh... I don't advise it. You'll be eaten."



From d726f6e at SDF.LONESTAR.ORG  Mon Aug 19 07:52:42 2002
From: d726f6e at SDF.LONESTAR.ORG (Dmitry DELTA Malykhanov)
Date: Mon, 19 Aug 2002 05:52:42 +0000 (UTC)
Subject: xfpager, and general observations
In-Reply-To: <m3bs7zz9mx.fsf@newsguy.com>
Message-ID: <Pine.NEB.4.44.0208190546160.8677-100000@otaku.freeshell.org>

OK, just a short explanation. Those prefix numbers are just xfpager
process id. I've added this to distinguish output of the differnt xfpager
instances. Please see below my comments to the output.

On Sun, 18 Aug 2002, Harry Putnam wrote:
> Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:
>
> > Once you will have the modifed xfpager installed, just do the usual thing
> > -- restart xfwm/xfce (keep your xfwmrc file the same, and keep checkbox
> > checked), and post the XFPAGER.LOG here. NOTE: my code will create
> > XFPAGER.LOG file in /tmp
>
> For the record.  A restart shows this in the log.
> Should the prefix number be the same like that?
>
> cat /tmp/XFPAGER.LOG
>
>   22517: ClickTime 300
>   22517: length = 14
>   22517: *xfpager.geometry 170x120+1141+1050
xfpager was able to establish communication with xfwm process and
request configuration parameters

>   22517: length = 36
>   22517: ParseOptions geometry spec '*xfpager.geometry 170x120+1141+1050
>   '
it found string describing the desired geometry

>   22517: ParseOptions() geometry '170x120+1141+1050'
>   22517: *xfpager.font 9x15
>   22517: length = 19
>   22517: MyName = 'xfpager'
>   22517: ParseOptions() window_x = 1141 window_y = 1050
internal variables have been initialized with the proper values (it
matches the geometry description from above)

>   22517: initialize_pager() hasConfig = 1
>   22517: initialize_pager() window_x = 1141 window_y = 1050
this happened right before asking X server to create a new window for
xfpager. requsted location matches the geometry specification.

Everything works as expected!

--
It's me -- Delta at SDF Public Access UNIX System - http://sdf.lonestar.org

"I don't advise it, citizen, mn-e-eh... I don't advise it. You'll be eaten."



From reader at newsguy.com  Mon Aug 19 08:14:29 2002
From: reader at newsguy.com (Harry Putnam)
Date: Sun, 18 Aug 2002 23:14:29 -0700
Subject: xfpager, and general observations
In-Reply-To: <Pine.NEB.4.44.0208190546160.8677-100000@otaku.freeshell.org> (Dmitry
 DELTA Malykhanov's message of "Mon, 19 Aug 2002 05:52:42 +0000 (UTC)")
References: <Pine.NEB.4.44.0208190546160.8677-100000@otaku.freeshell.org>
Message-ID: <m365y7z86y.fsf@newsguy.com>

Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:

> OK, just a short explanation. Those prefix numbers are just xfpager
> process id. I've added this to distinguish output of the differnt xfpager
> instances. Please see below my comments to the output.

Thanks Dmitry.... nice explanation....

I'm off to bed now..


From fourdan at xfce.org  Sat Aug 24 15:55:06 2002
From: fourdan at xfce.org (Olivier Fourdan)
Date: 24 Aug 2002 15:55:06 +0200
Subject: xfce-3.8.18 ?
Message-ID: <1030197307.22266.0.camel@localhost>

Hi all,

Anything that needs to be done/merged/fixed before 3.8.18 ?

Let me know.

Cheers,
-- 
Olivier               <fourdan at xfce.org>            http://www.xfce.org
-----------------------------------------------------------------------
XFce is a lightweight  desktop  environment  for  various *NIX systems. 
Designed for productivity,  it loads  and  executes  applications fast,
while conserving  system resources. XFce is all free software, released
under GNU General Public License.    Available from http://www.xfce.org



From huysmans at users.sourceforge.net  Sat Aug 24 16:11:50 2002
From: huysmans at users.sourceforge.net (Jasper Huijsmans)
Date: Sat, 24 Aug 2002 16:11:50 +0200
Subject: xfce-3.8.18 ?
In-Reply-To: <1030197307.22266.0.camel@localhost>
References: <1030197307.22266.0.camel@localhost>
Message-ID: <20020824161150.1cdc9ce9.huysmans@users.sourceforge.net>

On 24 Aug 2002 15:55:06 +0200
Olivier Fourdan <fourdan at xfce.org> wrote:

> Hi all,
> 
> Anything that needs to be done/merged/fixed before 3.8.18 ?
> 

This would be nice to have I guess, but there's no way for me to test
it:

http://moongroup.com/pipermail/xfce/2002-July/001437.html

It's a patch to integrate the mandrake menu.

Jasper

> Let me know.
> 
> Cheers,
> -- 
> Olivier               <fourdan at xfce.org>           
> http://www.xfce.org
> ---------------------------------------------------------------------
> -- XFce is a lightweight  desktop  environment  for  various *NIX
> systems. Designed for productivity,  it loads  and  executes 
> applications fast, while conserving  system resources. XFce is all
> free software, released under GNU General Public License.    Available
> from http://www.xfce.org
> 
> _______________________________________________
> Xfce-dev mailing list
> Xfce-dev at moongroup.com
> http://moongroup.com/mailman/listinfo/xfce-dev


-- 
IRC channel: #xfce on irc.openprojects.net


From edscott at imp.mx  Mon Aug 26 17:48:05 2002
From: edscott at imp.mx (edscott wilson garcia)
Date: 26 Aug 2002 10:48:05 -0500
Subject: xfce-3.8.18 ?
In-Reply-To: <1030197307.22266.0.camel@localhost>
References: <1030197307.22266.0.camel@localhost>
Message-ID: <1030376891.9981.143.camel@sagitario.eco.imp.mx>

On Sat, 2002-08-24 at 08:55, Olivier Fourdan wrote:
> Hi all,
> 
> Anything that needs to be done/merged/fixed before 3.8.18 ?
> 
> Let me know.

There's a couple fixes which should be applied to xftree. Just give me a
couple days to get it done. Basically it's finding and fixing a memory
leak in the dialog routines which causes ocasional crashes in Linux and
ocasional hangs in FreeBSD. 

saludos,

Edscott





From gammonj at indy.raytheon.com  Mon Aug 26 23:26:52 2002
From: gammonj at indy.raytheon.com (Gammon, John P)
Date: Mon, 26 Aug 2002 16:26:52 -0500
Subject: libgcc_s.so.1....
Message-ID: <AC6C0CB8F0B47A4FA7BB94B1BF463EA0244F1C@maila.indy.navy.mil>

I downloaded the XFCE4 and XFWM4 from the sourceforge.net location.  I also
went to ftp.gtk.org and downloaded the latest gtk+ and glib files (1.2.10).

I went to install the xfce4 and everything went fine.  However, when I went
to install the xfwm4, I get the message libgcc_s.so.1 is needed by
xfwm4-020724-1.

Where can I find this file and install it (or its owner package) on my
computer?

Thanks.

zorkerbatman


From edscott at imp.mx  Tue Aug 27 22:36:00 2002
From: edscott at imp.mx (edscott wilson garcia)
Date: 27 Aug 2002 15:36:00 -0500
Subject: xftree fixes for 3.18
Message-ID: <1030480560.22926.60.camel@mateco8.eco.imp.mx>

Hi,

  I just updated the CVS with a fix to what I believe was causing the
sporadic crashes of xftree in Linux with the open-with dialog
(referencing a null pointer in reg.c). I also corrected an incorrect
parsing for register application in gtk_exec.c. I'll try to locate and
fix the "hang on file-copy error dialog" which surfaces in FreeBSD.

saludos

Edscott




From edscott at imp.mx  Thu Aug 29 04:18:29 2002
From: edscott at imp.mx (edscott wilson garcia)
Date: 28 Aug 2002 21:18:29 -0500
Subject: on xftree
Message-ID: <1030587512.4188.54.camel@sagitario.eco.imp.mx>

I still haven't been able to find out why xftree hangs when a copy
operation fails in FreeBSD. It seems that stopping the flow of a pipe
has more adverse affect than in Linux, maybe. Gdb tells me the program
is at a pipe "read()", which it shouldn't since the flow has stopped.

Anyways, while looking I eliminated a different, but weird, bug. Remote
instances of xftree would think some xtree.reg entries were stale. To
avoid it, stale entries will now only be cleaned when DISPLAY is :0.0

I think I should also put in a small option to eliminate the fancy icons
and fall back to the basic xftree icons. This could be a workaround for
that inability surfaces here-and-there for the Xserver to deal with the
pixmaps. 

Edscott





From gammonj at indy.raytheon.com  Thu Aug 29 18:36:10 2002
From: gammonj at indy.raytheon.com (Gammon, John P)
Date: Thu, 29 Aug 2002 11:36:10 -0500
Subject: libgcc_s.so.1 needed...
Message-ID: <AC6C0CB8F0B47A4FA7BB94B1BF463EA0244F27@maila.indy.navy.mil>

Can someone please look up this file and see what package it belongs to?  I
need to download it and install it.

It seems the only way that I will get the XFCE4 to work.

Thanks.

John Gammon
work - gammonj at indy.raytheon.com
personal - zorkerbatman at hotmail.com

-----Original Message-----
From: Gammon, John P [mailto:gammonj at indy.raytheon.com]
Sent: Monday, August 26, 2002 4:27 PM
To: 'xfce-dev at moongroup.com'
Subject: libgcc_s.so.1....


I downloaded the XFCE4 and XFWM4 from the sourceforge.net location.  I also
went to ftp.gtk.org and downloaded the latest gtk+ and glib files (1.2.10).

I went to install the xfce4 and everything went fine.  However, when I went
to install the xfwm4, I get the message libgcc_s.so.1 is needed by
xfwm4-020724-1.

Where can I find this file and install it (or its owner package) on my
computer?

Thanks.

zorkerbatman
_______________________________________________
Xfce-dev mailing list
Xfce-dev at moongroup.com
http://moongroup.com/mailman/listinfo/xfce-dev


From klemmerj at webtrek.com  Thu Aug 29 19:10:46 2002
From: klemmerj at webtrek.com (Joe Klemmer)
Date: 29 Aug 2002 13:10:46 -0400
Subject: libgcc_s.so.1 needed...
In-Reply-To: <AC6C0CB8F0B47A4FA7BB94B1BF463EA0244F27@maila.indy.navy.mil>
References: <AC6C0CB8F0B47A4FA7BB94B1BF463EA0244F27@maila.indy.navy.mil>
Message-ID: <1030641046.2650.21.camel@computer122.belvoir.army.mil>

On Thu, 2002-08-29 at 12:36, Gammon, John P wrote:

> Can someone please look up this file and see what package it belongs to?  I
> need to download it and install it.
> 
> It seems the only way that I will get the XFCE4 to work.

	I don't have it on my system here at work.  Sorry.

-- 
Attention all planets of the Solar Federation.
We have assumed control.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 232 bytes
Desc: This is a digitally signed message part
URL: <http://mail.xfce.org/pipermail/xfce-dev/attachments/20020829/edb5db60/attachment.pgp>

From timtas at cubic.ch  Thu Aug 29 19:41:27 2002
From: timtas at cubic.ch (Tim Tassonis)
Date: Thu, 29 Aug 2002 19:41:27 +0200
Subject: libgcc_s.so.1 needed...
In-Reply-To: <AC6C0CB8F0B47A4FA7BB94B1BF463EA0244F27@maila.indy.navy.mil>
References: <AC6C0CB8F0B47A4FA7BB94B1BF463EA0244F27@maila.indy.navy.mil>
Message-ID: <E17kTIN-0000oM-00@trivadis.com>

Ho John


On Thu, 29 Aug 2002 11:36:10 -0500
"Gammon, John P" <gammonj at indy.raytheon.com> wrote:

> Can someone please look up this file and see what package it belongs to?
>  I
> need to download it and install it.


This belongs to dynamically linked gcc3. With gcc3, dynamic linking is the
default and at least Suse have a gcc3 package with a dynamic libgcc. So,
if you build an app there with gcc3 and install it on a machine without
gcc3 installed (and mind you, this is the default with Suse...), it will
not work. So much for Red Hat incompatibilites.

Solution on Suse:

- Get and install gcc3 rpm with:

rpm -Uvh gcc3...

- Get gcc3 RPM, then:
cd /tmp
rpm2cpio gcc3*.rpm |cpio -idv
cp `find usr/lib -name "libgcc_s*" ` /usr/lib
rm -rf usr

Solution for Developers:

- If building with suse gcc3, include libgcc_s with the package.

- Get rid of that crap suse build and compile gcc3 on your own with
--disable static:

tar xzf gcc-3.2.tar.gz
mkdir objdir
cd objdir
../gcc-3.2/configure  --prefix=/opt/gcc3 --enable-languages=c,c++
--with-local-prefix=/opt --disable-shared --enable-static
make bootstrap
su -c "make install"
cd ..
rm -rf objdir
rm -rf gcc-3.2

Sorry for the long explanation
Tim







> 
> It seems the only way that I will get the XFCE4 to work.
> 
> Thanks.
> 
> John Gammon
> work - gammonj at indy.raytheon.com
> personal - zorkerbatman at hotmail.com
> 
> -----Original Message-----
> From: Gammon, John P [mailto:gammonj at indy.raytheon.com]
> Sent: Monday, August 26, 2002 4:27 PM
> To: 'xfce-dev at moongroup.com'
> Subject: libgcc_s.so.1....
> 
> 
> I downloaded the XFCE4 and XFWM4 from the sourceforge.net location.  I
> also went to ftp.gtk.org and downloaded the latest gtk+ and glib files
> (1.2.10).
> 
> I went to install the xfce4 and everything went fine.  However, when I
> went to install the xfwm4, I get the message libgcc_s.so.1 is needed by
> xfwm4-020724-1.
> 
> Where can I find this file and install it (or its owner package) on my
> computer?
> 
> Thanks.
> 
> zorkerbatman
> _______________________________________________
> Xfce-dev mailing list
> Xfce-dev at moongroup.com
> http://moongroup.com/mailman/listinfo/xfce-dev
> _______________________________________________
> Xfce-dev mailing list
> Xfce-dev at moongroup.com
> http://moongroup.com/mailman/listinfo/xfce-dev


From fourdan at xfce.org  Thu Aug 29 23:06:19 2002
From: fourdan at xfce.org (Olivier Fourdan)
Date: 29 Aug 2002 23:06:19 +0200
Subject: libgcc_s.so.1 needed...
In-Reply-To: <AC6C0CB8F0B47A4FA7BB94B1BF463EA0244F27@maila.indy.navy.mil>
References: <AC6C0CB8F0B47A4FA7BB94B1BF463EA0244F27@maila.indy.navy.mil>
Message-ID: <1030655179.29505.5.camel@localhost>

John,

This lib ships with gcc. For my own use, I use a home made rpm of
gcc3.1, but for building packages, I fallback to default gcc 2.96

I, for once, forgot to switch back to 2.96 when I compiled
freetype-2.1.2 so that lib depends on libgcc_s.so.1

Then pango depends on freetype. gdk depends on pango, gtk depends on gdk
and xfwm4 depends on gtk. Therefore, because of just that, my rpm
packages depend on libgcc_s.so.1 !

It took me a while to figure out what package was depending on it, but I
finally found out. It's now fixed on my system, so next rpms I build
won't require libgcc_s.so.1

In the meantime, you may want to rebuild your own rpms using "rpm
--rebuild" on the src.rpm available from the site.

Thanks for pointing this out,

Cheers,
Olivier.

On Thu, 2002-08-29 at 18:36, Gammon, John P wrote:
> Can someone please look up this file and see what package it belongs to?  I
> need to download it and install it.
> 
> It seems the only way that I will get the XFCE4 to work.
> 
> Thanks.
> 
> John Gammon
> work - gammonj at indy.raytheon.com
> personal - zorkerbatman at hotmail.com
> 
> -----Original Message-----
> From: Gammon, John P [mailto:gammonj at indy.raytheon.com]
> Sent: Monday, August 26, 2002 4:27 PM
> To: 'xfce-dev at moongroup.com'
> Subject: libgcc_s.so.1....
> 
> 
> I downloaded the XFCE4 and XFWM4 from the sourceforge.net location.  I also
> went to ftp.gtk.org and downloaded the latest gtk+ and glib files (1.2.10).
> 
> I went to install the xfce4 and everything went fine.  However, when I went
> to install the xfwm4, I get the message libgcc_s.so.1 is needed by
> xfwm4-020724-1.
> 
> Where can I find this file and install it (or its owner package) on my
> computer?
> 
> Thanks.
> 
> zorkerbatman
> _______________________________________________
> Xfce-dev mailing list
> Xfce-dev at moongroup.com
> http://moongroup.com/mailman/listinfo/xfce-dev
> _______________________________________________
> Xfce-dev mailing list
> Xfce-dev at moongroup.com
> http://moongroup.com/mailman/listinfo/xfce-dev
> 
-- 
Olivier               <fourdan at xfce.org>            http://www.xfce.org
-----------------------------------------------------------------------
XFce is a lightweight  desktop  environment  for  various *NIX systems. 
Designed for productivity,  it loads  and  executes  applications fast,
while conserving  system resources. XFce is all free software, released
under GNU General Public License.    Available from http://www.xfce.org



From edscott at imp.mx  Sat Aug 31 02:31:51 2002
From: edscott at imp.mx (edscott wilson garcia)
Date: 30 Aug 2002 19:31:51 -0500
Subject: xftree ready for release
Message-ID: <1030753913.4174.108.camel@sagitario.eco.imp.mx>

Xftree is ready for the 3.8.18 release. The bugs described before have
been fixed. The memory leak which caused crashes in Linux was actually
referencing a null pointer in reg.c, AFAIK. The problem with hangs in
FreeBSD was actually data in a pipe not being flushed (hence xftree
hanged on a read()). A solution was very simple. Send a heartbeat to
unclog the pipe when necesary (fflush() wasn't working).


Saludos,

Edscott