Ubuntu
screen-profiles package

running applications at startup doesn't work

Bug #311443 reported by Nicolas Valcarcel on 2008-12-26

	Status	Importance	Assigned to
byobu	Invalid	Undecided	Unassigned
screen	Unknown	Unknown	savannah #25348
screen (Ubuntu)	Fix Released	Medium	Unassigned
screen-profiles (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

trying to open an application at screen creation doesn't work.
Steps to reproduce:
  - run 'screen $APPLICATION' (for example irssi)
Expected behavior:
  - Open screen and open irssi in one of it's tabs
Current Behavior:
  - Screen's open as if we where open it only with 'screen'

Related branches

lp:ubuntu/karmic/screen

Revision history for this message

Nick Barcet (nijaba) wrote on 2008-12-28: Re: [Bug 311443] [NEW] running applications at startup doesn't work

Thanks a lot for you report and help us make screen profiles better.
The issue is just that we do not pass the parameter to it at all and is
quite easy to fix.

status confirmed

Changed in screen-profiles:
status:	New → Confirmed

Dustin Kirkland  (kirkland) on 2009-01-08

Changed in screen-profiles:
status:	New → Confirmed

Revision history for this message

Dustin Kirkland  (kirkland) wrote on 2009-01-09:

Hmm, so this has something to do with our default windows, as defined in windows/common.

If I comment all of those out, I can do:
$ screen top

We need to find a solution to this.

:-Dustin

Revision history for this message

Nick Barcet (nijaba) wrote on 2009-01-17:

A closer look at this shows that it seems to be a limitation in screen. I have a the same problem with a base screenrc as soon as default windows are defined.

Linking to the bug I opened on the GNU Screen bug tracker.

Revision history for this message

Nick Barcet (nijaba) wrote on 2009-01-17:

Can't link to savannah unfortunately. Here is the link.

http://savannah.gnu.org/bugs/index.php?25348

Revision history for this message

Micah Cowan (micahcowan) wrote on 2009-01-18:

(It works so long as you remove the index.php part)

Revision history for this message

Nick Barcet (nijaba) wrote on 2009-01-26:

This was fixed upstream in the 25c4f34 upstream revision (4.1.0).

Revision history for this message

Dustin Kirkland  (kirkland) wrote on 2009-01-31:

Nick,

If you would prepare a debdiff, adding this patch to our screen in Jaunty, I'll be happy to sponsor.

:-Dustin

Revision history for this message

Dustin Kirkland  (kirkland) wrote on 2009-01-31:

I'm marking the screen-profiles part of this bug invalid, since it was solved in upstream screen itself.

:-Dustin

Changed in screen-profiles:
status:	Confirmed → Invalid
status:	Confirmed → Invalid
Changed in screen:
importance:	Undecided → Medium
status:	New → Triaged

Revision history for this message

Dustin Kirkland  (kirkland) wrote on 2009-02-01:

Micah-

I tried to track down this commit against upstream VCS, but I couldn't find it. Could you provide me with a URL directly to the diff?

Thanks,
:-Dustin

Revision history for this message

Dustin Kirkland  (kirkland) wrote on 2009-02-01:

#10

Doh, found it...

http://git.savannah.gnu.org/cgit/screen.git/commit/?id=25c4f34d19c9f7d7262ef2a173238fdab7e283be

:-Dustin

Revision history for this message

Launchpad Janitor (janitor) wrote on 2009-02-06:

#11

This bug was fixed in the package screen - 4.0.3-11ubuntu3

---------------
screen (4.0.3-11ubuntu3) jaunty; urgency=low

  * debian/patches/56-source-file-not-found-warning.dpatch: When sourcing a
    file in a screenrc which is not found, fail more gracefully by not
    interrupting normal operation; instead, print a debug message. LP: #323756
  * debian/patches/57-screen-invoked-with-a-command.dpatch: Cherry pick from
    upstream source; fixes LP: #311443