=== duoi_afk is now known as duoi
[01:02] <n-iCe> would you say lubuntu is the lighter desktop for Ubuntu out there?
[01:02] <Unit193> Unless you build from the core, yep.
[01:03] <ianorlindesktop> yes
[01:03] <n-iCe> lighter than xubuntu?
[01:06] <ianorlindesktop> yes
[01:10] <n-iCe> thanks!
[01:47] <one> Where is the per window kbd layout changed?
[01:54] <vrr_> hey
[01:54] <vrr_> has anyone got lubuntu running on an asus UX31A?
[01:54] <holstein> one: not sure about that.. might have to send them somehow in a script when you change to the windows in question
[01:54] <holstein> vrr_: it'll be more about the chips in there
[01:55] <holstein> vrr_: likely some graphics related problem for you? wifi? related to safe boot?
[01:55] <vrr_> no problems just trying to see if the install will be hassle free
[01:56] <holstein> vrr_: try it live
[01:56] <vrr_> im downloading the 14.04 right as we speak
[01:56] <holstein> vrr_: thats what the live CD's are for... you get to see how the operating system is, first hand, on your actual hardware, without installing
[01:57] <holstein> vrr_: 14.04 *should* be fine, and i do suggest you try it, but, keep in mind, its not officially released yet
[01:58] <vrr_> right now im running arch but it keeps breaking with updates and im tired of fixing them
[01:58] <vrr_> and i've heard lubuntu does wonders to battery life
[01:59] <holstein> vrr_: it really shouldnt
[02:00] <holstein> vrr_: its the same kernel.. and, typically, moving to linux *decreases* battery life
[02:00] <ianorlindesktop> but compared to arch?
[02:00] <holstein> the question is, why?.. and that is due to hardware support
[02:00] <vrr_> ^ in compairson to arch
[02:01] <ianorlindesktop> I still get a few hours battery life out of my laptop although it has a massive battery
[02:01] <holstein> should be similar to arch as well
[02:01] <holstein> arch would have a newer kernel..
[02:01] <ianorlindesktop> might just be lxde uses less cpu than other Desktop enviornemnts
[02:02] <vrr_> yes
[02:02] <ianorlindesktop> or will in the future
[02:02] <one> holstein: It is a gnome thing.
[02:02] <holstein> its not usually battery life that is noticable
[02:02] <holstein> but, im sure it wont be worse...
[02:02] <ianorlindesktop> turning screen brightness down helps more
[02:02] <holstein> one: why not just use gnome, then?
[02:02] <holstein> yup... screen brightness is the killer for my rig..
[02:03] <vrr_> is less of a memory ho
[02:03]  * ianorlindesktop thinks one was saying gnome uses lots of battery
[02:03] <vrr_> hog^
[02:03] <ianorlindesktop> I think cpu is more important for power
[02:03] <holstein> sure.. but the "memory" is using power.. its not like the power goes off if you have a few free mb's
[02:03] <vrr_> also lxde idles about 1%-2% cpu
[02:03] <holstein> i mean, less resource use could and likely does result in less use of battery, but, id be surprised if you'd notice
[02:04] <holstein> still.. whats that equate to in power savings?
[02:04] <holstein> the cps is up.. and powered up.. and at a lower step.. anyways, this is probably more suited for a hardware channel
[02:04] <ianorlindesktop> on desktops it could work out to power savings if you take out a graphics card and use integrated graphics
[02:04] <holstein> i dong think lubuntu will be worse on power, and its likely one of the best.. but folks tend to use it becuase its light.. not the battery savings
[02:08] <vrr_> k, just finished the dd im going in.
[02:08] <vrr_> thanks
[03:35] <bluesabre0> any lubuntu-devs about?
[03:36] <bluesabre0> we've just recently released light-locker 1.4.0 and light-locker-settings 1.2.0
[03:36] <bluesabre0> if we could get a signoff for each, please comment on each of the FFe's
[03:36] <bluesabre0> https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1296456
[03:36] <ubottu> Launchpad bug 1296456 in light-locker (Ubuntu) "[FFe] Upgrade to light-locker 1.4.0" [High,Triaged]
[03:37] <bluesabre0> https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/1297058
[03:37] <ubottu> Launchpad bug 1297058 in light-locker-settings (Ubuntu) "[FFe] [UIFe] Please update light-locker-settings to 1.2.0" [Undecided,Confirmed]
[03:38] <bluesabre0> updated translations will be collected and released near final release
[03:38] <bluesabre0> please let me know if you have any questions
[03:40] <one> How does one get a list of all kernel options?
[03:41] <holstein> one: the default kernel just is what it is.. you'd have to build your own.. i would start with kernel.org
[03:41] <holstein> !kernel
[03:41] <ubottu> The core of Ubuntu is the Linux kernel: see https://help.ubuntu.com/community/Kernel - You shouldn't have to compile your own, and if you need to troubleshoot issues, you can try a !Mainline kernel instead, but if you insist, see https://help.ubuntu.com/community/Kernel/Compile (see also !Stages)
[03:41] <holstein> !stages
[03:41] <ubottu> The Ubuntu Kernel gets updated in stages.  If you have the updated kernel, but do not have the corresponding restricted modules, you may be leaving yourself with no X when you reboot.  If you have compiled binary versions of your video driver, eg from the nVidia site, you will need to recompile them for the new kernel.  This is normal, and not a bug.
[03:42] <holstein> hmmm.. id look at a custom compiling kernel guide
[03:45] <one> holstein: I am talking about boot options.
[03:46] <one> what is the manpage called for kernel?
[03:52] <holstein> one: kms?
[03:53] <holstein> !kms
[03:53] <holstein> https://wiki.debian.org/KernelModesetting
[04:01] <one> holstein: why https?
[04:02] <holstein> one: ?
[04:02] <holstein> one: i just searched kernel mode settings and got that to share.. its relevant, if thats what you are looking for
[04:21] <one> holstein: no https
[04:21] <one> holstein: is there a corresponding manpage?
=== one is now known as these_eyes
[07:10] <guest0292> using Lubuntu 13.04.  I updated my system with sudo apt-get update, apt-get upgrade and apt-get dist-upgrade.
[07:10] <guest0292> Is it recommended to use dist-upgrade?   My firefox browser keeps crashing.  I don't know if it's related to the dist-upgrade.
=== duoi is now known as duoi_afk
=== wizonesolutions is now known as kkaland
=== kkaland is now known as wizonesolutions_
[12:10] <koell> when will lubuntu 14.04 release?
[12:11] <koell> be
[12:16] <s991533> koell: Lubuntu 14.04 (Trusty Tahr) wil be released following the general Ubuntu release schedule (more or less). Check it out at the release table for dates.
[12:16] <s991533> frome http://lubuntublog.blogspot.tw/
[12:16] <JohnDoe_71Rus> https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule
[12:16] <s991533> release schedule: https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule
[12:17] <koell> thanks guys
[14:31] <loggg> having odd problems, maybe hardware related?  Using Lubuntu 13.10, Windows 7 dual boot.  GRUB 2 should have a countdown timer, but sometimes does not.  While booting, Linux sometimes finds errors on the hard drive:
[14:31] <loggg> Mar 25 09:23:50 diamond kernel: [  303.748470] EXT4-fs (sda6): error count: 4 Mar 25 09:23:50 diamond kernel: [  303.748496] EXT4-fs (sda6): initial error at 1395685407: ext4_find_entry:1309: inode 664854 Mar 25 09:23:50 diamond kernel: [  303.748505] EXT4-fs (sda6): last error at 1395689778: ext4_remount:4755: inode 664854
[14:31] <holstein> i would start with a hard drive test
[14:31] <holstein> grub should be static.. check its config
[14:31] <holstein> !grub
[14:31] <ubottu> GRUB2 is the default Ubuntu boot manager. Lost GRUB after installing Windows? See https://help.ubuntu.com/community/RestoreGrub - For more information and troubleshooting for GRUB2 please refer to https://help.ubuntu.com/community/Grub2
[14:32] <holstein> if its changing at boot, who knows what is going on there.. did you mess with it? or manually install it?
[14:32] <loggg> If I Ignore these errors, Linux finishes booting.  I booted a FreeDOS USB stick and ran WD's official test software, and it said the hard drive was fine.
[14:33] <holstein> how long did the test take? i like smart tests that take hours.. but, its likely OK if that test says so
[14:33] <loggg> WD software is dlgdiag5.exe.  Did the quick test, took about 2 minutes.
[14:33] <holstein> i would maybe do a file system check, but, yes.. those messages may be just fine to ignore
[14:34] <holstein> i would do the normal exclusion tests.. try live CD's.. test the hardware..
[14:34] <loggg> The next problem I saw, for the first tiem yesterday, was with USB flash drives.  Says all my flash drives are read only.
[14:34] <holstein> search for and apply upgrades.. look for anything that im doing unique from the default setup, and explore
[14:35] <holstein> loggg: what format are the drives? you can have permissions issues there
[14:36] <loggg> Error creating mount point '/media/u/A219-3D7B': Read-only file system.  Most of them are FAT.  Tried monting them on another computer, and they all worked fine.
[14:36] <holstein> loggg: you may not have permission, as i suggested, for that user to create the mountpoint
[14:36] <holstein> !mount
[14:36] <ubottu> mount is used to attach devices to directories. See also https://help.ubuntu.com/community/Mount
[14:37] <holstein> i would try from the commandline as sudo, and rule out the issues being with the stick or not
[14:37] <holstein> if you are testing them on other machines, then you know they work.. if you are testing them on other linux machines, then you know they work there.. so, that leaves motherboard, which could be causing the other errors, and your users config, as well as your operating syste
[14:38] <holstein> one easy test.. run a live CD on the hardware, plug in a USB stick
[14:38] <holstein> this removes your user, and your OS from the equation.. when i say "live CD", i mean the live media without installing.. that can be USB or whatever
[14:38] <loggg> Had no problem using flash drives, until yesterday. Yeah, all these odd problems seem to point to hardware issues.  So...  I got out an air hose and blew out all the dust.  Didn't change.  Opened the computer up and reseated the memory and hard drive connections.  Still no change.
[14:40] <loggg> Remembering the capacitor plague from about 10 years back, I also looked at the capacitors. They all look fine, no bulging tops, no leaks from the base.
[14:40] <holstein> if a live CD works "fine" on the hardware, that can be telling
[14:41] <loggg> Hmm, yes, I'll try that next.  I have a Puppy Linux CD handy
[14:48] <loggg> checking /var/log/syslog...  Only 3 reports of EXT4 errors, and the position is not the same:  Initial error at 1394961716 on Mar 16, 1395591012 on Mar 23, and 1395685407 pn Mar 25 (today).
[14:49] <loggg> Oh yes, seems Ubuntu's memtest86+ is bugged again.  Got that error about there not being enough low RAM when I tried that.
[14:52] <vn151502510> loggg: you should run a live CD, open GParted, use Check function with /dev/sda6
[14:58] <loggg> On my system, sda6 is /,  sda5 is swap, sda7 is /home, sda1 is Windows 7, sda2 is FreeDOS.  ok, I'm off to try the live CD.  I'll get back on here on another computer shortly.
[15:03] <loggg_> huh, when I put the Puppy Linux CD in, Lubuntu gave me the same read only error as I got for the USB sticks.  But, the CD is supposed to be read-only.  Booting Puppy now...
[15:05] <loggg_> USB flash drive works fine under Puppy Linux.  Trying Gparted next...
[15:08] <vn151502510> it's better having some errors
[15:08] <vn151502510> or not
[15:17] <loggg_> gparted found and fixed a bunch of error, like this one: Pass 3: Checking directory connectivity '..' in /usr/src/linux-headers-3.11.0-18-generic/include/config/leds/pca9532 (664772) is <The NULL inode> (0), should be /usr/src/linux-headers-3.11.0-18-generic/include/config/leds (664755). Fix? yes
[15:19] <vn151502510> it seems harddisk wasnot turned off properly, or maybe out of date
[15:21] <loggg_> maybe that was it.  This time, GRUB had the countdown.  Lubuntu did a disk check, and found no errors.  Trying a USB flash drive now...
[15:22] <loggg_> Yes, it is reading the flash drive fine now.
[15:23] <vn151502510> congratulation
[15:23] <pmatulis> anyone running 14.04?  any bumps?
[15:31] <loggg_> Thanks vn1515... guess you already left.  I wonder though.  How did / get corrupted to start with?  Should the OS be able to fsck the / partition and fix it?
=== TheSchaf2 is now known as TheSchaf
=== jono is now known as Guest59567