[15:13] <dgroos> Good Morning!
[15:14] <dgroos> Anyone know how to install Java JRE in localapps so i can run programs based on Jave as localapp?
[15:14] <dgroos> Also, I need to install java firefox plugin in localapps.
[15:16] <dgroos> I've gotten nothing useful in an hours worth of googling...
[15:41] <highvoltage> hi dgroos
[15:41] <highvoltage> dgroos: I think you'll have to install firefox and the java plugin as localapps and then run firefox as a localapp
[15:41] <dgroos> Hi highvoltage!
[15:42] <dgroos> OK--I've got firefox installed as localapp--not seen instructions on how to install plugins to localapps...
[15:42] <dgroos> Also...
[15:42] <dgroos> are you saying that JRE won't work in localapp?
[15:43] <highvoltage> dgroos: ok, I think you'll just have to install the java plugin in the ltsp chroot then
[15:43] <highvoltage> dgroos: not 100% sure that it will work, but it should
[15:43] <dgroos> I'm all eyes ;)
[15:48] <dgroos> To install a java plugin, all I have to do is: sudo chroot /opt/ltsp/i386 apt-get install the name of plugin?  I'll try it!
[15:49] <dgroos> I couldn't find how to install a downloaded file (ie the JRE) into a local app.
[16:31] <dgroos> highvoltage: pretty quickly I was able to install the plugins but got this message--been getting it since yesterday--and can't seem to find a solution w/google.  Not even sure if it's a problem:
[16:31] <dgroos> Errors were encountered while processing:
[16:31] <dgroos>  /var/cache/apt/archives/hal_0.5.12~rc1+git20090403-0ubuntu1_i386.debE: Sub-process /usr/bin/dpkg returned an error code (1)
[16:32] <highvoltage> dgroos: what follows that?
[16:32] <dgroos> highvoltage: the regular prompt line.
[16:33] <highvoltage> ah, hal might be unhappy because proc isn't mounted
[16:34] <highvoltage> before entering the chroot, do a mount --bind /proc proc
[16:34] <highvoltage> and try installing again
[16:35] <dgroos> highvoltage: Thanks, I'll try...
[16:37] <dgroos> highvoltage: so I entered "bind /proc proc" at the prompt and hit enter.
[16:38] <dgroos> then I re-ran the previous command and got the same error.
[16:42] <highvoltage> dgroos: I remember having problems with hal inside a chroot before, but I remember seeing an error message that helped me figure it out
[16:42] <highvoltage> dgroos: sure there was no hal error message before that dpkg error message?
[16:45] <dgroos> highvoltage: yes there was--I posted it here...http://pastebin.ubuntu.com/209086/
[16:47] <highvoltage> ah now I remember
[16:47] <highvoltage> you have to do a mount --bind /dev dev
[16:47] <highvoltage> and then a mount --bind /dev/pts dev/pts
[16:47] <highvoltage> remember to unmount then again before doing the image rebuild
[16:47] <highvoltage> *them
[16:49] <dgroos> highvoltage: I'll try all this.
[16:54] <dgroos> hmmm... root@gcos2:/home/dgroos# mount --bind /dev dev
[16:54] <dgroos> mount: mount point dev does not exist
[16:55] <dgroos> is this related to the previous "bind /proc proc"  no idea what that did.
[17:20] <dgroos> so...  I've been googling the problem "mount: mount point dev does not exist" and also to figure out what the, "bind /proc proc".   I'm not getting anywhere--further help is appreciated...
[18:55] <bencrisford> !info apcalc
[22:33] <dgroos> I've entered the command: sudo mount --bind /dev dev
[22:34] <dgroos> and gotten this printout: "mount: mount point dev does not exist"  Anyone know what this means and what I need to do to mount it?
[22:38] <Svenstaro> dgroos, do "ls -lha|grep dev" and post the output
[22:38] <Svenstaro> apart from that, you probably shouldn't be doing what you are trying to do
[22:39] <dgroos> The output was... nothing--no text
[22:39] <Svenstaro> then theres no folder dev in your current folder which is right
[22:40] <Svenstaro> you are trying to bind /dev to a non-existing folder ./dev
[22:40] <dgroos> Svenstaro: I'm trying to solve an issue...
[22:40] <Svenstaro> binding /dev is generally not a good idea, what are you exactly trying to do?
[22:41] <dgroos> Here's how I typed it up earlier:
[22:41] <dgroos> dgroos: Errors were encountered while processing:
[22:41] <dgroos> [10:31am] dgroos:  /var/cache/apt/archives/hal_0.5.12~rc1+git20090403-0ubuntu1_i386.debE: Sub-process /usr/bin/dpkg returned an error code (1)
[22:42] <Svenstaro> Oh come on, how can you have so much trouble with apt-get :(
[22:42] <dgroos> Here is some more output from the problem: http://pastebin.ubuntu.com/209086/
[22:42] <Svenstaro> do apt-get clean and apt-get autoclean and repeat
[22:43] <Svenstaro> invoke-rc.d: initscript hal, action "stop" failed.
[22:43] <Svenstaro> invoke-rc.d: initscript hal, action "stop" failed.
[22:43] <Svenstaro> woops
[22:43] <Svenstaro> Anyway, what I just pasted is the critical part of the error.
[22:44] <Svenstaro> Can you kill X, switch to vt1 and stop hal manually?
[22:44] <dgroos> not sure where my X gun has gone... ;)
[22:45] <Svenstaro> try: /etc/init.d/gdm stop
[22:45] <dgroos> seriously, I can only guess at what you mean and don't know how to do it.
[22:45] <Svenstaro> but careful, it kills your session
[22:45] <Svenstaro> when in vt1, do /tc/init.d/hal stop
[22:45] <Svenstaro> and try the upgrade again
[22:46] <dgroos> OK--I'm working on NXclient, but will get off that and go right to the server...
[22:46] <dgroos> and how do I 'switch to vt1'?
[22:47] <Svenstaro> that's the blinking terminal thingie that comes up when you kill X
[22:47] <Svenstaro> this: /etc/init.d/gdm stop kills X
[22:47] <Svenstaro> so be careful not to have any work open
[22:47] <dgroos> right.
[22:49] <dgroos> Did so.  It said, * Stopping GNOME Display Manager...  [OK]
[22:49] <Svenstaro> Yeah, you should be dropped to a terminal now
[22:50] <dgroos> and then went back to the prompt.  I thought it would kill the gui?
[22:50] <Svenstaro> Did it not?
[22:50] <dgroos> No
[22:50] <Svenstaro> Prompt?
[22:51] <dgroos> Everything looks the same as before I entered the command.
[22:52] <Svenstaro> sudo killall gdm
[22:52] <dgroos> hmmm.... I didn't use sudo...
[22:52] <Svenstaro> press ctrl+alt+f1
[22:52] <Svenstaro> login as root
[22:52] <Svenstaro> do /etc/init.d/gdm stop
[22:53] <dgroos> I don't have root account set up--I typed root and my admin password but said login incorrect.
[22:54] <Svenstaro> well just login normally
[22:54] <dgroos> that is, I don't know root password...
[22:54] <Svenstaro> then type sudo -i
[22:54] <Svenstaro> and then do /etc/init.d/gdm stop
[22:55] <dgroos> In the terminal, right?  how do I get out of the ctrl+alt+f1?
[22:56] <Svenstaro> you get back using ctrl+alt+f7 but you want to do the stuff I just told you in vt1
[22:58] <dgroos> OK did and says, OK
[22:58] <Svenstaro> good, not stop hal likewise
[22:58] <Svenstaro> now*
[23:00] <dgroos> so... I type "hal" where I had previously typed "gdm" in the previous command?
[23:00] <dgroos> Oh I see above...
[23:02] <dgroos> I typed: /tc/init.d/hal stop and it says, "No such file or directory".
[23:02] <Svenstaro> Hang on, is that normal in Ubuntu?
[23:02] <Svenstaro> Can anybody else confirm?
[23:04] <Svenstaro> #ubuntu confirmed it
[23:04] <Svenstaro> You don't have that file and it's kind of bad
[23:04] <Svenstaro> It takes care of starting/stopping HAL which is important for periphal
[23:04] <dgroos> ls /    reveals nothing called "tc" at root level
[23:04] <Svenstaro> peripherals*
[23:04] <Svenstaro> tc?
[23:04] <Svenstaro> huh
[23:05] <dgroos> member:identifier:svenstaro when in vt1, do /tc/init.d/hal stop
[23:05] <dgroos> did you not mean tc?
[23:06] <Svenstaro> I meant etc, of course /etc/init.d/hal stop
[23:06] <dgroos> :) got it!
[23:06] <Svenstaro> Now try upgrading
[23:09] <dgroos> Interesting!  I updated and upgraded and it said 0000 on upgraded, newly installed, removed, not upgraded.  This is good?
[23:10] <Svenstaro> 0000?
[23:10] <Svenstaro> That means it failed
[23:10] <Svenstaro> do apt-get update && apt-get upgrade and post results
[23:11] <dgroos> Sorry. 0 upgraded, 0 newly installed, 0 to remove, 0 not upgraded
[23:13] <Svenstaro> Those are the results of
[23:13] <Svenstaro> do apt-get update && apt-get upgrade and post results ?
[23:13] <dgroos> OK did it and said: Reading package lists... Done  then it says...
[23:14] <dgroos> The program 'apt' can be found in the following packages: *openjdk-6-jdk  * sun-java5-jdk  * sun java6-jdk  and then it says...
[23:15] <dgroos> Try: sudo apt-get install <select package> then...
[23:15] <Svenstaro> wait what
[23:15] <dgroos> -bash: apt: command not found
[23:15] <Svenstaro> you made a typo
[23:15] <Svenstaro> do apt-get update && apt-get upgrade
[23:17] <dgroos> OK... this time it said: "E: Could not open lock file /var/lib/dpkg/lock - open (13 permission denied) then on next line...
[23:18] <dgroos> E: Unable to lock the administration direcotry (/var/lib/dpkg/), are you root?
[23:18] <Svenstaro> well, ARE you root?
[23:18] <dgroos> I'm sudo...
[23:19] <Svenstaro> well delete the lock
[23:19] <Svenstaro> rm /var/lib/dpkg/lock
[23:19] <dgroos> Actually, I just sudo su so now I'm root.  shall I repeat the update/upgrade?
[23:20] <Svenstaro> sudo su is not a good idea
[23:20] <Svenstaro> sudo -i is better
[23:21] <dgroos> I had tried that earlier and it didn't work--said didn't know the command i or something.
[23:22] <dgroos> Anyway, I did the sudo su thing, did update/upgrade and again said there was 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded...
[23:22] <Svenstaro> So there was nothing to upgrade.
[23:23] <dgroos> right... so it seems like the stuff you had me do earlier corrected things?  I'll go back to the gui and try to carry on and see if I get the hal complaint again.  right?
[23:24] <Svenstaro> Yeah
[23:24] <Svenstaro> Actually, better you reboot right now.
[23:24] <Svenstaro> Will fix things up faster.
[23:24] <dgroos> cool!
[23:26] <dgroos> Thanks for your help!!!  And, I'm looking forward to our next edubuntu meeting where the issues you brought up in your last e-mail to the devel list.
[23:27] <dgroos> oops--...we can discuss...
[23:36] <dgroos> looks like I spoke too soon...  http://pastebin.ubuntu.com/209351/
[23:36] <Svenstaro> duh. youve been doing that in the chroot all the time?
[23:36] <dgroos> ...though certainly thanks for your help.
[23:37] <Svenstaro> you kind of should have told me
[23:37] <dgroos> right.
[23:37] <dgroos> Indeed.
[23:41] <Svenstaro> Try this: sudo chroot /opt/ltsp/i386
[23:41] <Svenstaro> sudo -i
[23:41] <Svenstaro> apt-get upgrade
[23:42] <dgroos> did the first line and it put me in as root--skip the second line?
[23:43] <Svenstaro> yep
[23:44] <dgroos> same results as in pastebin, I believe.
[23:44] <Svenstaro> ok, still within the chroot, do /etc/init.d/hal stop
[23:45] <dgroos> ok did so--went right back to the prompt...
[23:46] <Svenstaro> Huh, what happened?
[23:46] <Svenstaro> Doing that command *within* the chroot should not do anything except give "hal stopped" or somethin
[23:47] <dgroos> I typed this: root@gcos2:~# /etc/init.d/hal stop
[23:47] <dgroos> And it said this: root@gcos2:~#
[23:48] <Svenstaro> Looks like it worked.
[23:48] <dgroos> OK did the upgrade--seems to be the same output.
[23:49] <Svenstaro> No idea, then. I suggest you google for "chroot hal upgrade" or something like that.
[23:52] <dgroos> I've been doing that and will continue--thanks so much for your effort and sorry I hadn't been explicit about working in the chroot.  I've got 1 more thought, might be related...
[23:53] <dgroos> Starting yesterday, when I open up the system log viewer it started to say:
[23:54] <dgroos> test...
[23:55] <dgroos> hmmm... 2 entries went to etherspace...
[23:55] <dgroos> It said: /var/log/btmp  You don't have enough permissions to read the file.
[23:57] <dgroos> This warning panel was strange.  I just hit the Close button and the message panel went away, but I could see the logs anyway.
[23:59] <Svenstaro> You can't normally view system logs as a normal user.