public inbox for
help / color / mirror / Atom feed
From: "Benjamin Richards" <>
To: "'Marco Atzeri'" <>,	<>
Subject: RE: Need help to replicate old behavior of my X setup scripts with latest Xfree86 update
Date: Fri, 09 Jan 2015 18:55:00 -0000	[thread overview]
Message-ID: <3b5201d02c3d$c549f510$4fdddf30$> (raw)
In-Reply-To: <>

> -----Original Message-----
> From: Marco Atzeri []
> Sent: Tuesday, December 23, 2014 2:17 PM
> To:
> Subject: Re: Need help to replicate old behavior of my X setup scripts with
> latest Xfree86 update
> try putting "sleep inf" in .startxwinrc
> It should simulate the old behaviour
> Regards

Thanks for the suggestion.

I actually figured out something similar. I launched fbpanel instead with this command:
exec /usr/bin/fbpanel -p multiwindow

I also discovered that the X server is not always opened on display 0, which I wanted to force, so I did some digging and found I can do that by creating a ~/.xserverrc file to change how it launches the X server. I put this in the file instead:
/usr/bin/XWin :0 -multiwindow -nolisten tcp

I don’t need external connections as I’m primarily using the X server for local programs or with ssh -Y, so the nolisten switch works fine for me.

I also didn’t want xterm to start up at launch, so I had to create an empty ~/.Xclients file.

Finally, I had change my startup script so that, if the X server isn't running yet, it would launch startxwin in the background and loop until it sees the fbpanel process in the process list, or time out (after 30 seconds). If it sees the process start, it sets up my configurations as before.

It works, albeit not as cleanly as before. I get the extra icon in my taskbar for fbpanel since it’s running, and I see the job number get echoed out to the terminal when it backgrounds the startxwin script. It also takes longer to start since I’m launching fbpanel on top of the server, though I suppose putting the sleep command would alleviate some of that. I’ll look into it. Thanks!


Benjamin Richards

Unsubscribe info:
Problem reports:

      parent reply	other threads:[~2015-01-09 18:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23 18:24 Ben Richards
2014-12-23 19:17 ` Marco Atzeri
2014-12-24 17:47   ` Jacob Niehus
2015-01-09 18:55   ` Benjamin Richards [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='3b5201d02c3d$c549f510$4fdddf30$' \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).