opvask

Thanks for the suggestion even though it did not solve the problem. I have been out of town for a while so I have not been able to try this before now. I did manage to solve the problem today though. I did a real quick "ctrl+alt+backspace" immediately when the nvidia screen appeared. I was then able to go to the login screen before Gnome started loading and log in to KDE. :) Now I only wonder why Gnome keeps hanging when installed with task-gnome. It has never worked for me in 2007.1 Thanks for the help O

in Mandriva 2007.1 Spring, when I install Gnome (task-gnome or task-gnome-minimal) I run into problems. I must add that I normally use auto login on boot. 1. I cannot login to Gnome. Gnome will hang during login. The splash screen will appear but then nothing else happens. 2. I cannot login to (my main environment) KDE instead. The system will automatically choose Gnome during boot, but as mentioned in #1, Gnome does not startup properly. If I use CTRL+ALT+Backspace I can go back to the Login screen, but if I try to login to KDE then I will be directed back to the login screen immediately. The same thing will happen if I try with failsafe. How to solve this? Why does Gnome hang during boot? All files needed should be installed with "task-gnome". How can I manage to login with KDE again?

I often use this approach after installing a new Linux OS with Grub on the new root partition. Example with new Suse OS on sda7 and Suse grub on sda7: # linux installation on /dev/sda7 title Suse configfile (hd0,6)/boot/grub/menu.lst This way every OS keeps it's grub menu and grub graphics. When choosing Suse on startup you'll be presented with the full Suse Grub menu and graphics. This is just an easy alternative. :)

Sounds perfect. I'll do some research about ReiserFS and possibly use that when I do my next install. IF my system is doing a FSCK it's nearly always of the "storage partition" and this process is taking a long time. It will be a tough job formating this partition with ReiserFS, since it's 300 GB and full of data. I'll be testing OpenSuse tomorrow and I'll try installing it on a ReiserFS partition. Thanks for the info. :)

I've been experimenting a bit with Compiz Fusion and the beta nvidia driver on a "test partition (sda6)" with Mandriva 2007.1, which has resultet in a couple of system freezes and a "ALT+PRTSCN+B" reboots. After these reboots the system starts with a forced FSCK of sda5, which is not a root, boot or home partition (it's a storage partition). The partition is about 300 GB and therefor a forced FSCK takes at least an hour. Possibly I could change the fstab line (defaults 0 0) for the given partition to avoid this, but I'd like to understand a few things better first. I'm not sure if this would be adviced either. :) 1. Why does the system force a fsck of a storage disk? It does not suggest a system disk check of the root/home partition. I wonder why the need of a fsck is concentrated on the big storage (sda5). Is there a problem with this partition? 2. What would be the best way to setup the storage (sda5) in fstab? Currently I have: /dev/sda5 /media/storage ext3 defaults 1 2 I did have defaults 1 1 before but I changed it to 1 2 after reading more about fstab. The fstab line I use now is generated by drakdisk. 3. ext3 is a journalized file system afaik. I tried reading about this online and found this: When using NTFS in Windows in the "old" days I really enjoyed that there rarely was any "forced" disk check on boot. Even after a hard shutdown. Shouldn't ext3 be able to work that way? Sorry, I hope someone understand what I'm talking about. English is not my main language. :( 4. Could using ReiserFS improve something in this area? Short boot time on forced fsck? Or perhaps even less occurences of fsck after a bad shutdown? Sorry for the many questions about this, but I see a lot of very experiences Linux users here. I hope someone will answer a few of these questions. Especially #1 but I guees it's all kind of related. Any links to good (non expert) info would also do. Thanks in advance :)

1. How can I change the size/resolution of a custom kde boot screen theme? Most of the default themes are working with my new HP 22" WS (resolution 1680x1050) but the ones added only fill parts of the screen (1280x1024). The result = a black area on the right side. I've tried editing "BaseResolution = 1280,1024" to "BaseResolution = 1680,1050" in the theme.rc files and I've tried changing the background image size for the themes, but it does not help. 2. Where's the powerpack kde splash screen located? I'm on "free DVD" but I use the powerpack theme to get a black theme for boot and login. That works but the kde splash screen remains blue (free DVD color).

This is what I thought too. I just wanted to hear if anyone else got this message and if the solved it somehow. Unfortunately I cannot try it now, because my trial period ran out (so I'm not sure how important this is). The couple of discs I did burn work fine though. Thanks :)

I hardly ever use mplayer. I normally prefer xine players. The only reason I'm testing in mplayer is because "DeVeDe" has mplayer as a dependency (so one would think that it uses mplayer for previewing, where the subtitles are working). I was just wandering why they didn't work in mplayer, so I thought this could be related to the problems I'm having with the subtitles on my Philips Stationary. From what you tell me this behavior is normal in mplayer and does not indicate a problem with the subtitles in the VOB files from the DVD. I will try to load the subtitles manually from the CLI with mplayer, as you suggest. The subtitles are in the VOB files. They are not external "text" files like e.g. srt files. What I don't understand is. Why are the subtitles black on the Phillips Stationary, when perfectly positioned and white during preview in DeVeDe and play in Xine/Kaffeine?

I'm having problems with subtitles when doing backups of DVD VOB files. I primarily use "DeVeDe" which has always worked for me in the past. After re authoring the VOB files the subtitles do not work in Mplayer or on my stationary Phillips player. Btw, I'm not using external subtitle files. Just the VOB files. When playing the disc or iso: - In Mplayer I don't get any subtitles at all. I cannot enable any either. - When watching the movie on my Phillips player the subtitles are kinda there, but they are in black color and are hidden in front of/or behind the black bars, when viewing a movie (letterbox format). When previewing the files in "DeVeDe" before authoring, the subtitles work perfectly. The font color is white and the position is perfect, like it should be. When viewing the final discs in Xine players like Kaffeine, subtitles also work perfectly. The result is 100% the same when using ManDVD or other similar programs instead of DeVeDe. Most of these use programs like Mplayer and mencoder, right? I'm not sure if the problem could be with one of these programs. Any experts in here? Everything I've tried does not help. Cheers opvask

Background and black kicker - nuevoXT theme. Icon theme - vista-inspirate. Emerald theme - vistaQ (I think). (why are themes so often named vista-something ) I use Beryl to make the kicker transparent. IF you are using Beryl you can do this from: beryl settings manager, choose "window management", tick "Set windows attrib by...." and open the flag "Window opacity" w:Dock:65 or click plus and select "Window type", use "grab" to select the kicker in KDE and set the desired value (65 in my case). It's possible that you need to alter your xorg.conf to make it work. I followed the instructions in the Beryl wiki for Mandriva & xorg.conf, rather than using the default code generated by Mandriva.

It is less buggy. I still get the occasional issues with it though. Another thing is the lack of information during installs or upgrading. Thanks for the tip on #2. I think I'll do just that. :)

I already tried that, but it did not work. Perhaps I did something wrong. I will try this again, ty. :)

Joke of the day? BTW: Not a declaration of war, either B)

