[05:05] <bazzle31> Who is online?
 Was anyone able to install i3 in Lubuntu successfully with sudo apt get?
 It just freezes on startup when you change the window manager before you login to desktop
[14:57] <haczak> just wanting to let people know that  lubuntu i386 runs perfectly on acer aspire 5610 bl50
[20:13] <scitex59> hi, all.  I am new to Lubuntu.  I am currently using Ubuntu 14.04 on another machine, but would like to use Lubuntu LTS.
[20:16] <mead> hello
[20:19] <mead> Lubuntu is going through some changes. you might want to go with 18.10 or wait for 19.04 for the lxqt gui
[20:19] <teward> but be aware that in 9 months you'll have to upgrade *again* if you use 18.10 or 19.04.
[20:20] <teward> 9 months or less*
[20:21] <scitex59> Just wondering if the LXQt desktop environment will be more resource hungry than the current LXLE desktop
[20:21] <mead> I installed 18.10 by mistake after my storage device died, the layout was the major difference... I went back to my comfort zone of 18.04
[20:29] <scitex59> If I install Lubuntu 18.04 LTS, how long will it be supported ?
 3 years
[20:33] <genii> So you should be able to go from 18.04 to 20.04 up to around a year after 20.04 comes out
[20:36] <scitex59> I have greatly enjoyed my experience with Ubuntu 12.04 and 14.04.  However, with each new release my hardware is becoming more outdated.  I may have to migrate to a lighter weight distro soon.
 @scitex59 [<scitex59> I have greatly enjoyed my experience with Ubuntu 12.04 and 14.04.  Ho …], Lubuntu 18.04 is the best choice for you. Works like a charm on older hardware.


[17:51] <ypwong> Hi MOTU, I have a new package and could use some help for review and sponsor :)
[17:51] <ypwong> it is bug 1392283
[22:13] <sney> Noskcaj: what's irc.fef.net?
[22:14] <sney> wrt ubuntu defaults in hexchat
[22:17] <sney> hmm, never mind I suppose, though I wonder why your diff says you added it.


[03:51] <hallowed> hey,
[03:52] <hallowed> what is the easiest way to do the equivalent of 'remote desktop' with ubuntu?
[03:52] <hallowed> via ssh...then how would one go about forwarding the gui?
[03:52] <fabricator4> For a terminal session ssh
[03:53] <hallowed> the whole gui
[03:53] <hallowed> i remember it was X..something
[03:53] <fabricator4> there's a remote desktop available... Never used it.
[03:53] <hallowed> hmmm
[03:54] <hallowed> remmina?
[03:54] <fabricator4> Under system -> preferences there's settings for "remote desktop"
[03:54] <hallowed> ok
[03:55] <hallowed> do you know what protocol it uses
[03:55] <head_victim> VNC from memory
[03:55] <hallowed> ok, i was going to ssh then forward gui
[03:55] <fabricator4> Looks like an old tute: http://www.howtoforge.com/configure-remote-access-to-your-ubuntu-desktop
[03:56] <hallowed> be more secure wouldn't it...
[03:56] <hallowed> righto, sounds simple enough
[03:56] <hallowed> work from windows/mac?
[03:57] <fabricator4> Don't know, but there's tutes on that too...
[03:58] <hallowed> k
[03:59] <head_victim> !vnc
[03:59] <head_victim> That should do it ;)
[03:59] <fabricator4> :-)
[04:00] <hallowed> sounds nice
[04:00] <fabricator4> System -> Preferences -> Startup Applications -> Remote Desktop
[04:01] <head_victim> Yeah there's always HEAPS of documentation floating around. It's just a matter of finding the right set to follow.
[04:01] <hallowed> so !VNC come with ubuntu or is a package i need to download?
[04:01] <head_victim> It's all in the link. Most of it should already be there or easily installed with apt-get (or the software centre)
[04:02] <hallowed> ok
[04:02] <hallowed> how many og you guys installed gnome on natty?
[04:03] <hallowed> much better!
[04:03] <head_victim> I don't have natty installed anywhere. I have 10.04 on this pc and 11.10 on virtualbox installs
[04:03] <hallowed> oh.....
[04:03] <fabricator4> No, tried Debian for a while though.  Same problems as Unity, but looks pretty.
[04:04] <head_victim> Yeah as many people that complain about Unity I've heard the same number complain about gnome-shell. The beauty of linux, you can choose what you like.
[04:04] <hallowed> Unity is too clumsy
[04:04] <hallowed> Yeah
[04:04] <fabricator4> Let's just forget about 25 years OO GUI development and go with a dock...
[04:04] <head_victim> I want a little more config in Unity, but I'm thinking 12.04 will be the one I really test out.
[04:05] <hallowed> whens 12.04 due?
[04:05] <head_victim> Worst case scenario, I move to LXDE
[04:05] <fabricator4> 12.04 :-)
[04:05] <head_victim> hallowed: April 2012 :)
[04:05] <hallowed> isn't it still6 month releases
[04:06] <fabricator4> 11.10 in October, then 12.04 in April
[04:06] <hallowed> k
[04:06] <fabricator4> Lxde is a bit minimal.  I like though...
[04:07] <hallowed> what is lxde?
[04:07] <hallowed> debian based?
[04:07] <head_victim> !lxde
[04:07] <head_victim> Awww it doesn't have that
[04:07] <fabricator4> :-)  hahah
[04:07] <head_victim> !lubuntu
[04:07] <head_victim> It's another desktop environment, like gnome or kde.
[04:08] <fabricator4> Tried Kde, null pointer crashes here...
[04:08] <hallowed> ya
 you work shifts?
