KDE 3.5.10 && 10-CURRENT r235646 (May 19)

[Matthias Apitz]

Hello,

The Good message first: KDE 3.5.10 compiles clean in 10-CURRENT; thanks!

With a recent 10-CURRENT and clean ports from CVS (both from May 19) I
encounter some crashes on KDE start or stop; there are messages from
'startkde':

Warning: kbuildsycoca is unable to register with DCOP.
kbuildsycoca running...
kbuildsycoca running...
Reusing existing ksycoca
...
startkde: Starting up...
kbuildsycoca running...
>> running as realtime process now (priority 15)
kdecore (KProcess): WARNING: Can't open a pseudo teletype
QSocketNotifier: Invalid socket specified
QSocketNotifier: Socket descriptor too large for select()
QSocketNotifier: Internal error
kbuildsycoca running...
Reusing existing ksycoca

and on KDE exit it says:

Segmentation fault (core dumped)
startkde: Shutting down...
startkde: Running shutdown scripts...
startkde: Done.

and a file dcop.core is written;

What does this mean?

Thanks

matthias

--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <gu...@unixarea.de> - w http://www.unixarea.de/
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"

[John Baldwin]

On Saturday, May 26, 2012 4:36:28 am Matthias Apitz wrote:
>
> Hello,
>
> The Good message first: KDE 3.5.10 compiles clean in 10-CURRENT; thanks!
>
> With a recent 10-CURRENT and clean ports from CVS (both from May 19) I
> encounter some crashes on KDE start or stop; there are messages from
> 'startkde':
>
> Warning: kbuildsycoca is unable to register with DCOP.
> kbuildsycoca running...
> kbuildsycoca running...
> Reusing existing ksycoca
> ...
> startkde: Starting up...
> kbuildsycoca running...
> >> running as realtime process now (priority 15)
> kdecore (KProcess): WARNING: Can't open a pseudo teletype

Maybe it's using the old pty's? Try putting 'device pty' back in your kernel
config perhaps?

--
John Baldwin