[00:00] <cantinstall> i also tried 15.04 and it doesn't work
[00:01] <cantinstall> I'm seing others with syslinux issues
[00:01] <drc> like I said, it did or me today, so I have no idea.
[00:26] <a1fa> is no one going to fix the indicator plugin?
[00:45] <cantinstall> finally!
[00:45] <cantinstall> I don't know why I didn't use dd before
[00:45] <cantinstall> but using dd and not the crappy unetbootin etc tools, it worked
[00:47] <cantinstall> thanks for the help!
[00:47] <cantinstall> 3 am, time to sleep.
[02:13] <zacwalls> hey so I am running Xubuntu 14.04 right now, and I was looking at themes for xfce4. And I found one. But then I realized, I didn't know how to install themes on xfce. So a few Duckduckgo results later and I came up with this: http://wiki.xfce.org/howto/install_new_themes So I followed each instructions exactly and found out I have no folder titled themes in my /.local/share/ dir. So, where do I go from here?
[02:14] <drc> make ~/.themes and put the theme you want there.
[03:33] <imthenachoman> hey guys. anyway to install xubuntu without all the bloat? like firefox or xchat and all the other stuff?
[04:04] <bazhang> just an xfce core with the mini install
[04:04] <bazhang> ah quit
[04:05] <Unit193> !xubuntu-core
[04:06] <cfhowlett> I usually give my most brilliant advice after they've left channel .,,
[04:09] <bazhang> heh same
[04:09] <bazhang> safer that way
[13:54] <a1fa> where did the screensaver settings disappear?
[13:56] <cfhowlett> xscreensaver is known to conflict with lightlocker.  in fact, it's recommended for removal
[14:04] <a1fa> cfhowlett: so under power management, i select a lock
[14:05] <a1fa> i dont really care about screensaver, i care about the lock
[14:05] <cfhowlett> state your actual question
[14:06] <a1fa> my screen does not lock on idle
[14:06] <a1fa> the screen goes blank after 15 minutes...
[14:06] <a1fa> sleep in 20 minutes, but there is no way to enable locking
[14:06] <cfhowlett> bring this question to #ubuntu please.
[14:07] <a1fa> why to ubuntu?
[14:08] <cfhowlett> more eyes
[14:08] <drc> More eyes
[14:08] <a1fa> does your lock work?
[14:09] <drc> a1fa: To make clear...you want the machine to lock on IDLE not SLEEP ?
[14:09] <a1fa> both
[14:10] <drc> I don't think ther's a easy way to make it sleep on idle...don't remember ever seeing that option.  Sleep is another matter
[14:10] <drc> But then I never care about locking, so I may have missed something.
[14:10] <a1fa> under light-locker, it says my screensaver is managed by xfce-power
[14:11] <a1fa> so both xfce power manager, and light locker have the same setting
[14:12] <a1fa> so i cant activate light locker when monitor goes blank?
[14:12] <drc> No idea, don't use it.
[14:12] <a1fa> you dont lock your screen?
[14:13] <drc> nope...I don't go anywhere I don't trust whoever is around.
[14:15] <drc> a1fa: You're not having problems locking when the machine goes to sleep, are you?
[14:17] <a1fa> my machine does not go to sleep
[14:17] <a1fa> my guess is, that works fine
[14:17] <drc> Then why "<drc> a1fa: To make clear...you want the machine to lock on IDLE not SLEEP ?
 both"
[14:18] <drc> Well, you might test it, just to make sure the process works, then worry about "idle"
[14:29] <a1fa> drc: do you use the indicator plugin?
[14:29] <drc> yes
[14:29] <a1fa> click about computer, tell me if it works
[14:30] <drc> I have no "About Computer" in my indicator plugin
[14:30] <drc> You mean "About"?
[14:30] <drc> Yes it works.
[14:34] <a1fa> does the logout work?
[14:34] <a1fa> and lock within indicator plugin
[14:35] <drc> We must have two different Indicator Plugins.
[14:35] <flocculant> a1fa: you know that different people use different versions of xubuntu - with different defaults - what do you use?
[14:39] <a1fa> this didnt work on 15.04, and 15.10
[14:40] <flocculant> ok - so you reported it as a bug or can link to the one you me too'd I assume
[14:41] <drc> a1fa: I'm going to go out on a limb here and say: 1) Something's wrong with your setup...re-install, 2) You are trying to do something it's not designed to do...forget it, or 3) report it a a bug.
[14:42] <flocculant> ftr - locking screen works fine in the 4 or 5 wily's I've installed/had installed on hardware and in vm's that I've tested for weeks
[14:42] <drc> flocculant: on just idle, not sleep?
[14:43] <flocculant> idle
[14:44] <a1fa> odd, i wiped my .config/xfce4
[14:44] <a1fa> and problem persisted
[14:44] <a1fa> got a bug report opened
[14:46] <drc> a1fa: Does that mean that you opened a new bug report or there already was one?
[14:47] <flocculant> just set to lock sleep at one minute in Display tab of Power, and auto lock session when screensaver is activated
[14:47] <flocculant> wandered off - came back, locked
[14:49] <flocculant> crisis averted
[14:49] <flocculant> found bottle opener ...
[14:50] <flocculant> a1fa: just a comment here - there actually isn't a screensaver as such - so wording in the power manager could do with changing perhaps
[14:51] <drc> OK, let's define things here:  1) Sleep and 2) Idle...just to make sure we're talking about the same things.  Go ahead.
 sleep in 20 minutes, but there is no way to enable locking - yes there is, Security tab - set Auto lock session to when screensaver is activated
