map7's questions

I'm following the tutorial following tutorial to get my Intel D2700DC motherboard's graphics working: http://daily.siebler.eu/2012/06/ubuntu-12-04-driver-for-intel-cedarview-atom-n2000-und-d2000-serie/

When I boot I'm getting a blank screen. I followed the tutorial and read all the comments. I've also tried:

Install gdm and use this instead of lightdm (ubuntu default)

sudo apt-get install gdm

Remove previous pae kernel: http://www.liberiangeek.net/2011/11/remove-old-kernels-in-ubuntu-11-10-oneiric-ocelot/

Reboot before adding cedarview packages.

Have tried with and without the video=LVDS-1:d to GRUB_CMDLINE_LINUX_DEFAULT variable in /etc/default/grub.

I still get a blank screen. I am plugged into a HD screen through the HDMI and have tried the DVI connector also. I can see the grub menu, then a little of the loading and then 'No signal'. I can still ssh into the box though so it is logging in.

lspci -v -s 00:02.0
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
    Subsystem: Intel Corporation Device 2011
    Flags: bus master, fast devsel, latency 0, IRQ 45
    Memory at 80100000 (32-bit, non-prefetchable) [size=1M]
    I/O ports at 20d0 [size=8]
    Expansion ROM at <unassigned> [disabled]
    Capabilities: <access denied>
    Kernel driver in use: pvrsrvkm
    Kernel modules: cedarview_gfx


uname -a
Linux test-desktop 3.2.0-35-generic #55-Ubuntu SMP Wed Dec 5 17:45:18 UTC 2012 i686 i686 i386 GNU/Linux

I've just upgraded to Libreoffice 3.6.3 from 3.5.7 due to a bug, it fixed the bug but presented a new problem. When I save my ODS spreadsheet with many password protected sheets (20) to an Excel spreadsheet I'm presented with a dialogue box to Re-type Passwords for every protected sheet.

I have many of these spreadsheets is there an easier way to fix this problem or will I have to re-type passwords many times to fix this?

I am having this problem as well, LO version "3.5.6.2".

I have the original documents saved as ".xls". So in theory, this should not be an issue at all. However, the end users love to make straight forward processes more complicated than is necessary, so here I am.

I did some testing: I can save my file (with protected sheet) as a ".ods" file, THEN save it to ".xls" format without issue. IF, however, I close LO after saving the file as ods, and then open LO and the ods file AGAIN, and attempt to save as xls, it fails with the error the OP has described: "Hash incompatible".

Something is being lost when Libre closes that is necessary for ODS files to be saved with password protected sheets.

EDIT:

When prompted, if you elect to "re-type", you actually get presented with several options. One option is to save without the password. However, the other option allows you to retype WITHOUT verifying a match. I used this option, and after that, the status message changed from "Hash incompatible" to "Hash compatible". I saved the document as ".xls" type, then closed Calc.

I then opened calc, and saved it as ".ods". Closed calc again. Opened the ".ods" file, and attempted to save as ".xls". Would you like to overwrite? Yes I would! And I got the password retype message again.

So, however the hash was saved the first time I retyped the password (overwriting the old hash?), it was not saved correctly because the hash was incorrect upon the same process a second time.

I'm using Mythbuntu 12.04 and I have it setup as a LTSP server.

When I boot a fat-client as my 'mythfrontend' it asks me the normal questions, language, server, username, password, then it saves that in the .mythtv/mysql.txt file. When I reboot my client it resets that file back to default. Why does mythtv or ltsp do this?

The work around I use at the moment is to create a sript called ~/bin/start_myth with the following:

#!/bin/sh

cp ~/mysql.txt ~/.mythtv
mythfrontend

The ~/mythtv.txt file holds the correct settings. I would like to remove this workaround and find out what exactly is causing this error.

I'm running Ubuntu 10.04 64bit Desktop on my server with LTSP5.2 and 10 workstations.

Everytime I put a CD or USB disk into the server it shows up with an error on all the workstations saying 'Unable to Mount '

Is there a way to stop these messages from showing on thin clients?

I've been using LTSP5.2 under Ubuntu for a while, mostly with mythbuntu. When I used to create a client image with the mythbuntu switches it created an overlay to store data for each client persistently over reboots. I could store any files in there I wanted specifically for that client.

