[kde-freebsd] WARNING: NEW XORG
I made the mistake of migrating to BSD 10.0-STABLE on 24 Feband trying the WITH_NEW_XORG. And like many people I was rewarded with a blank screen. When I can get "Xorg -configure" to work it keeps creating a layout for 3 screens, 3 monitors, and 3 video devices on my Toshiba Satellite laptop with a intel GM45. After the log seem to be complaining about the mouse and keyboard, the HAL came into suspicion and when this persisted after multiple attempts to rebuild it and Xorg and their dependencies, I forced rebuilt all my ports (over 1180). Three days later there was still no joy, so yesterday I had to give up on NEW_XORG and revert back to 1.7.7. But now I find kde-freebsd has made the NEW_XORG that doesn't work, a dependency for KDE. I've updated my port directory again today and am rebuilding yet again, but it seems to me that there needs to be new documentation for the new Xorg before KDE or others make people dependent on it. - Email sent using Optus Webmail ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
[kde-freebsd] KDE 4.12 on FreeBSD 10.0 Thick Client
Hi, I am trying to get KDE to work on a diskless client. I am not having much luck getting the initial environment to come up correctly. Everything is NFS mounted. System partitions are mounted read only (/ and /usr), things that require writing (/var, /usr/home, /usr/local/share/config/kdm) are mounted with memory disks or NFS mounted with read/write. The issue is when I log in. This happens whether it's a user in the 'local' (NFS mounted) password file or the LDAP that I have now managed to invoke with a KDE PAM module: I get a black screen with no toolbar with a 'close a window' red X button where the 'K' menu should be and two 'new activity' launchers in the upper and lower right corners. Does anyone have a list as to what KDM/KDE does upon startup (like copying files to user accounts and the locations of said files) so that I can track down what is wrong? Thank you, Paul Pathiakis ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] Weird KDE & VirtualBox problem
On 2014-02-28 19:01 Dwayne MacKinnon wrote: > Hi all, > > I recently upgraded my amd64 box to FreeBSD 10.0-RELEASE so that I could > get > the new amd kms drivers and move up to KDE 4.11/4.12. > > I've discovered an odd bug when running VirtualBox > (emulators/virtualbox-ose) > under the current KDE. Namely, it won't work. > > When I attempt to launch VirtualBox while running KDE VirtualBox > complains > that it isn't setuid root, and promptly segmentation faults. > > If I run VirtualBox under twm, this problem does not occur. If I ssh -Y > into > my own box from KDE, and run VirtualBox in the ssh session, the problem > doesn't occur. > > Do any of the KDE gurus here have any idea how KDE could be interfering > with > VirtualBox's being setuid to root? > > Cheers, > DMK Hi, AFAIK the segfault thing originates in the fact VirtualBox is linked against gcc's c++ libraries while the Qt ports used by VirtualBox link against clang's libraries by default on FreeBSD-10 which causes undesirable side-effects. Someone posted instructions on how to build an alternate/inofficial VirtualBox port with clang to avoid the issue to emulation@: http://lists.freebsd.org/pipermail/freebsd-emulation/2014-January/011224.html Hope that helps. VirtualBox doesn't need root over here, though I need to load the vboxdrv kernel module and start the vboxnet service both as root in order for VirtualBox to work. Alonso ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
