Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - phenigma

Pages: 1 ... 59 60 [61] 62 63 ... 79
Users / Re: LinuxMCE Splash Screen - a start
« on: August 27, 2010, 03:43:26 pm »
Your welcome.  I'm trying to remove the kubuntu specific branding from the boot/shutdown screens (and ultimately the dvd install) and I'm going to see if I can tackle any of the other issues mentioned by Thom here:


Users / Re: LinuxMCE Splash Screen - a start
« on: August 26, 2010, 11:54:34 pm »
I'm glad you like it.  The image is the lmce logo from the wiki, ddamron posted the logos originally.  I simply applied a single effect to it and moved the progress bar to the bottom.

Because I only have a very limited amount of hardware to test, could you share with me:
1. what video card you use (intel xxxx, nvidia xxx, etc...)
2. The video connection method (vga, hdmi, dvi, svga, ...)
3. The avwizard resolution you use
2. is the splash screen garbled or showing correctly on shutdown



Installation issues / Re: How to keep LinuxMCE up-to-date with updates
« on: August 25, 2010, 04:17:59 pm »
The lower section should be removed to properly permit updates.  Recent changes have made that portion of preferences obsolete and it can interfere with getting updates.


Users / Re: Versions Snapshot 8.10
« on: August 23, 2010, 03:57:49 pm »


Users / LinuxMCE Splash Screen - an end in sight
« on: August 23, 2010, 03:45:39 pm »
Although I've seen some concept art, I have not yet seen a functional boot splash screen for LinuxMCE.  I had some spare time so I learned a little debian packaging and played (a little) with The GIMP.  The result, a splash screen for LinuxMCE to test.  This is by no means a finished product, and I am not a graphic designer by any stretch of the imagination, but I want to know how well it works for people.  Try it out and let me know!

Grab the .deb here:

Install (as root):
Code: [Select]
dpkg -i usplash-theme-linuxmce_0.2-1_i386.deb

update-initramfs was updating an older kernel on my system so I had to execute the following to force it to build a new initrd.gz for the kernel I'm using:
Code: [Select]
update-initramfs -k $(uname -r) -u

If you run an nvidia card.... I had to add a vga=xxx line to defoptions in /boot/grub/menu.list and run update-grub to have a working splash on shutdown.  My EeePC didn't need this worked without a vga=xxx line,

The package is simply the xubuntu-artwork-usplash repacked in a new .deb with new images/throbber location (which is centered at the bottom of the image but not shown in the attached file).

It's likely to change but if you don't like it or don't want to keep it you can 'apt-get remove' the package and you'll return to the kubuntu splash.


Users / Re: Versions Snapshot 8.10
« on: August 23, 2010, 02:59:34 pm »
The snapshots are are numbered by svn revision, so you can tell which are the latest by highest svn revision in the file name.

The files you point to that show a size of '2' are snapshots that did not build correctly.  You won't have much luck with a 2 byte DVD. ;-)  Use a snapshot that is 3.8G (note that this could change, not likely to get any smaller though...)  Typically the most recent snapshot is the one to go with just remember that snapshots are just that - snapshot of the source code at a given moment.  Some contain bugs, some work well, some don't work at all.

Hope that helps.


Installation issues / Re: How to keep LinuxMCE up-to-date with updates
« on: August 23, 2010, 02:49:58 pm »
Sorry 'bout that it should've been a '-i /etc/apt/sources.list' on that line to remove the avenard repo.

Glad to hear you've got updates again!


I had built and tested a DVD before submitting the changes, but I've also done multiple installs of the Aug 18, 23248 snapshot and it's using the local repo during installation and during and MDs have access to it after creation.  If /usr/pluto/bin/deb-cache can be kept up to date when the core updates then the MDs will have access to updates without having to re-dl them.

I've only been waiting for a repo update to verify that apt is seeing updates properly before I'm fully satisfied.  Have you any updated .debs to throw in the repo?  :-)


For anyone following along the required changes were submitted to svn and are in the Aug 18, 2010 (23248) snapshot.  No repository signing was required.  If you have signed your local repository using the script you should still have no problems updating your system.