When using Beryl in Mandriva I have a small problem. The "drop menu shadow" (kcontrol - style/effects) keeps re enabling itself everytime I log in or restart. I can disable the "menu drop shadow" effect from kcontrol, but every time I login it's enabled. It's just that particular effect. Looks very ugly with Beryl. Is it possible in some way to completely remove this feature? Uninstall? Editing it out somewhere? Cheers opvask [moved from Software by spinynorman]

I don't think so. It seems it has to be the full hdlist. But it works. I can use Synaptic now with Mandriva. Can't get the non-free updates (not plf) working yet though. All the others work great. I often use the hdlists with RPMdrake anyway. Doing the first apt-get update takes awhile (just like adding full hdlist sources to rpmdrake) but afterwards Synaptic seems to be working quite nice. I'm merely testing alternatives to rpmdrake, since using it has been quite buggy for some time. I'm also trying out smart and I have also considered the old rpmdrake, although I have never used it before. Regards opvask

I'm growing a bit tired of rpmdrake these days, so I wanted to try using Smart for a while, as an alternative. I would really like to use the "GUI way" while rpmdrake is being improved, so I figured Smart would be the solution (or even the old rpmdrake). It seems to be a nice program but I'm having a few issues. Hopefully someone here can explain me how to do this. I already looked at the Smart WIKI, but I didn't find the info I needed. 1. If I select "Upgrade all packages" I get a list of upgrades. How can I remove/de-select something from this list? Like a kernel update I do not want right now. 2. I have setup the channels, but where can I select if some sources (like PLF free/nonfree) should only be used for installs and NOT updates? Other than these "problems" it seems to be a nice program. Can someone solve this for me? :D

I want to try nerolinux 3 on Mandriva 2007.1 kde although I normally use k3b. When starting nero 3 I get this message: "/proc and /sys are not correctly mounted" Is this normal? I can tick the sign so it does not appear the next time I start Nero, but I'm not sure if the message indicates a problem that I should fix. How to fix this?

Thanks ianw1974. I haven't tried it yet, because I removed Kubuntu/Ubuntu. I Hardly ever used it anymore. BUT, I'll be needing/using your tips regarding this, in the future. That's for sure. :D

I guess sleep is overrated. :D I didn't do it quite that way. You're right, that is pretty simple. I did it almost that way, but I installed the driver myself before running XFdrake, no wonder I thought XFdrake was doing double work, when it also seemed to install the driver. I'll remember the correct procedure from now on. I guess real simple would be - install driver/restart X and voilá, but the procedure you describe is quite simple also. BTW: thanks to your answers at the club forum, I already knew more about the correct procedure. I'm also know now, that this procedure is even easier with the "ONE" CD.

Mandriva 2007.1 (KDE) with Beryl & black transparent kicker