[04:10] <hallowed>  so are guys part of the ubuntu australia mob or just into ubuntu?
[04:10] <head_victim> Indeed I do.
[04:10] <head_victim> hallowed: both :)
[04:10] <fabricator4> both
[04:10] <hallowed> ahha
[04:12] <hallowed> i checked out some screenshots of lxde
[04:12] <hallowed> looks nice
[04:13] <hallowed> very clean
[04:13] <head_victim> I found it for when I needed some P4s to work snapp
[04:13] <head_victim> snappy*
[04:13] <fabricator4> It is.  Xubuntu (Xde) isn't bad either
[04:14] <hallowed> for lubuntu where its version is 11.04
[04:14] <head_victim> I found very little performance difference between gnome and xfce
[04:14] <hallowed> does that mean its built on ubuntu 11.04? just new GUI
[04:14] <fabricator4> hallowed: correct
[04:14] <head_victim> hallowed: it's all Ubuntu, just different GUIs
[04:14] <head_victim> With varying feature sets.
[04:15] <hallowed> but i can get gnome individually but it looks like lubunut only comes as lubuntu! lol
[04:15] <head_victim> I actually spent 30 mins last night at work discussing translation with a guy at work. He couldn't understand how you could just go and fix something when you find it broken and everyone would have it fixed.
[04:15] <hallowed> can i get the lxde package and just install?
[04:15] <fabricator4> Hallowed: Yes
[04:16] <hallowed> nice
[04:16] <hallowed> looks like kde to me - hopefully it does run snappy!
[04:16] <head_victim> hallowed: just type "sudo apt-get install lubuntu-desktop" into a terminal and you can then log into it when you next go to log into your computer
[04:17] <hallowed> I might come to this channel more often!
[04:17] <hallowed> good for learning
[04:17] <head_victim> We're here to help
[04:17] <fabricator4> http://sourceforge.net/projects/lxde/files/
[04:17] <head_victim> And if we're not here, just try the mailing list
[04:18] <hallowed> natty comes with IRC client ya?
[04:18] <fabricator4> Yes, but I prefer Xchat
[04:18] <head_victim> Yep, I personally use Xchat
[04:19] <hallowed> i read ages ago that xchat on windoes i think was unsecure... ::
[04:19] <fabricator4> Windows in unsecure :-)
[04:19] <hallowed> :)
[04:19] <hallowed> righto then
[04:19] <fabricator4> People use adminstrative logins all the time.
[04:20] <fabricator4> I believe Windows 7 addresses that.
[04:20] <hallowed> oh no :0
[04:20] <hallowed> all that *right clicking 'run as admin'*
[04:20] <fabricator4> That's it :-)
[04:21] <fabricator4> Took 'em 30 years to learn that.
[04:21] <hallowed> winows was around b4 unix tho ya?
[04:21] <hallowed> *windows
[04:22] <fabricator4> No, But DOS was
[04:22] <fabricator4> Those were the days...
[04:22] <hallowed> u saying unix was around b4 dos?
[04:23] <fabricator4> Actually, AT&T had things happening with a portable system in the 70's
[04:23] <fabricator4> Heard of Kernigan and Ritchie?
[04:24] <hallowed> no
[04:24] <fabricator4> The Linus Torvolds of the 60/70s
[04:24] <hallowed> ahha
[04:25] <fabricator4> You can trace the origins of *nix all the way back to K & R
[04:25] <hallowed> :o
[04:25] <hallowed> where did dos originate then?
[04:26] <fabricator4> Digital Research, sometime around 1970
[04:26] <fabricator4> William Gates used to work for DResearch
[04:27] <fabricator4> When IBM wanted a CP/M type OS for their PC, up he popped.  The rest, as they say, is history.
[04:27] <fabricator4> http://en.wikipedia.org/wiki/Brian_Kernighan
[04:28] <hallowed> how long u used linux/unix?
[04:28] <fabricator4> http://en.wikipedia.org/wiki/Dennis_Ritchie
[04:28] <fabricator4> First used it in the early 90's
[04:28] <hallowed> long time...
[04:29] <fabricator4> Didn't use it at home until Ubuntu 8 something or other.
[04:29] <hallowed> yeah thats what i first installed i think
[04:29] <hallowed> but when i installed it it was old already!
[04:30] <hallowed> one of the free discs canonical used to post out
[04:30] <fabricator4> In the early 90's *nix only supported SCSI drive systems, so not suitable for home PCs
[04:30] <hallowed> do you pronounce scsi as SCUZZI?
[04:31] <fabricator4> Yep
[04:31] <hallowed> ah ha
[04:31] <fabricator4> Stands for.... ?
[04:31] <hallowed> nope -.-
[04:31] <fabricator4> Small Computer Systems Interface
[04:31] <fabricator4> !scsi
[04:31] <hallowed> nevder had a box with scuzzi
[04:32] <hallowed> what is that exclamation mar mean?
[04:32] <hallowed> everyone on here uses them?
[04:32] <fabricator4> Trying to get the info bot to give a definition
[04:32] <fabricator4> !SCSI
[04:32] <hallowed> oh cool
[04:33] <hallowed> does it work for anything?
[04:33] <fabricator4> !ubuntu
[04:33] <hallowed> OMG
[04:33] <hallowed> !PC
[04:33] <hallowed> not work
[04:33] <fabricator4> !SSH
[04:33] <hallowed> does it pull definitions out of database?
[04:34] <fabricator4> Must do
[04:34] <hallowed> !TCP
[04:34] <hallowed> still not work
[04:34] <fabricator4> !TCPIP
[04:34] <fabricator4> Too basic.
[04:34] <hallowed> ah
[04:35] <fabricator4> !TCP/IP
[04:35] <fabricator4> Nope
[04:35] <hallowed> you heard of airstream
[04:35] <hallowed> pretty cool
[04:35] <fabricator4> No
[04:35] <hallowed> huge wifi network
[04:35] <hallowed> covers like a state
[04:36] <hallowed> they link towns with directionals and stuff
[04:36] <hallowed> pretty neat
[04:36] <fabricator4> Cool
[04:36] <hallowed> all users can go on the mini network
[04:36] <hallowed> free of course once your on there
[04:37] <fabricator4> Speed?
[04:37] <hallowed> i think its just fast wifi
[04:37] <hallowed> depends where you weer i guess
[04:37] <fabricator4> Expensive to set up, cheap to run
[04:37] <hallowed> yeah hey
[04:38] <hallowed> always thought of making something similar
[04:38] <hallowed> even just a really long point to point
[04:38] <hallowed> free phone calls!
[04:38] <fabricator4> this it? http://www.air-stream.org.au/
[04:40] <hallowed> looks like it - i think there is spin offs in WA etc cos i remember seeing a map of coverage way out of perth
[04:40] <hallowed> which state you in?
[04:40] <fabricator4> Qld
[04:40] <hallowed> wow
[04:40] <hallowed> tropical
[04:40] <hallowed> in wa here
[04:40] <fabricator4> Raining and blowing a gale
[04:40] <hallowed> ahh no
[04:41] <hallowed> that cyclone way back must have been crazy
[04:41] <fabricator4> That was up north
[04:41] <fabricator4> I'm near Brisbane
[04:41] <hallowed> ahah
[04:42] <hallowed> oh well
[04:42] <hallowed> i will come on here some time in the future
[04:42] <fabricator4> Now worries, someone is always here (usually)
[04:42] <hallowed> cya
[04:42] <fabricator4> bye
[08:46] <hallowed> hey folks
[08:46] <hallowed> i am chasing a benchmark/stress test program for ubuntu
[08:46] <hallowed> just overclocking an old mobo
[08:47] <hallowed> and got the 1386 ubuntu disc ready...
[08:47] <hallowed> *i386
[08:48] <hallowed> i have never benchmarked using ubuntu - any ideas
[08:48] <fabricator4> http://manpages.ubuntu.com/manpages/hardy/man1/stress.1.html
[08:48] <fabricator4> Might be an old reference.  I haven't done it either.
[08:49] <head_victim> phronix have a bench test suite for linux from memory
[08:49] <head_victim> Depends on what you want to test
[08:49] <fabricator4> Most of my old machines, I try NOT to stress them too much :-)
[08:51] <hallowed> cheers
[08:51] <hallowed> the program "stress" sounds nice - just got the package
[08:52] <fabricator4> Hey that's not a bad program for testing.  Might have a look myself.  CPU torture anyone?
[08:52] <hallowed> we will see how hot it gets... :)
[08:52] <head_victim> If it's just cpu I use burnP6
[08:52] <fabricator4> You can target different areas, CPU, Memory mallocs, io sync
[08:53] <hallowed> yeah looks good
[08:54] <hallowed> but how keep a check on temp & CPU usage?
[08:54] <hallowed> or does it show that aswell?
[08:54] <hallowed> in windows everst dows the trick
[08:54] <hallowed> *everest
[08:54] <fabricator4> No idea.  You might need to display temp separately.
[08:55] <hallowed> any apps built into ubuntu? system properties perhaps...
[08:56] <fabricator4> Not that I know of.  I use Gkrellm for system monitoring
[08:57] <head_victim> lm-sensors
[08:57] <head_victim> !sensors
[08:59] <hallowed> thanks
[09:00] <head_victim> No worries, I'm just sitting here trying to work out how I can make google send me reminders about birthdays. Apparently it's not as easy as I thought.
[09:00] <hallowed> :)
[09:01] <hallowed> someone needs to call it a day...!
[20:25] <Tonjevic> Yo
[20:25] <Tonjevic> I was just wondering what this team does
[20:33] <Tonjevic> hrm, well, having read some of your website, I guess I've answered my own question!
[20:33] <Tonjevic> apologies for popping into the channel at such an early hour :)


