[Bug 2056485] Comment bridged from LTC Bugzilla

2024-04-19 Thread bugproxy
--- Comment From jldo...@us.ibm.com 2024-04-19 13:51 EDT---
It was decided internally that the Novalink team will be taking a patched socat 
.deb and placing it within their own repo to provide the correct behavior in 
their customer environments.

Thank you to everyone that spent time on this bug.

We are awaiting confirmation from the Novalink team that this method of
providing the correct behavior is working successfully. Thank you to
Frank for building the .deb that will be used.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056485

Title:
  Behaviour of socat in Ubuntu 20.04 unexpected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056485/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056485] Comment bridged from LTC Bugzilla

2024-04-03 Thread bugproxy
--- Comment From jldo...@us.ibm.com 2024-04-03 14:36 EDT---
I am very curious if anyone else has been able to work around this while 
passing stdio as an argument. I just assumed socat was not a very popular 
package. When I pass stdin (vs stdio) to socat within mkvterm it works.

Let me check with the Novalink team to see if this is an acceptable
workaround for them. Either way - I do not feel like the testcase parts
are needed, but they do not hurt anything. I also feel like the code
change impacting the socat binary is unlikely to break someone else's
workaround within a script. Many thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056485

Title:
  Behaviour of socat in Ubuntu 20.04 unexpected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056485/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056485] Comment bridged from LTC Bugzilla

2024-03-11 Thread bugproxy
--- Comment From jldo...@us.ibm.com 2024-03-11 14:03 EDT---
Test build of socat provided by Frank is showing the expected behavior of socat.

1) Ctrl-] closes the connection
2) Ctrl-c does not close the connection
3) Password is not being displayed
4) Up arrow is working correctly, and not outputting junk characters

Many thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056485

Title:
  Behaviour of socat in Ubuntu 20.04 unexpected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056485/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056485] Comment bridged from LTC Bugzilla

2024-03-07 Thread bugproxy
--- Comment From jldo...@us.ibm.com 2024-03-07 15:35 EDT---
Frank and Patricia -

This is related to launchpad bug 2023243 (Multiple issues found on
Ubuntu 20.04 against drmgr)

I split out the remaining issues into two bugs - one for the kernel
changes needed (launchpad bug 2056373) and this one for socat

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056485

Title:
  Multiple issues found on Ubuntu 20.04 against socat

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/socat/+bug/2056485/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs