Opened 6 years ago

Last modified 2 weeks ago

#31528 new defect

rdesktop 1.6.0: segmentation fault

Reported by: thomas.granvej6@… Owned by: cshbell@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: lion Cc:
Port: rdesktop

Description (last modified by ryandesign (Ryan Schmidt))

When using the "-r sound:local" option, rdesktop connects to my Windows XP, and as soon as it hits the desktop, the application crashes with this:

Segmentation fault: 11

Removing the "-r sound:local" option eliminates the problem.

It works flawlessly with the same rdesktop version, compiled for Slackware Linux, and the VirtualBox rdesktop-vrdp client also works from Linux, so there doesn't appear to be anything wrong with the RDP server, nor with rdesktop's ability to forward sound to the client. The official Microsoft RDP client for Mac also forwards sound without issue.

Change History (4)

comment:1 follow-up: Changed 6 years ago by ryandesign (Ryan Schmidt)

  • Description modified (diff)
  • Keywords lion added
  • Milestone MacPorts 2.0.4 deleted
  • Owner changed from macports-tickets@… to cshbell@…
  • Port rdesktop added
  • Summary changed from rdesktop 1.6.0 segfaults with Lion 10.7.1 to rdesktop 1.6.0: segmentation fault
  • Version changed from 1.6.0 to 2.0.3

The Version field is for the version of MacPorts you're running, not the version of the port. I'll assume you're running the latest MacPorts, 2.0.3.

The Milestone field is not used for port tickets.

Do remember to fill in the Port field though and Cc the maintainer of that port.

comment:2 in reply to: ↑ 1 Changed 6 years ago by thomas.granvej6@…

Replying to ryandesign@…:

The Version field is for the version of MacPorts you're running, not the version of the port. I'll assume you're running the latest MacPorts, 2.0.3.

Your assumption is correct. I am using 2.0.3.

The Milestone field is not used for port tickets.

Gotcha!

Do remember to fill in the Port field though and Cc the maintainer of that port.

Gotcha!

Thanks. I promise I'll do better next time. :o)

comment:3 Changed 6 years ago by jmroot (Joshua Root)

Probably want to update the port to 1.7.1 (#34525) before digging into this too much.

comment:4 Changed 2 weeks ago by jmroot (Joshua Root)

Is this still a problem with the current version?

Note: See TracTickets for help on using tickets.