Bug 7799 - Authentication and Segmentation fault.
Authentication and Segmentation fault.
Product: Red Hat Linux
Classification: Retired
Component: rp3 (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Nalin Dahyabhai
Depends On:
  Show dependency treegraph
Reported: 1999-12-14 02:46 EST by Neil Darlow
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-07 14:53:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Neil Darlow 1999-12-14 02:46:19 EST
As a non-root user, rp3-config (or Configure from rp3 menu) gives the
following authentication error:

> (gdb) run
> Starting program: /usr/bin/rp3
> GnomeUI-WARNING **: While connecting to session manager:
> Authentication Rejected, reason : None of the authentication protocols
> specified are supported and host-based authentication failed.
> $(gdb) quit
> The program is running.  Exit anyway? (y or n)

For all users, rp3-config generates a segmentation fault (this reported
for root X session):

> (gdb) run
> Starting program: /usr/sbin/rp3-config

> Program received signal SIGSEGV, Segmentation fault.
> 0x4045aee9 in chunk_free (ar_ptr=0x404ef040, p=0x80df4a8) at
> 3047    malloc.c: No such file or directory.
> Current language:  auto; currently c
(gdb) bt
> #0  0x4045aee9 in chunk_free (ar_ptr=0x404ef040, p=0x80df4a8) at
> #1  0x4045ad75 in __libc_free (mem=0x80df4b0) at malloc.c:2959
> #2  0x807a57d in svCloseFile (s=0x80df458) at shvar.c:367
> #3  0x807a851 in interface_shvarfiles_close (ifcfg=0x80df458) at >
> #4  0x807af7c in interface_free (i=0x80db570) at interface.c:366
> #5  0x80541a8 in load_accounts () at account.cc:473
> #6  0x805ec5e in rp3_mainwin_new () at mainwin.cc:518
> #7  0x80663f5 in main (argc=1, argv=0xbffffc34) at main.cc:149
> (gdb) quit
> The program is running.  Exit anyway? (y or n) y
Comment 1 Michael K. Johnson 1999-12-14 11:25:59 EST
Please try the test release at
and see if it fixes the problem.

Comment 2 Nalin Dahyabhai 2000-02-07 14:53:59 EST
This bug has lain dormant for more than six weeks.  I therefore assume that the
original reporter has solved the problem.

Note You need to log in before you can comment on or make changes to this bug.