[00:30] <sam__344> Hi. I asked this last night but maybe everyone was asleep
[00:30] <sam__344> Is there a trick to running "juju quickstart mediawiki-single"
[00:30] <sam__344> under virtualbox using Ubuntu 14.04..
[00:31] <sam__344> Both the computer and the virtualized computer are Ubuntu 14.04
[00:31] <sam__344> It just hangs on machine 1 provisioning is pending
[07:27] <BlackDex> sam__344: Did you start the second box? Is it running via maas? etc..
[07:29] <sam__344> BlackDex: I did nothing but follow the instructions here, up to step #2. https://jujucharms.com/get-started
[07:29] <sam__344> I'm running it inside virtual box, not deploying to virtualbox
[07:30] <BlackDex> Ah, so the machine you need to deploy it to is bare-metal
[07:31] <sam__344> Well I'm just playing with it for fun. But I don't want it to mess up my laptop so I'm using VirtualBox. I'd expect it to just work the same as if I was following the directions directly on my laptop
[07:32] <BlackDex> sure
[07:32] <BlackDex> if you just select the create a local environment
[07:33] <BlackDex> You need to have JuJu know where to deploy stuff to. That may be virtual, lxc, bare-metal, cloud etc..
[07:34] <sam__344> okay. So what should I type instead of "juju quickstart mediawiki-single"
[07:36] <sam__344> By the way BlackDex - I just rebooted the virtual machine and tried it again. Got  INFO jujuclient:328 Juju upgrade in progress...
[07:36] <sam__344> over and over again
[07:36] <sam__344> until finally "juju-quickstart: error: cannot retrieve the environment type: upgrade in progress - Juju functionality is limited"
[08:07] <BlackDex> hmm
[08:07] <BlackDex> that is strange
[08:07] <BlackDex> never did a local deploy btw
[08:45] <BlackDex> Hello there, on my setup juju seems to timeout after a while. The bootstrap node is running on a KVM-Instance and can connect to MAAS etc.. the deployed nodes are also receiving commands from juju, but after a while it seems to stop
[08:46] <BlackDex> if i then reboot the bootstrape node, some of those machines come to life without doing anything.
[08:46] <BlackDex> Is this a problem with the juju-api or mongodb? what can i do to try and solve this?
[13:11] <shruthima> Hi, We are developing IBM HTTP Server as subordinate charm we want to test the charm with ubuntu-devenv .((http server is a webserver which can be used by other  ibm products Eg: WAS .we are developing it as a layer and decide to use http interface which is present in interfaces.juju.solutions.)) so could you please include http interface in ubuntu-devenv metadata.yaml file under provides...//?
[13:18] <marcoceppi> shruthima: what is ubuntu-devenv? Do you have a link to it somewhere?
[13:21] <shruthima> this is the link  https://jujucharms.com/u/kwmonroe/ubuntu-devenv/trusty/5/
[13:21] <icey> any chance of get ting https://code.launchpad.net/~chris.macnaughton/charm-helpers/pids-can-be-a-list/+merge/288014 reviewed soon?
[13:22] <beisner> icey, i'll review/comment
[13:23] <icey> thanks beisner :)
[13:24] <cory_fu> shruthima: I'm not sure that ubuntu-devenv makes sense to support the http interface, as it provides a developer environment and not anything related to HTTP or web services.  Maybe it would make more sense to test the IBM HTTP server with the existing haproxy charm?
[13:25] <cory_fu> https://jujucharms.com/haproxy/
[13:29] <shruthima> ok will explore on how i can use haproxy charm to test http server . if any queries il get back . Thank you :)
[13:40] <beisner> coreycb, thx for the swift-* reviews.  with your +1 and the full test pass, i think we're clear to land those, yah?
[13:41] <coreycb> beisner, yes I think so
[13:43] <coreycb> beisner, I've also tested with jamespages nova-cc patch successfully but that should probably have a more active charmer review it
[13:45] <beisner> coreycb, yep thedac is queued up on the n-c-c review.
[13:45] <coreycb> cool
[13:58] <beisner> icey, remind me, which charm test were you updating to take that list validation?
[13:59] <icey> a ceph-mon test
[13:59] <icey> looking...
[14:00] <icey> beisner: https://review.openstack.org/#/c/287446/7/tests/basic_deployment.py
[14:00] <icey> line 185, changed from {'ceph-osd': 2} to {'ceph-osd': True}
[14:01] <icey> would rather be: {'ceph-osd': [2, 3]}
[14:14] <beisner> icey, thx. see review comment.
[14:14] <icey> beisner: saw it, thanks
[14:17] <beisner> icey, i'd be +1 to rename to just e_pids in that whole method
[14:17] <beisner> as it's also a funky name for the existing bool scenario
[14:17] <beisner> icey, or just "expected"
[14:48] <narindergupta> jujucharms.com is down
[14:49] <urulama_> narindergupta: seems a company network issue, we're looking into it
[14:49] <urulama_> narindergupta: thanks
[14:50] <narindergupta> urulama: thanks
[14:54] <magicaltrout> this is why juju needs multicloud models, so you can fail over outside of the core network ;)
[14:55] <rick_h__> magicaltrout: :)
[14:56] <urulama> :D
[15:22] <jcastro> jamespage: do you have the bundle you used openstack on your laptop in brussels pushed somewhere?
[15:23] <jcastro> I'm ready to melt my PC
[15:23] <lazyPower> yessssss
[15:24] <marcoceppi> jcastro: I think jamespage is on vacay
[15:28] <lazyPower> marcoceppi - do we know if 1.25.x is capable of using the devel channel in the store or is that a 2.0+ only feature?
[15:28] <marcoceppi> lazyPower: no idea, urulama ^?
[15:29] <urulama> lazyPower: 2.0 only
[15:29] <lazyPower> ack, ta
[15:35] <gnuoy> tinwood, novaclient.v1_1.client fix landed
[15:35] <tinwood> great stuff.  Thanks gnuoy!
[15:36] <gnuoy> np
[15:55] <dames> beisner: you said jamespage's nova-cc PR has already passed full amulet tests? Or I need to just aprove the workflow bit?
[15:56] <beisner> thedac, re: https://review.openstack.org/#/c/291721/   Yep, if you're not seeing it, hit the Toggle CI button to expand the history a bit.
[15:56] <beisner> thedac, my only hold-back was the self-comment on https://review.openstack.org/#/c/291721/1/hooks/nova_cc_hooks.py
[15:56] <thedac> ok
[16:05] <lazyPower> jcastro - bite sized PR if you have a moment to TAL - https://github.com/juju-solutions/bundle-logstash-core/pull/1
[16:06] <jcastro> +    juju deploy ~containers/bundle/logstash-core
[16:06] <jcastro> is that right? wouldn't it not be in the containers namespace?
[16:06] <lazyPower> thats what works today
[16:06] <lazyPower> when is promulgated, either/or
[16:07] <lazyPower> wait, i just committed an act of heresy, i just reference a bundle as "promulgated"
[16:07] <beisner> thedac, fyi it'll take a code-review +2 along with that workflow +1 to trigger the merge.  lmk if you don't have privs for the +2.
[16:07] <jcastro> it just seems that you would document where it will be at with a clean namespace
[16:07] <lazyPower> if it doesn't work in a copy/pasteable format, i'm hesitant to plug it in there ya know?
[16:07] <jcastro> who is going to remember ~containers/logstash-core?
[16:07] <jcastro> I just want to remember logstash-core
[16:07] <thedac> beisner: I do. I am going to respond back to jamespage about the liberty-> mitaka upgrade path.
[16:07] <lazyPower> also jcastro - should i rename it ot elastic-stack?
[16:07] <beisner> thedac, ok cool, thx
[16:07] <lazyPower> or elk-stack?
[16:08] <jcastro> yeah
[16:08] <jcastro> elk-stack
[16:08] <lazyPower> ok, will rename the repository after PR feedback, already updating the README
[16:09] <jcastro> looking at the bundle, one charm is in ~containers, one's in the promulgated store, and the jdk is in kwmonroe's personal namespace
[16:11] <jcastro> nod, don't block on me
[16:12] <jcastro> I'm just saying we should be pushing for bundles using reviewed charms, not that I don't trusty kev, heh
[16:12] <kwmonroe> :)
[16:12] <lazyPower> its in the revq ;)
[16:12] <lazyPower> currently at what? #7?
[16:12] <kwmonroe> lazyPower: 'zulu8' is a drop-in layered promulgated openjdk replacement if you'd rather use that.
[16:13] <jcastro> heh, he just went from reviewing a readme diff to "retest the whole thing with a new java layer"
[16:13] <lazyPower> jcastro - this is all pretext work to propose for ~charmer, things have to work when you submit for review or we tend to nack them. charms are never done after all ;)
[16:13] <lazyPower> kwmonroe - you're not helping me by adding work
[16:13] <lazyPower> <3
[16:13] <kwmonroe> lolz.
[16:13] <lazyPower> but thats easily done
[16:14] <lazyPower> actually, kwmonroe - want me to kick the tires on testing that?
[16:14] <kwmonroe> testing what?  java is java.  just use it: https://jujucharms.com/zulu8/
[16:14] <kwmonroe> AMIRITE MATT?!?!
[16:15] <lazyPower> the one day java was set up for a slam dunk, and matt is in Hawaii
[16:15] <kwmonroe> no doubt
[16:15]  * lazyPower grins at the irony
[16:16] <magicaltrout> i read ironing
[16:16] <magicaltrout> which was a little odd
[16:18] <lazyPower> indeed
[16:26] <thedac> gnuoy: I am thinking the keystone case issue, a compromise would be not to create as lowercase but in the checks. read only. I see that keystone/hooks/manager.py may be partialy at fault.
[16:31] <gnuoy> thedac, sorry, you're suggesting we create case sensitive but read case-insensitive ?
[16:32] <thedac> gnuoy: yes, one sec
[16:33] <thedac> gnuoy: something like http://pastebin.ubuntu.com/15393100/
[16:36] <gnuoy> thedac, that makes sense to me
[16:36] <thedac> gnuoy: ok, I'll submit a pull request
[16:37] <gnuoy> kk
[16:37] <cholcombe> beisner, looks like the tests on the ceph-osd charm were deploying the wrong services
[16:37] <stokachu> when you destroy-model the model still shows up in list-models but as 'no longer alive'
[16:37] <stokachu> is this expected?
[16:37] <cholcombe> beisner, it was deploying ceph and not ceph-mon
[16:38] <beisner> cholcombe, indeed.  the test in ceph-osd deploys the ceph charm.  https://github.com/openstack/charm-ceph-osd/blob/master/tests/basic_deployment.py#L47
[16:38] <stokachu> nm found the bug
[16:39] <cholcombe> beisner, yeah i changed it to ceph-mon which should fix the problem
[16:41] <beisner> cholcombe, ok.  be aware, that marks the beginning of the end of ceph+ceph-osd functional integration.   i'd suggest that we add ceph-osd to the ceph charm's amulet test @ https://github.com/openstack/charm-ceph/blob/master/tests/basic_deployment.py#L47 right along with these changes so we don't completely lose coverage.
[16:41] <cholcombe> beisner, yeah goo dpoint
[16:42] <cholcombe> beisner, yeah i'll cut a branch for that integration
[16:42] <beisner> cholcombe, sweet, thanks
[16:57] <thedac> gnuoy: fyi: https://review.openstack.org/293043
[17:03] <jcastro> marcoceppi: https://bugs.launchpad.net/juju-core/+bug/1557633
[17:03] <mup> Bug #1557633: status has duplicate entries for relationships <juju-core:New> <https://launchpad.net/bugs/1557633>
[17:03] <jcastro> look at how huge that list ended up being
[17:05] <thedac> marcoceppi: nuage charms:
[17:05] <thedac> https://jujucharms.com/nuage-vsc/trusty/
[17:05] <thedac> https://jujucharms.com/nuage-vsd/trusty/
[17:05] <thedac> https://jujucharms.com/nuage-vrs/trusty/
[17:05] <thedac> https://jujucharms.com/nuage-vrsg/trusty/
[17:13] <gnuoy> tinwood, +2'd your keystone change. Thanks for all your work on that
[17:14] <tinwood> gnuoy, sadly OSCI doesn't agree!  (I'm guessing keystone auth problems).
[17:15] <beisner> tinwood, gnuoy - hook failed: "install" for trusty and wily on that keystone change, inspecting unit logs now..
[17:16] <tinwood> thanks beisner
[17:16] <beisner> tinwood, gnuoy 2016-03-15 17:09:55 INFO install ImportError: cannot import name get_admin_domain_id
[17:17] <tinwood> beisner, oo, nasty - that must be me.
[17:17] <beisner> tinwood, gnuoy - http://pastebin.ubuntu.com/15393468/
[17:17] <beisner> gnuoy, gotta wait for both "Jenkins" and "Canonical CI" to +1
[17:18] <beisner> looks like patchset 3 is the culprit
[17:18] <tinwood> I will check and get back to you both.  My box is broken (until I can get an install of amulet working).
[17:20] <tinwood> yeah, definitely me with merge conflicts.  However, there's no test for get_admin_domain_id() - i.e. it passes unit tests.  I'll dig into that too.
[17:24] <cholcombe> beisner, where does amulet get ceph-mon from?
[17:25] <cholcombe> beisner, i realize this is a vague question haha.  What i'm wondering is which version of ceph-mon is it using.  There's a few different ceph-mon's under different namespaces
[17:25] <beisner> cholcombe, if it's in other_services, launchpad.   if it's the ceph-mon charm test itself, it gets it from wherever the change originated (refspec)
[17:25] <cholcombe> beisner, yeah it's in other_services
[17:25] <beisner> cholcombe, it should be pulling from ceph-mon/next
[17:26] <cholcombe> beisner, ok that's what i was wondering.  I'm failing to deploy on precise and I'm wondering if it exists
[17:26] <beisner> cholcombe, it uses the trusty charm for everything currently (precise through xenial)
[17:26] <cholcombe> beisner, hmm ok
[17:26] <cholcombe> i must've broken something then
[17:33] <bdx> whats up everyone? I'm trying to bootstrap lxd provider using juju2, does anyone know where I can find an example of a config.yaml to feed juju2?
[17:47] <icey> bdx `juju bootstrap lxd lxd --upload-tools --config="default-series=trusty"` is what I've been doing
[17:47] <icey> anybody have suggestions for subordinate charms being a mix of layered and old-school charms?
[17:48] <bdx> icey: thanks
[17:48] <marcoceppi> thedac: thanks
[17:49] <marcoceppi> thedac: these are already promulgated though?
[17:49] <thedac> marcoceppi: I suspected that. jamespage promulgated them last week. Again I am trying to get straight the review process for future changes to those charms.
[17:50] <marcoceppi> thedac: yes, so that's not 100% clear, I'll look into it to find out exactly how they were uploaded, etc
[17:50] <thedac> Sounds like http://review.juju.solutions/ will be (but is not yet) the correct location for nuage (or anyone else) to submit change proumulgation requests. Is that correct?
[17:51] <thedac> marcoceppi: ok, thanks. We could surely use some documentation on this. That or I have not had enough coffee today.
[17:52] <marcoceppi> thedac: documentation definitely, we're locking down a new reviewqueue with the new charm command due out this month (charm command)
[17:52] <marcoceppi> thedac: but basically yes, nuage, or whomever, would upload charms to their development channel - since those charms are promulgated, they'll have to got through a review to get them published to the stable channel
[17:53] <marcoceppi> but development will be done wherever the code for the charm lives, where previously anyone could contribute by just opening a merge requests against an lp branch
[17:53] <marcoceppi> so if they house the code for teh charms in gerrit, or github, or lp, that's where people will contribute to, and it's up to them to do uploading/submitting to the store
[17:53] <thedac> ok
[18:05] <tinwood> yay! amulet reinstalls under xenial :)
[18:08] <cory_fu> rick_h__: Hey.  Has anyone suggested adding a message param to `charm publish` so that we can indicate just what is included in the new rev?
[18:09] <urulama> cory_fu: yes, that part is still missing
[18:09] <rick_h__> cory_fu: yes, it's supposed to be updated to take one like a 'commit message'
[18:09] <cory_fu> Ok, cool, so it's already planned.  Nice
[18:10] <cory_fu> I'm finding that the lack of info about the charm revs is making my development process more difficult because I can't recall what I've released when
[18:12] <beisner> tinwood, just to confirm, we need to tackle keystone @ master as a crit.  she's bust.
[18:14] <beisner> tinwood, ie.  with keystone install hook failing, all other amulet tests for other peeps will also be blocked.
[18:14] <beisner> tinwood, two paths forward:  post a change to fix it, or post a change to revert that last one.  whaddaya think?
[18:14] <tinwood> beisner, I've sorted it out.  I'm just finishing the merge and will push again.
[18:15] <beisner> tinwood, awesome
[18:22] <bdx> charmers, core, dev: I see spaces can be assigned like so -> juju deploy mysql --bind "server=database cluster=internal"
[18:22] <bdx> charmers, core, dev: does this indicate that I should have an affinity between subnets and spaces?
[18:23] <bdx> charmers, core, dev: if my space-0 has multiple subnets e.g http://paste.ubuntu.com/15393950/
[18:23] <bdx> charmers, core, dev: how can I `bind` a specific subnet in a space? .... Is this a thing yet?
[18:24] <tinwood> beisner, it seems that my review is closed.  Do I need to branch again and push a new review?
[18:25] <lazyPower> bdx - I would redirect that at the list. The primary author of the spaces feature is in EU time, and is the most well equipped to answer those questions
[18:26] <bdx> lazyPower: totally, thanks
[18:26] <tinwood> beisner, or do I hit the revert button?
[18:56] <beisner> tinwood-dinner, since that change was merged, it'll have to be a separate proposal
[18:56] <tinwood-dinner> Okay, will do. Just finishing eating.
[18:57] <beisner> me too
[19:26] <tinwood> beisner, I'm just running some tests to make sure it is all still okay.  Be about 5-10 minutes for the review to pop up (I hope!)
[19:27] <beisner> tinwood, excellent, thank you
[19:34] <cory_fu> bcsaller: I went ahead and added the --show-report option to charm-build: https://github.com/juju/charm-tools/pull/135
[19:38] <bcsaller> cory_fu: utils.delta_signatures wasn't helpful there? (thanks btw :)
[19:38] <cory_fu> ...
[19:38] <cory_fu> It probably would have been
[19:38] <bcsaller> the validate method above this commit is similar, but not the same
[19:40] <cory_fu> bcsaller: Ah, yeah.  delta_sigs checks if the files on disk don't match the manifest, but by the time the files on disk are updated, the manifest has been overwritten as well.  I guess I could call report before write_signatures
[19:41] <cory_fu> I could do the same with clean_removed.  Hrm
[19:45] <pmatulis> should this "just work"? i get 'ERROR cmd supercommand.go:448 no registered provider for "lxd"' : 'juju bootstrap mycontroller lxd'
[19:47] <tinwood> beisner, it's gone up and failed it's CI?  It failed very quickly, so I'm wondering if that's because it's blocked?
[19:49] <beisner> tinwood, fail fast ;-)  ...
[19:49]  * beisner looks
[19:58] <marcoceppi> tinwood: yeah, sorry about that, amulet is fixed again though
[19:58] <marcoceppi> pmatulis: what version of Ubuntu?
[19:58] <tinwood> beisner, hey, no that's fine.  This is, after all, of my doing sadly.
[19:59] <pmatulis> marcoceppi: 2.0-beta2-0ubuntu1~16.04.1~juju1
[19:59] <pmatulis> sorry, Xenial
[20:00] <marcoceppi> pmatulis: when do you get that error? is there a bunch of text first or is it almost immediately, if it's the former --upload-tools is needed for now, otherwise that's another issue
[20:01] <pmatulis> marcoceppi: oh yeah, it runs for a good while
[20:01] <pmatulis> marcoceppi: lemme try --upload-tools . why do i need that again? b/c it tries to use a trusty container?
[20:01] <beisner> tinwood, unit test really did fail on that
[20:02] <marcoceppi> pmatulis: because the trusty agent doesn't have lxd provider compiled in
[20:02] <tinwood> beisner, hmm, strange, everything passed on my bastion.  what was the problem?
[20:02] <pmatulis> marcoceppi: roger. trying now...
[20:03] <beisner> tinwood, see priv channel for priv link
[20:03] <icey> beisner: any chance on more review on https://code.launchpad.net/~chris.macnaughton/charm-helpers/pids-can-be-a-list/+merge/288014 ?
[20:06] <pmatulis> marcoceppi: thank you - works
[20:08] <beisner> icey, on a hot issue atm, will circle back
[20:08] <cory_fu> bcsaller: Actually, I can't use delta_signatures for clean_removed after all, because the whole point is that they don't get removed, so d_s won't pick them up.  :/
[20:08] <icey> no worries beisner
[20:09] <bcsaller> cory_fu: :-/
[20:09] <bcsaller> heh
[20:48] <lazyPower> jcastro - how much ram do you ahve in your rig? and what did resource usage look like  with openstack in lxd on your lappy?
[20:52] <cory_fu> bcsaller: PR updated
[20:52] <cory_fu> Also, lazyPower and marcoceppi, since you both commented
[20:53] <cory_fu> marcoceppi: Your :BOAT: didn't sail.  ;)
[21:49] <roryschramm> is it possible to specify a custom apt repository when juju deploys an app to an lxc container? ie the lxc container will use http://myrepo/ubuntu in /etc/apt/sources.list
[22:40] <stub> roryschramm: Not globally. Each charm needs to add its required custom repositories. Charms that need custom repositories generally provide a config item for them (or hard code them).
[22:42] <stub> roryschramm: You might also find the apt_ environment settings in your juju environment can help (eg. juju set-env apt-mirror=...)
[22:44] <roryschramm> aha the apt-mirror setting is what i was looking for
[22:44] <roryschramm> thanks
[22:45] <roryschramm> will that override the default repos in the trusty lxc image?


