I use portmaster -a to upgrade my ports. After upgrade to KDE4.10.5,System becomes unstable. When I click on Dolphin icon twice on desktop, disk led is light, and then the system is hang.After a few seconds, the system will reboot. When I click shutdown from KDE menu, the system will reboot. When I click shutdown in KDM kdm interface, the system will reboot. If I work in kde environment, I don't know when it will suddenly crash and reboot. I checked in /var/log/message, but did not see the useful information. Now I'm in fluxbox environment, everything is fine. Before update to kde 4.10.5, I'm work in kde 4.10.3, everything is fine. My make.conf: #================================= #clang+FreeBSD10 NO_WERROR=1 WERROR=0 #Jail nv NO_FSCHG= #no debus MALLOC_PRODUCTION="YES" WITH_LIBCPLUSPLUS=yes #set cc as clang: WITH_CLANG_IS_CC=yes ###WITHOUT_CLANG_IS_CC=yes # use libc++ instead of libstdc++: #CXXFLAGS+=-stdlib=libc++ #include llvm WITH_CLANG_EXTRAS=yes #remove gcc: WITHOUT_GCC=yes WITHOUT_GNU=yes
Responsible Changed From-To: freebsd-bugs->freebsd-ports-bugs ports PR.
After many tests, I get the follow result: 1. FreeBSD 10.0-CURRENT r251499 + Clang + ZFS + KDE4.10.3, work fine. 2. FreeBSD 10.0-CURRENT r251499 + Clang + ZFS +KDE4.10.5, work fine. 3. FreeBSD 10.0-CURRENT r253040 + Clang + ZFS +KDE4.10.5, dbclick Dolphin on desktop, will cause reboot 4. FreeBSD 10.0-CURRENT r253040 + Clang + ZFS +KDE4.10.5, dbclick Dolphin on desktop, will cause reboot That's to say: At r251499, KDE4.10.3 and KDE4.10.5 will wok fine. At r253040, KDE4.10.3 and KDE4.10.5 will crash. Which version from r251499 to r253040 will cause the problem? I don't know. But I'll try more tests to do with it.
Responsible Changed From-To: freebsd-ports-bugs->kde Despite the subject, i think this is about the kde4 dolphin so over to kde@
Is this still an issue?
(In reply to Raphael Kubo da Costa from comment #4) I have experienced unexpected reboots on shutdown also. I'll try to test if this is indeed dolphin related (at least).
Closing this for now. As no one seems to be able to reproduce it. Please reopen a bug report should this reoccur. Thanks.