the first was the kd4, after the automatic update(kdeinit4 could not start…), some people know what I’m talking about. My solution: zypper dup.
Second: When I activate compiz configuration - my screen was write and I’ll forced to reinstall everything… and now… a bug in the suse bootloader. Let me explain, I use vista + ubuntu and my bootloader is ubuntu of course. For it I install suse in it’s root directory, thinking in ubuntu fstab insert the configuration to boot suse, but I had a surprise, suse install at MBR I think, because when I reboot the system suse appears as my bootloader, I used ubuntu cd and change it. Everythink ok until I open in suse his bootloader to delete ubuntu entry, just because when suse was the bootloader it never boot at ubuntu. When I reboot the system suse got the bootloader again. I was very angry because I had sure it installed at his root directory. I don’t know why it’s everytime install at MBR. I was curious about suse, but it need to evolve very very much. the positive point was the sound in my machine very loud and because i can watch dvd without problem because suse don’t install 3D function of my ati video card (radeon hd 2400 - 3D function there is a bug video stays flashing and firefox takes the whole screen). Danger, take care with compiz, because you can stay without x.
Well, it seems that you are confusing some terms here.
You wrote:
“For it I install suse in it’s root directory, thinking in ubuntu fstab insert the configuration to boot suse, but I had a surprise, suse install at MBR I think, because when I reboot the system suse appears as my bootloader, I used ubuntu cd and >change it. Everythink ok until I open in suse his bootloader to delete ubuntu entry, just because when suse was the bootloader it never boot at ubuntu. When I reboot the system suse got the bootloader again. I was very angry because I had sure it installed at his root directory. I don’t know why it’s everytime install at MBR. I was curious about suse, but it need to evolve very very much.”
I don’t understand this part very well, but there is no such thing like suse installing on MBR. Suse and any OS installs in a disk partition. fstab is a file which is used to tell linux what partitions to mount at system boot, but before that your system have to know where to find the initial code to boot the kernel, that info is provided outside the OS itself by a program called bootloader, in opensuse and ubuntu the default bootloader is grub. That is the program which get installed on your MBR.
Also, I don’t get it but it seems that you want to install opensuse in the same partition than ubuntu? If this is case, forget it, you will be overwriting your ubuntu, that has nothing to do with MBR.
Please let me know if there was something I didn’t get right about your post.
Sorry, but sounds like there is more misunderstanding than bugs. Is there a question, or more than one? If so, let’s take it one at a time, and please try to explain the problem clearly and completely.