Linked by Thom Holwerda on Fri 29th Apr 2011 22:06 UTC, submitted by sjvn
SuSE, openSUSE Attachmate now owns Novell and therefore, by extension, also owns SUSE and openSUSE. With Oracle currently doing everything in its power to thoroughly destroy what's left of Sun's open source commitments, scepticism abound about the future of SUSE, and more specifically of openSUSE. Attachmate's CEO has answered some questions about the future of SUSE and openSUSE, and as far as words go, it's looking good.
Thread beginning with comment 471506
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Using openSUSE - Dolphin and Nepomuk
by jabbotts on Sun 1st May 2011 16:08 UTC in reply to "Using openSUSE"
Member since:

I'd say the most frequent crashout on my system is Dolphin. It's a very nice file manager but it frequently bombs out when I've lots of directories open. The novelty of opening a second directory and selecting some files only to see all my Dolphin instances disappear has long since worn off. If it's a flaky plugin taking the whole thing down then fair enough; fix the plugin and fix Dolphin so a crashing plugin doesn't kill the entire thing.

Nepomuk. this is becoming detestable. When ram maxes out, swap use grows and my machine crawls too a halt, there is one consistency. Not the vm'd server with similar uptime to the host (groupware and various monitoring apps; it's not sitting still). Not the pentarget VMs or related heavy load tasks on the host os. The 72 hours of Ophcrack or John burning away on multiple cores.. anything productive I'm doing?.. nah.. it's Nepomukservices. Even Firefox on Windows causes less grief leaking memory everywhere and crashing out.

This is Debian 6; stability and security are core project goals. But, I can accept that other distributions may be shipping a more stable Dolphin build. Dolpin may be falling below Nepomuk seems to be a steaming pile everywhere it lands out of the cow though. I'd be happy to see both significantly improved or at least enough so that I'm not shipping crash reports so regularly.

(and with that, I'm off to disable Nepomuk. Even if other apps are using it's index library.. I'll take the performance drop over the Nepomuk crap happily. It's had it's chance until I see an updated package.)

Reply Parent Score: 2

superstoned Member since:

the good news for you is that this will indeed be solved in the upcoming version of Dolphin. The problem is that the file information plugins can crash Dolphin. While many bugs in those have been fixed, they still aren't perfect and Dolphin will use them in a separate process to prevent this issue in the future.

Reply Parent Score: 2

jabbotts Member since:

Sweet! I'll be watching for a package update in Debian's repositories; hopefully it's not a version update that will get stuck in Deb Testing rather than being included into Deb Stable.

Now, if someone would just fix the Samba "resource unavailable" nonsence. I have one machine that has no issue reading Samba shares off my NAS and another machine build from the exact same package list and config script which consistently returns the "unavailable" error. Dolphin displays it as "password incorrect" when it's not and smb4k just repeatedly asks for the uname/passwd regardless of what config settings I change. Since they are both relying on mount.cifs, I blame the "unavailable" error.

Samba itself is a necessary evil in it's own right which I'd drop like a hot potato if Windows wasn't so NIH objectionable to any other network sharing standard. (why on earth is there still no native SSH in Windows and what I would do for a native sshfs for windows cause any of the implementations tried so far suck).

But that news about Dolphin is happiness. Thank you for that.

Reply Parent Score: 2