Installation issues / Re: How to keep LinuxMCE up-to-date with updates
« on: August 21, 2010, 09:35:34 pm »
The snapshots have all current changes/updates as of the moment they are created.  If you have installed from a recent snapshop then you would have the recent changes already.

Many of the snapshots have been problematic with updates.  If your snapshot install was prior to Aug 18, 2010 then there are some things you can do that should enable updates again properly.  I'll try to make this easy and painless.  Execute each of these from the terminal prompt as you have been doing already:

Remove the avenard repository from /etc/apt/sources.list:
Code: [Select]
sudo sed -e '/avenard/d' -i /etc/apt/sources.list

Re-order the local repository properly in sources.list:
Code: [Select]
sudo sed -e '/deb-cache/d' -e '1ideb file:\/usr\/pluto\/deb-cache .\/' -i /etc/apt/sources.list

Set apt preferences properly:
Code: [Select]
sudo echo 'Package: mythtv mythtv-frontend mythtv-backend mythtv-common mythtv-database mythtv-transcode-utils mythweb libmythtv-perl libmyth python-myth mythtv-themes mythplugins mytharchive mytharchive-data mythbrowser mythgallery mythgame mythmovies mythmusic mythnetvison mythnetvision-data mythnews mythvideo mythweather mythzoneminder myth-doc  
Pin: origin
Pin-Priority: 1001
'  | sudo tee /etc/apt/preferences

Update your package lists and try to upgrade:
Code: [Select]
sudo apt-get update
sudo apt-get upgrade

Try that out and let me know how it goes.


Okay, since I'b been back I've been playing a little... and although I believe that signing the repo is the ultimately the proper way to go, it needs some additional glue to keep everything synchronized.

But... I've had great success with removing the pinning, re-ordering the sources.list (placing the local repo above all others) and doing an apt-get update.  No signing required.  I'm going to test this a few more times and when I'm happy that it's not a co-incidence I'll create, and submit, a proper patch.


Users / Re: MD won't play audio from read-only NAS share
« on: July 26, 2010, 08:19:42 pm »
Check the thread I mentioned above for your foreign character issues.


Your very welcome.  Thank you!  I'll dig into more when I return.


Okay, so after a little more testing, a little more specific.

By default the local repo is actually being prioritized over because of their order in sources.list and neither is trusted and this works regardless of pinning at 500 or 600 for the local repo (I removed the local repo pinning from preferences and the local repo is still prioritized over, because of the sources.list order.)

Unfortunately the ubuntu internet repos are prioritized over the local repo becuase they are 'trusted', and the local repo is not, regardless of their order in sources.list.  Pinning the local repo >990 will overtake the ubuntu net repos but will also prevent ubuntu repo upgrades to newer versions of packages that have older versions in the local repo.

To overcome this: leave the pinning at 500 (or remove it since 500 is default anyways), order sources.list by preferred source and sign the local repository.  Everything 'just works'... fast.  :-)  I've tested this pretty extensively from lots of different angles now.

My script makes changes that should probably be implemented in:
changes to:, for sources.list order
changes to: for local repo pin-priority (it's still 600 and doesn't need to be)
changes to: to generate a key/import to apt and sign the local repo

Unfortunately I'm leaving in 5 hours for 2wks so I don't have time to set up a builder and attempt to create a proper patch before then.


I read that here: so I implemented it being safe.  And... the man page for sources.list, 2nd sentence, 2nd paragraph 'The file lists one source per line, with the most preferred source listed first.'

Pinning the local repo at 600 is functionally no different than 500 if the local repo is 'untrusted'.  The snapshots I'm using have the local repo pinned at 600 and it still downloads everything from the net.  My testing shows that the local repo doesn't overtake the internet repo until it is pinned above 990.  The problem then is that updates on the internet repo are ignored in favour of outdated versions on hte local repo.  Not desireable.  It works very much as described here:, under 'How Apt Interprets Priorities'.  Fixing the sources.list order and making the local repo trusted fixes these issues completely.

I have tested these changes with the local repo pinned at 600 and 500 and in my tests it works either way when the local repo is trusted and sources.list is ordered correctly.


Pages: 1 ... 59 60 [61] 62 63 ... 79