Dotan Cohen wrote:
2008/12/23 Wendell Nichols
: I'm not sure what bothered James specifically but I'll tell you what bothered me about kde4 and suse 11.1 in general:
kde: 1. It does not remember settings from one session to another. I add things to the quick launch area and they're gone when I login. I add the "new tab" button to Konsole and its gone next session.. plus many others.
My KDE 4.x installation is on Ubuntu, and it is nearly trunk, and I cannot reproduce this. So it is either Suse-specific or fixed.
2. The task bar documentation says that there is a task list but there is no way to enable it in the dialog for the task bar settings... so no task list.
A quick google did not turn this up for me. Can you provide a link? I will look into it. Thanks!
3. It is really hard to get the task bar to look right. It took me half an hour of fiddling around and still the clock is wrapped on two lines (neither of which I can see completely).
Please send to me a screenshot. I'll try to reproduce and file a bug if needed. Thank you!
4. Neither Konqueror or Dolphin have a "picture" view mode for looking at my photographs. I'm not talking about icons.. but a proper photo browser. I'll really miss that (not really cause I'm not keeping kde4)
I will file a wish-bug on that. Any particular features that you'd like in that mode?
Suse 11.1 itself. ( Fresh install on a thinkpad t61p with an nvidia card) 1. during the install it failed to write the boot loader. I was able to continue however. 2. after the install it regularly hangs starting the jexec service. However you have to boot the rescue disk, go into the shell and manually remove it from the various runlevels where it exists to get rid of it. 3. The system has locked up solid on me several times... nothing in the log. it was not pingable when locked up. 4. I suspended to disk (to see if it would work) and it seemed to suspend correctly but on resume it destroyed my boot partition! I had to reinstall and since I was there I figured out how to get past the bootloader failure: click the detailed options panel and select to install the bootloader on the mbr. argggg! 5. routinely when I logout of a session the screen just stays blank and I don't get the login screen. It seems that the (yast installed nvidia driver from nvidia repo) does not restart correclty. In these cases I have to reboot! 6. after being installed and working (sorta) for half a day the wireless network inexplicably stopped working! I try to connect to my wireless router and the icon does not show any activity.
I really am not the person to address those issues! But you should seriously file bugs on the bootloader issues: those seem serious.
I have another machine that I'll use for work till I figure out what to do. I'll either go back to suse 10.3, or try Fedora 10. This has been the most disappointing Suse release I've ever tried and its cost me about 2 days of work time.
I haven't used Fedora since FC6 but Fedora is known to be problematic. If you are looking for a trouble-free distro then either stick with Suse, or try one of the Debian-based distros.
Well there is some more to this story. I just didn't believe a dist could get through beta testing and be this bad so I redid the installation. I was careful to specify the mbr for the grub loader and this time I disabled the use of "images" in the install. This time things seem much more stable but I'm not going to do anything crazy like try to suspend or hibernate it :) wcn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org