[00:08] <ninanina> Hello. I was trying the new kde5 build but strangely when I get to the KDE Welcome screen and choose Try Kubuntu Plasma 5, it reloads the Welcome screen so I'm stuck there. Is it just me?
[00:41] <valorie> TheFakeazneD525: depends on what you mean by "backed"
[00:41] <TheFakeazneD525> financially
[00:41] <valorie> most of our infra is still on ubuntu servers/lauchpad etc.
[00:41] <valorie> Canonical no longer pays for any kubuntu development
[00:42] <valorie> or offers paid support
[00:42] <TheFakeazneD525> :c
[00:42] <valorie> Blue system employs quite a few devels for kubuntu and KDE
[00:43] <valorie> http://kubuntu.emerge-open.com/buy for paid support
[00:44] <valorie> otoh the Ubuntu donors paid my way to Akademy in Brno, CZ along with quite a few others
[00:45] <valorie> flights alone from Seattle <> Vienna were about $1k
[00:45] <TheFakeazneD525> hopefully the *buntus don't split from the main Ubuntu due to canonical meddling
[00:45] <valorie> so not cheap
[00:46] <valorie> can we take this to #kubuntu-offtopic ?
[05:50] <tekkbuzz> If anyone can help, I need to know how to get a menu back up. What I did was: right clicked the desktop, then ▶ Default Desktop Settings then ▶ Mouse actions then ▶ Right-Button and selected Application Launcher, but now I wish to switch back to default. I can't get back to that menu now. Can anyone help? thanks in advance.
[05:52] <tekkbuzz> It looked like this: http://www.staerk.de/thorsten/Kde-contextmenu
[06:07] <valorie> tekkbuzz: use alt+f2 and type systemsettings
[06:07] <valorie> you should be able to get to your default desktop settings from there
[06:08] <tekkbuzz> valorie: I went to system settings but can't find that menu in there anywhere.
[06:12] <valorie> tekkbuzz: did you install it like that, from a zip file?
[06:13] <valorie> or from packages
[06:13] <tekkbuzz> nope, just used the default menu.
[06:13] <tekkbuzz> didn't install anything.
[06:15] <valorie> so you right-clicked on the desktop and got roughly that menu, but now can't get that same menu back?
[06:15] <valorie> my right-click menu looks very different than that
[06:17] <tekkbuzz> you got to select desktop settings first.
[06:17] <tekkbuzz> to get to that.
[06:18] <valorie> tekkbuzz: which version of kubuntu are you running?
[06:19] <valorie> desktop settings isn't in my context menu on the desktop
[06:19] <valorie> folder settings is, perhaps because I'm using folder view (without folders)
[06:20] <tekkbuzz> latest LTS I think it's Trusty?
[06:20] <valorie> ah, there it is
[06:20] <tekkbuzz> good you found it.
[06:21] <valorie> and you no longer can choose Standard Menu?
[06:21] <tekkbuzz> nope, there is no longer an option on the bottom, just the app menu launcher.
[06:22] <valorie> ok, I've changed to that
[06:24] <valorie> I think you've found a bug, because I get Kdialog: http://paste.kde.org/pwopazlnz
[06:24] <valorie> when I select input method
[06:24] <tekkbuzz> hope you don't get stuck like me.
[06:25] <valorie> I believe I am
[06:25] <valorie> filing a bug....
[06:26] <tekkbuzz> got to be an rc file somewhere or something, but Im not a programmer.
[06:26] <tekkbuzz> err, not a real one. lol.
[06:30] <tekkbuzz> thanks for helping, sorry you got stuck too.
[06:31] <valorie> the kdialog says that restarting x will help, but I'm not so sure about that
[06:31] <valorie> rc files are just text, found in ~/.kde
[06:32] <tekkbuzz> yeah, I spent a bit of time trying to find it already, without success.
[06:33] <tekkbuzz> must be something to bring that menu back up though?
[06:41] <valorie> could be kdedrc
[06:41] <valorie> in ~/.kde/share/config
[06:41] <tekkbuzz> I'll have a look
[06:43] <tekkbuzz> not much there, but it says [Module-appmenu]   autoload=false
[06:44] <tekkbuzz> I was looking in plasma-desktoprc
[06:45] <valorie> mine says the same
[06:45] <tekkbuzz> err, no I was looking at: plasma-desktop-appletsrc
[06:46] <valorie> this isn't an applet, I don't think
[06:47] <tekkbuzz> yeah but I just seen some applet launcher bits in there.
[06:51] <lordievader> Good morning.
[07:13] <tekkbuzz> valorie: you here?
[07:16] <valorie> yes, still here
[07:16] <tekkbuzz> I posted solution on wrong channel #kde
[07:17] <valorie> I can't figure out where to file a bug
[07:17] <valorie> but I guess against plasma-applets
[07:18] <tekkbuzz> sure is a bug, it bugged me for hours.
[07:20] <valorie> not many people still working on plasma for kde4 though
[07:20] <valorie> all the effort is in plasma 5
[07:20] <valorie> I'll file a bug anyway
[07:21] <tekkbuzz> yeah, I know, but it is still the latest LTS.
[09:35] <sysop3> hi
[09:36] <sysop3> I set my resoution too high for my monitor what file can I edit to change the resolution.
[09:37] <sysop3> xorg.conf is no longer being used I am not sure where to change it.
[09:38] <lordievader> sysop3: You can change it with the xrandr utility.
[09:40] <sysop3> how?  xrandr wont run on the command line unless I am in a x terminal
[09:41] <sysop3> where is the file so I can just edit that?
[09:41] <sysop3> displayconfigrc is also no longer in use.
[09:41] <sysop3> so where can I find the settings?
[09:41] <lordievader> sysop3: Login to KDE, open a terminal either there or in a tty and run "export DISPLAY=:0" then you can use xrandr.
[09:41] <sysop3> I cant see kde
[09:42] <sysop3> the resolutin is set to high
[09:42] <lordievader> sysop3: Doesn't matter.
[09:42] <sysop3> but what file is the settings in now?
[09:42] <lordievader> No idea. But ^ works...
[09:45] <sysop3> ok but why does kde keep changing the file where the settings are stored?
[09:49] <sysop3> does anyone else know where the settings are stored?
[09:49] <TJ-> sysop2: The X server dynamically configures the displays in the absence of "/etc/X11/xorg.conf", but if there is such a file it will use it
[09:49] <sysop3> so when I go into system settings and change the resolution it does not save it anywhere?
[09:50] <TJ-> sysop2: See "/var/log/Xorg.0.log" for what the X server and drivers are configuring the system as and what modes the monitor is telling the server it supports (via EDID)
[09:50] <sysop3> but that does not tell me where kde saves the settings?
[09:50] <sysop3> what happened to displayconfigrc ?
[09:51] <TJ-> sysop2: Under the users's local ~/.config/ and/or ~/.kde/
[09:51] <sysop3> yes but there are lots of files in there, which one?
[10:00] <sysop3> OK here is my question "what file name does KDE save the display settings into?" can anyone answer that?
[10:48] <jason__> :)
[10:50] <Ironcore> lol
[10:51] <sysop2> yea its pretty laughable I cant get a simple asnwer to a simple question.
[10:51] <Ironcore> Hahahaaaa
[10:52] <sysop2> can you answer it?
[10:52] <Ironcore> nope
[10:52] <sysop2> the shut the fuck up
[10:52] <Ironcore> :D
[10:53] <lordievader> sysop2: Watch your language please.
[10:54] <lordievader> This is a family friendly channel.
[10:54] <Ironcore> Otherwise the lord will come... ;)
[10:54] <Ironcore> Thanks
[10:54] <sysop2> ok. but how about an information friendly channel?
[10:58] <lordievader> sysop2: Its in ~/.kde/share/config/krandrrc
[10:59] <sysop2> thank you.
[11:06] <sysop2> that file doesnt exit in 14.04
[11:06] <lordievader> ...
[11:07] <lordievader> Guess it is a leftover then, let me dig a little deeper.
[11:08] <sysop2> thanks again. sorry I was little frustrated.
[11:08] <lordievader> sysop2: Then it is likely somewhere in ~/.kde/share/apps/kscreen
[11:09] <BluesKaj> Hiyas all
[11:10] <sysop2> I think thats it. there is a random named file in there containing what looks like some json with the diisplay settings.
[11:12] <lordievader> Kscreen is what we use nowadays so I suppose it should be right ;)
[11:13] <sysop2> whats weird is on my 13.10 box  there is a file in there and it has settings, but they are fake.
[11:13] <sysop2> but on my 14.04 box iit shows what look like are the real settings.
[11:13] <lordievader> sysop2: That one likely doesn't use kscreen.
[11:13] <lordievader> The switch to kscreen is relatively recent.
[11:14] <sysop2> ahh. ok thanks.
[11:18] <sysop2> one last question lordievader how di d you find that out?
[11:18] <sysop2> I gogoled around forever and couldnt find it.
[11:18] <lordievader> sysop2: Looking around in the obvious places ;)
[11:19] <sysop2> enlighten me because they are not ovvious to me. is there a page somewhere that has this sort of info or did you dig through the code?
[11:24] <sysop2> weird I guess they dont mind cloning anymore, I had opened two clients on accident.  used to one of them would get kicked.
[11:31] <lordievader> sysop2: Look around in ~/.kde/share/conf or ~/.kde/share/apps ;)
[11:35] <sysop2> is that file we were talking about not the right one?  or are you just saying in gerneral? I tried greping for what I tought was the resolution but I was wrong thats why I could never find the file.
[11:36] <sysop2> thought I mean.
[11:36] <lordievader> sysop2: You asked me how I found it, ^ is my answer.
[11:36] <sysop2> ah ok.
[12:59] <fuorviatos> using Kubuntu with kde 13.3 I have no hibernate button as upower deamon shows the laptop doesn't provide that but it did with unity. What may be the problem?
[13:03] <Tm_T> fuorviatos: kde 13.3 ?
[13:03] <BluesKaj> think he means 4.13.3
[13:03] <fuorviatos> sorry, my bad - 4.13.3
[13:03] <Tm_T> aaah now I understand
[13:04] <fuorviatos> just before you ask - swap partition is set up
[13:04] <BluesKaj> I guess my bad now means my mistake
[13:04] <fuorviatos> BluesKaj: it does in english, indeed ;]
[13:05] <BluesKaj> the english langauge is being pummeled by street so calle "cool talk"
[13:05] <BluesKaj> so called
[13:06] <fuorviatos> that's off-topic discussion I'm afraid ;] (besides; even "cool talk" is part of a language)
[13:07] <fuorviatos> Do you have any idea why upower shows my laptop cannto hibernate while it normally does?
[13:07] <fuorviatos> cannot*
[13:07] <BluesKaj> it sucks fuorviatos,and it's not offtopic when the laguage is used improperly
[13:07] <BluesKaj> \langauge that is :)
[13:08] <BluesKaj> it's apet peeve of mine , I'm old and cranky
[13:08] <fuorviatos> BluesKaj: Buddy, I've studied lingustics and even if I'm not an expert I do have a broader perspective than you. (get one - it is only language ;) )
[13:09] <Tm_T> please move language discussion to more suitable channel (:
[13:09] <fuorviatos> that's why I was saying
[13:09] <BluesKaj> fuorviatos, if you can't find the hibernate button m, tru sudo pm-suspend in the cli
[13:09] <Tm_T> fuorviatos: how large is the swap space compared to your RAM?
[13:09] <BluesKaj> fuorviatos, tru=try
[13:10] <fuorviatos> it works, thanks, but I'd like to understand why it is not present in my kubuntu?
[13:11] <BluesKaj> fuorviatos, I'm not your "Buddy" , and someone who has studied linguistics should know better then to use "street talk"
[13:12] <BluesKaj> fuorviatos, good question , the "button" you're looking for doesn't seem to exist
[13:12] <fuorviatos> pm-suspend and hibernate both works
[13:13] <fuorviatos> it does on some systems
[13:13] <BluesKaj> fuorviatos, another thinhgdon't crosspost
[13:14] <BluesKaj> !crosspost
[13:16] <BluesKaj> better watch my spelling if I'm going to be a correction troll
[13:17] <lordievader> fuorviatos: How much swap and ram do you have?
[13:17] <fuorviatos> lordievader: 8GB
[13:18] <lordievader> fuorviatos: Ram or swap?
[13:18] <fuorviatos> both
[13:18] <lordievader> Hmm okay.
[13:18] <BluesKaj> then you should hibernate successfully
[13:19] <fuorviatos> I do
[13:20] <fuorviatos> gonna open it upstream for upower
[13:21] <BluesKaj> fuorviatos, you can install the 'hjibernate" app from the repos
[13:22] <BluesKaj> err hibernate
[13:22] <BluesKaj> I see it in muon
[13:27] <fuorviatos> BluesKaj: man are you a bot or smth?
[13:27] <sysop2> an agent smith?
[13:28] <BluesKaj> fuorviatos, smth?
[13:28] <sysop2> lol
[13:28] <BluesKaj> hehe
[13:28] <fuorviatos> BluesKaj: what difference will it make to install it if the problems lays in another layer?
[13:28] <fuorviatos> it is a bug indeed ---> https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1296133
[13:29] <BluesKaj> fuorviatos, well, i guess you have your answer
[13:29] <fuorviatos> I do but I'd reccomend you thinking before giving such sillis advices to users
[13:29] <fuorviatos> silly*
[13:30] <BluesKaj> fuorviatos, i just use pm-suspend, it's simple enough and effective
[13:31] <fuorviatos> I mean this:  fuorviatos, you can install the 'hjibernate" app from the repos
[13:31] <BluesKaj> i can't check every app that's available in the repos for bugs, that's up to the user who happens to be you
[13:31] <fuorviatos> help appreciated but it was trolling rather than
[13:31] <BluesKaj> fuorviatos, ^
[13:31] <fuorviatos> end of topic
[13:31] <lordievader> The bug is with KDE this time...
[13:33] <BluesKaj> lordievader, nm , he's just p** ed because i corrected his poor english usage.
[13:33] <lordievader> Actually you are both a bit grumpy. But lets drop this pointless discussion, or continue with a happier note.
[13:34] <BluesKaj> yes, but my excuse is that i'm old and entitled to be grumpy sometimes :)
[13:36] <fuorviatos> BluesKaj: what i think man is you don't know anything about computers but again, you're hanging around in a support channels. How possibly would you immagine that installing a software would solve my problem? I did tell you it was deamon-releated stuff when I mentioned upower, so cut the crap
[13:37] <lordievader> BluesKaj, fuorviatos: Please drop it.
[13:38] <fuorviatos> lordievader: you're right - sorry
[13:38] <fuorviatos> back to the topics - this is a upower bug
[13:39] <BluesKaj> fuorviatos, suggest you let launchpad know that the bug affects you too
[13:39]  * fuorviatos is doing that
[15:46] <rodolfojcj> hello everybody
[15:46] <lordievader> o/
[15:46] <rodolfojcj> I have only one computer in my house, with multiple accounts, one for me and one for each of my 3 brothers
[15:46] <rodolfojcj> so we use "Switch user" feature of Kubuntu desktop
[15:47] <SporkWitch> rodolfojcj: it's not twitter, you CAN form a complete question, with background, in one message (and it's MUCH easier to read that way ^^)
[15:49] <rodolfojcj> I have noticed that if two desktop sessions are opened at the same time and later one of the users closes its session first, the other user is left with a high resources consumption
[15:50] <rodolfojcj> kded4 process is left eating about 25% CPU resources (two core machine) and the overall RAM usage is about 1.2 GB (of 3.2 GB)
[15:51] <rodolfojcj> this happens even if the user keeping his session opened has no applications opened
[15:52] <rodolfojcj> the only workaround is to reboot, so an opened desktop session with no applications opened eats only 3% to 6% of CPU and about 0.6 GB of RAM
[15:53] <rodolfojcj> do you know what could be the cause and a possible solution?
[15:59] <harald> hello together, is it possible to get the sound notification working for evolution gnome app under kde?
[16:29] <cjwelborn> I've been working on an installer application that can be dropped as a single file into any python project. Where can I get a list of the most common /bin, /home/user/bin, and application data directories? I know I am forgetting some.
[16:30] <cjwelborn> Nevermind.
[16:31] <cjwelborn> I found the XDG spec I was trying to remember.
[16:54] <Walex2> cjwelborn: that's a very evil thing to do
[16:54] <Walex2> harald: the KDE notifications protocol is I think KDE specific, but I amy be wrong, XDG sometimes standardizes those things.
[16:55] <Walex2> harald: if you can get Evolution to run a script to do notification however it ought to be easy to do one with 'qdbus'
[16:56] <Walex2> rodolfojcj: 'kded4' often gets stuck, as it does many odd things. It is fairly easy to restart it, without restarting the whole of KDE.
[16:57] <Walex2> rodolfojcj: you can restart 'kded4' with 'qdbus' or kill it and run 'kwrapper5 kded4 &' and then use 'kcmshell4 kded' to start its subdaemons.
[16:58] <Walex2> rodolfojcj: or you can use actually 'kcmshell4 kded' to stop and restart its subdaemons and often that's good enough.
[16:59] <cjwelborn> Walex2: at least it has a 'installed_files.txt', auto-cleanup on failure, and installs itself along side the app (as a single file) for easy uninstallation.
[17:00] <cjwelborn> I guess in a way I am being lazy, because I don't want to maintain a system package.
[17:01] <Walex2> cjwelborn: but running two package maintenance systems in the same directories is still fraught with trouble.
[17:01] <Walex2> cjwelborn: it will "mostly" work until it breaks :-)
[17:02] <Walex2> cjwelborn: as to the "lazy" thing yes, because building ".deb" *well* is not entirely trivial, but that's because of all the details to prevent trouble from happening, things like declaring dependencies, incompatibilities, and various other checks.
[17:03] <Walex2> but hey, Lennart Poettering wants to bring the joys of DLL hell to GNU/Linux, so anything goes nowadays
[17:03] <TheFakeazneD525> only for GNOME :^)
[17:04] <TheFakeazneD525> not based KDE
[17:05] <Walex2> TheFakeazneD525: good point! :-)
[17:05] <Walex2> TheFakeazneD525: please wait a moment for a legendary "this is how I think GNOME and KDE developers look like" article
[17:06] <BluesKaj> started with pulseaudio, now we're going to be forced to use systemd
[17:06] <Walex2> BluesKaj: "forced" is a bit strong -- GNOME users are "forced" to use 'systemd'. And between now and Kubuntu 16 many things can still happen.
[17:06] <TheFakeazneD525> the only truly bad thing about SystemD
[17:07] <TheFakeazneD525> is binary logs
[17:07] <cjwelborn> Walex2: yeh. you're right. I am basically just making a smarter 'install.sh'. I have seen a lot of those that don't provide any method of removal, and sometimes you don't even know what they created.
[17:07] <TheFakeazneD525> say, can't someone fork SystemD to remove binary logs
[17:07] <TheFakeazneD525> maintain compatability with SystemD, but no binary logs
[17:07] <BluesKaj> I don't understand why the ppl in the know don't stop this if it's as nonsensical as I've read
[17:08] <Walex2> BluesKaj: I was talking a couple of says ago with a very skilled Debian Developer, and he was saying that he was at DebConf and several people were already running SystemD and it just works, so he does not see the problem.
[17:09] <Walex2> BluesKaj: that saddened me a lot, because "it works"/"it does not work" is not the issue. MS-Windows works. MS-DOS worked too.  Then issue is how flexible and maintenable it is, and how well it fits withing a "building blocks" architecture.
[17:11] <BluesKaj> lets hope sysemd doesn'r slow older <os
[17:11] <Walex2> BluesKaj: indeed, MS-Windows works, it has a vast market share, and by expending enough effort its system administrators can make it do everything that GNU/Linux does. Just with a lots more effort, fragility and longer term maintainability issues.
[17:11] <BluesKaj> OS/pcs like windows does
[17:12] <Walex2> I use KDE because it has a certain architectucal cleanliness and modularity that gives me confidence about its longer term maintainability. Same for GNU/Linux.
[17:12] <TheFakeazneD525> guys, push Kubuntu to those upset with Metro = profit
[17:12] <Walex2> plus they are truly *free* software.
[17:13] <TheFakeazneD525> hmm, we should make a kubuntu spin with PPAs for popular software...
[17:13] <TheFakeazneD525> chrome, steam, etc
[17:13] <Walex2> plus they are truly *free* software. and I would use even crappier systems if they were *freedom* software, because that is very important.
[17:13] <cjwelborn> Walex2: Exactly why i like KDE. I can see they have an idea or goal in mind, and they are trying to stick to it.
[17:13] <tsimpson> TheFakeazneD525: there are legal issues with that, which is why it's not done
[17:13] <BluesKaj> kuibuntu 14.10 runs great on my 2008 vintage amd dual core cpu sysetm wit 3G ram vs W7 which is agonizingly slow when more then one app is open
[17:13] <TheFakeazneD525> tsimpson: huh
[17:13] <TheFakeazneD525> doesn't Netrunner ship with steam and flash installed?
[17:14] <Walex2> cjwelborn: it is not just that KDE has an overall idea behind it, it is also mostly the right idea.
[17:14] <Walex2> ezxcept for details like the config files being in ".ini" format (like SystemD!)
[17:15] <Walex2> please wait for me to find the old article about imagined developer profiles
[17:15] <TheFakeazneD525> KDE probably won't have SysD integration
[17:15] <TheFakeazneD525> due to KDE portability
[17:15] <TheFakeazneD525> windows, solaris, OSX, bsd
[17:17] <tsimpson> TheFakeazneD525: this is what you have to comply with to distribute flash (without worry of Adobe filing a law suit) http://www.adobe.com/products/clients/all_dist_agreement.html
[17:17] <tsimpson> chrome is a little different as it's mostly that it contains copyrighted material from google (as opposed to chromium)
[17:25] <Walex2> this is a famous post, which the authors now says has become an exaggeration: https://github.com/paultag/fib.io/blob/master/notes/pages/kde-vs-gnome.md
[17:27] <BluesKaj> Walex2, we already have several systemd libs, systemd and systemd-shim installed on 14.10..seems like 14.10 is gearing up for it
[17:28] <Walex2> BluesKaj: yes it is, but it Ubuntu will only fully switch to SystemD in version 16. Hey even version is not fully 'upstart'ed yet anyhow.
[17:29] <tsimpson> there is no fixed time for the translation to SystemD, other than "when the TB decide we're ready"
[17:29] <rodolfojcj> ok Walex2. I took note of your recommendations so I can apply it the next time such situation arises. Thanks a lot!
[17:30] <Walex2> tsimpson: and it will only happen on an LTS release really.
[17:30] <tsimpson> Walex2: what makes you think that?
[17:31] <Walex2> tsimpson: because Canonical sells LTS releases... the rest are beta tests for LTS.
[17:31] <tsimpson> I don't think putting new infrastructure in an LTS without first testing it in non-LTS releases is a Good Idea™
[17:32] <Walex2> tsimpson: sure, it will be beta tested before LTS 16. But it won't count. Major tech switches like Mir or Upstart or now SystemD can only happen in LTSes.
[17:33] <|xk05|> there is no systemctl?
[17:33] <tsimpson> I expect it to be tested and working in 15.x
[17:34] <tsimpson> and that 16.04 will have it unless things go horribly wrong
[17:34] <Walex2> tsimpson: sure. but Canonical won't *commit* to it until 16.04, they'd be mad otherwise. And we can always hope that things change in next 18 months.
[17:34] <tsimpson> we're already committed to systemd
[17:34] <Walex2> tsimpson: as you were committed to 'upstart' :-)
[17:35] <tsimpson> even since debian decided it's going with systemd
[17:35] <Unit193> 14.10 can already use it, though it isn't the default.
[17:35] <tsimpson> canoncial wanted debian to go with upstart, debian went with systemd and so will ubuntu
[17:36] <Walex2> tsimpson: I know I know...
[17:36] <tsimpson> the transition is already ongoing
[17:36] <tsimpson> I don't see why the first release to use systemd would be an LTS, seems silly to do that without a non-LTS release first
[17:37] <|xk05|> ok, we dont have systemctl, BUT we do have /usr/bin/deb-systemd-helper
[17:37] <Walex2> tsimpson: sure, but it only counts if it is an LTS. Because the people who pay for Canonical support only use LTS hopefully
[17:37] <tsimpson> only counts if it's an LTS?
[17:37] <tsimpson> it counts as soon as it's the default :)
[17:38] <Walex2> tsimpson: once a tech is part of LTS then Canonical is committed to support it fopr 7 years. Otherwise they are not.
[17:38] <Walex2> tsimpson: paying customers and all that :-)
[17:39] <tsimpson> there's already a commitment from canonical that systemd is going to be PID 1, they really can't go back on that now
[17:39] <Walex2> tsimpson: that's different from a commitment to paying customers who run an LTS for X years...
[17:40] <Walex2> tsimpson: a plan and a support contract are different things.
[17:40] <tsimpson> it's not really up to canonical either, the TB will decide when it happens
[17:40] <BluesKaj> TB?
[17:41] <tsimpson> Technical Board
[17:41] <Walex2> tsimpson: for example I would expect Canonical to support 'upstart' until 2019 (IIRC)
[17:41] <Walex2> BluesKaj: "TB" are the initials of "Mark Shuttleworth" as you can see :-)
[17:42] <tsimpson> obviously, 14.04 is supported for 5 years
[17:42] <tsimpson> most TB members are not Canonical employees
[17:43]  * Walex2 is being slightly facetious
[17:45] <BluesKaj> Technical Board seems like a rather broad title, is this the Canonical TB?
[17:45] <BluesKaj> or some Linux group?
[17:46] <Unit193> Neither, Ubuntu's.  Also, I believe this would all be more fitting in #kubuntu-offtopic, no?
[17:46] <tsimpson> it's the Ubuntu team that decides the technical direction
[17:47] <tsimpson> https://wiki.ubuntu.com/TechnicalBoard
[17:52]  * BluesKaj wonders when Kubuntu will decide to break off from the ubuntu core and decide it's own fate rather than being swept along by decisions that affect the OS without much consultation
[17:52] <Walex2> BluesKaj: that's a crazy thought
[17:53] <BluesKaj> crazy? somehow I don't think so, it's already split it's dev support to another company
[17:53] <Walex2> BluesKaj: there are plenty of other KDE-oriented groups withing other distros: the Gentoo KDE team, the Debian KDE team, the openSUSE KDE team. Kubuntu is the Ubuntu KDE team in effect.
[17:54] <Walex2> BluesKaj: it is a less comfortable relationship because most other distros are not committed to another desktop environment the way the official Ubuntu is.
[17:54] <Walex2> BluesKaj: but it is not too different.
[17:55] <BluesKaj> Walex2, I'm well aware of that, but the kubuntu development is no longer supported by canonical
[17:55] <tsimpson> depends what you mean by that, Canonical do provide a lot of support in terms of infrastructure
[17:56] <Walex2> BluesKaj: neither are the KDE packaging teams for Gentoo, Debian and a few others :-)
[17:56] <BluesKaj> as i speculated earlier tho , how long before kubuntu changes it's name and goes it's own way
[17:57] <tsimpson> we already had the debate about the name, turns out we like "Kubuntu" :)
[17:57] <BluesKaj> :)
[18:57] <alvin> Oh, I missed a systemd discussion. Well, I wasn't a great fan of Upstart, but at least it worked more or less in the latest releases. Systemd brings new and exciting ways to fail booting. Currently, on my machine (14.10) it's random
[18:58] <alvin> Well, not entirely random. There's a pattern.
[18:58] <lordievader> alvin: Utopic doesn't use systemd.
[18:58] <alvin> boot, fail, boot, fail, boot, fail. 50% success
[18:58] <alvin> It doesn't? Oh, well.
[18:59] <alvin> I take back what I said about Upstart working more or less then.
[18:59] <Unit193> alvin: It's optional in utopic, at least.  Not default.
[19:00] <alvin> Imho, booting has been the weakest part of Kubuntu for the past 5 years.
[19:00] <alvin> (Ubuntu too)
[19:00] <alvin> I'm using Kubuntu for the KDE experience, but certainly not for the core Ubuntu.
[19:01] <alvin> I had a dream before Debian started this systemd nonsense. Kubuntu'
[19:01] <alvin> s KDE packaged on Debian. That would have been fantastic.
[19:03] <alvin> Well, if systemd is optional in Kubuntu 14.10, I think I'll give that a shot next week. See if it solved the boot troubles.
[19:04] <veqz> kubuntu's worked fine for me so far. never had a problem with booting
[19:04] <veqz> 14.10 that is
[19:05] <alvin> 10.04 was especially terrible in that regard while I can't complain about 14.04.  (NFS mounts could either halt the system or be mounted entirely random)
[19:06] <alvin> I ditched Ubuntu server for FreeBSD. A very, very good decision. But I stayed on Kubuntu for my desktop.
[19:07] <friti> I have used VLC for my phonon backend in 14.10 for a while now, and lately my audio just plain quits on me until my next relog. Going back to GStreamer for the moment, and see if this issue persists.
[19:07] <alvin> Now that sounds familiar
[19:11] <Papamatti> Hi
[19:12] <Papamatti> Is it useful to  upgrade kde via the backports?
[19:12] <Papamatti> Or does it break everything
[19:14] <BluesKaj> Papamatti, depends which kubuntu version and kde version
[19:14] <rkt> hi
[19:15] <Papamatti> I'm using Kubuntu 14.04.1 with KDE 4.13.3
[19:16] <BluesKaj> Papamatti, then you should be safe to upgrade
[19:16] <Papamatti> BluesKaj: :-) Thank you for the quick anwer.
[19:17] <BluesKaj> Papamatti, dist-upgrade
[19:18] <Papamatti> BluesKaj: Ok
[19:22] <alvin> Papamatti: There's a show stopper bug in Kmail, if you're using that with a Courier server. But otherwise it's mostly bugfixes.
[19:23] <Papamatti> alvin: Thank you for the info, but I still use thunderbird for email. ;-)
[19:24] <alvin> Go for it then. (Also, that bug will be fixed in the next version too.)
[19:26] <BluesKaj> alvin, kmail has been buggy since 2009... it's never really been fixed for certain HW
[19:34] <Papamatti> alvin: ppa:kubuntu-ppa/backports is correct?
[19:35] <alvin> I know. I only stayed with it because it was so greate in KDE3. But since Baloo it has gotten a lot better. Search even works again. (The bug I'm talking about here is that IMAP on Courier servers does not work - at all)
[19:36] <alvin> Papamatti: I believe so. You'll find the method on http://www.kubuntu.org/ in the latest post
[19:39] <mr-rich> Google earth ... need I say more?
[19:39]  * mr-rich sighs
[19:39] <Papamatti> Ok,  start dist-upgrading....
[19:45] <Papamatti> alvin: Ok, upgrade  finished...I restart my system...... :-[]
[19:46] <alvin> Good luck. It'll work
[19:52] <Papamatti> Seems to work
[19:52] <Papamatti> KDE 4.14.0 :-)
[19:58] <rberg> kmail doesnt :)
[19:58] <rberg> just fyi
[19:59] <rberg> the 4.14.1 change log looks like the issues I had are fixed now
[20:07] <Papamatti> rberg: When comes 4.14.1?
[20:07] <Papamatti> (to the backports-repository)
[20:10] <TheFakeazneD525> http://www.qt.io/ <new qt site :D
[20:13] <joseph__> Hello World?
[20:14] <TheFakeazneD525> hi
[20:14] <joseph__> I finally made the switch to Linux from Windows this past weekend, decided on Kubuntu.  This is my first time using IRC also
[20:15] <joseph__> Anything important to note going forward?
[20:15] <rberg> Papamatti: when its ready is the standard answer.. I suppose
[20:15] <Papamatti> rberg: Ok, I have to wait...
[20:16] <rberg> yep
[20:16] <Mamarok> joseph__: hi and welcome to Kubuntu. Reading the topic links is usually a good start
[20:17] <joseph__> ok, will do
[20:38] <alvin> TheFakeazneD525: Thanks for the link. I still had https://qt-project.org/ but I see now they have a link too
[20:38] <TheFakeazneD525> no prob
[20:39] <alvin> rberg: Papamatti. I believe that'll be the beginning of next month. Sometimes it's skipped though, so that's not 100% sure. There will be a new version, but it's not always packaged.
[20:41] <rberg> I over heard someone in #kubuntu-devel mention working on 4.14.1.. but no mention on how it was going
[21:03] <davls82> Hello i am using Kubuntu 14.04 64 Bit i have a Logitech c270 HD Webcam but it don't works good enough does anybody can help?
[21:05] <ozooner_> What does not working good enough mean?
[21:07] <davls82> slow and bad picture
[21:11] <ozooner_> I am no expert, but you can try installing cheese (or some other external webcam software) so you can narrow down wether it's your skype, drivers or Internet conection
[22:02] <TheFakeazneD525> hmm
[22:03] <TheFakeazneD525> any way to make menu appear with only windows key
[22:03] <TheFakeazneD525> I try inputting only windows key (meta) into the hotkey thing but it wont work, so using windows+z
[22:04] <ozooner_> TheFakeazne, have you tried using Ksuperkey?
[22:05] <ozooner_> Meta key alone can not be made into shortcut by default (in linux its a modifier, just like shift or control is)
[22:09] <ozooner_> While you are at it, Krunner is an awesome tool to bing to super key :)
[22:09] <TheFakeazneD525> ah its the super key
[22:28] <keithzg> My fingers just remember alt+f2, heh (or f12 to bring down Yakuake; I can't imagine using the terminal any other way).
[22:28] <TheFakeazneD525> same :P
[22:35] <Avihay> http://kde-apps.org/content/show.php/ksuperkey?content=154569
[23:14] <sinclairos> hallo
[23:15] <TheFakeazneD525> <3
[23:15] <TheFakeazneD525> what a nice person