Now that the mythbuntu switches are broken I'm going to use fat-client instead as they are maintained and work. However this does not create an overlay section.

Do I require an overlay section anymore?

Can I create one anyway? I found it good for putting settings in there per client.

Should I be using lts.conf instead?

Reference to the overlay which was in Mythbuntu 804: https://help.ubuntu.com/community/MythTV/Install/Hardy/Diskless

I'm trying to setup blackberry sync'ing with Evolution on a LTSP client. It works on the server.

I'm using Ubuntu 10.04 64bit on the server and here are the instructions I've followed to get the server working:

1. Install required syncing packages

    $ sudo apt-get install libopensync0 multisync-tools libbarry0 opensync-plugin-evolution opensync-plugin-barry
    $ msynctool --addgroup BB
    $ msynctool --addmember BB barry-sync
    $ msynctool --addmember BB evo2-sync
    $ msynctool --showgroup BB

1. Find PIN number on phone and entered it in to the config

   $ msynctool --configure BB 1

1. Syncing

   $ msynctool --sync BB

This all works but it's no good as the user logs into their thin client not the server.

Running the same steps on the client I get the error: : Synchronizing group "BBtofile" : Unable to connect : Error while synchronizing: Unable to open fifo

At first I thought this would be a USB issue, as I was plugging the device into the client and using a server side program. So I installed the following into my thin client image, rebuilt it and rebooted the client:

$ sudo apt-get install libopensync0 multisync-tools libbarry0 
opensync-plugin-evolution opensync-plugin-barry barry-util multisync0.90

On the client after reboot I tried the following command

$ ltsp-localapps xterm

within xterm

$ msynctool --sync BB

I get the same error!

So I tried btool

$ btool -M

btool displays ContactLdif Mapping information from the blackberry, so it's seeing the device.

If I unplug the device and type btool -M it tells me 'No device found'

Here are the two debug logs I get when trying to sync on the client:

Thread3078059712-6396.log

...
[1327296051.50333] >>>>>>>  osync_member_load(0x9ea8480, 
/home/dean/.opensync-0.22/group2/2, 0xbfb7c50c)
[1327296051.52517] <<<<<<<  osync_member_load: Loaded member: 0x9e9d298
[1327296051.53929] <<<<<<<  osync_group_load
[1327296051.55233]        +++++++++ This is the client #1 (barry-sync 
plugin) of group test
[1327296051.56548] >>>>>>>  
osync_queue_new(/home/dean/.opensync-0.22/group2/1/pluginpipe, 0xbfb7c50c)
[1327296051.57914] <<<<<<<  osync_queue_new: 0x9e9cda0
[1327296051.60535] <--- ERROR --- main: Unable to connect

Thread3079096000-6395.log

