I'm having severe problems with freezing, but it really doesn't have anything to do with LMCE... well except for one ushare bug... if you have a recursive symlink (/home/data pointing to /home, for example) ushare doesn't know how to handle it so it just fills the memory and effectively freezes the computer (this bug is filed in Mantis).

My main problems are diverse. I had some electrical problems, some MB problems, some video card problems. And now I'm having an HD problem (one of my HD's in my 4 disc RAID array is failing after being on for a period of time). That disc is serves my /home partition so if it fails the computer is lost (the linux savy should now know why I had a problem with ushare)... I must of done some seriously bad shit in a past life...

The point I'm trying to get at is random freezing can mean anything... and I mean ANYTHING! You should look at /var/log/messages and maybe keep an ssh session open (on another computer) running top. That would allow you to see if there is any process that decides to go 100% and lock up the computer just before it freezes.

If you have multiple HD's then cooling is a problem. This isn't mentioned much as most people don't have many HD's in their computer. BUT, if you have something like 4-5 HD's in your computer it is raising the temperature of your entire system! it is very important to at least have a powerful fan cooling them and at best have them water cooled. It may not be your HD that fails, but the extra heat could cause your MB or CPU to fail!

Actually the Nvidia drivers will always display that message if you attempt to enable compositing. The error messages, if any, would be below it.

Other possibilities are enabling options that your video card doesn't support. What is your video card and what options are enabled in the video card device section of xorg.conf? Also, in the previous log mentioned, what does it say about AGP (is it using apgart or the internal nvapg)? Sometimes switching those improves things greatly. What kind of FPS do you get in glxgears? That may not be an official benchmark, but it usually gives you a clue as to if something is wrong with OpenGL.

In my experience, the older your Nvidia video card the more problems you will find with the updated drivers. If you have at least a 7x series you really shouldn't have any issues with video on 0710. The 6x series is supposed to be supported... but I've had tons of issues with them in the past using updated drivers. If you have an 8x series... you shouldn't have any problem at all... they just work and damn well... In short Nvidia wants you to buy the new hardware so they support the old stuff less and less.

I honestly don't remember. It was a long time ago. I'm pretty sure I commented on it somewhere in the forums, but like I said, it was a long time ago.

That said, I'm pretty sure UI2 won't even load if DRI is disabled, so it most likely was.

I just installed b4 about two weeks ago, but I haven't got the damn thing stable yet... so I haven't really done any playing of media to say whether or not I get that issue with a vanilla b4 install or not.

Question, is compositing working? You should see a line such as below in /var/log/Xorg.0.log

Code: (Xorg.0.log)

NVIDIA(0): Enabling 32-bit ARGB GLX visuals

I'm sorry, but my God. I don't install any OS without checking what it removes; it's just a given. Think about it; it's an operating system, the very core of what runs the entire computer. Even Windows does this if you're not careful. You just need to check the documentation... If you install an OS on something and just assume your previous data is going to just be there when it's finished...

Yes, you are right. I wouldn't recommend this for general users yet as installation of hardware can be a pain and the UI needs some work, but certainly not for this reason!

You're definitely right about Linux and Java, Flash, and CoDecs. It's very annoying and usually has things to do with licenses and certain companies who own the applications just not caring. That said, I too love Linux and use it as my primary desktop... when I'm not working...

Many things in Windows/Linux/Mac/Solaris/etc. can't easily be undone. It's just the nature of the beast we call a computer.

1) The AVWizard isn't for adding capture cards, it's for changing the video resolution and audio settings. You can deal with the capture card from the obiter. Check the countless forum posts and wiki entries on the subject. The PVR-150 is supported.

2) Yes, you can, but wouldn't recommend it. There are forum posts that explain how.

I was messing around with several different versions of nVidia drivers using different settings. Basically what was happening was direct rendering wasn't fully working so the GL menu that popped up blinked constantly.

That's very odd... I actually got it working out of the box when running 0704. I do remember having a problem with it once, but it was related to the video drivers...