[16:11] <sadmac2> Keybuk: http://screwyouenterpriseedition.blogspot.com/2008/12/new-upstart-state-machine-part-2.html
[16:12] <sadmac2> ignore what you didn't understand from the last post
[16:12] <sadmac2> This should be simple enough
[16:13] <ion_> sadmac: Concrete examples would be easier to grasp.
[16:13] <sadmac2> ion_: that's part 4 :)
[16:13] <ion_> Actual use cases instead of thystate and crunchy
[16:14] <sadmac2> ion_: I don't want to redesign this thing again. Part of that means that rigor is very important to me.
[16:14] <sadmac2> I want this thing to be perfectly defined. Its only its /presentation/ that has to be perfectly comprehensible.
[16:19] <ion_> Explaining it in a way we mere mortals understand shouldn’t require changing the design. :-)
[16:19] <sadmac2> ion_: it doesn't :)
[16:19] <sadmac2> ion_: but designing it in a way mere mortals understand requires changing the design every time someone says "well what about this?"
[16:23] <sadmac2> ion_: the fact is mere mortals don't have to know how it works for most values of "how it works"
[16:24] <sadmac2> ion_: relational databases: "put shit in tables," "Use joins"
[16:24] <sadmac2> ion_: that's a piss-poor picture of the relational model, but its almost enough to not screw up with postgres
[16:27] <ion_> Please give us the piss-poor picture of your design. :-)
[16:30] <sadmac2> ion_: you have states. they are either on or off. they can require others to be on before they come on. they can be made to come on upon certain system events, whenever their dependencies are satisfied, or automatically.
[16:30] <sadmac2> ion_: there's another process that will start a service whenever a particular state is on
[16:32] <Keybuk> what about the process that sets the state based on the service?
[16:32] <sadmac2> Keybuk: when does that happen?
[16:33] <Keybuk> what else would you set states from?
[16:34] <sadmac2> devicekit signals, user request, etc
[16:34] <sadmac2> events
[16:45] <Keybuk> D-Bus signals (like those from DeviceKit) are very definitely events, not states
[16:46] <Keybuk> I think the most common case is dependencies on other jobs
[16:46] <sadmac2> right
[16:46] <Keybuk> with the second most common case being the existing of particular D-Bus objects
[16:46] <Keybuk> (which is defined as the period between two well known events with common parameters)
[16:46] <sadmac2> still with you
[16:52] <Keybuk> though defining D-Bus signals is just a world of ugh
[16:53] <sadmac2> the split beetween Pid 1 (the service manager) and Pid X (the state machine) is what I want to firm up the most
[16:54] <Keybuk> from dbus(NAME=org.freedesktop.DeviceKit, PATH=/org/freedesktop/DeviceKit, MEMBER=org.freedesktop.DeviceKit.DeviceEvent, 1="add") until dbus(NAME=org.freedesktop.DeviceKit, PATH=/org/freedesktop/DeviceKit, MEMBER=org.freedesktop.DeviceKit.DeviceEvent, 1="remove", 2=$2)
[16:56] <sadmac2> Keybuk: we can probably macrify a lot of that. especially for something like devicekit that we'll be hitting up all the time
[16:57] <sadmac2> from US_DEVKIT(1="add") until US_DEVKIT(1="remove", 2=$2)
[16:58] <Keybuk> of course, that requires from/until to match the right side against the left
[16:58] <Keybuk> which is pretty essential
[17:01] <sadmac2> Keybuk: I think we probably had it right before
[17:02] <Keybuk> before?
[17:02] <sadmac2> Keybuk: from have_device(%1) until lost_device(%1)
[17:02] <Keybuk> right
[17:02] <sadmac2> Keybuk: where have_device and lost device are something that is specifically sent to the state machine
[17:02] <Keybuk> while <STATE>  -- defines a match on STATE
[17:02] <sadmac2> and causing those events due to whatever is SEP
[17:03] <Keybuk> from EVENT until EVENT  -- defines a match on a state defined as EVENT ... EVENT (rhs of a state matches against left)
[17:03] <Keybuk> before <STATE> -- defines a match on the opposite side of the STATE transition to while
[17:03] <sadmac2> whoa. do we need that?
[17:04] <Keybuk> omgyes
[17:04] <Keybuk> while ~= started -> stopping
[17:04] <Keybuk> before =~ starting -> stopped
[17:04] <sadmac2> oic
[17:05] <sadmac2> I kind of like the idea of specifying the state names for each of these
[17:05] <sadmac2> foostate while otherstate
[17:05] <sadmac2> let me explain why:
[17:05] <Keybuk> but you're inherently specifying the state name
[17:05] <Keybuk> because you're writing it in the job file ;)
[17:06] <Keybuk> or the state definition file ;)
[17:06] <sadmac2> Keybuk: that's my issue
[17:06] <sadmac2> Keybuk: I want to dissociate states from files
[17:06] <sadmac2> Keybuk: consider replacing runlevels.
[17:06] <sadmac2> Keybuk: we have a series of states, defined however, but none of them have auto
[17:07] <Keybuk> I don't want to replace them, I want to kill them dead :)
[17:07] <sadmac2> Keybuk: well, we need some way to group services based on what kind of system the user wants running
[17:08] <Keybuk>   /etc/init/docked:
[17:08] <Keybuk>     while service1
[17:08] <Keybuk>     while service2
[17:08] <Keybuk>     while service3
[17:08] <Keybuk> docked is true if they're all running
[17:08] <Keybuk> and you can start/stop docked manually to enter/leave that state
[17:08] <sadmac2> ah, damn
[17:08] <sadmac2> I don't think in terms of pulling the dependencies well yet :)
[17:09] <Keybuk> of course, you might arguably want to separate the dependencies from the requirements
[17:09] <sadmac2> Keybuk: you might want them to come from another place
[17:10] <sadmac2> /etc/init/docked-foopkg: error: file not found
[17:10] <sadmac2> yum install foopkg
[17:10] <sadmac2> /etc/init/docked-foopkg:
[17:10] <sadmac2> docked while fooservice
[17:11] <Keybuk> makes it hard to find out what docked is
[17:11] <Keybuk> you have to grep multiple trees of files
[17:12] <sadmac2> Keybuk: we have to support that case somehow though
[17:13] <sadmac2> Keybuk: also, that case kind of demonstrates why "while" might be a poor choice
[17:13] <sadmac2> it reads "whe are docked while fooservice is running"
[17:13] <sadmac2> which feels particularly backward for that state
[17:13] <sadmac2> I propose "implies"
[17:13] <sadmac2> docked implies fooservice
[17:14] <sadmac2> brb lunch. my backlog should contain you if you keep going :)
[17:22] <ion_> For that,
[17:22] <ion_> /etc/init/foo:
[17:22] <ion_> while docked
[18:20] <sadmac2> ion_: that means the opposite
[18:20] <sadmac2> ion_: that means whenever you started foo, the system would enter the docked state
[18:20] <ion_> I propose it doesn’t. :-)
[18:21] <sadmac2> ion_: then what goes in /etc/init/docked?
[18:22] <ion_> from devicekit-said-dock-connected until devicekit-said-dock-disconnected
[18:26] <sadmac2> ion_: so foo gets while foo; auto
[18:28] <ion_> Huh?
[18:39] <sadmac2> ion_: while docked; auto
[18:39] <sadmac2> ion_: sorry
[18:39] <sadmac2> hmm... a implies a
[18:39] <sadmac2> how do tautological states behave?
[18:40] <ion_> What’s this auto thing?
[18:40] <sadmac2> ion_: a state doesn't start just because its deps are satisfied unless auto is specified
[18:40] <sadmac2> ion_: otherwise its deps satisfied + got event
[20:01] <sadmac2> The more I describe this state machine the more I realize its a great deal more powerful than I thought :)
[20:01] <sadmac2> Its can do some things I didn't think of
[20:04] <sadmac2> mount_state(dev: %1, mountpoint: %2) { action: mount $dev $mountpoint }
[20:04] <sadmac2> ^^ignore that...
[20:05] <sadmac2> mount_state(dev: %1, mountpoint: %2, type: %3) { action: mount -t $type $dev $mountpoint }
[20:05] <sadmac2> mount_state(dev: %1, mountpoint: %2, type: funkyfusefs) { action: funkyfusemounter $dev $mountpoint }
[20:07] <sadmac2> its like haskell, but in a good way
[21:44] <sadmac2> ion_, Keybuk: http://screwyouenterpriseedition.blogspot.com/2008/12/new-upstart-state-machine-part-3.html
[21:45] <sadmac2> ^^practical examples included (start reading when you see fstab lines)