...
osync_queue_new(/home/dean/.opensync-0.22/group2/2/enginepipe, 0xbf8bdd08)
[1327296050.887129] <<<<<<<  osync_queue_new: 0x84250c8
[1327296050.888562] <<<<<<<  osync_client_new: 0x8424dc8
[1327296050.890041] >>>>>>>  osengine_mappingtable_new(0x8424500)
[1327296050.891511]            osengine_mappingview_new(0x8425508)
[1327296050.892941]            osengine_mappingview_new(0x8424a78)
[1327296050.894376] <<<<<<<  osengine_mappingtable_new: 0x8425678
[1327296050.895807] <<<<<<<  osengine_new: 0x8424500
[1327296050.897254] >>>>>>>  osengine_init(0x8424500, 0xbf8bdd08)
[1327296050.898717] >>>>>>>  osync_group_lock(0x8420268)
[1327296050.900192]            [GRP] FULL DEBUG: locking file 
/home/dean/.opensync-0.22/group2/lock
[1327296050.904136]            [GRP] FULL DEBUG: Successfully locked
[1327296050.905556] <<<<<<<  osync_group_lock: OSYNC_LOCK_OK
[1327296050.906992]        Spawning clients
[1327296050.909177] >>>>>>>  osync_client_spawn(0x84255e0, 0x8424500, 
0xbf8bdd08)
[1327296050.918226]            Waiting for other side to create fifo
[1327296051.921123]            Waiting for other side to create fifo
[1327296052.924263]            Waiting for other side to create fifo
[1327296053.927407]            Waiting for other side to create fifo
[1327296054.930439]            Waiting for other side to create fifo
[1327296055.933628]            Waiting for other side to create fifo
[1327296056.936901]            Queue was created
*[1327296056.944148] <--- ERROR --- osync_client_spawn: Unable to open fifo
*[1327296056.945649]        [GRP] FULL DEBUG: unlocking group test
[1327296056.947855] <--- ERROR --- osengine_init: Unable to open fifo
[1327296056.949077] >>>>>>>  osengine_free(0x8424500)
[1327296056.950923] >>>>>>>  osync_client_free(0x84255e0)
[1327296056.952270] >>>>>>>  osync_queue_free(0x8424a28)
[1327296056.953582] <<<<<<<  osync_queue_free
[1327296056.954644] >>>>>>>  osync_queue_free(0x8424bc8)
[1327296056.956703] <<<<<<<  osync_queue_free
[1327296056.958002] <<<<<<<  osync_client_free
[1327296056.959311] >>>>>>>  osync_client_free(0x8424dc8)
[1327296056.960621] >>>>>>>  osync_queue_free(0x8424f28)
[1327296056.961947] <<<<<<<  osync_queue_free
[1327296056.963243] >>>>>>>  osync_queue_free(0x84250c8)
[1327296056.964282] <<<<<<<  osync_queue_free
[1327296056.965580] <<<<<<<  osync_client_free
[1327296056.966891] >>>>>>>  osengine_mappingtable_free(0x8425678)
[1327296056.968179]            Free mappings
[1327296056.969471]            Free unmapped
[1327296056.970866]            osengine_mappingview_free(0x8425508)
[1327296056.972018]            osengine_mappingview_free(0x8424a78)
[1327296056.973320] <<<<<<<  osengine_mappingtable_free
[1327296056.974651] <<<<<<<  osengine_free
[1327296056.975972] >>>>>>>  osync_env_finalize(0x841d008, 0xbf8be19c)
[1327296056.977317]        osync_plugin_free(0x84299e0)
[1327296056.978690]        osync_plugin_free(0x8435ce8)
[1327296056.980100]        osync_plugin_free(0x8436540)
[1327296056.981443]        osync_module_unload(0x841d008, 0x84298c0)
[1327296056.982661]        osync_module_unload(0x841d008, 0x8429840)
[1327296056.983849]        osync_module_unload(0x841d008, 0x8436120)
[1327296056.984954]        osync_module_unload(0x841d008, 0x8436a20)
[1327296056.986264]        osync_module_unload(0x841d008, 0x8436c98)
[1327296056.987456]        osync_module_unload(0x841d008, 0x8437160)
[1327296056.988763]        osync_module_unload(0x841d008, 0x8437708)
[1327296056.990114]        osync_module_unload(0x841d008, 0x8437f20)
[1327296056.991470]        osync_module_unload(0x841d008, 0x8437f60)
[1327296056.992781]        osync_module_unload(0x841d008, 0x8438a90)
[1327296056.994129]        osync_module_unload(0x841d008, 0x84397c8)
[1327296056.995480]        osync_module_unload(0x841d008, 0x8439d60)
[1327296056.996832]        osync_module_unload(0x841d008, 0x843a398)
[1327296056.998142]        osync_module_unload(0x841d008, 0x843a3e0)
[1327296056.999456]        osync_module_unload(0x841d008, 0x843a8a8)
[1327296057.869] <<<<<<<  osync_env_finalize

So I'm close but I don't know why I cannot get the sync working.

Mythbuntu's control center used to have an option to setup a diskless server. I've got it going manually but I wanted to know;

Is the option to make diskless systems coming back to mythbuntu-control-center?

Where can I download the development release of mythbuntu-control-center to help make this happen?

I've got a problem with my EPG grabber script 'shepherd' for the Australian EPG. These two commands below work when I type it as user mythserver but when I put them in cron the first command creates a file of zero length:

# Collect data
18 13 * * * mythserver        /usr/bin/tv_grab_au --notimetest --output /home/mythserver/.mythtv/farm2.xmltv

# Read in data
30 4  * * * mythserver        /usr/bin/mythfilldatabase --file 1 /home/mythserver/.mythtv/farm2.xmltv

What am I missing here?