SOLVED (I think). :D I've been trying to get a start up script working with different script solutions, but every time it gave me some other problem. Like no --force-aiglx, no Emerald themes etc. Editing out/deleting all entries in "compositing-vm" and starting Beryl with a working script in ~/.kde/Autostart instead, seems to do the trick. So I found this suggestion, which works BUT emerald window decorations start up a bit late after logging in: #!/bin/bash beryl --replace --force-aiglx & beryl-manager & So I switched it to this solution: #!/bin/bash beryl --indirect-rendering --force-aiglx --replace & beryl-manager & - This way there is no white screen during KDE startup. - KDE loads a lot faster (like starting a normal kwin session). - When KDE is loaded the screen will blink for a moment (very short time) and Beryl/Emerald then works perfectly. BTW: The --indirect-rendering and --force-aiglx (forced aiglx due to problems with the Nvidia driver) are recommended parameters, that I have been using all the time with Beryl to avoid black windows etc. These are not a direct part of the solution, since I was already using these in "compositing-vm" or in beryl-manager/advanced settings. I just didn't know how to get these parameters working in a start script, until now. I hope this can help others with similar problems with slow kde startup/white screen during startup when using Beryl. EDIT: By following the suggestions in the Beryl-Mandriva wiki for xorg.conf I solved this in a more simple way. 1. disabled 3D effects in MCC after editing xorg.conf 2. Removed all manual entries in "compositing-wm" 3. Start Beryl-manager automatically from ~/.kde/Autostart with the command "beryl-manager"

This is merely a cosmetic thing. Beryl and the system is working perfect (with --force aiglx) when I'm logged in. The white screen only occurs when the kde splash screen is loading/while kde is loading. I guess, this happens when beryl takes over the windows management/decoration. I think it's a pretty common thing in Mandriva and PcLinux. Having tried beryl with both Ubuntu and Sabayon I know that this can be avoided. I'm just not sure how. My idea at first, is to try loading beryl in some other way through a beryl-manager.desktop file in ~/.kde/Autostart or through some alternative code in "compositing-vm". Using a Autostart entry works, but with one problem - Beryl starts with normal kwin window decoration. Beryl/Emerald dosn't even take over the windows decoration in this case. It can be loaded manually from Beryl-manager or CLI. Another idea is to delay the start of beryl by a few seconds. Basically, making kde start before beryl loads. The problem is IMO related to this guide/problem/solution: http://wiki.beryl-project.org/wiki/Tips/Qu...artup_under_KDE But it's not a matter of "life or death". It's just a bit ugly with a 3-4 seconds white screen when kde is loading. I just found out that Beryl is still supported in the new "compix fusion" forum. I'll probably try to post the question there also. Regards o

I would definitely never bash PCLinuxOS or any other OS - I'm temped regarding Gnome sometimes though. B) I actually like PCL a lot and I keep it as my second OS. Mandriva is still my first choice though. PCLinuxOS still needs a bit more consistency to it's look IMO (compared to Mandriva). Other than that it's a damn fine OS and (like you mention) it's fast and very easy to install. I'm looking forward to try out future versions.

I guess some of you guys should know this scenario. When starting Mandriva KDE (same for PCLinuxOS) I get a white screen for a couple of seconds while KDE is loading. From looking in the Beryl forums, I think this is a problem with the way Beryl is being loaded (the commands "beryl" and "beryl-manager" being executed at the same time?). So I have been trying to make Beryl start with the recommended command "beryl-manager" instead of "beryl" (this also makes it easy to start beryl with commands like --Force AIGLX, because of the "advanced" options in Beryl manager). I've tried adjusting the "compositing-vm" file and I have tried disabling the 3d stuff in MCC and do things manually myself instead. I also tried delaying the "beryl-manager" command like someone suggests in the PCLinuxOS forum. None of my experiments have solved the problem. It must have something to do, with the way the 3d MCC setup is handling/starting beryl, because in other distro's like Ubuntu and Sabayon I do not get this problem. I use "native/AIGLX" and similar xorg config's in all those distro's. I'm not really sure what files the 3D option in MCC is using to start beryl. I'm only aware of the possibility to adjust the "compositing-vm" file, which can actually be a very handy thing to do, in general. My current compositing-wm: #MCC default is =yes COMPOSITING_WM_START=yes # if COMPOSITING_WM is not empty, it overrides the default compositing window manager (which is compiz) #MCC default is =beryl (tried changing this to =beryl-manager and skip the ARGS and DECORATOR options below + beryl-manager loads on startup BUT beryl then starts with kde windows decoration) COMPOSITING_WM=/usr/bin/beryl # if COMPOSITING_WM_ARGS is not empty, it overrides the default arguments for the compositing window manager COMPOSITING_WM_ARGS=--force-aiglx # the default window decorator, the specified program will be run after compositing window manager COMPOSITING_WINDOW_DECORATOR=/usr/bin/emerald Any ideas?

Thanks guys. I needed some info one the UID thing and I got it. I already considered the chmod -R 777 thing. I wasn't sure about the number though. This could be a solution, because I am the only one using this computer. At first I'll try what ianw1974 is suggesting. I think this is the exact solution I was looking for. :D