[00:01] <Ahmuck> so ... the live cd does not have an updated version of flash available for install
[00:02] <Ahmuck> 14.04.1
[03:21] <Demian_> Hey guys. I have a questions about installing lubuntu with OEM manufacturer option (sysprep)...
[03:25] <Demian__> Hey guys. I have a question about installing lubuntu with OEM manufacturer option (sysprep)...
[03:26] <Demian__> The installation does not retain settings with regards to the desktop (wallpaper, desktop icons).
[03:28] <Demian__> How could I fix the system so that I can set which desktop settings should be used by default (for new user accounts)?
[03:28] <Unit193> Not sure how that works, and not sure if that feature of ubiquity is heavily tested for Lubuntu.
[03:35] <Demian__> There seem to be a few hits on web search about the issue...
[03:36] <Unit193> Also, OEM is for you to install the system, and then give it to your client/user/parent/friend, so when they power it on it asks them for a password, user, system name, etc.  Just removes your defaults.
[03:36] <Demian__> BTW it works by choosing advanced options during installation and selecting OEM. This allows to install the system and prepare it for another end-user. After installation the computer will forget all user-specific system settings, and upon first boot it will ask the user to enter their details.
[03:36] <Demian__> Hehe. Yeah.
[03:37] <Demian__> I want to use it because at work we are installing countless PCs with Lubuntu and distributing them to individuals.
[03:38] <Unit193> Sounds like you want fog or clonezilla?
[03:39] <Demian__> Aye. We have a deployment server running Fog.
[03:40] <Demian__> So now when users start the PC, it already has a username and password. We want them to choose this for themselves, but we still want to do branding in form of the wallpaper.
[03:41] <Unit193> /etc/xdg/pcmanfm/lubuntu/pcmanfm.conf has the wallpaper.
[03:42] <Unit193> /usr/share/lubuntu/pcmanfm/main.lubuntu does too, don't remember which is used but think and hope it's that first one.
[08:37] <bong2> why is it that almost everytime i start the  pc, i would almost always change the monitor resolution settings to a higher one on lubuntu?
[09:02] <bong2> why is it that almost everytime i start the  pc, i would almost always change the monitor resolution settings to a higher one on lubuntu? im on 1280x1024 right now  but it would almost always default to 1024x768.
[09:14] <bong2> why is it that almost everytime i start the  pc, i would almost always change the monitor resolution settings to a higher one on lubuntu? im on 1280x1024 right now  but it would almost always default to 1024x768.
[09:27] <bong2> why is it that almost everytime i start the  pc, i would almost always change the monitor resolution settings to a higher one on lubuntu? im on 1280x1024 right now  but it would almost always default to 1024x768.
[13:51] <rambutan> Don't know if there are any Lubuntu devs on channel, but I'd like to express my thanks for their work.
[13:51] <rambutan> I work for a public library, and I'm rehabbing some old laptops to give to a local school
[13:51] <rambutan> that wants to start teaching Linux. Tried several lightweight distros that just wouldn't work
[13:51] <rambutan> Lubuntu, in contrast, works very well. Loads without problems, functions as expected, and
[13:51] <rambutan> recognizes the USB wireless adaptors.
[14:17] <testdr> rambutan: nice - can you list the type of hardware/laptops, so other owner of such hardware may be elated?
[19:13] <Jordan_U> I'm having a problem with the Gnome Keyring on Lubuntu 14.04. I have an SMB share that I regularly connect to (using either PCManFM or Nautilus), and I would like to store the credentials for this in a keyring which is automatically unlocked at login, so that I only need to enter my password once (when I login at lightdm). I'm having two problems with this, the first is that my Gnome Keyring does not get unlocked ...
[19:13] <Jordan_U> ... automatically at login, and my second (which is probably not an issue if the first problem is resolved) is that when I first try to connect to the share, and I am asked for my password to unlock the keyring, I am still asked for the SMB username, domain, and password. If I simply cancel and retry connecting, after having unlocked the keyring, it connects without entering any additional credentials (as it should). ...
[19:13] <Jordan_U> ... TLDR: How can I get my Gnome Keyring to be unlocked automatically at login?
[19:13] <Jordan_U> I can reproduce this problem when creating new users, and am currently booted from an Lubuntu 14.04 LiveCD just so that I have as default a system as possible for troubleshooting.
[19:17] <Jordan_U> It looks like this may be related to https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1077289 , so I'm currently trying the workaround listed there.
[19:29] <Jordan_U> Well, installing libpam-gnome-keyring has made it so that both the "login" and "Default" keyrings are unlocked automatically at login, but my credentials (which I asked to be "stored forever") are not being used when I try to connect to the share, I'm still prompted for a username, domain, and password :(
[19:35] <Unit193> Jordan_U: What libpam modules do you have installed?
[19:37] <Jordan_U> Unit193: "dpkg -l | grep libpam" outputs the following: http://sprunge.us/chWM
[19:39] <Unit193> Jordan_U: Shouldn't you have libpam-winbind too then?
[19:42] <Jordan_U> Unit193: I don't know :) Let me try installing that, though the fact that the keyring is unlocked, and I can't connect to the share by manually entering credentials, makes me think that more is going on than missing libpam-winbind.
[19:42] <Unit193> Oh, I did read some of that wrong, sorry then.
[19:43] <Unit193> I don't use a setup like yours, I just have cifs-utils and mount.cifs in my fstab.  Fuse seems to be a fair bit slower than "native" plain ol' mount.cifs.
[19:45] <Jordan_U> Unit193: Do you have your credentials unencrypted on disk?
[19:48] <Unit193> Jordan_U: Yes.  The creds for that are different, and thus it's acceptable in this setting.  Else I could try a different method, or encryptfs, or even libpam-encfs.  Sorry I can't seem to help much here.  Does fuse work otherwise?
[19:51] <Jordan_U> Unit193: Yes, ntfs-3g (and the gvfs connection to the share itself) work fine.
[19:54] <Jordan_U> Well, I'm going to reboot into my installed system and confirm that libpam-gnome-keyring is installed there, and see if I get lucky.
[19:54] <Unit193> Good luck.
[20:54] <Jordan_U> Progress! I now am at the point where I can log in, try to mount the share, have it ask me for credentials, cancel, then try again and have it succeed.
[20:55] <Unit193> Hah, well that's something.  Funny too.  Anything in .cache/upstart/lxsession.log?
[20:57] <Jordan_U> What's happening is that I now have two keyrings, "login" and "Default Keyring". At login, the "login" keyring is unlocked, but the "Default Keyring" is not unlocked. Normally, this wouldn't be a problem, as the "Login" keyring contains the password for "Default Keyring". That means that what should be happening is that when I first try to access default it should be transparently unlocked and used. The problem is that I'm hi
[21:00] <Jordan_U> So, my attempt at an ugly hack to work around that was to try to use gnome-mount to mount the share in my .profile, and run gnome-mount twice (as I know that it will fail the first time). The frustrating thing is that since gnome-mount also has the same bug (unlocks the keyring on first attempt, but fails to use it) it tries to ask for credentials on the controlling tty, but if I'm logging in graphically there is no controlli
[21:01] <Jordan_U> My hack on a hack around that was to try "echo | gnome-mount ...", but of course, (being a securely written application) gnome-mount doesn't actually use stdin to get the password from the user, so this doesn't even fail properly!
[21:03] <Jordan_U> If I make a script that runs gnome-mount twice, then run "echo ./my_really_ugly_hack | at now" it works, with the first mount spewing tons of password prompts to stdout before finally giving up. I'm tempted to do this in my .profile, and I think it would work, but the levels of uglyness here are getting astronomical. Also, the documentation for gnome-mount is almost non-existant.
[21:09] <Jordan_U> ... And it doesn't work :(
[21:10] <Unit193> Jordan_U: You may want to /run splitlong.pl, you're getting cut off a lot.
[21:13] <Jordan_U> Unit193: Thanks.
[21:14] <Unit193> "The problem is that I'm h" and "logging in graphically there is no controll".
[21:15] <Jordan_U> Unit193: With slighly not great formatting: http://pastebin.ubuntu.com/8382653/
[21:16] <Jordan_U> And my current really_ugly_hack script: http://pastebin.ubuntu.com/8382669/
[21:17] <Jordan_U> Note that the script actually does eventually mount the share if I run it a few times, so I'm thinking I may need to add some delays to allow the keyring to unlock before retrying. Making the script even more ugly.
[21:19] <Unit193> I'm sure you saw LP 1235034 and comment #4 then.
[21:21] <Unit193> Sorry for not being of any use.
[21:22] <Jordan_U> Unit193: It's nice to have someone to rant to at least :) And explaining things is helping me think more clearly about them.
[21:25] <Jordan_U> Unit193: And I had not read that comment before. I figured that if they were in the Login keyring they would work, as it would be already unlocked, but I can't figure out how to transfer credentials to a different keyring.
[21:26] <Unit193> Right, so seahorse is telling me I have 'Login', it's been unlocked, but yet I know of system boot first time I use my gpg key I have to type in the password, then gnome-keyring will cache it.  Same thing on my headless box (pineentry-curses+gpg-agent, with a timeout) too.
[21:27] <Unit193> (But gpg is all I use that for.)
[22:05] <Jordan_U> Great. My script works if I run it after login from lxterm, but not if I just allow it to run via .profile. Either way the jobs are added to atq, and I would expect that since the commands are being run by at they would have a similar environment.
[22:17] <Jordan_U> With "env -i ./my_really_ugly_hack" it also fails, so I'll have to try to figure out what from the environment is needed.
[23:31] <Jordan_U> Unit193: I finally have my hack working, if you're curious here is the final script (with the process documented in comments): http://pastebin.ubuntu.com/8383411/
[23:33] <Unit193> Jordan_U: Nice.  Also, great idea to actually use enough comments so you know what's going on if you need to look again in a few months!
[23:44] <Jordan_U> Unit193: :)