[00:51] <hippiehacker> xnox: thanks
[03:49] <fastway> where can I find info about isolinux.cfg used on live cd (12.04)? Mainly how "maybe-ubiquity" is appended on boot parameters. Thanks
[04:13] <ogasawara> @pilot out
[04:42] <vibhav> cyphermox: ping
[05:09]  * vibhav marvels at dget
[06:04] <pp7> how do i change the color of my panel (not launcher)?
[07:27] <erappleman> slangasek, what's the best way to get around the lack of "co-installable -dev packages"? i'm not familiar with chroot or pbuild. would a 32-bit vm suffice for building stuff like wine?
[07:34] <RAOF> erappleman: That'd work fine, but is a bit of overkill.
[07:35] <RAOF> Installing ubuntu-dev-tools and running ‘mk-sbuild --arch=i386 quantal’ will net you an i386 schroot.
[07:40] <erappleman> hmm thanks
[09:21] <vibhav> jamespage: ping
[10:25] <vibhav> infinity: ping
[14:46] <vibhav> Any idea why libvoikko was built with dh_python2 in ubuntu?
[14:47] <vibhav> doko__, doko_ : ^
[15:08] <cjwatson> vibhav: We don't want either of the old python helpers (-central or -support) in main - we went to some effort to consolidate on one
[15:10] <vibhav> ah wait, libvoikko is built with dh_python2 in debian too. We could have a sync now
[15:11] <vibhav> cjwatson: https://bugs.launchpad.net/ubuntu/+source/libvoikko/+bug/1010907
[15:12] <cjwatson> Sure
[15:13] <vibhav> thanks!
[15:20] <vibhav> micahg: you there?
[15:31] <vibhav> cjwatson: Thanks! (again)
[16:11] <vibhav> cjwatson: If you are not busy, could you have a look at https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1010920 ?
[22:37] <_pants> How do you programmatically make something run at login in Ubuntu (preferably both in Gnome and Unity)? I tried searching docs first and didn't turn anything up.
[22:39] <_pants> mdz: do you know, by chance? ^
[22:42] <maxb>  /etc/xdg/autostart/ ?
[22:42]  * _pants looks
[22:45] <_pants> Thanks, maxb. That's odd though, I'd expect these to be defined per-user.
[22:47] <maxb> _pants: ~/.config/autostart/
[22:47] <_pants> ah, that's the ticket
[22:47] <_pants> thanks
[22:49] <_pants> maxb: So to have a setting in my application the user can toggle to launch it on startup, is all I have to do to add or remove a corresponding .desktop file in the user's ~/.config/autostart directory?