I would say your definitely on the right track and that would be the first thing I would check. I've even had that particular issue once or twice.

That being said, random hanging is hard to diagnose. Right now I just discovered that my core is randomly freezing at relatively idle periods because of an electrical problem that I thought I fixed. You have to be careful when you plug in a phone, tv, sip adapter, core system with 5 HD's and an AMD 2.4Ghz dual core processor, Cable modem, Comcast DVR, and regular digital cable box in one outlet... Really, it should be able to handle it as it's not drawing more power than the circuit breaker can handle, but I'm getting some serious feedback or something as it's shorting out the cable modem when the core is on for extended periods of time and the core can freeze after anywhere between 2 - 12 hours. I'm going to have to verify proper grounding and such, again...

My point is there are many possible causes of such things...

I also have a possible solution here: http://forum.linuxmce.org/index.php?topic=2291.msg11276;topicseen#msg11276

That's not true. The NVidia driver definitely does use modelines. I have to use a specific one to work with my TV. It will, however, automatically ignore any modelines that the video card doesn't support. It could also ignore the modeline if the connected display isn't actually connected and turned on as it verifies that the display will actually accept the modeline. Check the log and see what it's doing. It always says if it ignores a modeline that's entered in xorg.conf.

One thing I should note that can be really confusing. If you have an xorg.conf file in /root that will be used instead of /etc/X11. I once made a backup of the xorg.conf to /root and I couldn't figure out why none of my changes to /etc/X11/xorg.conf were being used...

colinjones, have you tried using a fake username and password. Even though Windows XP has the share anonymous smbfs still requests a password to mount. I never matters what you use for a password, but it will always ask for one. CIFS may have the same quirk.

Of course, that should be handled by the script, but I don't have it handy to say if it actually does.

I never heard of Clutter before now, but it does at the very least look like a step in the right direction.

Still I would like to the the meeting minutes so I know the direction that we are heading...

From what I understand the options are to use and build upon GNash, use and build upon another OSS project (Clutter would be in this category), or just start from scratch. From my understanding GNash is a no go and this would likely have to be started from scratch to deal with licensing.

I just reported this as a bug, but I figured I'd post it here as well to see if anyone here has any thoughts:

I'm not entirely certain that installing the HDHomeRun caused it, but that's when I started seeing the issue (during the install process). The HDHomeRun still isn't completely setup as I had to hard reset in order to to regain control. Now after every boot Ushare starts and eats all the memory very quickly.

I should note that this is a brand new install (0710b3 64bit) and the Core/Hybrid was only running for a day prior to the install of the HDHomeRun. It was, however, running without issue up to that point.

I am currently working around this by quickly killing the ushare process after boot.

I'm not sure what other information would be pertinent as I have never actually used ushare before...

I guess I was wrong. I assumed (incorrectly) that the AVWizard would adjust the ModeLine. Adjusting just the UI would prove more compatible and be much easier to program, so I understand why it was done that way. However, since LinuxMCE is moving more to the Desktop arena it should be changed, which is what the mantis bug is about no doubt... I'll have to actually read it now 

In order to do this you'll have to first, back up your xorg.conf, re-run the AVWizard and select any resolution that works (it's unimportant which one) and be sure when it ask about the zoom stuff do not change anything (just leave it zoomed in). Now go to the admin page and change the MD and Onscreen Orbiter devices to the 1080i resolution, reload router, regen the Orbiter and adjust the xorg.conf to your 1080i resolution from the xorg.conf that you backed up, and reboot. Now you can tweak the Modeline using the guide in my previous post (again, I do not envy this process). Once you got that set back up that modeline! Then change the MD and Onscreen Orbiter devices to the true resolution you selected after all the modeline tweaking (only if it really changed and keep the tv standard setting), reload, regen, then edit your Xorg.conf to use that Modeline and reboot.

GOOD LUCK!

After thinking about it more, what you really need to do is look at the Handlers property listed for the device in /proc/bus/input/devices and change KERNEL=="event[0-3]*" to match it.