[00:16] <bazhang> #xubuntu-offtopic is the place for that
[00:17] <knome> superkuh, right, i'll get you your money back.
[00:19] <superkuh> Hm. No. It doesn't seem like -offtopic is the place for talking about bugs.
[00:20] <bazhang> the sarcastic whining is
[00:21] <superkuh> But not sarcastic whining about bugs.
[00:21] <bazhang> of course not. we appreciate any bug follow-ups
[00:26] <wrongplace> knome, i feel you have a problem with people standing up to your bully ways
[00:27] <wrongplace> 3..
[00:28] <knome> wrongplace, not really, but this is not the channel to discuss that.
[00:37] <ahklerner> hi
[00:39] <D-coy> o/
[00:39] <D-coy> hi all
[00:44] <xubuntu59w> Is it possible to remove the enevlope form the indicator plugin ? after i open thunderbird it show up.
[00:45] <Unit193> You can remove indicator-messages if you don't use or like it.
[00:46] <xubuntu59w> i dont use it.. how can i remove it ?
[00:46] <D-coy> I lost the grub, cuz replace the motherboard,and i have a partition in efi :S
[00:46] <Unit193> Use the software center, synaptic, or  sudo apt-get purge indicator-messages  and it'll go away.
[00:46] <brent2> xubuntu59w: http://i.imgur.com/drXG0WB.png
[00:46] <brent2> xubuntu59w: or from terminal: sudo apt-get remove indicator-messages -y
[00:46] <Unit193> Or that. :P
[00:48] <brent2> Unit193: is the indicator-messages package xfce-specific or does it show up in the unity indicator set? because there's a second package which spawns an independent message indicator
[00:48] <brent2> for xfce
[00:49] <Unit193> brent2: indicator-messages is used in both unity, and xfce4-indicator-plugin for Xfce.
[00:49] <brent2> alright thanks
[00:49] <brent2> are all of the indicator-* packages unity indicators?
[00:52] <xubuntu78w> iI disconnected here.
[00:53] <xubuntu78w> the envelope on the indicator plugin is still there after i try to make it hidden.
[00:53] <xubuntu78w> is it permanent after i open thunderbird ?
[01:14] <brent2> is the fact that thunar stops being able to set a wallpaper after a few wallpaper changes a known bug?
[01:14] <brent2> I can change it a bunch of times but eventually it no longer works from within thunar and I have to restart my system (or probably just my session)
[01:14] <brent2> always works from the xfdesktop menu
[01:14] <brent2> kind of annoying though since that doesn't have very good sorting
[01:20] <knome> brent2, just pick one and use it ;)
[01:20] <brent2> I want to use the one that's broken
[01:20] <brent2> which is the problem
[01:20] <brent2> :p
[01:20] <knome> i mean, a wallpaper...
[01:21] <brent2> "doctor, it hurts when I do this"  - "so don't do that"
[01:21] <knome> i'd search for that bug in launchpad, if you can't find one, file it so we can potentially fix it later
[01:22] <brent2> do I join this? https://launchpad.net/~xubuntu-users
[01:22] <knome> brent2, feel free to if you consider yourself a xubuntu user, but it's not a requirement to file a bug :)
[01:23] <brent2> I've never used launchpad--how do I go about filing the bug?
[01:24] <brent2> (assuming it's not already filed)
[01:24] <knome> https://bugs.launchpad.net/ubuntu/+source/thunar
[01:24] <knome> search there first
[01:25] <brent2> alright, ty
[08:40] <sohail-ahmed> I have cloned the : https://bitbucket.org/fenics-project/dolfin, and have successfuly done make web, now when I do make import_doc, it gives an error. This error means that DOLFIN_DIR is not an environment variable. fenics is already installed on my computer, have even imported dolfin in my certain programs. How can I define this variable. I mean to what directory should I point to for this variable?
[09:26] <knome> sohail-ahmed, i'd ask the fenics/dolfin support channels
[12:02] <xubuntu983> ???
[12:02] <xubuntu983> anyone?
[12:02] <cfhowlett> you have to actually ask a support question to get an answer.  ms. cleo has retired.
[12:39] <xubuntu080> test
[13:18] <bgdmota> Hi
[13:19] <bgdmota> Screen brightness is not working, could you help me?
[13:21] <bgdmota> It displays the animation, but it does not change anything after that, I think I need to install drivers, but acer only has support for windows. Is there a way to fix this problem? Thanks in advance.
[13:24] <mpmc> Hey folks, I'm having an issue with xubuntu, pavucontrol refuses to show my bluetooth speakers, I've installed the module (pulseaudio-module-bluetooth), Any ideas guys?
[13:37] <bgdmota> Hello, I installed xubuntu and I am having some trouble with drivers, my hi (acer) only supports windows, do you know if there is a fix for this problems, (I am having problems with the screen, touchpad and bluetooth). Could you help me? Thank you.
[13:44] <bgdmota> Help me please.
[13:44] <cfhowlett> !help
[13:45] <bgdmota> ok.
[13:45] <bgdmota> Sorry
[16:57] <jarnos> Saving session on logout does not work in 14.04. What's the fix?
[17:11] <phenom> Any idea how to resolve the black screen on lid close bug? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357090
[17:12] <phenom> Is it safe to remove lightlocker and reinstall xscreensaver?
[17:12] <brainwash> phenom: did you read all the comments?
[17:12] <phenom> brainwash,
[17:12] <phenom> yes
[17:12] <phenom> and followed another thread
[17:13] <brainwash> yes, you can remove light-locker and install xscreensaver
[17:13] <phenom> similar or dupe
[17:13] <brainwash> did you verify that the bug only occurs with light-locker?
[17:13] <phenom> no
[17:14] <brainwash> you should deactivate light-locker and test again
[17:15] <brainwash> jarnos: clearing ~/.cache/sessions would be the first thing to do
[17:16] <jarnos> brainwash, while you are on a xfce session?
[17:17] <brainwash> jarnos: try it
[17:17] <brainwash> you can easily clear the session cache via settings manager > startup and session > session
[17:21] <jarnos> brainwash, I did that, loggod out with saving session enabled, logged back in, and have xchat and xfce4-terminal running. But not chromium-browser even if it was running when I logged out.
[17:21] <phenom> disabling lightlocker and installing/running xscreensaver doesn't raise any flags does it? I'm timid about installing non default lock/window managers etc.
[17:22] <holstein> i would just autostart things
[17:23] <brainwash> xscreensaver is not the default locker app anymore, but it's well tested
[17:24] <brainwash> jarnos: yeah, it's somewhat buggy and there is no one to actually fix the messy session restore functionality
[17:24] <jarnos> phenom, running "xfce4-session-logout && xflock4" on terminal works better, if xscreensaver is running than when light-locker is running.
[17:25] <brainwash> jarnos: maybe it's not even possible, because some apps just behavior differently
[17:25] <jarnos> phenom, sorry, I meant "xflock4 && xfce4-session-logout -s"
[17:25] <holstein> i like xtrlock, but its quite "bare-bones"
[17:26] <brainwash> however, the screen locking might not even be the actual problem
[17:26] <holstein> as far as adding "non-default" lockers.. which i agree can be problematic, or feel bolted on
[17:26] <phenom> This appears to be a well known problem.
[17:26] <phenom> http://xubuntu.org/news/screen-locking-in-xubuntu-14-04/
[17:27] <brainwash> this one has been fixed
[17:27] <holstein> yeah... thats just one of my default things i do on a system.. add xtrlock and remove whatever other locker
[17:27] <jarnos> holstein, you can use that. Write a script in /usr/local/bin which runs xtrlock.
[17:27] <phenom> links to,, https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1259339
[17:27] <brainwash> but your linked bug report is different
[17:27] <holstein> jarnos: right.. thats the one i *do* use
[17:27] <phenom> different bug
[17:27] <phenom> blah
[17:28] <phenom> I have 0 preference on locker. I just want it to wake up hah..
[17:28] <holstein> doesnt address session state saving, which, i personally am not interested in having
[17:29] <brainwash> phenom: so, it's your turn to remove specific packages and test other ones
[17:31] <phenom> also seems like some light locker settings have no effect. I set the screen to lock on screen close but it wants to suspend anyway. I have to mod  logind.conf to HandleLidSwitch=lock
[17:31] <brainwash> it suspends and locks the screen?
[17:31] <brainwash> this would be the expected behavior
[17:31] <phenom> yes
[17:32] <brainwash> you need to change the power manager settings instead
[17:33]  * m3n3chm0 nasZ
[17:33] <phenom> power manager is set to lock screen when closed also.
[17:33] <phenom> to no effect.
[17:33] <brainwash> well
[17:33] <brainwash> bug 1307545
[17:34] <brainwash> using the workaround is one way to fix it
[17:34] <phenom> yea, that's essentially what I did.
[17:34] <phenom> Not to the T
[17:34] <phenom> I'll look in to it.
[17:35] <brainwash> this issue should be fixed since xubuntu 13.10, but people still experience it
[17:37] <jarnos> brainwash, It seems that only app session restore can't open is chromium-browser, even if it is mentioned in ~/.cache/sessions/xfwm4-2a04da60c-30c7-4c9e-8d5f-b72e93ef7a9f.state
[17:37] <phenom> Let me try #13
[17:38] <jarnos> brainwash, and when I open chromium-browser manually, it will complain it didn't shut down correctly.
[17:38] <brainwash> jarnos: mmh
[17:38] <brainwash> maybe closely related to bug 1175601
[17:38] <phenom> Yea, never had it the issue 12.04
[17:40] <phenom> I'm going to reboot. Thanks guys. brb.
[17:40] <brainwash> bye
[17:56] <phenom> https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/Xubuntu
[17:56] <phenom> grrrr
[17:56] <phenom> jeez guys, looks like my issue is the first "known issue" on the 14.04 release notes.... https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/Xubuntu
[17:59] <brainwash> phenom: but this one has been fixed with 14.04.1
[17:59] <brainwash> http://xubuntu.org/news/xubuntu-14-04-1-released/
[17:59] <brainwash> see "Bug fixes for the first point release"
[17:59] <phenom> Not that I disagree but.
[18:00] <phenom> The xrandr "fix" still works.
[18:00] <brainwash> try this:
[18:01] <brainwash> 1a. Turn "Enable Light Locker" Off. Click "Apply".
[18:01] <brainwash> 1b. Turn "Enable Light Locker" On. Click "Apply".
[18:01] <brainwash> if you are still using light-locker
[18:02] <phenom> I did hah
[18:02] <phenom> it did something weird
[18:03] <phenom> actually
[18:03] <phenom> when it resumes, it shows a notification with a lock that the screen is currently locked and will resume in 5 seconds. Something to that effect. I have never seen that with light locker
[18:05] <brainwash> but it fixed your problem?
[18:05] <brainwash> the notification screen is part of light-locker
[18:05] <phenom> brainwash, After I did what you just said, and edited logind.conf and set HandleLidSwitch=lock
[18:06] <phenom> that came up. ok.
[18:06] <brainwash> great :)
[18:06] <phenom> but,
[18:06] <phenom> it worked for 3 or so "unlocks"
[18:06] <phenom> which this issue has seemed to be intermittent anyway.
[18:07] <phenom> If I set HandleLidSwitch=ignore
[18:08] <phenom> it seems to heed powermanagers settings
[18:09] <brainwash> it can be troublesome, sadly
[18:10] <phenom> can anyone tell me the default setting of ResetControllers=,, in gksu mousepad /etc/systemd/logind.conf please
[18:11] <phenom> it's blank is my guess
[18:11] <brent2> it's not in here: http://www.freedesktop.org/software/systemd/man/logind.conf.html
[18:11] <brent2> if you comment it out it'll reset to default
[18:12] <brent2> Does apport file the bug through launchpad or do I have to use launchpad's web interface?
[18:14] <phenom> can someone just open theirs and check please? :)
[18:14] <phenom> I'm pretty sure I didn't change the setting.
[18:14] <phenom> But I'm just a bit curious that is has no value.
[18:14] <brent2> http://i.imgur.com/5PhxeOv.png
[18:14] <brainwash> apport collects crash information and submits it to launchpad
[18:14] <brent2> ok thanks brainwash
[18:15] <elfy> utopic - not even in the file
[18:15] <brent2> phenom: is there any reason not to simply comment it out?
[18:15] <brent2> phenom: mine's blank as well as per the pic
[18:16] <phenom>  Well, I'm pretty sure I didn't change it.
[18:16] <brent2> blank is apparently the default
[18:16] <phenom> Other than I have no idea of the effect of commenting it out. :)
[18:16] <phenom> nice
[18:16] <phenom> thank you sir
[18:16] <brent2> commenting it out uses default setting
[18:17] <elfy> ahh = trusty is ResetControllers=
[18:19] <phenom> I'm going to try a few things, may disconnect. If anything thinks of an ahh ha! Please let me know.
[18:19] <phenom> This bug sucks
[18:19] <phenom> :)
[18:19] <phenom> If anyone,,, rather
[18:20] <brent2> what's your bug phenom
[18:20] <phenom> https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1259339
[18:20] <phenom> I fear
[18:21] <brent2> lol i was just going to file that one..
[18:21] <brent2> or similar
[18:21] <brent2> my solution: kill xfce4-power-manager
[18:21] <brent2> problem solved
[18:21] <phenom> eyes elfy
[18:21] <brent2> I run a script at startup which kills that amongst other things
[18:21] <brent2> I'd uninstall it but it's a dependency
[18:21] <brent2> xfce4-power-manager is useless
[18:22] <brent2> just mucks up the system and does nothing
[18:22] <brainwash> dependency for?
[18:22] <brent2> phenom: is your black screen before or after logging into lightdm
[18:22] <brent2> brainwash: brightness indicator applet
[18:22] <phenom> after
[18:22] <phenom> well,,
[18:22] <brent2> phenom: i get this problem when lidswitch is set to 'ignore' and i close my lid before the laptop can fully suspend
[18:22] <brent2> this is reproducible 100% of the time
[18:23] <phenom> on boot,, I log in fine. then I close lid, and light locker appears albeit dim,, and when I input my password it goes black.
[18:23] <brent2> on boot after suspend, or cold boot
[18:23] <brent2> ?
[18:23] <phenom> on cold boot it works fine
[18:23] <phenom> never had a problem
[18:24] <brent2> alright, we have the same problem then
[18:24] <phenom> but after suspend and apparenlty lock.
[18:24] <brent2> exactly
[18:24] <brent2> it works fine if I wait until the laptop is fully suspended before closing the lid
[18:24] <brent2> e.g. use fn+suspend key
[18:24] <brent2> but if I close the lid before the laptop has suspended, this problem occurs
[18:24] <brent2> works totally fine without xfce4-power-manager running, so that is the problem
[18:25] <phenom> I changed lidswitch to "lock",,, and it worked fine a few times.
[18:25] <brainwash> isn't suspend super fast anyway?
[18:25] <brent2> brainwash: not with power manager running
[18:25] <brainwash> it takes like 1sec here
[18:25] <brent2> on my end it's almost instant without power manager
[18:25] <brent2> 1sec or less
[18:25] <brent2> with power manager, using the fn+suspend key, it takes 3 sec or more
[18:25] <brainwash> I see
[18:25] <brent2> and by that time I've usually closed my laptop
[18:25] <brent2> which then induces this bug
[18:26] <brent2> based on something i read on launchpad, there was a patch added recently to restore the state of the display prior to logging out, and since this form of this bug didn't occur for me in the past I can only assume that the new patch caused this regression
[18:26] <brent2> not sure though
[18:26] <brainwash> power manager has a builtin 2sec delay I think
[18:26] <brainwash> before it triggers lock screen + suspend action
[18:27] <brent2> I see
[18:28] <brainwash> feel free to file a bug report, but make sure that you don't create yet another duplicate :)
[18:28] <brent2> is there an alternate way to do so apart from apport brainwash ? apport crashes for me when submitting the bug
[18:28] <brent2> pic: http://i.imgur.com/w1YgtUw.png
[18:28] <brainwash> try "ubuntu-bug xfce4-power-manager"
[18:28] <brent2> that's what I did
[18:29] <brent2> http://i.imgur.com/6Zh540R.png
[18:29] <brainwash> did this crash happen while the web browser was loading to open the launchpad site?
[18:29] <brent2> yes
[18:30] <brent2> am I mistaken?
[18:30] <brent2> it seems to hang after this occurs, waited quite a while
[18:30] <brainwash> bug 1160569
[18:32] <brainwash> no clue
[18:32] <brainwash> tons of comments to read
[18:32] <brent2> nevermind
[18:33] <brainwash> furthermore, it's a general ubuntu issue
[18:33] <brent2> indeed
[18:33] <brent2> http://i.imgur.com/nWHGESV.png
[18:33] <brent2> I was mistaken though
[18:34] <brainwash> cross channel discussion? :D
[18:35] <phenom> brent2, How are you killing power manager?
[18:35] <Unit193> Yeah sorry, didn't see it here.
[18:35] <brent2> phenom: with conviction
[18:35] <phenom> hah
[18:35] <brent2> hang on let me check
[18:35] <phenom> thanks
[18:35] <brent2> phenom: you can literally just pkill it though
[18:35] <brent2> if you want
[18:36] <phenom> ok
[18:36] <brent2> phenom: http://i.imgur.com/VH8bOxL.png
[18:36] <brent2> i have this and i run it at boot
[18:36] <brent2> using settings -> session -> autostart
[18:36] <phenom> right
[18:36] <phenom> thank you sir
[18:36] <brent2> np
[18:36] <brent2> I use sleep 5 because otherwise some issue arises
[18:36] <brent2> although I don't remember exactly what
[18:36] <brent2> keep that in mind
[18:37] <phenom> I'm going to leave it as I have it for  a while. It's unlocked correctly the past 10 or so times.
[18:37] <phenom> understood.
[18:38] <phenom> thanks. I'm going to give that a shot if it fails. Do you notice any other issues by killing it out of curiosity?
[18:38] <brent2> none, completely solves all issues related to this bug i think
[18:39] <brent2> light locker works perfectly too
[18:39] <phenom> Have you tried a different locker by chance?
[18:39] <brent2> simpler ones like i3lock
[18:39] <brent2> but that's a standalone program with no relationship with your power settings
[18:39] <brent2> in power manager or otherwise
[18:39] <brent2> it always Just Works
[18:40] <brent2> phenom: any idea if there's a bug filed already for the fact that the logind.conf settings override power manager settings? (e.g. lid switch)
[18:40] <brent2> I don't see one
[18:41] <brainwash> that's bug bug 1307545
[18:41] <phenom> My understanding is it was supposed to.
[18:42] <phenom> ok, my misunderstanding
[18:42] <brent2> thanks brainwash
[18:42] <phenom> Oh yes,,
[18:42] <phenom> I followed that one also..
[18:42] <brent2> lol
[18:42] <phenom> I tried rm ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-power-manager.xml
[18:43] <phenom> after changing the settings.
[18:43] <brent2> so far, my black screen issue seems tied completely to whether or not I close the lid before the system suspends
[18:43] <brent2> took me a while to narrow it down to that
[18:45] <phenom> I want to start a linux,, thinkpad movement.. Keep dev's on a single platform. Preferably mine hah..
[18:45] <brent2> which thinkpad are you using?
[18:45] <phenom> x220
[18:45] <brent2> same..
[18:45] <phenom> high five
[18:46] <phenom> ;)
[18:46] <brent2> :P
[18:46] <brent2> I wonder if this could be a hardware-specific thing
[18:47] <phenom> Kind of spooky. Thinkpad is a very popular platform for dev's. I'm surprised I've had the amoung of issues in the past with this laptop.
[18:49] <phenom> My fingerprint sensor has gone bad.
[18:50] <ObrienDave> carefully clean it, q-tip and rubbing alcohol
[18:51] <brent2> mine has a few issues, ethernet port stopped working unfortunately, IPS display has all kinds of issues
[18:51] <phenom> I'm getting a million: http://pastebin.com/e6CWVCPN
[18:51] <phenom> ObrienDave, I'm afraid the hardware has failed
[18:51] <brent2> might be able to simply disable it in bios
[18:52] <ObrienDave> ^^^ worth a shot
[18:53] <phenom> I'm not getting the green led anymore,, and am getting flooded with that in dmesg.
[18:53] <phenom> ObrienDave, right on.
[18:53] <phenom> I need to get in to the machine..
[18:53] <phenom> I have no tools at present.
[18:53] <phenom> Just need a frikkin tweaker..
[18:54] <phenom> I'm living in a hotel room at present on assignment. ;P
[18:54] <phenom> Forgot the leatherman. :)
[18:55] <ObrienDave> leatherman, vise grips, duct tape. don't leave home without them ;P
[18:55] <phenom> I'll try to disable it again. I was putzing around in the settings earlier to try it and got side tracked.
[18:55] <phenom> In bios*
[18:57] <phenom> ObrienDave, Don't forget the cipro!
[18:57] <phenom> ahh
[18:57] <phenom> haha
[18:57] <ysanders> hi all, not sure if i'm in the right place but i'm having a sound issue
[18:58] <ysanders> is anyone here capable/willing to help?
[18:59] <phenom> ysanders, You should try to explain the problem in the chan.
[18:59] <ysanders> here? OK
[19:00] <phenom> indeed
[19:00] <ysanders> i recently upgraded to 14.04 and it mostly worked fine
[19:00] <ysanders> had to reinstall tex, but that was about it
[19:00] <ysanders> however, after rebooting, i don't have any sound in my headphones
[19:00] <ysanders> i have volume control open
[19:00] <ysanders> and some sound playing (a youtube video)
[19:01] <ysanders> it seems like there is sound being output, but not to my headphones
[19:02] <ysanders> i googled a bit and tried reinstalling pulseaudio and alsa-base
[19:02] <ysanders> that's pretty much it
[19:02] <phenom> Click the volume icon, sound settings, output devices, port, headphones. try that.
[19:05] <phenom> I have to sleep.
[19:05] <brent2> phenom:
[19:05] <phenom> yo
[19:05] <brent2> phenom: http://i.imgur.com/vQeRYTk.png
[19:05] <ysanders> wasn't quite sure on your instructions, but if you have to sleep maybe someone else can help?
[19:06] <brent2> ysanders: try pavucontrol
[19:06] <ysanders> ok, one sec
[19:06] <brent2> ysanders: apt-get install pavucontrol
[19:06] <ysanders> i have it open
[19:06] <ysanders> so on the output devices tab, there are two things
[19:07] <ysanders> HDMI/DisplayPort (unplugged)
[19:07] <ysanders> the volume bar thingy below the volume mixer is moving around... seems to notice the sound from the youtube video
[19:07] <phenom> click the output tab
[19:07] <ysanders> and the second port is Headphones (plugged in)
[19:07] <phenom> brent2, That looks good to me.
[19:08] <phenom> ysanders, select it.
[19:08] <brent2> phenom: http://i.imgur.com/ytWhmPv.png
[19:08] <brent2> that doesn't work for you?
[19:09] <ysanders> just a sec, let me screenshot
[19:11] <ysanders> http://imgur.com/6qTVZwq
[19:11] <ysanders> i'm afraid i didn't understand what you meant by "selecting"
[19:11] <brent2> h,,
[19:11] <brent2> hmm*
[19:11] <ysanders> the bar for the first port fluctuates as though sound is coming through, but nothing on the second port
[19:12] <brent2> can you change the first from hdmi to headphones?
[19:12] <brent2> where it says Port:
[19:13] <phenom> It looks muted
[19:13] <brent2> mute's on the far left, I don't think that's it
[19:13] <brent2> the button would look indented
[19:14] <ysanders> no, hdmi is the only option on the first port
[19:14] <ysanders> the mute button looks different if it's actually muted. also greys out the volume mixer
[19:14] <phenom> oh
[19:14] <phenom> brent2, thanks man
[19:15] <ysanders> i'm using the dark version of this xfce theme: http://xfce-look.org/content/show.php/axiom+xfwm?content=90145 -- this might make the icons look different to what you're used to
[19:15] <phenom> See you guys. Zzzz
[19:15] <brent2> ysanders: try toggling the fallback
[19:15] <brent2> phenom: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1374830
[19:15] <brent2> bug there
[19:16] <brent2> not sure how this works, do other people upvote them?
[19:16] <brent2> phenom: http://i.imgur.com/inrD2Si.png
[19:16] <knome> brent2, and you're sure it's not bug 1303736?
[19:16] <ysanders> toggling fallback didn't do anything. currently have both fallback icons toggled to "off"
[19:17] <phenom> knome, if it is,, it's not fixed
[19:17] <brent2> knome: I could be wrong but 1303736 was fixed on Aug 28th
[19:17] <knome> phenom, are you using a PPA?
[19:17] <brent2> knome: mine is a similar but different bug
[19:17] <brent2> should I note this in my bug report?
[19:18] <phenom> no
[19:18] <phenom> knome, default
[19:18] <knome> brent2, how is it different?
[19:18] <brent2> knome: it occurs exclusively when shutting the display off before the system can suspend
[19:18] <brent2> knome: it does not occur when suspending and resuming without shutting the lid
[19:18] <knome> brent2, like, closing the lid? that's the same bug.
[19:19] <brent2> clarification: lid suspension is disabled
[19:19] <brent2> e.g. I can close the lid and open the lid and nothing happens
[19:19] <knome> ok... so when do you get that bug then?
[19:19] <brent2> I press suspend key on my keyboard, then close the lid (which, on its own, does nothing)
[19:19] <brent2> if I close the lid *before* the system can suspend, I get a black screen upon reusme
[19:20] <brent2> resume*
[19:20] <brent2> after logging in
[19:20] <knome> i would argue that's still the same bug
[19:20] <brent2> knome: I don't think it is because on the 28th of last month they updated it to patch this bug
[19:21] <brent2> but this form of the bug in question still exists. Same basic issue with same symptoms but it no longer occurs for the same reason
[19:21] <brent2> should I delete my report and add the note to the one you linked?
[19:21] <brent2> (or something else)
[19:21] <knome> brent2, yes, which isn't working until you do the disable/enable cycle
[19:21] <knome> at its core, the bug might imply that you simply have problems with suspending generally
[19:21] <brent2> yes but I just installed
[19:21] <brent2> I have no problem with suspending in general
[19:21] <knome> how do you know?
[19:22] <brent2> I can suspend and resume as expected in every other case
[19:22] <brent2> literally every other method of suspension and so on
[19:22] <brent2> the only time this occurs is when the display shuts off before the system can suspend
[19:22] <knome> i still haven't heard anything that says it's a different bug...
[19:22] <brent2> ok
[19:22] <brent2> in the past, I'd get a similar bug (same symptoms, same problematic result) whenever I suspended
[19:23] <brent2> that was fixed and I confirmed that it was because I no longer got the issue
[19:23] <brent2> now, however, this new thing happens
[19:23] <brent2> that's why I think it's different
[19:23] <brent2> if that's the same by the definition typically used for bug reports then I accept that
[19:23] <brent2> but the procedure to reproduce it is not the same on my end
[19:23] <brent2> do you understand my point?
[19:23] <knome> i understand, but usually it's still the same bug
[19:24] <knome> what does "xfconf-query -c xfce4-power-manager -p /xfce-power-manager/logind-handle-lid-switch" on terminal say?
[19:24] <brent2> the workarounds and fixes in that thread don't seem to affect me on this specific one
[19:24] <brent2> sec
[19:24]  * brent2 Property "/xfce-power-manager/logind-handle-lid-switch" does not exist on channel "xfce4-power-manager".
[19:25] <phenom> knome, just fyi. I have the same exact issue. I can't speak of it being the same bug or not without sacrificing another hour of sleep. :)
[19:25] <brent2> lol
[19:26] <brent2> I just want to help get it fixed, and if it turns out to be a separate issue from bug 1303736, that will only take longer
[19:26] <phenom> And no fix has remedied the issues on any of the bug threads if found so far.
[19:26] <knome> brent2, sorry, that should be "xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch"
[19:27] <brent2> knome: 'false'
[19:27] <brent2> (as I intended)
[19:27] <knome> brent2, try setting that to true: "xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch -s true"
[19:27] <knome> brent2, then logout and login
[19:27] <knome> brent2, and try suspending
[19:27] <brent2> that works as expected but I don't want that to happen
[19:27] <brent2> unless I'm mistaken
[19:28] <brent2> that causes it to suspend when closing the lid, no?
[19:28] <knome> brent2, np.
[19:29] <knome> *no
[19:29] <brent2> ok
[19:29] <brent2> brb will try
[19:32] <brent2> knome:
[19:32] <brent2> problem occurs exactly as before
[19:34] <brent2> is it possible to edit my launchpad report for clarity?
[19:36] <bluesabre> hey brent2
[19:36] <brent2> hello
[19:36] <knome> brent2, yes
[19:36] <bluesabre> I just want to confirm a few things... so this happens when you suspend from the menu, but close your laptop lid before disk activity has stopped?
[19:37] <brent2> yes but that's much harder to do because the delay between clicking the UI button and the actual suspension occuring is much smaller
[19:37] <brent2> so, to answer you simply: yes, it still happens
[19:37] <brent2> it's just harder to reproduce
[19:37] <ysanders> in case anyone cares, i fixed my problem. it was something pretty dumb.
[19:38] <knome> ysanders, great to hear that
[19:38] <bluesabre> ok, and you have light-locker-settings configured to "Lock on Suspend" = "ON"?
[19:38] <ysanders> thanks for indulging me. tata
[19:38] <brent2> what was it ysanders
[19:38] <brent2> bluesabre: yes
[19:38] <brent2> bluesabre: but this is unrelated to the problem at hand
[19:38] <brent2> (I think)
[19:38] <brent2> problem occurs regardless of light locker settings afaik
[19:39] <bluesabre> right, just trying to get an overall idea of the conditions leading up to the issue
[19:39] <brent2> ok
[19:42] <brent2> switching devices
[19:46] <bluesabre> brent2/3: can you paste your light-locker args from `ps ux | grep light-locker`?
[19:47] <brent2> bluesabre: should/can I edit the bug report I just submitted for clarity? is it possible and/or necessary?
[19:47] <bluesabre> yes please
[19:48] <brent2> how do I go about editing it?
[19:48]  * brent2 light-locker --lock-after-screensaver=0 --lock-on-suspend --no-late-locking
[19:48] <brent2> output
[19:49] <bluesabre> Just add comments to it, or you can click the yellow edit button on the right
[19:49] <brent4> .
[19:50] <phenom> light-locker --lock-after-screensaver=0 --lock-on-suspend --no-late-locking
[19:50] <phenom> my output is the same
[19:50] <bluesabre> yeah, that looks right
[19:52] <bluesabre> brent2: I'll let the light-locker devs know, this looks like a new corner case
[19:52] <bluesabre> since the issue is fixed for you otherwise
[19:52] <brent2> I don't think this is related to light-locker as the problem stops when xfce4-power-manager is disabled
[19:53] <bluesabre> ah
[19:53] <brent2> the issue isn't fixed though
[19:53] <brent2> I have to kill or uninstall power manager for it to work
[19:53] <brent2> which means I do lose the display power management functionality
[19:53] <brent2> such as dimming etc
[19:53] <brent2> and also the nice UI
[19:56] <bluesabre> This might be fixed in the latest xfce4-power-manager, if you'd like to test it with our staging ppa?
[19:57] <brent2> I will, although I've got to leave now, I'll give it a shot when I get back
[19:57] <bluesabre> ok
[19:57] <brent2> thanks
[19:57] <brent2> :P
[20:16] <brent2> bluesabre: ppa name?
[20:16] <bluesabre> brent2: https://launchpad.net/~xubuntu-dev/+archive/ubuntu/xubuntu-staging
[20:17] <bluesabre> this will upgrade light-locker-settings as well, so be sure to open it and toggle lock-on-suspend off, apply, on, apply
[20:18] <brent2> is it possible to selectively update just those two packages?
[20:23] <bluesabre> brent2: yes
[20:24] <bluesabre> install the ppa, then sudo apt-get install xfce4-power-manager xfce4-power-manager-data xfce4-power-manager-plugins light-locker-settings
[20:24] <brent3> done and done
[20:25] <brent3> testing
[20:27] <brent3> bluesabre: same problem, same symptoms, same solution
[20:29] <bluesabre> ok, good to know
[20:29] <bluesabre> I'll ping the devs
[20:30] <vrkalak> what Dev?  Xfce devs?
[20:30] <bluesabre> yeah
[20:31] <bluesabre> one other things to try with the new xfpm...
[20:31] <brent3> bluesabre: potentially helpful information in post 178: https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1303736
[20:31] <vrkalak> bluesabre, try > /join #xfce,#xfce-devs
[20:31] <brent3> If the patch mentioned in post 178, which caches the brightness level upon suspend, was implemented, that could explain why the issue I'm experiencing occurs. If the display is completely off when the lock occurs, xfce4-power-manager may simply be turning the display off again from some errant code in that patch
[20:32] <brent3> just speculation though
[20:32] <bluesabre> good note
[20:32] <bluesabre> vrkalak: I know, I'm an xfce dev, just not one of the power-manager maintainers
[20:32] <brent3> bluesabre: this issue will be much more widespread once the unrelated bug concerning the lid switch UI setting is fixed
[20:33] <livingdaylight> greetings
[20:33] <brent3> because it requires manual configuration to even reach this point (in practice)
[20:43] <livingdaylight> I am looking for the component in xubuntu-restricted-extras responsible for playing .wmv files. Does anyone know?
[20:44] <livingdaylight> don't want to install  entire restricted-extras because already have oracle java and don't want to create conflict with ice-tea for e.g.
[20:47] <livingdaylight> I am looking for the component in xubuntu-restricted-extras responsible for playing .wmv files. Does anyone know?
[20:47] <livingdaylight> don't want to install  entire restricted-extras because already have oracle java and don't want to create conflict with ice-tea for e.g.
[20:48] <knome> livingdaylight, no need to repeat quickly; you can search for an answer in other places (like askubuntu and ubuntuforums) while you wait
[20:49] <livingdaylight> knome, sure... i just wanted those two sentences together and a lot of people had joined after I posted who wouldn't see that I thought might now
[20:50] <knome> a lot of people = two?
[20:50] <livingdaylight> i have googled but the basic message is install restricted
[20:50] <livingdaylight> knome, 6
[20:52] <brainwash> you could install and use vlc
[20:53] <brainwash> if you want to avoid xubuntu-restricted-extras
[20:53] <livingdaylight> I have vlc but it doesn't work
[20:53] <livingdaylight> i want the w32 package but medibuntu seems no longer to exist. How do we install w32 codecs these days, please?
[20:54] <livingdaylight> !medibuntu
[20:54] <livingdaylight> !w32
[20:55] <brainwash> so it's a general question, maybe someone in #ubuntu knows how to resolve your problem
[20:55] <livingdaylight> !w64codecs
[20:56] <livingdaylight> ok, I'll try there - thx.
[20:56] <knome> !bot | livingdaylight
[22:41] <vik_> hello
[22:42] <vik_> ok
[22:42] <vik_> any one there ?
[22:42] <vik_> helllo
[22:42] <vik_> need help in creating a boot disk for xbuntu on mac
[22:44] <vik_> Hii
[22:44] <vik_> any one can help
[22:48] <vik_> Hello
[22:50] <brainwash> !patience | vik_
[22:50] <brent2> vik_: use dd
[22:50] <brent2> i think macs have that
[22:51] <vik_> when i use dd
[22:51] <brent2> assuming you're using a flash drive
[22:51] <vik_> it says dd not found
[22:51] <brent2> try sudo
[22:51] <brent2> i dunno much about osx
[22:51] <brent2> sudo dd
[22:51] <vik_> ok trying
[22:51] <vik_> thanks
[22:52] <vik_> now sure any one was listening so typed question sorry.
[22:54] <brent2> https://langui.sh/2011/04/02/using-dd-in-os-x/
[23:06] <sergio-br22> hello
[23:06] <sergio-br22> someone knows how to add bluetooth in the context menu?
[23:08] <brent2> indicator-bluetooth maybe
[23:08] <brent2> sudo apt-get install indicator-bluetooth
[23:11] <brent2> sergio-br22: for that to work you might need to have xfce4-indicator-plugin and have it active on a panel
[23:11] <sergio-br22> no way, it install a lot of packages
[23:11] <brent2> and restart the panel afterward
[23:11] <brent2> lol
[23:11] <brent2> works for me: http://i.imgur.com/8v7ZVYz.png
[23:12] <sergio-br22> but i need in the context menu, don't in panel
[23:12] <sergio-br22> i want to click with right button in one file, and send it easily
[23:13] <brent2> oh
[23:13] <brent2> I think you have to make a thunar custom action for it then
[23:23] <PMunch> Is there a way to set a webmail (GMail in this case) as default for mailto links in xfce? There's an app in the software center which does it for Gnome, what about xfce?
[23:25] <Unit193> !info desktop-webmail | This looks like it.
[23:25] <xangua> You can set default webmail for mailto in Firefox
[23:31] <PMunch> xangua: Want them to work anywhere though. So to be sure I want to register directly in XFCE. Unit193: Looks promising, right now I'm looking at just creating a small script to run a browser command with a link.
[23:33] <PMunch> Unit193: Tried it but the XFCE default mail chooser didn't find it
[23:34] <Unit193> PMunch: Should be able to select /usr/bin/desktop-webmail
[23:36] <vik_> Hi
[23:36] <vik_> i have created the live usb
[23:36] <PMunch> Unit193: Didn't get recipient in the composing window..
[23:36] <PMunch> Hi vik_
[23:36] <vik_> when i boot form that usb nothing happens just the windows boot happens
[23:36] <vik_> any thing ican do
[23:37] <PMunch> vik_ are you sure you are in fact booting from the USB?
[23:37] <vik_> yes i went into F2 boot and selected the usb
[23:38] <PMunch> Hmm, seems like it doesn't recognize the drive as bootable or it's unable to find the boot part of the live usb.
[23:38] <PMunch> What does the base folder in your USB look like?
[23:39] <Unit193> PMunch: YOu could change 'URL=https://mail.google.com/mail/?extsrc=mailto&url=%s' if you can pickup the new one.
[23:39] <vik_> 1 sec
[23:40] <vik_> i have boot
[23:40] <vik_> casper
[23:40] <vik_> dists etc ..
[23:40] <vik_> on the usb
[23:40] <PMunch> Hmm, seems like you managed to write it correctly..
[23:41] <Unit193> And that looks right, would have to poke at it.
[23:42] <PMunch> vik_: Try steps 7-10 from here: http://www.johnpapa.net/bootfromusb/
[23:42] <vik_> ok
[23:45] <PMunch> Unit193: This did it for me: https://mail.google.com/mail/?view=cm&ui=2&tf=0&fs=1&to=WHOEVER%40COMPANY.COM&su=SUBJECTHERE&body=LINE1%0aLINE2
[23:45] <PMunch> Just changed it to: https://mail.google.com/mail/?view=cm&ui=2&tf=0&fs=1&to=%s