After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 341701 - [PATCH] gnome-system-tools locks up on FreeBSD
[PATCH] gnome-system-tools locks up on FreeBSD
Status: RESOLVED FIXED
Product: gnome-system-tools
Classification: Deprecated
Component: general
2.14.x
Other All
: Normal critical
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
: 315254 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-05-14 01:13 UTC by Joe Marcus Clarke
Modified: 2006-05-29 12:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

Attachments
Fix g-s-t on FreeBSD (2.48 KB, patch)
2006-05-14 01:15 UTC, Joe Marcus Clarke 		committed Details | Review

Description Joe Marcus Clarke 2006-05-14 01:13:47 UTC 
Please describe the problem:
The forkpty implementation in FreeBSD does not like threads.  Therefore, all of
the g-s-t tools will lock up trying to get root's password.  The attached patch
reimplements forkpty() on FreeBSD in terms of grantpt() and friends.  The result
is a working g-s-t on FreeBSD.

The other patch corrects a previously reported typo with polling.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Joe Marcus Clarke 2006-05-14 01:15:50 UTC 
Created attachment 65414 [details] [review]
Fix g-s-t on FreeBSD
Comment 2 Carlos Garnacho 2006-05-29 10:54:11 UTC 
Thanks for the patch! it's now in the stable branch.

As for HEAD, I don't know if you were aware of the development plans, but the module has abandoned the forkpty + su 'hacks', instead it communicates through DBus, PolicyKit will be very probably used to do the authentication, so communication with the backends should work out of the box :)
Comment 3 Carlos Garnacho 2006-05-29 12:00:01 UTC 
*** Bug 315254 has been marked as a duplicate of this bug. ***