Unable to start KDE4 on freebsd 7.4-RELEASE
I updated my FreeBSD box from 6.4 to 7.4 using freebsd-update, got my installed ports in order and updated and installed/updated kde4-4.6.3 and all its dependancies. Xorg works ( i can run twm successfully), but trying to start kde bombs out. It looks like kded is barfing trying to get a a lock on the shared cache. Everything's up to date as of a portsnap fetch this morning. Output from startx follows. Hopefully someone can help, as I'm out of ideas. Thanks, mnavarre. Script started on Sun Jun 5 13:42:25 2011 startx xauth: file /home/mnavarre/.serverauth.59871 does not exist X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.4-RC3 i386 Current Operating System: FreeBSD reichlieu.lan 7.4-RELEASE FreeBSD 7.4-RELEASE #0: Thu Feb 17 03:51:56 UTC 2011 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Build Date: 28 May 2011 10:30:45PM Current version of pixman: 0.21.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Jun 5 13:42:25 2011 (==) Using default built-in configuration (30 lines) (EE) Failed to load module fbdev (module does not exist, 0) expected keysym, got XF86TouchpadToggle: line 123 of inet kbuildsycoca4 running... kbuildsycoca4(59915) KConfigGroup::readXdgListEntry: List entry MimeType in .hidden/kommander.desktop is not compliant with XDG standard (missing trailing semicolon). startkde: Starting up... Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kded(59942)/kdeui (KIconLoader): Unable to find an appropriate lock to guard the shared cache. This *should* be essentially impossible. :( kded(59942)/kdeui (KIconLoader): Unable to perform initial setup, this system probably does not really support process-shared pthreads or semaphores, even though it claims otherwise. QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPixmap: It is not safe to use pixmaps outside the GUI thread QObject: Cannot create children for a parent that is in a different thread. (Parent is KApplication(0xbfbfe35c), parent's thread is QThread(0x2a322050), current thread is QThread(0x2a322c88) KGlobal::locale() must be called from the main thread before using i18n() in threads. KApplication takes care of this. If not using KApplication, call KGlobal::locale() during initialization. kded(59941): Communication problem with kded , it probably crashed. Error message was: org.freedesktop.DBus.Error.ServiceUnknown : The name org.kde.kded was not provided by any .service files KCrash: Application 'kded4' crashing... KCrash: Attempting to start /usr/local/kde4/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/mnavarre/.kde4/socket-reichlieu.lan/kdeinit4__0 kcminit(59944)/kdeui (KIconLoader): Unable to find an appropriate lock to guard the shared cache. This *should* be essentially impossible. :( kcminit(59944)/kdeui (KIconLoader): Unable to perform initial setup, this system probably does not really support process-shared pthreads or semaphores, even though it claims otherwise. QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPixmap: It is not safe to use pixmaps outside
Re: Unable to start KDE4 on freebsd 7.4-RELEASE
Mathew, On Sun, Jun 5, 2011 at 3:53 PM, Matthew Navarre mnava...@cox.net wrote: I updated my FreeBSD box from 6.4 to 7.4 using freebsd-update, got my installed ports in order and updated and installed/updated kde4-4.6.3 and all its dependancies. Xorg works ( i can run twm successfully), but trying to start kde bombs out. It looks like kded is barfing trying to get a a lock on the shared cache. Everything's up to date as of a portsnap fetch this morning. Output from startx follows. Hopefully someone can help, as I'm out of ideas. Thanks, mnavarre. Script started on Sun Jun 5 13:42:25 2011 startx xauth: file /home/mnavarre/.serverauth.59871 does not exist X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.4-RC3 i386 Current Operating System: FreeBSD reichlieu.lan 7.4-RELEASE FreeBSD 7.4-RELEASE #0: Thu Feb 17 03:51:56 UTC 2011 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Build Date: 28 May 2011 10:30:45PM Current version of pixman: 0.21.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Jun 5 13:42:25 2011 (==) Using default built-in configuration (30 lines) (EE) Failed to load module fbdev (module does not exist, 0) expected keysym, got XF86TouchpadToggle: line 123 of inet kbuildsycoca4 running... kbuildsycoca4(59915) KConfigGroup::readXdgListEntry: List entry MimeType in .hidden/kommander.desktop is not compliant with XDG standard (missing trailing semicolon). startkde: Starting up... Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kded(59942)/kdeui (KIconLoader): Unable to find an appropriate lock to guard the shared cache. This *should* be essentially impossible. :( kded(59942)/kdeui (KIconLoader): Unable to perform initial setup, this system probably does not really support process-shared pthreads or semaphores, even though it claims otherwise. QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPixmap: It is not safe to use pixmaps outside the GUI thread QObject: Cannot create children for a parent that is in a different thread. (Parent is KApplication(0xbfbfe35c), parent's thread is QThread(0x2a322050), current thread is QThread(0x2a322c88) KGlobal::locale() must be called from the main thread before using i18n() in threads. KApplication takes care of this. If not using KApplication, call KGlobal::locale() during initialization. kded(59941): Communication problem with kded , it probably crashed. Error message was: org.freedesktop.DBus.Error.ServiceUnknown : The name org.kde.kded was not provided by any .service files KCrash: Application 'kded4' crashing... KCrash: Attempting to start /usr/local/kde4/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/mnavarre/.kde4/socket-reichlieu.lan/kdeinit4__0 kcminit(59944)/kdeui (KIconLoader): Unable to find an appropriate lock to guard the shared cache. This *should* be essentially impossible. :( kcminit(59944)/kdeui (KIconLoader): Unable to perform initial setup, this system probably does not really support process-shared pthreads or semaphores, even though it claims otherwise. QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is
Re: Unable to start KDE4 on freebsd 7.4-RELEASE
On Jun 5, 2011, at 3:17 PM, Antonio Olivares wrote: Mathew, On Sun, Jun 5, 2011 at 3:53 PM, Matthew Navarre mnava...@cox.net wrote: I updated my FreeBSD box from 6.4 to 7.4 using freebsd-update, got my installed ports in order and updated and installed/updated kde4-4.6.3 and all its dependancies. Xorg works ( i can run twm successfully), but trying to start kde bombs out. It looks like kded is barfing trying to get a a lock on the shared cache. Everything's up to date as of a portsnap fetch this morning. Output from startx follows. Hopefully someone can help, as I'm out of ideas. Thanks, mnavarre. Script started on Sun Jun 5 13:42:25 2011 startx xauth: file /home/mnavarre/.serverauth.59871 does not exist X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.4-RC3 i386 Current Operating System: FreeBSD reichlieu.lan 7.4-RELEASE FreeBSD 7.4-RELEASE #0: Thu Feb 17 03:51:56 UTC 2011 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Build Date: 28 May 2011 10:30:45PM Current version of pixman: 0.21.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Jun 5 13:42:25 2011 (==) Using default built-in configuration (30 lines) (EE) Failed to load module fbdev (module does not exist, 0) expected keysym, got XF86TouchpadToggle: line 123 of inet kbuildsycoca4 running... kbuildsycoca4(59915) KConfigGroup::readXdgListEntry: List entry MimeType in .hidden/kommander.desktop is not compliant with XDG standard (missing trailing semicolon). startkde: Starting up... Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kded(59942)/kdeui (KIconLoader): Unable to find an appropriate lock to guard the shared cache. This *should* be essentially impossible. :( kded(59942)/kdeui (KIconLoader): Unable to perform initial setup, this system probably does not really support process-shared pthreads or semaphores, even though it claims otherwise. snip startkde: Shutting down... klauncher: Exiting on signal 1 kde3: not found kde3: not found startkde: Running shutdown scripts... startkde: Done. waiting for X server to shut down Script done on Sun Jun 5 13:42:36 2011___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I can see that startx might be looking for kde 3, the line : kde3: not found kde3: not found I was wondering about that myself, but KDE has never been installed on this machine until now. I thought I'd gotten all the old KDE cruft rm'ed from $HOME and you have kde 4.6.3 latest and greatest. Question: Do you have exec startkde in ~/.xinitrc or exec /usr/local/kde4/bin/startkde in ~/.xinitrc The kde4 line is in ~/.xinitrc Because the first one is for kde 3 while the next one(above) is for kde 4. If you try to create another user and the user is able to login, then it might be a problem with the old settings? I created a new user with an empty $HOME, added the startkde line to .xinitrc and had the same problem. I did notice that drkonqi is crashing and writing out a .core file, so I'll see if gdb can tell me anything. Thanks, mnavarre Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Unable to start KDE4 on freebsd 7.4-RELEASE
I created a new user with an empty $HOME, added the startkde line to .xinitrc and had the same problem. I did notice that drkonqi is crashing and writing out a .core file, so I'll see if gdb can tell me anything. Thanks, mnavarre Read about something called kchildlock : kchildlock on an archlinux page: https://bbs.archlinux.org/viewtopic.php?pid=940823 one solution is to remove kchildlock. problem now becomes how does one do this? Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