[15:49] <a1fa> ok waking up monitor from sleep asked for password
[15:51] <flocculant> right - so it locked
[15:53] <a1fa> yes
[15:55] <flocculant> a1fa: as far as reporting things and hoping to get them fixed, if you see it in the released version (especially if it's only supported for 9 months) check and see if the same thing is there in the dev version - as early as possible - then report it - when you do make sure you tag the LP bug xubuntu-exp
[15:55] <flocculant> people actually use that tag
[15:56] <a1fa> i'm on 15.10 at the moment, and i've had issues with indicator plugin since 14.10 (i think)
[16:00] <flocculant> and you reported things ?
[16:01] <a1fa> yes
[16:02] <flocculant> link?
[16:02] <a1fa> https://bugs.launchpad.net/ubuntu/+source/xfce4-indicator-plugin/+bug/1484214
[16:04] <flocculant> a1fa: I don't recognise those options at all
[16:05] <a1fa> which version are you on?
[16:05] <flocculant> 15.10
[16:05] <a1fa> on the far right, do you have the wheel looking icon?
[16:05] <flocculant> I'm always on the dev version
[16:05] <a1fa> indicator-session under indicator-plugin
[16:06] <flocculant> let me boot the daily vm
[16:06] <a1fa> k
[16:06] <a1fa> one more annoyance, mouse wheel can scroll out of focus windows
[16:06] <flocculant> never seen that
[16:07] <a1fa> it took me a while to find the setting to disable focus on mouse wheel
[16:07] <drc> a1fa: Window Manager Tweaks->Workspaces-> use mouse... ?
[16:07] <a1fa> "Raise Windows when any mouse button is pressed"
[16:08] <a1fa> and one more annoyance under Panel Settings > Window Buttons
[16:08] <a1fa> siwtch windows using mouse wheel
[16:08] <drc> OK, I'm out
[16:08] <flocculant> a1fa: http://i.imgur.com/IRXTMkk.png
[16:09] <a1fa> flocculant: can you bring xfce into focus
[16:09] <a1fa> click on the furthest right icon, the session icon, and see if there is "About this Computer"
[16:09] <flocculant> on the left Xubuntu, on the right Ubuntu - Xubuntu doesn't have the gear icon and has none of the things you've listed in that bug report
[16:10] <a1fa> let me take a screenshot
[16:10] <a1fa> should i remove my xfce4 config first
[16:10] <a1fa> so its, apples to apples?
[16:11] <flocculant> a1fa: so you've installed Ubuntu then added xfce?
[16:11] <a1fa> Xubuntu, then added Unity
[16:11] <a1fa> actually, sorry you are correct
[16:11] <a1fa> i installed Ubuntu, then added xubuntu-desktop
[16:12] <flocculant> mmm
[16:13] <flocculant> well I would either remove all the ubuntu packages and see where you are
[16:13] <flocculant> though - probably quickest to reinstall with an up to date 15.10 daily after backing things up
[16:13] <a1fa> can you take another screenshot, but expose the top of xfce
[16:14] <a1fa> let me also take a screenshot
[16:14] <flocculant> we have enough on our plate trying to support xubuntu - without trying to support ubuntu with xubuntu added :)
[16:15] <flocculant> http://i.imgur.com/DXrT8eE.png
[16:16] <a1fa> here is my screenshot
[16:16] <a1fa> http://i.imgur.com/W1t61Xx.png
[16:16] <a1fa> ignore plank
[16:17] <flocculant> a1fa: right - so you have stuff there from ubuntu :)
[16:17] <a1fa> flocculant: ok
[16:19] <a1fa> the only reason why i like it, is for the sound panel
[16:22] <a1fa> http://i.imgur.com/VrEZGeO.png
[16:22] <a1fa> this is how it usually looks
[16:36] <flocculant> a1fa: can you add that info to the bug report so people know you're talking about ubuntu bits rather than xfce ones - thanks
[16:37] <a1fa> no problem
[16:37] <flocculant> thanks :)
[16:39] <a1fa> One mistery is solved
[16:40] <a1fa> I thought this was the default Xubuntu "session", and it was driving me nutts why no one else experienced it
[16:40] <a1fa> i guess new question is, why is my default "xfce4" sceleton config different than one that comes with normal Xubuntu install
[16:42] <flocculant> a1fa: well it's not a normal Xubuntu install is it :)
[16:42] <knome> the xfce4 session is supposed to be different from the xubuntu session
[16:43] <flocculant> my bad - didn't read that properly
[16:43] <a1fa> flocculant: so i got another one for you..
[16:43] <a1fa> https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1484212
[16:44] <flocculant> a1fa: ok - can you confirm that with a real Xubuntu install - if you do that then I will see if I can confirm it
[16:44] <a1fa> k
[16:48] <flocculant> actually not going to be able to confirm that bug - not got anything to confirm it with
[16:53] <a1fa> flocculant: is there a keyboard shortcut to show desktop
[16:53] <a1fa> ctrl+alt+d
[16:53] <a1fa> nice
[16:54] <a1fa> i made a plank thing to show desktop
[16:54] <a1fa> xdotool key --delay 100 ctrl+alt+d
[16:58] <a1fa> (reinstall time)
[16:58] <Hudsonkem> wrong resolution of plymounths// any idea
[19:33] <xubuntu97w> help to install xubuntu
[19:42] <morf> that was good one
[19:44] <a1fa> halp!
[19:47] <a1fa> anyone using docker?
[19:47] <a1fa> err plank
[23:32] <vista__> Hello, I am having a really severe problem with my WiFi connection ever since I upgraded
[23:32] <vista__> to 15.04
[23:33] <vista__> basically, if I downloading anything large (say, a 1GB test file), my WiFi connection fails about halfway into it (it has failed at ~380 and 670MB, to say the extremities)
[23:33] <vista__> failing meaning my computer just forgets about the existence of my AP
[23:33] <vista__> I can connect to another AP just fine
[23:34] <vista__> but to see my own AP again, I have to restart my computer
[23:34] <vista__> even using the hardware on-off WiFi switch did not help.
[23:34] <vista__> dmesg says 'disassociation reason 7' - unexpected layer 3 frame
[23:34] <mrkramps> driver issue
[23:35] <vista__> I am using a ThinkPad T420 with an Intel 6205 card
[23:35] <vista__> I did not have this problem on 14.10 or 14.05
[23:35] <vista__> Is it possible to roll back on this specific driver?
[23:36] <mrkramps> yes, but as you have to ask IF it is possible i doubt you get it done
[23:36] <vista__> I see
[23:37] <vista__> This problem is quite peculiar, though. For example, I was able to download some software off of VmWare's site no problem. However, when the actual software wanted to update itself, it consistently always failed.
[23:38] <vista__> wgetting something works, but doing the same from inside a Windows VM always gets the connection killed about halfway.
[23:40] <vista__> Connection got killed again, bit of a timeout.
[23:40] <knome> wait, is this problem occurring only inside a vm?
[23:40] <vista__> Oh, I am running Windows inside a VM.
[23:40] <vista__> No, this occurs on the host.
[23:41] <knome> the last lines made it sound like it happened in a vm only
[23:42] <vista__> well yeah, that's what I was saying. This problem only occurs during one, single download.
[23:42] <vista__> Downloading a bigger torrent (e.g. a pack of legal-to-distribute distros), e.g. lots of small, short connections cause no issue
[23:43] <vista__> I have found a (so far) 7/7 times reproducible way of getting my connection killed
[23:44] <vista__> Perhaps if I did some logging, someone could look into what could be causing the problem?
[23:48] <knome> if it's a driver issue, then the likelihood of somebody looking at it are smallish
[23:48] <knome> because then it means that person needs to have the same device as you
[23:48] <knome> that said, it never hurts to file a bug
[23:54] <vista__> Well, after reading a bit about it
[23:54] <vista__> It seems that other people have this problem as well
[23:54] <vista__> and they have been able to fix it by disabling 802.11n