bugGNU Screen - Bugs: bug #54458, Session name length causes problem...

 
 

bug #54458: Session name length causes problem to "reopen fifo"

Submitter:  None
Submitted:  Tue 07 Aug 2018 04:03:42 PM UTC
   
 
Category:  Crash/Freeze/Infloop Severity:  3 - Normal
Priority:  * 5 - Normal Status:  Ready For Test
Privacy:  Public Assigned to:  None
Open/Closed:  Open Release:  4.6.2
Fixed Release:  None Planned Release:  None
Work Required:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 02 Feb 2022 11:14:13 PM UTC, comment #3: 

This should be fixed in 4.9.0.
Please test it again.

 Alexander Naumov <anaumov>
Group administrator
Sat 10 Nov 2018 09:32:02 PM UTC, comment #2: 

Hm... interesting, so it seems that sockaddr_un that is used in MakeServerSocket can only hold 108 characters (last one being \0 it's 107), which including path to socket directory leaves even less place for actual socket name.

 Amadeusz Sławiński <amade>
Group administrator
Wed 22 Aug 2018 10:56:53 PM UTC, comment #1: 

Hey, thanks for your report.

Yes, actually there are a lof of changes between these versions. For example, we migrated from fifos to sockets in version 4.6.0. That could be the reason, but I'm not sure.

Take a look at this commit: bab73f99a2dc99604fb38b8fa2c73e3453c12b2a

Did you tried to update screen and reopen the old sessions?
There are no PATHs like /run/*, we use /tmp/sceens/S-name. Are there some addition pathes?

@Axel, can you please confirm this problem in (K)ubuntu? Is it really problem with session name length?

 Alexander Naumov <anaumov>
Group administrator
Tue 07 Aug 2018 04:03:42 PM UTC, original submission:  

Hi all,

I have been using screen from earlier than 4.3.1 versions, and with the new kubuntu 18.04 LTS a newer version 4.6.2 is available.

However, I noticed the difference from version 4.3.1 (from kubuntu 16.04LTS) to this one. The problem I found on this newer version is that longer session names cause dead screens and it shows the message "reopen fifo /run/screen/S-pc/9973.[session name with 81chars]: No such file or directory". Additionally, the pid number also influences this behavior, since its length seems to be also accounted for the total length.

So, I tested in version 4.3.1 with plenty more characters without any problem.

Hence, I have to ask, is this a bug? For my needs it would be beneficial to handle longer names as in earlier 4.3.1 version.

If otherwise, this maximum session name length is from now on mandatory, an error should alert the user for this case.

Just to let you know.
Thanks for your attention.



Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by amade (Posted a comment)
  • -email is unavailable- added by anaumov (Posted a comment)

    •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-02-02 anaumov StatusConfirmed Ready For Test
    2018-11-10 amade StatusNone Confirmed

    Back to the top

    Copyright © 2024 Free Software Foundation, Inc.
    Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
    The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team.
    Page source code

    Powered by Savane 3.13-ec04.
    Corresponding source code