[00:08] <ianorlin> I have checked the md5sum on two saucy 64 bit alt install disks both of which the self tests at the menu with teh disk returns a bad │
[00:08] <ianorlin>                    | md5sum for lubuntu software center and I checked the md5sum of the download is this two bad burns?
[00:53] <phillw> ianorlin: try burning r e a l l y slow. The write LED will die long before the read one does.
[00:54] <ianorlin> I can't slow it down any more
[01:04] <phillw> ianorlin: that is a problem I've had in the past. the easiest work round is to get a cd-RW (or dvd-RW). It forces the writer to slow down.
[01:05] <phillw> for a usb stick, try http://www.pendrivelinux.com/multiboot-create-a-multiboot-usb-from-linux/
[01:06] <ianorlin> ah
[01:06] <phillw> I recall my trying to tell my cd writer to run at 4X for the data burn, and it decided to gallop off at 48X.. needless to say, said CD was useless :)
[01:08] <phillw> I only have -RW medai now. stops the burners getting carried away with what they *think* they can do... this is no music CD :P
[01:08] <phillw> *media*
[01:09] <ianorlin> doesn't help that I have like 100 cd-rs
[01:10] <Trabble> I'm running lubuntu (currently LiveCD, but if I confirm my HDD isn't trashed I'll install it on there) on a macbook, and can't figure out how to get it to right click
[01:10] <Trabble> any suggestions on either how to do it or where to change the settings?
[01:14] <phillw> ianorlin: try a different burner programme .. xfburn is pretty god, but there are others that may be able to run the slow burn,,, Brassero may be better for you. It really is find the one that best supports you cd/dvd writer
[01:14] <phillw> Trabble:with 13.10?
[01:18] <Trabble> yes
[01:18] <Trabble> it's an older macbook, only has a single button
[01:18] <Trabble> in OSX I would hold applekey+click and it was right click
[01:18] <Trabble> I tried that, I tried alt, and i tried ctrl, none worked
[01:19] <phillw> Trabble: which version of lubuntu are you trying to install? We have several for macs..
[01:19] <Trabble> 13.10+mac
[01:22] <phillw> Trabble: can you give me the model number so that I go search? (I am not familar with mac books, but am familiar with looking up FAQ's for people who have them).
[01:22] <Trabble> Macbook 2-1
[01:22] <Trabble> also called the "Late 2006 macbook"
[01:22] <Trabble> but I think ubuntu calls it Macbook 2-1
[01:24] <phillw> Trabble: when you said a bit old... https://help.ubuntu.com/community/MacBook2-1
[01:25] <Trabble> ;) I'm well aware. however, it's a supported processor and has a RAM bump. wifi works, sound works...only problem I'm having is the right click issue
[01:25] <Trabble> when I used ubuntu back in the day (2007 or 08 I htink this was) I know there was some ways to modify right click stuff but it was gnome
[01:26] <Trabble> oh
[01:26] <Trabble> it's on that wiki
[01:26] <Trabble> https://help.ubuntu.com/community/MacBook2-1/Hardy
[01:26] <Trabble> old version
[01:26] <phillw> VERY old version :)
[01:27] <Trabble> gotta edit xorg...herm
[01:27] <Trabble> and install a driver. double herm
[01:28] <Trabble> (i hate macbooks. just an aside)
[01:28] <Trabble> took me a few hours to get to this point. it wouldn't boot off of my USB drive, I had to go find some blank DVDs, and the first one wasn't +mac so it wouldnt' boot off of that either.
[01:28] <Trabble> anyways, I'll be back later I'm sure. hopefully I can figure this out. cheers.
[01:29] <phillw> Trabble: our mac people tend to hang out on the mailing list. If you get stuck and http://ubuntuforums.org/forumdisplay.php?f=328 cannot answer, do ask someone here about our QA team.
[01:30] <phillw> Trabble: a hint.. use the alternate and also read the release notes at https://help.ubuntu.com/community/Lubuntu/Documentation/FAQ/PPC :)
[08:42] <lozio_> salve! ho installato lubuntu e vorrei sapere come aggiungere un widget per tenere sottocontrollo la temperature della cpu. grazie
[08:43] <Unit193> !it
[08:43] <lozio_> vorrei sapere anche se fare l'aggiornamento alla 13.10 e cosa cambia dalla 13.04
[08:44] <lozio_> ok! sorry
[08:45] <lozio_> hello! I installed Lubuntu and would like to know how to add a widget to keep under control the temperature of the CPU. thanks
[08:48] <lozio_> I would also like to know if I should upgrade to 13.10 and what changes from 13.04. tnk
[08:51] <lozio_> anyone?
[08:52] <costin_> hi ppl
[08:52] <Unit193> lozio_: You can update in the update manager.
[08:54] <lozio_> Unit193: yes..but what changes from the previous version?
[08:56] <Unit193> https://wiki.ubuntu.com/SaucySalamander/ReleaseNotes/Lubuntu
[08:59] <costin_> Next release 14.04 will have supports 5 years?
[08:59] <Unit193> 3 years.
[09:00] <costin_> why not 5 ?
[09:00] <phillw> costin_: because it is not a server release :)
[09:00] <Unit193> At least because not everything is in main, and so max would be 3.
[09:00] <Unit193> phillw: Ubuntu has 5.
[09:01] <costin_> i love lubunt on my Intel e8400 is very fast :)
[09:02] <lozio_> Unit193: tnk!
[09:02] <phillw> Unit193: as there is presently no TB; things could change again, but the out going were 5 years for server, 3 years for desktop.
[09:05] <Unit193> phillw: https://wiki.ubuntu.com/Releases
[09:06] <phillw> Unit193: you have not been following closely the TB. they now await sabdfl to sort the mess out... also most of CC go time expired... c'est la vie :)
[09:08] <phillw> AS to if this relevant chat on here... I'll leave that for you. I asked on a different channel.
[11:05] <andreiiar> Can I make the choose language and the menu after ( boot live, install, check mem, boot hardisk ) dissapear for a usb live disk? I am choosing english all the time anyway and boot as live disk, I dont want it to ask me that anymore.
[12:49] <jarnos> Just upgraded to 13.10 (amd64) from 13.04  using Update manager.  System could not reboot after update, but left black screen.  Alt-SysRq-s  Alt-SysRq-u Alt-SysRq-b helped and second reboot worked.
[12:50] <jarnos> This page is still partly about Raring: http://www.lubuntu.net/blog/lubuntu-1310-saucy-salamander-released
[12:52] <jarnos> ^ link to release notes,  "1.1.0" at least.
[13:00] <jarnos> It is told in the release notes that Firefox is the default browser. I have even set it preferred in Preferred Applications dialog, but the Internet application launched using the panel item starts Chromium: http://askubuntu.com/questions/100768/why-do-firefox-preferred-applications-and-x-www-browser-disagree-on-default-bro
[13:29] <costin_> hi
[13:58] <jarnos> costin_, what's up dude?
[13:59] <costin_> what's up :)
[14:02] <costin_> i join lubunt :)
[14:59] <brainwash> locking the screen just switches to the greeter and leaves the actual session unlocked, I assume that this behavior is intended, right? otherwise it would have been fixed months ago after the xscreensaver removal
[15:20] <utusan> what does lubuntu uses for display brightness control?
[15:26] <costin_> hi ppl
[15:47] <rourick> hi :)
[15:52] <ZeThomas> hey, can somebody help me get my wifi and sound working? lubuntu 13.10, fresh install
[15:59] <costin_> Are there any core Lubuntu?
[16:00] <costin_> ?
[16:11] <rourick> 13.10 has been awesome 4 me :)
[16:11] <rourick> i love it!
[16:13] <phillw> ZeThomas: my best guess is that you have a broadcom wifi chip...
[16:13] <phillw> !broadcom | ZeThomas
[16:13] <ZeThomas> phillw: nope, realtek: lspci gives me: "Network controller: Realtek Semiconductor Co., Ltd. Device b723"
[16:13] <rourick> oh u got broadcom? i can help you that's what i use
[16:14] <rourick> oh sorry
[16:14] <phillw> ZeThomas: for sound, head over to http://ubuntuforums.org/showthread.php?t=1885240 (sound sticky, at the top)
[16:15] <phillw> ZeThomas: realtek *should* work out of the box. let me hunt :)
[16:15] <ZeThomas> phillw: sound magically started working by installing pulse, so I'm good there :)
[16:16] <phillw> ZeThomas: that is a common way to fix sound :P
[16:17] <phillw> ZeThomas: bug 1240940
[16:17] <phillw> does not look too good at the moment :(
[16:17] <phillw> "This device is appearing in some OEM machines, but driver is not yet available upstream. "
[16:17] <ZeThomas> phillw: yes, I saw that one too... damn it
[16:18] <ZeThomas> so there is no hope? a proprietary driver maybe?
[16:21] <phillw> ZeThomas: I can only suggest posting on http://ubuntuforums.org/forumdisplay.php?f=336 and mentioning the bug number. hopefully one of WiFi people there can give you a way around the bug. Sorry, but I cannot find a [solved] tag for the issue :(
[16:22] <phillw> also, do click on the bug and mark it as "affects me" so as to increase its heat and be kept in touch as to progress.
[16:23] <ZeThomas> phillw, ok, thanks
[16:27] <phillw> ZeThomas: it seems there is a windows driver for it http://wikidevi.com/wiki/Realtek_RTL8723BE_Reference_Design If that is your device then the ndiswrapper may well be a solution for you.
[16:27] <phillw> as it can 'read' windows drivers.
[16:27] <ZeThomas> phillw, how would that work?
[16:28] <phillw> ZeThomas: http://ubuntuforums.org/showthread.php?t=885847 I hasten to add that I've never used it, it is just that I'm aware it can 'read' windows drivers.
[16:31] <phillw> it really is a 'roll your sleeves up' approach, but in the absence of a linux driver, it is all I can suggest, I'm sorry to not be able to be of more help
[16:34] <phillw> ZeThomas: when you get it fixed using that. do comment on the bug report so that others who follow you can see what is required to get it working.
[18:18] <brainwash> how do I lock the session in lubuntu 13.10?
[18:19] <costin_> hi
[18:23] <SonikkuAmerica> brainwash: In Lubuntu? It should be in the Logout menu
[18:24] <brainwash> there is an entry to "lock" the session, but it simply switches to the lightdm greeter
[18:24] <brainwash> this doesn't actually lock the session
[18:30] <brainwash> so.. anyone knows what going on?
[18:31] <Unit193> brainwash: You'll not find many (or any) Lubuntu devs in the support channel.
[18:31] <brainwash> is there even a dev channel?
[18:32] <Unit193> Nope.
[18:32] <brainwash> what a bummer
[18:32] <brainwash> gotta get out of here :)
[20:47] <rourick> hi :)
[20:54] <brainwash> bug 1205384
[21:55] <rourick> hi anyone running docky with compton?
[21:55] <jarnos> brainwash, holy smoke what a security hole!
[21:56] <jarnos> Why is power manager not used in 13.10?
[21:57] <brainwash> jarnos: indeed :)
[21:59] <jarnos> brainwash,  and the bug has been known for more than two months before 13.10 was released.
[21:59] <brainwash> jarnos: yeah, kinda sad
[22:00] <brainwash> you can try http://www.webupd8.org/2013/08/lightdm-session-locker-light-locker.html
[22:00] <brainwash> this is a working solution
[22:01] <brainwash> utilizing the lightdm greeter
[22:12] <jarnos> Xfce power manager has option to lock screen on suspend/hibernate, but it does not work anymore on 13.10. 13.04 used Xscreensaver. These things should be stated in release notes.
[22:16] <phillw> jarnos: it needs a bug raising. Release notes can only be updated with a confirmed bug,
[22:17] <phillw> We will update the release notes, but those are the rules :)
[22:17] <jarnos> phillw, it is a confirmed bug.
[22:17] <phillw> jarnos: bug number, please?
[22:18] <jarnos> bug 1205384
[22:20] <phillw> jarnos: are you happy with "Lock can be circumvented by switching to console" as it does not describe your bug?
[22:21] <phillw> You have a bug, which should be raised; by all means mention the othr bug. But you need to raise one bug report per issue.
[22:21] <jarnos> phillw, as for the security with power manager, I am not aware of a report. If you run xscreensaver before suspending by the power manager, screen locks ok, but with a little delay.
[22:23] <phillw> jarnos: please do have a read of https://wiki.ubuntu.com/QATeam/Overview/#Bugs
[22:24] <phillw> jarnos: for a bug to be raised, and be looked at; it needs to follow the rules :)
[22:25] <jarnos> phillw, are you saying there is something wrong with the mentioned bug report?
[22:28] <phillw> jarnos: not at all, but you have said a different bug to what you quoted :)
[22:28] <brainwash> bug 1229486
[22:31] <jarnos> phillw, release notes do not tell anything about the change in the way screen locking in handled. xscreensaver is no more used by default, xfce power manager is no more used by default.
[22:34] <brainwash> lxsession does not lock the screen on suspend?
[22:35] <brainwash> well, lock is not the right term, should be "lock"
[22:37] <jarnos> brainwash, it does, but the lock can be broken by pressing ctrl-alt-f7.
[22:38] <brainwash> yea, so it's only one (critical) issue
[22:39] <brainwash> if everything else seems to work just fine
[22:41] <jarnos> Why does lubuntu-desktop still depend on xfce4-power-manager? Is there a point to use it?
[22:42] <phillw> brainwash: your reported bug has been reported 'upstream.'; it requires a fix from them.
[22:42] <jarnos> It does not use same means for locking display.
[22:42] <brainwash> battery tray icon? power management?
[22:42] <brainwash> phillw: the xscreensaver one?
[22:43] <phillw> jarnos: there is little point in trying to re-invent the wheel. The people who actually make the flavours work together.
[22:54] <jarnos> phillw, What exactly do you mean by re-inventing wheel here?
[22:56] <brainwash> wow, I did not expect that the switch to lightdm locking was done in upstream
[22:58] <brainwash> jarnos: what is the exact issue with xfce4-power-manager? is it missing/not installed? not doing its job?
[23:02] <phillw> jarnos: raise a bug, it wwas fixed in https://bugzilla.xfce.org/show_bug.cgi?id=8205
[23:07] <jarnos> brainwash, well, it remains installed as lubuntu-desktop depends on it. If you use it to suspend/hibernate, and you have set it in its preferences to lock screen then, it won't work unless you run xscreensaver first.
[23:07] <jarnos> phillw, but that was a bug in xfce4-session.
[23:08] <brainwash> jarnos: let me check, what the power manager actually does to lock the screen
[23:28] <brainwash> jarnos: right, xscreensaver needs to run in the background already
[23:28] <brainwash> xfce4-power-manager simply calls xscreensaver-command to lock the screen
[23:29] <brainwash> it worked before the xscreensaver removal
[23:30] <brainwash> and is now broken in 13.10
[23:38] <jarnos> brainwash, does it call xscreensaver-command in background or does it wait that the command finishes before it suspends?
[23:38] <jarnos> brainwash, maybe running in background causes that it is not ready on resume?
[23:40] <brainwash> it waits 2 seconds and calls xscreensaver, and xscreensaver waits another second to prevent the lock screen from being revealed accidentially
[23:42] <brainwash> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/xfce4-power-manager/saucy/view/head:/src/xfpm-power.c#L317
[23:42] <brainwash> weird stuff
[23:44] <phillw> brainwash: has lubuntu dropped a part needed? No one is perfect and I'm open to what you find.
[23:46] <brainwash> I'm not even using lubuntu/lxde, xscreensaver or lightdm screen locking, so I'm not familiar how exactly everything works (and what is broken now)
[23:47] <brainwash> however, I want to make sure that lubuntu is able to lock the session properly
[23:47] <brainwash> so I've pushed the bug report and tried to inform the people
[23:48] <phillw> brainwash: bug number, please :)
[23:49] <brainwash> still the same, bug 1205384
[23:49] <brainwash> and yes, it's broken upstream like you said
[23:50] <phillw> brainwash: it is not that bug, it needs a new bug reporting. one issue per bug report.
[23:51] <brainwash> it's one issue
[23:52] <phillw> brainwash: as you have diagnosed... but, ::meh::
[23:53] <brainwash> am I wrong?
[23:53] <LuvLinuxOS> Hi all
[23:53] <brainwash> maybe I'm a bit confused due to the recent bug report flood
[23:54] <brainwash> LuvLinuxOS: hello
[23:56] <LuvLinuxOS> Everyone needs to pat themselves squarely on the back for the latest Ubuntu releases!!!
[23:56] <phillw> brainwash: is bug 1205384 an issue for hibernation / sleep ?
[23:56] <LuvLinuxOS> I am really enjoying Lubuntu 13.10 Great work!!!
[23:57] <phillw> LuvLinuxOS: thanks, just wait for our 1st LTS... :D
[23:57] <brainwash> phillw: it's not (directly)
[23:59] <phillw> brainwash: then, they are two different bugs and need  reporting as such. By all ways, do refer the new bug to the other bug; but it is not our call as to if they are linked.