On Sun, 2007-08-19 at 08:59 +0200, Hans de Graaff wrote:
> On Sat, 18 Aug 2007 13:45:22 -0400, Rick Bragg wrote:
> 
> > I have emerged f4l (media-gfx/f4l-0.2.1) and that went fine.
> > 
> > Now if I run the program from the icon, or just the command f4l, I get a
> > Segment fault.
> 
> Try to start it from a shell to see if it gives any more indication of 
> what is wrong. Otherwise start it using gdb to see if you can get a 
> backtrace of the crash. You might also want to comment on this bug: 
> https://bugs.gentoo.org/show_bug.cgi?id=82154
> 
> > If I run the f4l command as root, i get the same thing with a bit more
> > info:
> > Session management error: Authentication Rejected, reason : None of the
> > authentication protocols specified are supported and host-based
> > authentication failed
> > Segmentation fault
> 
> This provides you with more info, but not regarding the bug. It tells you 
> that root can't access your X session because that X session is used by 
> another user (you as non-root).
> 
> > Does anybody know what I should do?
> 
> Given that f4l is not officially supported you can check with the people 
> providing the ebuild in sunrise, or check with upstream, but unless you 
> can provide some more info on the segmentation fault it will be hard to 
> diagnose the problem.
> 
> Kind regards,
> 
> Hans


Thanks Hans,

I used gdb to run the program, and it does give me more info:
I will also try to check with Sunrise.

here are the results of running f4l with gdb:

(gdb) run /usr/bin/f4l 
Starting program: /usr/bin/f4l /usr/bin/f4l
(no debugging symbols found)
Failed to read a valid object file image from memory.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1223379280 (LWP 16671)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1223379280 (LWP 16671)]
0x08069a55 in ?? ()

All that happens is the splash screen shows up, then it dies.

Thanks
Rick

-- 
[EMAIL PROTECTED] mailing list

Reply via email to