Description of problem: 1)rdesktop everytime segfaults when connecting to FQDN. 2)rdesktop segfaults for first time if I change some parameter. Does not matter which parameter. Second start with same parameters is OK. Version-Release number of selected component (if applicable): rdesktop-1.9.0 Steps to Reproduce: 1) rdesktop everytime segfaults when connecting to FQDN. 1a) segfaults [user@localhost ~]$ rdesktop w2k12 Autoselecting keyboard map 'cs' from locale Protocol(warning): Protocol negotiation failed with reason: SSL not allowed by server Retrying with plain RDP. Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen]) [user@localhost ~]$ rdesktop w2k12 Autoselecting keyboard map 'cs' from locale Protocol(warning): Protocol negotiation failed with reason: SSL not allowed by server Retrying with plain RDP. Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen]) 1b) correct execution [user@localhost ~]$ host w2k12 w2k12.linuxbox.cz has address 10.76.8.22 [user@localhost ~]$ rdesktop 10.76.8.22 Autoselecting keyboard map 'cs' from locale Protocol(warning): Protocol negotiation failed with reason: SSL not allowed by server Retrying with plain RDP. 2) rdesktop segfaults for first time if I change some parameter. 2a) start with previously used parameter is OK [user@localhost Pixel2]$ rdesktop -k en 10.76.8.22 Keyboard(error): xkeymap_read(), failed to open keymap en Protocol(warning): Protocol negotiation failed with reason: SSL not allowed by server Retrying with plain RDP. 2b) After changed keyboard parameter rdesktop segfaults [user@localhost Pixel2]$ rdesktop -k cs 10.76.8.22 Protocol(warning): Protocol negotiation failed with reason: SSL not allowed by server Retrying with plain RDP. Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen]) 2c) Second run with same parameter is OK [user@localhost Pixel2]$ rdesktop -k cs 10.76.8.22 Protocol(warning): Protocol negotiation failed with reason: SSL not allowed by server Retrying with plain RDP.
CC: (none) => raiko
Thank you for this report and the evidence. Can you say whether this happened only after the update from rdesktop-1.8.6-1.mga7 to rdesktop-1.9.0-1.mga7 but was OK before? If this is so, it would be worth you downgrading the package to the previous version (and not letting it be updated). Assigning to Stig as the active rdesktop maintainer.
Assignee: bugsquad => smelrorSummary: rdesktop-1.9.0 segfaults => rdesktop-1.9.0 segfaults always with FQDN, and once after a parameter change
(In reply to Lewis Smith from comment #1) > Thank you for this report and the evidence. > Can you say whether this happened only after the update from > rdesktop-1.8.6-1.mga7 to rdesktop-1.9.0-1.mga7 > but was OK before? > If this is so, it would be worth you downgrading the package to the previous > version (and not letting it be updated). > > Assigning to Stig as the active rdesktop maintainer. After uninstall 1.9.0 I see rdesktop-1.8.5-1.mga7 only in repo. With this version I can't connect at all. [user@localhost ~]$ rdesktop w2k12.linuxbox.cz Autoselected keyboard map en-us Failed to negotiate protocol, retrying with plain RDP. ERROR: Failed to extract public key from certificate ERROR: recv: Spojení zrušeno druhou stranou [user@localhost ~]$ rdesktop 10.76.8.22 Autoselected keyboard map en-us Failed to negotiate protocol, retrying with plain RDP. ERROR: Failed to extract public key from certificate ERROR: recv: Spojení zrušeno druhou stranou It seems to be fixed bug.
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Hi bug reporter and hi assignee and others involved, Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly. This report is being closed as OLD because it was filed against Mageia 7, for which support ended on June 30th 2021. Thanks, Marja
Status: NEW => RESOLVEDResolution: (none) => OLD