[03:36] <benlake> Folks, I hate to bother, but I’ve been at this for a while. Attempting to commission a my first node on a fresh 16.04.2 MAAS install using the 16.04 image and cloud-init is failing with “no datasource found”. Here is a screen cap with the interesting points being at times 1:27, 1:32, and 1:44, https://www.screencast.com/t/iSyL4IAPiI
[03:37] <benlake> I can’t quite tell if this issue is related: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1648380
[03:39] <benlake> Possibly relevant, at 0:59 mid screen you can see eth0 being renamed to enp1s0. I manually added the node (because this same issue prevented PXE based enlisting), and manually changed the interface name to enp1s0 in MAAS. Thinking that perhaps that was playing a part in preventing communication between controller and node.
[03:46] <benlake> 1:06 the line “Invalid path for Logical Volume” when referring to the iSCSI LUN seems troubling too, but it then goes on to seemingly mount and read /scripts/, so I guess OK?
[03:46] <benlake> The next step I suppose will need to be backdooring the image to dig around locally.
[03:50] <benlake> Attempting to poke around the “MAAS datasource” section on https://docs.ubuntu.com/maas/2.1/en/troubleshoot-faq led me to files that don’t exist on my controller. So I don’t know if that information is just old or if something didn’t get installed.
[03:51] <benlake> any pointers are appreciated.
[09:37] <cnf> ugh, silly maas networking :/
[13:10] <mup> Bug #1681278 opened: bootstrap failure on MAAS <bootstrap> <maas> <juju:Incomplete> <juju 2.0:Won't Fix> <MAAS:New> <https://launchpad.net/bugs/1681278>
[13:48] <jeevan> hi
[14:01] <benlake> Hmm, so I don’t have any files denoted by the “backdoor steps”, ie. no /var/lib/maas/boot-resources/*/*/*/*/*/*/root-image
[14:01] <benlake> but I think it just dawned on me that process is referring to images that actually manage to get deployed.
[14:01] <benlake> I instead, am stuck at cloud init issues during PXE boot.
[14:55] <benlake> should the cloud-init package been installed via the maas metapackage?
[15:26] <benlake> is there a way to get into the PXE booted image to check network config?
[15:26] <benlake> I’m working under the assumption “no datasource found” might be a failed MAAS API call
[15:29] <pmatulis> benlake, i cannot see your original screenshot. got some kind of java problem trying to view
[15:29] <benlake> this? https://www.screencast.com/t/iSyL4IAPiI - it is a flash video
[15:30] <benlake> I’ll snap pics at the times I noted.
[15:35] <benlake> iSCSI path issue (maybe?) https://www.screencast.com/t/d74xmHp8tt6L
[15:35] <benlake> cloud-init init https://www.screencast.com/t/tJXY2WzefYl
[15:35] <benlake> cloud-config apply no datasource https://www.screencast.com/t/rvKCTWh1xv7
[15:36] <benlake> cloud-init stage final no datasource https://www.screencast.com/t/zZ3KnTDZAPV
[15:37] <benlake> I’ve been poking around the maas node to try and find/understand what config is being sent to cloud init
[15:41] <pmatulis> benlake, can you explain your network topology and what the underlying machines are?
[15:45] <benlake> maas controller has 2 interfaces, same wire. Untagged and VLAN 100 interfaces. Untagged is <IP_ADDRESS>/25 the “provisioning subnet”. I set a dynamic range of <IP_ADDRESS>-.254. I enabled maas DHCP on the untagged interface.
[15:45] <benlake> the controller is a supermicro + ubu 16.04, and the node attempting to be deployed is the same spec supermicro
[15:45] <benlake> both with IPMI 2.0+
[15:46] <benlake> the node I’m attempting to deploy properly PXE’s via maas
[15:47] <benlake> and DHCP is assigning <IP_ADDRESS>
[15:47] <benlake> since enlistment didn’t work, I manually added. maas is properly managing IPMI to control power to the machine.
[15:50] <benlake> because I don’t want you to have to believe me, here is the PXE boot https://www.screencast.com/t/9vlNb5rfRM
[15:50] <benlake> oh balls.
[15:50] <benlake> oh pmatulis, you rubber ducky you
[15:50] <pmatulis> benlake, hm?
[15:51] <benlake> I just noticed there is a config-url displayed in that last screenshot
[15:51] <benlake> and it has the tagged interfaces IP!
[15:51] <benlake> but the iscsi target IP is correct. why the hell is maas deciding to use both?
[15:59] <benlake> anyone know where maas is pulling the config-url IP from?
[16:13] <kiko> blake_r, mpontillo, or maybe newell might know that one
[16:14] <kiko> benlake, those addresses do look suspicious
[16:14] <kiko> benlake, I assume the 74.x network is not accessible from the node itself
[16:14] <benlake> the IPs are valid, just not what maas should be using here.
[16:14] <blake_r> benlake: what is the maas_url= in the /etc/maas/regiond.conf
[16:14] <benlake> correct, 74. is not.
[16:15] <blake_r> benlake: that needs to be the same IP address that the PXE booting nodes can reach the region controller
[16:15] <benlake> I just found this command, sudo maas-region local_config_set
[16:16] <blake_r> benlake: you can use that command to change the value in /etc/maas/regiond.log, or manually change it
[16:16] <benlake> and set it to the correct IP, so /etc/maas/regiond.conf has the correct IP. Not sure if it did before. Let me check history
[16:16] <benlake> ding, ok so that command prolly changed it
[16:16] <blake_r> benlake: if you change it you need to restart
[16:16] <blake_r> systemctl restart maas-regiond
[16:16] <kiko> benlake, this is a very common problem, it stems from us trying to guess the address during MAAS insteall
[16:16] <blake_r> to get the updated IP and then try to enlist
[16:16] <kiko> install
[16:17] <kiko> blake_r, where did we end up with putting a debconf option to request upon installation?
[16:17] <kiko> blake_r, or alternatively, leaving it unconfigured until the user sets it explicitly
[16:17] <kiko> instead of trying to guess
[16:17] <kiko> as when we guess wrong, which is almost always on a multi-homed regiond, the failure more is horrible?
[16:17] <blake_r> kiko: dpkg doesnt request
[16:17] <kiko> I had a bug filed on this since prehistoric times I think
[16:17] <blake_r> kiko: this is a change the snap has done, to make this process better
[16:18] <blake_r> kiko: the snap asks you when you configure
[16:18] <kiko> that's nice -- but dpkg could too if we wanted it to?
[16:18] <blake_r> kiko: another fix would be to proxy all requests through the rack, then that IP doesn't matter
[16:18] <blake_r> kiko: I think it doesn't because it breaks installation from the ISO
[16:18] <blake_r> kiko: but I don't fully remember why
[16:18] <kiko> I think it depends on the priority set in the ISO installer
[16:19] <kiko> indeed, that would work and is probably the right solution
[16:19] <benlake> blake_r: restarted, testing. I concur with not guessing. Especially since MAAS most definitely is OK working with VLANs, so the controllers will likely always have multiple interfaces...
[16:19] <kiko> right
[16:20] <kiko> https://bugs.launchpad.net/maas/+bug/1418044
[16:20] <benlake> why are the iscsi paths using the other IP?
[16:20] <kiko> because they talk to the rack controller
[16:20] <kiko> which is a separate component
[16:20] <benlake> seems odd that discovery isn’t at least consistent
[16:20] <benlake> oh, gotcha
[16:20] <kiko> well that is due to a design artifact:
[16:21] <kiko> a) region and rack are separate, for scalability reasons (you'll want many rack controllers)
[16:21] <kiko> b) the nodes mostly talk to the rack, but for metadata requests currently talk to the region
[16:21] <blake_r> benlake: you can also change the /etc/maas/rackd.conf maas_url
[16:21] <kiko> c) at install time it's unclear what the internal interface for the region controller actually is, and we guess
[16:21] <blake_r> benlake: that is unique per rack controller
[16:22] <benlake> blake_r: that’s currently localhost, so it’s OK
[16:22] <blake_r> benlake: if its localhost, MAAS will use the IP set in regiond.conf
[16:22] <benlake> oh wow, that’s opaque
[16:23]  * benlake changes it
[16:23] <blake_r> benlake: it tells the rack controller how to talk to the region controller
[16:23] <kiko> blake_r, wtf??
[16:23] <blake_r> benlake: but the machines that PXE boot from that rack controller, must also be able to contact the region controller at that address
[16:23] <benlake> yeah, I follow that, but detecting localhost and then using another config is a bit rough
[16:24] <kiko> what benlake said
[16:24] <benlake> if it says localhost, I expect localhost to be resolved.
[16:24] <kiko> anyway, it's really unclear that that config means "the IP which nodes trying to talk to me should use"
[16:24] <kiko> which leads to putting localhost in be fine
[16:24] <benlake> blake_r: yup, gotcha.
[16:24] <blake_r> really what should happen is that all comunication should proxy through the rack controller
[16:24] <blake_r> removing the need for the nodes to use the maas_url in rackd.conf
[16:24] <kiko> sorry, leads to people thinking that putting localhost in is fine
[16:25] <kiko> yeah
[16:25] <blake_r> butting localhost is fine
[16:25] <blake_r> in a simple MAAS
[16:25] <blake_r> in complex networking things get more difficult
[16:25] <blake_r> but proxy through rack would solve this problem
[16:26] <benlake> one thing I did after manually adding this node, then marked it broken, was to change the interface name from eth0 to enp1s0 - is that necessary? is that interface name meaningful to cloud-init/deployment?
[16:26] <benlake> I did this in my troubleshooting quest
[16:27] <kiko> it should not be necessary
[16:27] <blake_r> benlake: that is not necessary
[16:27] <blake_r> benlake: but when you deploy that interface will always get that name
[16:27] <benlake> great! trying commission again, if it moves along, I’ll blow everything away and try a raw enlist via pxe.
[16:28] <benlake> “get that name” - as in end up in /etc/network/interfaces?
[16:29] <blake_r> benlake: yep, and udev rules to make sure it has that name
[16:29] <benlake> sweet, cloud init worked!
[16:29] <benlake> blake_r: ah, ok then.
[16:31] <cnf> so MaaS won't allow a default gateway outside of the CIDR i define
[16:32] <cnf> but the CIDR is a lot larger, i just have a small part of it assigned to me
[16:33] <mpontillo> cnf: MAAS expects the CIDR to match how it is defined on the network; if you only control a small part you can make it an "unmanaged" subnet in MAAS 2.2 (reserve a range for IP allocation). if you want MAAS to use DHCP on that subnet, define the entire subnet, and make sure to define it as a managed subnet with reserved ranges for the portions MAAS is not
[16:33] <mpontillo> allowed to allocate from
[16:34] <cnf> mpontillo: yeah, that's a pain, because i have a /29 in it and a /28 in it, used for different things
[16:34] <mpontillo> cnf: worth noting is that MAAS is happier with non-overlapping subnets as well; users are allowed to model overlapping subnets but there might be edge cases, so I would recommend against it
[16:35] <mpontillo> cnf: if it's just one bit, should be easy to mask off the unusable-to-MAAS portion with a reserved range?
[16:35] <cnf> you can recommend against it, but i don't decide on the network ranges used
[16:35] <cnf> 2 bits, i have 2 non- following parts of a /24
[16:36] <cnf> both with the same gateway
[16:36] <mpontillo> cnf: oh okay, so there are at least three overlapping subnets, a /24, /28, and /29?
[16:36] <cnf> yeah
[16:36] <mpontillo> cnf: are you managing DHCP on the subnet?
[16:37] <mpontillo> cnf: rather, do you expect MAAS to manage DHCP on your portion of the subnet?
[16:37] <mpontillo> cnf: if yes, how is the traffic isolated from the larger subnet?
[16:37] <cnf> it's not DHCP, but juju needs to ask for IP's in it
[16:38] <cnf> mpontillo: which is used for IPs for containers
[16:42] <cnf> legacy, so much fun
[16:43] <mpontillo> cnf: ok. so if I understand you correctly, you have /24, you don't manage DHCP on the subnet, and you want to carve out /28 and /29 networks for specific container-IP-assignment purposes?
[16:43] <benlake> blake_r: pmatulis: kiki: thanks for your help. The machine is now progressing. Some other things to tinker with, but those are likely with my setup.
[16:43] <kiko> benlake, thanks, please chime in on the bug so it's not just me :-)
[16:43] <cnf> mpontillo:  yes
[16:44] <benlake> kiko: will do!
[16:44] <cnf> it's the only way i know to get juju the IP's for containers, when running on MaaS
[16:45] <mpontillo> cnf: how do you plan to tell juju which subnet to use? (are you using spaces? if yes, MAAS 2.2 may actually break you, since spaces moved to be associated with VLANs instead of subnets)
[16:46] <cnf> i am using spaces
[16:46] <cnf> and ugh
[16:46] <cnf> why would you associate spaces with VLANs?
[16:46] <cnf> how can you then tell juju what subnet to use?
[16:48] <mpontillo> cnf: well, there was a significant debate about that. basically there is no perfect solution, but in order to deploy OpenStack in certain scenarios we needed to have a way to have an "empty" VLAN with a space, but no subnets assigned yet
[16:48] <mpontillo> cnf: it was understood at the time that people weren't using spaces how you're using them =(
[16:48] <blake_r> cnf: there is no true isolation unless a space is a VLAN
[16:48] <cnf> i have been struggleing with openstack on MaaS / juju for a LONG time now
[16:48] <cnf> list of open bugs is growing...
[16:50] <cnf> i mean, if you want a vlan, define a vlan!
[16:50] <cnf> the usefulnes of spaces was that you could put several subnets in a single space
[16:50] <mpontillo> cnf: right, so as blake_r implied, spaces were envisioned as a "color" for a vlan/subnet the defined its security properties. you might have a "red" space for your DMZ, "green" for your intranet, "purple" for your protected health care data, etc
[16:50] <mpontillo> cnf: if you combine all those things onto the same VLAN is sort of defeated the purpose of spaces modeling the security properties of the network
[16:50] <blake_r> cnf: you can have 2 vlans in the same space
[16:51] <blake_r> cnf: just a router between them
[16:51] <mpontillo> *can't I think you mean blake_r?
[16:51] <blake_r> mpontillo: can(
[16:51] <blake_r> can*
[16:51] <cnf> this is going to be a fun RFI
[16:51] <blake_r> as for the subnet you don't control
[16:51] <blake_r> add the whole subnet
[16:52] <blake_r> set it to unmanaged
[16:52] <cnf> so i can almost start from scratch
[16:52] <cnf> and it STILL doesn't fix my problems
[16:52] <blake_r> and define a range
[16:52] <blake_r> then Juju will only use those IP's
[16:52] <cnf> blake_r: and then add the same subnet again?
[16:52] <blake_r> cnf: how does it not fix your problem?
[16:52] <cnf> and maas won't mind that?
[16:52] <blake_r> you add the whole subnet, and set that subnet to unmanaged
[16:53] <blake_r> in that subnet you create an IP range
[16:53] <blake_r> MAAS will only use those IP's in that range
[16:53] <cnf> there is a /24, out of which i have non - sequential a /29 and a /28
[16:53] <cnf> with different purposes
[16:53] <blake_r> cnf: that is fine
[16:53] <blake_r> cnf: add the whole /24
[16:53] <cnf> so i need to add the same /24 twice in maas
[16:54] <blake_r> cnf: define the range you want your IP's to be assinged in that fall with in the /29 and /28
[16:54] <cnf> define them where? how do i distinguish between the 2?
[16:56] <cnf> blake_r: i have no idea what you mean
[16:57] <blake_r> cnf: what subnets do you have now?
[16:57] <blake_r> cnf: in MAAS
[16:58] <cnf> uhm, tons
[16:58] <cnf> i have the /24
[16:58] <cnf> the other 2 are a problem
[16:58] <blake_r> did you add those manually? or where they discovered?
[16:59] <cnf> i have discovery turned off
[16:59] <cnf> that was just a mess
[16:59] <blake_r> "the other 2"? did you add them manually or did they just show up?
[16:59] <cnf> they are not defined
[16:59] <cnf> as i don't know how to
[16:59] <mpontillo> cnf: well, MAAS will "discover" subnets outside of "device discovery"; it will automatically add subnets it finds configured on rack controllers
[16:59] <blake_r> cnf: okay
[16:59] <blake_r> cnf: what MAAS version?
[17:00] <cnf> mpontillo: i have _all_ discovery turned off
[17:00] <cnf> 2.1.3+bzr5573-0ubuntu1 (16.04.1)
[17:00] <mpontillo> cnf: there is no option to disable discovery of subnets found on rack controllers
[17:01] <blake_r> mpontillo: he means device discovery
[17:02] <blake_r> cnf: with your setup you will want the unmanaged subnet feature
[17:02] <blake_r> cnf: since that is a subnet that MAAS doesn't manage
[17:02] <cnf> which i guess is in 2.2
[17:04] <cnf> right?
[17:04] <blake_r> sudo add-apt-repository ppa:maas/next-proposed
[17:04] <blake_r> sudo apt update && sudo apt upgrade
[17:05] <cnf> yeah, but that would completely break my juju openstack
[17:05] <blake_r> why is that? thought it didn't work at all?>
[17:06] <cnf> it's running, just without the ip's from the /29
[17:06] <cnf> which are the routable ones
[17:06] <cnf> which means i need weird tunnels to access the openstack
[17:06] <cnf> because, hell, putting them behind a single ip isn't something that works atm with charms
[17:07] <cnf> anyway, it's 19:07, time to go home...
[17:07] <blake_r> cnf: you can set static IP addresses on nodes
[17:07] <cnf> blake_r: not on containers
[17:07] <blake_r> cnf: ah true
[17:08] <cnf> so you need a LOT of routable IP's just to have a workable chams openstack
[17:08] <cnf> which is what the /29 is for
[17:08] <cnf> i won't even start on the long, long list of other bugs i have on juju etc :(
[17:09] <cnf> a lot of which come from assumptions of network layouts
[17:09] <cnf> anyway, 7 pm, i'm hungry
[17:09] <cnf> tomorrow is another day
[17:09] <cnf> i'll have to look at how the new spaces work, i guess
[17:09] <cnf> thanks for the help
[18:00] <cnf> aaand home
[18:10] <mpontillo> cnf: please let us know how things work out (or don't work out) for you; you can bring things up on the maas-devel list and/or the bug tracker (Launchpad) if you want more visibility for your use cases
[19:13] <mup> Bug #1651316 changed: Disks are found but not shown <MAAS:Fix Released> <https://launchpad.net/bugs/1651316>
[19:41] <benlake> what does it mean to use the “retain network configuration” option when commissioning?
[20:07] <kiko> benlake, the network interfaces, do you want them reset back to unbonded, unvlanned etc?
[20:07] <kiko> benlake, also, c'mon https://bugs.launchpad.net/maas/+bug/1418044
[20:08] <benlake> I promise I am going to do that thing!
[20:08] <kiko> cnf, I'd love you to share the current issues you're running into with juju, ivoks nobuto and I are tracking this closely
[20:08] <benlake> so network temporarily reset to a defailt state, ignoring any setup done in maas?
[20:09] <benlake> *setup - any network configuration adjustments setup in maas
[20:09] <kiko> correct
[20:09] <benlake> kk
[20:24] <cnf> kiko: https://bugs.launchpad.net/~cnf is a start :P
[20:25] <cnf> kiko: a very large part of them are proxy related
[20:31] <kiko> cnf, you and ivoks would be best friends
[20:31] <kiko> cnf, we actually started on a plan with jamespage to address that more widely, let me find it
[20:32] <cnf> kiko: i have been in contact with jamespage for most of it
[20:32] <cnf> also, place i work at is launching an RFI for an openstack install
[20:32] <cnf> so i'll be using that  channel to add some weight to some issues
[20:33] <kiko> cnf, https://www.dropbox.com/s/qvhi0wyfj87tyxq/PROXY.txt
[20:33] <kiko> cnf, see if that matches what you think could work. there is backwards-compatibility problem thrown in the mix but it should be solvable
[20:34] <benlake> finally have a fully deployed node. really surprised the base install is 9.5GB O.o
[20:34]  * benlake checks if he installed Windows
[20:34] <cnf> kiko: you can add "openstack picks up htt-proxy and ignores no-prozy"
[20:34] <kiko> benlake, 9.5GB can't be right. fully deployed with what?
[20:34] <benlake> ubuntu xenial
[20:34] <kiko> benlake, uhhh that can't be right
[20:34] <benlake>  /dev/mapper/vgroot-lvroot  219G  9.5G  199G   5% /
[20:34] <kiko> cnf, "openstack" as in the system or the charms or what?
[20:35] <cnf> kiko: openstack as installed with charms
[20:35] <cnf> totally ignores no-proxy settings
[20:35] <cnf> so _nothing_ can talk to keystone
[20:35] <cnf> because my proxy can't talk to keystone
[20:35] <kiko> cnf, but my question is whether the charms themselves ignore no_proxy or whether the systems are configured without them or..?
[20:36] <cnf> oh, no, no-proxy envs are set
[20:36] <cnf> it's populated wherever i know to look?
[20:36] <cnf> but openstack just seems to ignore it
[20:36] <cnf> which isn't a juju problem, of course
[20:36] <kiko> hmm... that's weird.
[20:36] <cnf> but it causes problems with other software, which i can't fix with juju
[20:37] <kiko> so how does http_proxy get used by openstack itself?
[20:37] <cnf> kiko: whish is where https://bugs.launchpad.net/juju/+bug/1681495 came from
[20:37] <benlake> well, I found the reason./swap.img is 8GB
[20:37] <cnf> kiko: yes
[20:37] <kiko> does it pick up from env vars set when launching the control plane services?
[20:37] <kiko> benlake, that looks more like it
[20:37] <benlake> I guess we’ve switched to file based swap!
[20:37] <cnf> kiko: it sure looks that way, yes
[20:37] <cnf> kiko: jamespage was involved with debugging this, byw
[20:38] <kiko> benlake, maybe we do that if you don't define a swap partition? I'm surprised tbh, also because I'm not a big fan of file based swap for i/o path reasons
[20:38] <benlake> slightly unfortunate side effect of that transition is that the swap space is hidden. guess I’ll get used to that
[20:38] <kiko> benlake, can't you just define a swap partition?
[20:38] <benlake> I did nothing special, just pushed buttons to get a thing deployed. wanted to see a success before mucking around
[20:39] <benlake> I have an existing PXE+preseed environment. Is there somewhere I can use my existin pressed with MAAS?
[20:39] <benlake> or do some merging?
[20:40] <benlake> honestly, I need to continue reading the docs. This is the farthest I’ve made it, and most of my time had been on reading setup and troubleshooting
[20:40] <cnf> kiko: i also have a need for the openstack loadbalancer charm
[20:40] <cnf> but i understand resources are not available for that atm
[20:40] <kiko> cnf, for lbaasv2?
[20:41] <cnf> kiko: http://specs.openstack.org/openstack/charm-specs/specs/pike/approved/openstack-load-balancer.html
[21:19] <kiko> cnf, oh, on the infra layer -- L3 HA basically
[21:19] <cnf> uhu
[21:19] <cnf> solves HA, AND openstack services not being on routable networks
[21:20] <kiko> we are probably likely to have to work on this -- our telco customers all have these requirements
[21:20] <cnf> count me as "a telco customer" :P
[21:20] <kiko> and for many of them we've done the setup manually
[21:21] <cnf> kiko: our contact at canonical is Richard Card, i believe
[21:21] <kiko> cnf, oh are you an existing customer?
[21:21] <cnf> well, we just launched an RFI
[21:22] <cnf> we'll be doing an RFP end Q3, early Q4?
[21:22] <kiko> ah, yes, I read it earlier this week
[21:23] <cnf> it under Telenet, or Liberty Global
[21:23] <cnf> i think it's under Telenet
[22:34] <sanjay> hi
[22:34] <sanjay> I have an issue for node deployment in maas
[22:35] <sanjay> the deployment of ubuntu os gets completed but at last moment the system goes to grub rescue mode
[22:35] <sanjay> and then doesn't move on for deployment suceessfull
[23:55] <benlake> interesting. I’m configuring the firewall of the maas controller, and I’ve noticed that enlisting discovers the power type when the firewall is off, but is unable to discover it with the firewall on. What service is providing that discovery?
[23:56] <benlake> I figured it’d all be happening on the server using local IPMI tools and then hitting the maas api with the deets
[23:57] <benlake> maybe a round trip to the api, to trigger a reach out to the IPMI to confirm, but I’m not blocking outbound connections, so not sure why that would break.


[00:51] <pikapika> can we clamp both upper and lower time thresholds for double clicks
[13:19] <Ninten> Hi, folks! Ubuntu 22.04.1 is expected to be released today. Is it appropriate to assume the same for Xubuntu?
[13:21] <kryten> Yes, all official flavors will also be released at the same time.
[13:38] <Ninten> @kryten Thank you for your response! I'm so happy I will be able to upgrade
[19:43] <Ninten> Hi, folks! After upgrading to 22.04.1 I can't boot in default mode, I always get the emergency mode. Can anyone be of assistance
[20:05] <ReadyPlayerZeroO> hello?
[20:06] <ReadyPlayerZeroO> any1 home?


[00:43] <ScottK> Riddelll: I'm running from perlkde.
[06:40] <lordievader> Good morning.
[07:30] <apachelogger> Riddelll: since when do we actively track bugs?
[08:43] <Riddelll> apachelogger: only the next PPAs have arm cos shadeslayer asked for it
[08:51] <apachelogger> ah
[08:51] <apachelogger> Riddelll, shadeslayer: could someone please send a mail about that to the list :P
[08:58] <kdeuser56> whats the problem with debugging stuff on kubuntu-plasma5? whenever a crash happens dr konqi shows nothing despite me installing many debug symbols
[09:28] <Riddell> ScottK: remember bug 1353973 for SRU
[09:28] <Riddell> or MRE or whatever it's called
[09:28] <kdeuser56> Riddell: is it just me or does drkonqi not really work on the kubuntu-plasma5 image?
[09:30] <Riddell> kdeuser56: I've not tried thus far, maybe apachelogger has with his porting of kubuntu-debug-installer
[09:30] <kdeuser56> Riddell: I installed tons of debug symbols and it still does not show a useful trace
[09:30] <kdeuser56> Riddell: if you wanna try you know the kill -s SIGSEGV $(pidof <application-name>) trick, right?
[09:30] <Riddell> ok I'll try it later when doing the beta 1 tests
[09:30] <Riddell> yeah I know :)
[09:31] <kdeuser56> Riddell: what kubuntu-debug installer is he porting? you mean the apport patches?
[09:31] <apachelogger> drkonqi is kaput
[09:31] <apachelogger> that's why
[09:31] <kdeuser56> apachelogger: I have ported the apport patches
[09:31] <apachelogger> also there was an upstream bug in 5.0.1 that rendered stacks broken AFAIK
[09:32] <Riddell> is it kaput? that's a bad thing to be
[09:33] <apachelogger> was repaired
[09:33] <apachelogger> I think
[09:34] <kdeuser56> apachelogger: I only have one problem leftwith kubuntu_drkonqi_whoopsie_integration.patch: it does not create the dr.konqi accept file, so something broke :-(
[09:35] <kdeuser56> apachelogger: although the diff did not apply anymore not much has changed. I manaully applied the diff, changed kdebug to qdebug and it compiled
[09:36] <kdeuser56> apachelogger: new diff: http://paste.ubuntu.com/8157817/
[09:37] <kdeuser56> apachelogger: and that would be the one for kcrash: http://paste.ubuntu.com/8157820/
[09:38] <kdeuser56> apachelogger: both compile, second works as expected, first not yet, I'll have a look again, in the next hours
[09:41] <kdeuser56> apachelogger: to be more precise, it seems like only the if in the destructor does not seem to work in http://paste.ubuntu.com/8157817/
[09:43] <apachelogger> well, the destructor thing is a bit of an ugly hack anyway :P
[09:43] <Riddell> ScottK: and also a gstreamer backend on bug 1358312
[09:43] <kdeuser56> apachelogger: yeah, but where else to put it? after the close button has been pressed it should be invoked
[09:45] <kdeuser56> apachelogger: and all the other buttons like restart etc. so the destructor does not seem that ugly ...
[09:45] <Riddell> sgclark: did you do any ISO tests?
[09:45] <sgclark> yeah
[09:45] <Riddell> oh yes you marked it as fail :)
[09:45] <sgclark> I did. Power management is a game breaker for me
[09:51] <apachelogger> kdeuser56: one option would be: have a q_global_static qobject and connect it to the checked signal of the checkbox, write data in its dtor
[09:52] <apachelogger> the problem with doing it in the dialog's dtor is that the patch doesn't have scope control, or all the patch knows s_whoopsieCheckBox might have been deleted by then already because of qobject parenting
[09:58] <kdeuser56> apachelogger: and the whoopsie/apport upload process really starts as soon as the accept file is created? does not sound logical to me
[10:01] <kdeuser56> apachelogger: oh nevermind
[10:01] <apachelogger> no
[10:01] <apachelogger> apport starts as soon as the signal is re-raised by kcrash
[10:02] <kdeuser56> apachelogger: yeah, i know ... sorry do not knwo what I've benn thinken
[10:16] <Riddell> kubotu: newversion kdevelop 4.7.0
[10:16] <kubotu> https://bugs.launchpad.net/bugs/1362107
[10:20] <Riddell> kubotu: newversion wacomtablet 2.1.0beta1
[10:20] <kubotu> https://bugs.launchpad.net/bugs/1362111
[10:55] <Riddell> shadeslayer: alive?
[10:56] <shadeslayer> Yea
[10:56] <shadeslayer> Meet you in 20 mins for lunch?
[10:57] <Riddell> okay dokay
[10:58] <Riddell> no plans for lunch as yes, I'm in favour of buying a bagette and making some sandwiches
[10:58] <shadeslayer> Ah :p
[10:58] <Riddell> cos that's what we used to have to do back in the getto where I grew up
[10:58] <shadeslayer> Riddell: OK then I will head into the office, be there in 20
[11:11] <soee> there is new section available in System Settings -> Display Cofiguration that should allow configure monitors etc i think.
[11:12] <soee> but if we enter there we hane only The shared library was not found.
[11:16] <BluesKaj> Hiyas all
[11:32] <Riddell> soee: ah something is up with kscreen in plasma 5 I guess
[11:32] <soee> hi BluesKaj
[11:32] <soee> Riddell: ok good to know its not me only
[11:33] <BluesKaj> hey soee
[11:36] <sgclark> Riddell: that ISO using the frameworks kscreen?
[11:36] <Riddell> sgclark: should be yes, Ihave not checked yet
[11:37] <Riddell> yes it will be or it would not be shown at all
[11:37] <sgclark> Riddell: ok I will take a look to make sure it is not the packaging
[11:37] <Riddell> but why it doesnt want to load it I dont know
[11:37] <sgclark> Any clues on the power manangement?
[11:38] <Riddell> also not had a chance to look
[11:38] <Riddell> some issue upstream I suspect but it may be an issue only exposed on kubuntu
[11:38] <BluesKaj> in the plasma5 daily, copy and paste doesn't work unless the source file is left open
[11:43] <yofel> sounds like klipper isn't running
[11:43] <BluesKaj> but that will probly be solved soon ... too lazy to file a bug atm since it's not real serious
[11:43] <BluesKaj> yofel, let me check
[11:46] <BluesKaj> had to check the desktop pc and klipper is running
[11:47] <yofel> then it's not working :/
[11:51] <BluesKaj> and the virtual desktops aren't accepting different backgrounds/wallpapers...I remember a similar problem early in 14.10 plasma 4 which eventually was corrected without filing a bug
[12:28] <BluesKaj> running plasma 5 daily on the desktop since it's just a media sever and seems to do it's job ok atm ..plasma 5 on this laptop is still too frustrating
[12:31] <sgclark> not sure what the deal is with kscreen, nothing jumping out at me in build log. all depends satisfied. Lintian good and no missing. Think I will try a new snapshot..
[12:33] <sgclark> blech nothing new.
[12:34] <Riddell> sgclark: does it run standalone_
[12:35] <Riddell> kcmshell5 kscreen ¿
[12:35] <Riddell> ...spanish keyboards are fun
[12:36] <sgclark> Riddell: nope... missing shared library. lemme strace.
[12:36] <Riddell> "Rex Dieter<EMAIL_ADDRESS>has been successfully subscribed to kubuntu-devel." yay rdieter still loves us... wait, hes a fedora spy¡
[12:39] <Riddell> sgclark: I think it also claims missing even if it just cant load the plugin for whatever reason
[12:39] <rdieter> double blind spy worm mole
[12:39] <Riddell> e.g. if its binary incompatible
[12:39] <sgclark> Riddell: ok very strange, I saw ENOENT (No such file or directory)  on files I know were in package so I reinstalled wih my local build deb and viola it works.. I changed nothing
[12:40] <sgclark> somehow files are missing on what was uploaded
[12:41] <Riddell> apt'get install ''reinstall
[12:41] <Riddell> fixing ' for dashes
[12:41] <Riddell> dpkg 'L kscreen
[12:41] <Riddell> lists all the files
[12:41] <Riddell> maybe thereś a .install file gone missing somewhere
[12:42] <sgclark> I used the debain from bzr
[12:44] <sgclark> Riddell: the paths are wrong in the next PPA, did it get built with the wrong ECM? then a rebuild outta fix it
[12:46] <sgclark> .I think that is the problem. There was an ECM that broke lots of stuff
[12:46] <shadeslayer> Riddell: https://git.reviewboard.kde.org/r/119901/
[12:53] <Riddell> sgclark: ooh that could be the case
[12:53] <Riddell> sgclark: can you upload it to next'staging again_
[12:54] <sgclark> yeah
[12:54] <sgclark> I wonder if maybe powerdevil got the same bug
[12:55] <Riddell> possibly but it has a separate error
[12:55] <Riddell> worth trying
[12:55] <soee> so thsi can fix the kscreen problem ?
[12:55] <sgclark> yes
[12:55] <soee> btw what is ECM ?
[12:56] <sgclark> extra-cmake-modules
[12:58] <soee> oh, thakn you
[12:59] <Riddell> "Install Plugins and Qt5 Imports to the Qt5 install dir" → "Install Qt Plugins, Imports and QMake mkspecs to the Qt install dir"
[13:01] <Riddell> soee: cmake modules from KDE Frameworks
[13:09] <sgclark> unfortuantely it looks like powerdevil plugins are in the correct place
[14:03] <soee> kscreen works now, though connecting TV through hdmi makes plasmashell crash, laso on the display list hdmi is listed twice not sure why
[14:09] <soee> can i chnage phonon backend from cli ?
[14:23] <Riddell> hmm so the plasma5 image is a bit broken :(
[14:23] <Riddell> no ubiquity-dm
[14:23] <Riddell> then weird permissions issues connecting to the network
[14:23] <Riddell> and running ubiquity
[14:24] <Riddell> we have the same problem with non-english keyboards as we had in the alphas
[14:25] <Riddell> and the syslinux menu has the weird back option still and can't boot OEM but then it is broken for other flavours too
[14:25] <shadeslayer> yep
[14:25] <shadeslayer> known issue that
[14:25] <shadeslayer> bug colin
[14:26] <shadeslayer> whoa
[14:26] <shadeslayer> I have systemd
[14:26] <shadeslayer> in my dmesg
[14:26] <shadeslayer> or well
[14:26] <shadeslayer> my dmesg is colored
[14:26] <shadeslayer> and what not
[14:26] <shadeslayer> fancy
[14:37] <shadeslayer> Riddell: https://code.launchpad.net/~rohangarg/ubiquity/plasma5/+merge/228528
[15:31] <shadeslayer> oh oh oh
[15:31] <shadeslayer> im-config pulling in zenity
[15:31] <shadeslayer> why
[15:31] <shadeslayer> why on why
[15:31] <Riddell> it likes to do that
[15:31] <Riddell> I've removed it more than once in the past I'm sure but eventually one loses the will
[15:32] <shadeslayer> plasma 5 has mir because of that
[15:32] <Riddell> umm
[15:32] <Riddell> why does zenity need mir?
[15:32] <Riddell> infact why does anything need mir
[15:33] <shadeslayer> zenity needs libgtk3-0 which depends on libmirclient
[15:34] <Riddell> mm
[15:56] <apachelogger> shadeslayer: what
[15:56] <apachelogger> I sent a patch to the debian maintainer
[15:56] <apachelogger> to do kdialog and shit
[16:00] <shadeslayer> to what
[16:00] <shadeslayer> what
[16:00] <shadeslayer> ENOCONTEXT
[16:00] <apachelogger> im-config needing zenity
[16:00] <apachelogger> ohohoh
[16:00] <apachelogger> I think the im-config dep might need adjusting
[16:01] <apachelogger> because like, the package where kdialog lives is different
[16:01] <apachelogger> or does kdialog live in baseapps
[16:01] <apachelogger> !find kdialog
[16:01] <apachelogger> shadeslayer: we seeding baseapps-bin?
[16:02] <shadeslayer> ah hm I see
[16:02] <shadeslayer> apachelogger: no
[16:02] <shadeslayer> which is why we end up with libmir
[16:03] <apachelogger> polish that turd!
[16:04] <shadeslayer> such long emails
[16:04] <apachelogger> and here I thought I held back
[16:04] <shadeslayer> Riddell: mind adding kde-baseapps-bin to the seed ^^
[16:04] <shadeslayer> apachelogger: pft
[16:06] <Riddell> shadeslayer: plasma5 seed?
[16:06] <shadeslayer> yes
[16:08]  * Riddell makes it sew
[18:08] <genii> Did kubotu always do that?
[18:08] <yofel> not really, was added recently
[18:08] <genii> Ah, OK
[18:10] <apachelogger> clearly a contender for best bot on freenode
[18:19] <lordievader> Good evening.
[18:37] <kdeuser56> apachelogger: okay I just looked at the patches again: both patches are working, the only problem is, the destructor does not get called when pressing the close button in the application
[18:37] <apachelogger> space ships
[18:37] <kdeuser56> apachelogger: the close button in the titlebar works fine though
[18:37] <apachelogger> kdeuser56: that seems silly
[18:38] <apachelogger> but yeah, if one were to not do stuff in the dtor but rather in a global static that would not be a problem
[18:38] <kdeuser56> apachelogger: yeah it is silly
[18:38] <apachelogger> the static would get cleaned through the exit_handler so it always gets destructed
[18:38] <apachelogger> kdeuser56: I suspect there's is a parenting problem somewhere actually
[18:39] <apachelogger> which also should be resolved as that is a theoretical leak if the scope of the dialog is changed to be smaller than the application scope
[18:40] <kdeuser56> apachelogger: it seems to have happened by porting from KDialog
[18:42] <apachelogger> I blame shadeslayer
[18:42] <kdeuser56> apachelogger: what for?
[18:42] <apachelogger> he's drkonqi maintainer don't you know ;)
[18:43] <kdeuser56> apachelogger: yeah but not calling the destructor is an upstream but as it would not save the window size ...
[18:43] <kdeuser56> *bug
[18:44] <shadeslayer> wat
[18:44] <apachelogger> I doubt anyone cares about drkonqi window size :P
[18:44] <shadeslayer> I am not
[18:44] <apachelogger> it's not like you can play HD prn in there
[18:44] <apachelogger> shadeslayer: you moved it across repos, that makes you 300% more the maintainer than anyone else :P
[18:55] <kdeuser56> apachelogger: could we simply package the diffs and try to fix the destructor not being called or is that a nogo?
[18:56] <kdeuser56> *later
[18:58] <apachelogger> kdeuser56: if it is non-functional what is the point of packaging it
[18:58] <apachelogger> actuaaaaaaaaaaaally I was thinking about upstreaming the patches
[18:58] <apachelogger> at least the kcrash one
[19:00] <kdeuser56> apachelogger: it is functional, but not for the close button in the application
[19:00] <kdeuser56> apachelogger: so 50% ;-)
[19:01] <apachelogger> that's half broken then :P
[19:09] <kdeuser56> apachelogger: perfectionist :-)
[19:12] <apachelogger> kdeuser56: nono, the perfectionist in me says that it is a 100% broken because there is no formal test saying otherwise (:
[19:12] <kdeuser56> apachelogger: true ^^
[21:25] <shadeslayer> hurray
[21:25] <shadeslayer> Riddell: ubiquity-dm starts now
[21:25] <shadeslayer> Riddell: but no background
[21:25] <shadeslayer> ok shit
[21:25] <shadeslayer> something broke
[21:27] <shadeslayer> yeah
[21:27] <shadeslayer> Riddell: I broke it too much I think
[21:28] <apachelogger> lol
[21:28] <apachelogger> shadeslayer: wallpaper is likely because ubiquity wallpaper loading is shit and depends on the weird kde-wallpaper link we introduces as a workaround for shit being shit
[21:29] <shadeslayer> yeah
[21:29] <shadeslayer> so basically
[21:29] <shadeslayer> ubiquity-dm does not play nice with sddm
[21:29] <apachelogger> shadeslayer: how's that?
[21:29] <apachelogger> there's no interaction supposed to be is there?
[21:29] <shadeslayer> clicking on Try Kubuntu leads to a loop
[21:29] <shadeslayer> idk why, but you never see the desktop after hitting try Kubuntu
[21:29] <shadeslayer> launches ubiquity-dm after 2 minutes
[21:30] <shadeslayer> atleast sddm doesn't come up with text now
[21:34] <shadeslayer> anyway, something to look forward to tomorrow morning
[21:35] <shadeslayer> because my head hurts so bad right now :/
[21:35] <apachelogger> kubotu: order painkiller for shadeslayer
[21:35]  * kubotu slides awesome pain killing painkillers down the bar to shadeslayer.  Voilà your Bloody Mary.... muhahahahah :P
[23:18] <valorie> woah, so detailed
[23:23]  * valorie installs neon5 on the netbook to see how it runs on an atom
[23:25] <apachelogger> valorie: as I said ealier, kubotu  clearly is a contender for best bot on freenode ;)
[23:27] <valorie> I fully agree


[10:07] <Hmzaniac> mornin' people...
[10:07] <Hmzaniac> i just registred at launchpad, but when i click the validation link in my mail, i get a message that that part of launchpad isn't working yet.
[10:07] <Hmzaniac> what's up with that?
[10:23] <SteveA> Hmzaniac: that's not good.  I'll see if i can find out what's up.
[10:23] <SteveA> Hmzaniac: thanks for letting us know!
[10:23] <Hmzaniac> i already got it by registring through www.ubuntu.com
[10:23] <Hmzaniac> but it's still a bit odd for new users.
[10:23] <SteveA> sure is
[10:34] <Kinnison> Morning guys
[10:35] <Hmzaniac> morning
[12:19] <salgado> yo kiko
[01:19] <lifeless> SteveA: thats the production launchpad offering a link to foaf
[03:29] <GenghisKhan> hi all
[03:29] <GenghisKhan> i am trying to register in launchpad to send a translation
[03:29] <GenghisKhan> but when i click in the e-mail i receive
[03:30] <GenghisKhan> it says that that part of launchpad isn't ready yet
[03:33] <salgado> GenghisKhan, right now, you must register on www.ubuntu.com. the account you create there will be valid in launchpad too
[03:34] <GenghisKhan> ok
[03:34] <GenghisKhan> going to create it now, thanks
[08:41] <GenghisKhan> hello, i'm trying to translate in rosetta
[08:41] <GenghisKhan> i have the po file in my computer because i have translated wordpress on my own
[08:41] <GenghisKhan> how can i upload it?
[08:54] <GenghisKhan> hello
[08:54] <GenghisKhan> anyone knows how to upload a po translation into rosetta
[08:54] <GenghisKhan> ?


[02:02] <nhaines> Hello, hello.  It's meeting time.
[02:47] <lynorian> sorry for being so late
[02:48] <nhaines> lynorian: it's okay.  I ironically got called away as soon as I typed the above.


[01:32] <_kbulgrien> I have a web host that has an old python so only bzr 2.3.4 is usable.  Is there an easy way to know what versions of a plugin are compatible.  I'm interested in fast-export/import etc. as I made my repo too big and want to break it into smaller pieces.
[01:34] <AfC> _kbulgrien: do the work on your local system, then send the results back up to the server. Distributed.
[01:35] <_kbulgrien> Hmm.  Heh.  Yeah, new to the whole distributed thing.  Thanks for that thought.
[02:00] <_kbulgrien> hrm.  not having luck installing the plugin.
[02:01] <_kbulgrien> bzr plugins lists it, but when I try to use it I get bzr: ERROR: Unable to import library "fastimport": bzr-fastimport requires the fastimport python module
[02:03] <_kbulgrien> I guess that means my python installation needs something called fastimport.
[02:04] <_kbulgrien> fun. nothing in the distribution that looks like that.
[02:11] <AfC> _kbulgrien: it's the bzr-fastimport plugin on Debian/Ubuntu
[02:12] <_kbulgrien> I got that, but I think I need https://launchpad.net/python-fastimport too
[02:13] <AfC> _kbulgrien: you're obviously not on Ubuntu, or this would Just Work™
[02:14] <lifeless> _kbulgrien: how are you installing the plugin ?
[02:14] <_kbulgrien> i untarred the tarball and put it in ~/.bazaar/plugins/fastimport then ran python setup.py build_ext -i there.
[02:15] <_kbulgrien> bzr plugins shows it installed
[02:16] <_kbulgrien> Now I just found python-fastimport and have run python setup.py install for it... (working through it bit  by bit as I'm not a python guy)
[02:17] <_kbulgrien> I think I might have to set up PYTHONPATH now
[02:19] <lifeless> _kbulgrien: ok, so the usual way if you are using ubuntu etc is to do 'apt-get install bzr-fastimport' which will take care of all the dependencies for you.
[02:19] <lifeless> _kbulgrien: thats what AfC was referring to above.
[02:19] <lifeless> _kbulgrien: you might find docs in README or something in the source tree for bzr-fastimport documenting its dependencies.
[02:19] <_kbulgrien> Yeah, but I am not an ubuntu user
[02:20] <lifeless> _kbulgrien: ok
[02:20] <_kbulgrien> and apparently this distro does not have python-fastimport packaged or I do not have the right source set up for it.
[02:21] <lifeless> you might find 'pip install fastimport' works
[02:22]  * _kbulgrien isn't aware of pip
[02:23] <_kbulgrien> ok, got it.
[02:24] <_kbulgrien> did python setup.py install --user for python-fastimport
[02:24] <_kbulgrien> now bzr fast-export worked
[02:25] <_kbulgrien> this would be so much simpler with partial checkout... just sayin...
[02:25] <mgrandi> how would you do partial checkout with no .bzr directories in every folder
[02:26] <mgrandi> which makes me loathe svn
[02:26] <mgrandi> so much
[02:26] <_kbulgrien> well, I don't know the techie details... sorry... but I am so used to partial checkout I haven't figured how to emulate it in bzr yet.
[02:27] <_kbulgrien> I don't like svn either
[02:27] <mgrandi> i dont see the need for partial checkouts when you have branches
[02:27] <_kbulgrien> I probably would get abused if I said I was a cvs user
[02:27] <_kbulgrien> of course not, you're not me
[02:28] <_kbulgrien> everyone sees things from the way they learned to work.
[02:28] <mgrandi> we used to use svn with partial checkouts, but it was different projects inside a root folder managed by svn
[02:28] <mgrandi> which could of easily been split up into branches, but i dunno
[02:29] <_kbulgrien> I happen to find partial checkouts in cvs really powerful.  I have to learn a new way now, but since I only used cvs and svn enough to know I didn't want to migrate to it... well, I have to figure it out.
[02:29] <mgrandi> haha
[02:29] <mgrandi> my teacher told the students to use cvs
[02:29] <mgrandi> for the final, at the end he asked how many people lost data / had problems, nearly everyone raised their hands
[02:31] <_kbulgrien> I must be old and musty because I think cvs works fine as I use it all the time at work and find it easy compared to picking up distributed vcs, though bzr comes the closest to fitting the idea I think a vcs should work.
[02:31] <mgrandi> instead of partial checkouts, put the things you would partially checkout into separate branches/repos
[02:31] <_kbulgrien> we never loose data in cvs.  the reason we are on cvs is because we lost data on everything else.
[02:32] <_kbulgrien> but then that was maybe 15 years ago when cvs came to the shop.
[02:32] <mgrandi> and yes bzr is nice cause you don't have to be forced into one way of doing things
[02:32] <mgrandi> which i dont like about git
[02:32] <_kbulgrien> I tried git first.
[02:32] <mgrandi> git is nice with a pretty UI, which on osx there are plenty of
[02:32] <mgrandi> on windows, nopenopenopenopenope
[02:33] <mgrandi> the only thing ive seen is the github app for windows, which is using a c# library that produces/consumes git stuff, rather then actually using the git program itself
[02:33] <_kbulgrien> After two weeks of struggling, I ran into  wall.  In <1hr I had converted the git repo to bzr and was working without even looking in a manual.
[02:35] <_kbulgrien> only I find now that doing stuff like this is more complicated.  I also find bzr has some annoying bugs that seem like they will not get fixed.
[02:35] <mgrandi> like
[02:36] <_kbulgrien> https://bugs.launchpad.net/bzr/+bug/1012907
[02:37] <_kbulgrien> and similar file system permissions issues with command-line
[02:38] <mgrandi> ah yes.
[02:38] <mgrandi> i should take a look at that, that shouldn't be very hard to fix.....
[02:39] <mgrandi> its probably doing a 'os.walk()' without catching exceptions
[02:39] <_kbulgrien> well what is odd is that it goes digging around where it shouldn't go in the first place.
[02:39] <_kbulgrien> then if you have anything fail, the whole operation fails
[02:39] <_kbulgrien> cvs would baulk but would keep going
[02:39] <mgrandi> so what folder are you trying to actually monitor?
[02:39] <_kbulgrien> bzr upchucks and bails without doing anything
[02:41] <_kbulgrien> well in this use-case, I am controlling user directory type stuff so I can share my setups between machines... keep a reference setup to push/pull in and out off.
[02:41] <mgrandi> hmm yes
[02:41] <mgrandi> C:\Documents and Settings\kbulgrien\Favorites\yadayada.url
[02:41] <_kbulgrien> exactly
[02:41] <mgrandi> it went down a directory then went into all users
[02:41] <mgrandi> weird
[02:41] <mgrandi> i'll take a look at it, ive been meaning to actually write some code for bzr
[02:41] <_kbulgrien> In that case, I could go command-line and make it work.
[02:42] <_kbulgrien> But the problem is that I also deliberately control areas of the filesystem that have stuff I can't read too, and command-line is just hosed there.
[02:43]  * SamB_MacG5 doesn't remember noticing a lack of gitk on Windows ... wonders why?
[02:43] <mgrandi> git was written by linus, so it pretty much depends on the gnutils or whatever its called
[02:43] <mgrandi> _kbulgrien: where is the bzr repo on your disk?
[02:44] <_kbulgrien> C:/ for that scenario in that bug
[02:44] <mgrandi> ahh
[02:44] <SamB_MacG5> oh, right, that's because it works finefine
[02:44] <mgrandi> but then you go onto windows, you need cygwin
[02:44] <mgrandi> which sucks sometimes
[02:44] <_kbulgrien> oh... repo... no... the repo is somewhere else
[02:44] <SamB_MacG5> msys doesn't suck as slowly, I think
[02:45] <_kbulgrien> like bzr+ssh://linushost....
[02:45] <mgrandi> well the local copy of the repo
[02:45] <_kbulgrien> I use msys
[02:45] <mgrandi> cause a repo monitors things inside of it, so its in C:/ ?
[02:46] <_kbulgrien> no... repo is completely somewhere else... .bzr is in C:\
[02:46] <_kbulgrien> I answered wrong the first time
[02:46] <SamB_MacG5> As I recall, gitk on Windows actually looks a lot nicer than on OS X ...
[02:46] <mgrandi> well the thing is with bzr and other DVCS, if you have a 'branch ' of something, then you technically have the complete copy of the history
[02:46] <SamB_MacG5> something to do with the font metrics...
[02:46] <mgrandi> so you technically have the repo on C: and on your server
[02:46] <_kbulgrien> except in this case I used --lightweight or whatever
[02:46] <mgrandi> unlike svn where you don't have the history ever, its all on the server
[02:47] <mgrandi> ah
[02:47] <mgrandi> but its in C:/
[02:47] <mgrandi> so thats slightly better, i thought bzr was going up a directory
[02:47] <SamB_MacG5> mgrandi: that's what bzr-svn is for ;-)
[02:47] <mgrandi> and thats kind of bad
[02:47] <mgrandi> but like i said, its probably doing some sort of os.walk() without any error handling
[02:47] <mgrandi> i'll take a look at it, this seems like a nice place to start~
[02:48] <_kbulgrien> I also don't like that bzr status doesn't allow --no-recurse
[02:48] <mgrandi> well, it makes sense when you think about it...
[02:48] <mgrandi> the whole point is that stuff under the repo folder is monitored
[02:49] <_kbulgrien> well when, say I am working on a webserver, I lots of times don't give a rip about status anywhere except where I am, and all the boatload of status is annoying
[02:49] <mgrandi> you can probably do bzr status --versioned
[02:49] <_kbulgrien> hm...
[02:50] <mgrandi> you have a weird case where your repo is your entire hard drive
[02:50] <_kbulgrien> ok... will have to try to remember that
[02:50] <mgrandi> but you are only versioning certain parts
[02:50] <mgrandi> usually everything (like in a code project) in the folder wants to be versioned unless you specifically ignore it
[02:50] <mgrandi> but yeah, use --versioned, will only show files that are actually versioned instead of all those ? ones
[02:51] <_kbulgrien> well  I know my grief is that I want to do version control for things that aren't typical software dev, but I think version control transcends software dev...
[02:51] <mgrandi> but no recurse wouldn't make sense, cause where would it not recurse?  =P
[02:51] <mgrandi> well bzr/git/whatever works fine for this, but yeah have to do some things a little different
[02:51] <mgrandi> the same thing with dropbox, everything in the dropbox folder gets uploaded
[02:52] <_kbulgrien> well, I don't know what you are saying because cd ~/public_html; bzr status --no-recurse makes sense to me.
[02:52] <mgrandi> but if there are files in /public_html/stuff and /public_html/stuff2, it has to enter those folders
[02:53] <_kbulgrien> why does it have to?
[02:53] <mgrandi> but no recurse makes me think that it just only goes into public_html
[02:53] <mgrandi> i kinda get what you are saying,
[02:53] <_kbulgrien> All I care about most of the time is the folder where I am, and I don't really need to know status for the whole sub-tree all the time
[02:53] <mgrandi> kind of like ls
[02:54] <_kbulgrien> Sure, at some point I care, but not while I'm working locally in that folder only.
[02:54] <_kbulgrien> I use bzr status . all the time to not get history outside a sub-tree.  It's the same principle.
[02:54] <mgrandi> have you filed a bug report on this yet? (just so people remember)
[02:54] <_kbulgrien> Not yet.
[02:55] <_kbulgrien> I'm still getting used to things and the annoyance pressure hasn't built up to file a bug level yet.
[02:55] <mgrandi> should and link it, again shouldn't be that hard
[02:55] <mgrandi> to add --no-recurse
[02:58] <_kbulgrien> well  I guess I'm not sure if bzr status is the only thing that doesn't have --no-recurse that I wish had it... so part of the delay is to see if there are other commands that get annoying because of no --no-recurse.
[02:58] <mgrandi> might as well start with the status one =P
[02:59] <_kbulgrien> otoh bzr status not having it _is_ the most annoying.
[02:59] <mgrandi> i'll look into it and see if its easy
[02:59] <_kbulgrien> I guess I'm skeptical that anyone cares these days.
[03:00] <mgrandi> open source software for you =P
[03:00] <_kbulgrien> And I feel since I don't know python that people think I'm just whining... you know... submit a patch then doofus...
[03:00] <mgrandi> hehe
[03:00] <_kbulgrien> but learning python to patch a vcs is not something done lightly
[03:01] <_kbulgrien> well, really, its not the learning python part... its learning the bzr source part.
[03:02] <mgrandi> yes
[03:02] <mgrandi> people have discussed that bzr and any vcs is hard cause of complex data structures that really can't fail ever =P
[03:02] <mgrandi> but if its just command stuff like this, i feel i can take a stab at it
[03:02] <_kbulgrien> I code in so many languages and scripting languages that its really not about learning python.
[03:04] <_kbulgrien> This is the other bug that kills me https://bugs.launchpad.net/bzr/+bug/964338
[03:04] <_kbulgrien> heh, I see bug listed for bzr revert needs --no-recurse
[03:04] <_kbulgrien> Ok, so maybe I add one
[03:05] <mgrandi> yeah, it seems that bzr should not be failing on these
[03:38] <_kbulgrien> ok, its been did
[03:40] <mgrandi> link?
[03:41] <_kbulgrien> https://bugs.launchpad.net/bzr/+bug/1053778
[03:41] <mgrandi> ok
[03:41] <mgrandi> i;ll take a look at it
[03:41] <mgrandi> but now need to go, later!
[05:08] <_kbulgrien> Hmm. well, I guess that went ok.  Looks like I broke apart the repository the way I intended out, though I went about removing the top-level directory in a harder way than was necessary... it turns out fast-import-filter public_html/ with the trailing slash is the right way to prune top-level folder levels out of the fast-export.
[05:09] <_kbulgrien> I guess the grammar on that was bad... I meant ...specifying extra path levels is the way to prune...
[07:28] <mgz> morning
[07:28] <emeric_> moin moin
[09:58] <Ovocean> Hi! I'm quite new to bzr and I have come across a situation I don't know how to deal with:
[09:58] <Ovocean> I have uploaded a branch for Lutris on Launchpad, it's been merged with the main branch. But I had done a couple commits to my local branch before the merge, and didn't upload them yet. Now I need to get/merge back the last version of the main branch (rev 163) and have my last commits (rev 176 & 177 on my local branch) put on top of that as rev 164 and 165. How would I do that?
[10:08] <fullermd> Why do you want to?
[10:10] <Ovocean> To be able to continue to work on my branch, and not loose my last commits. What's the normal way to do this?
[10:11] <fullermd> Just merge trunk and move on.
[10:24] <Ovocean> Right, but then the rev numbering doesn't match the main branch. It doesn't matter? Doesn't look clean to me.
[10:24] <fullermd> Doesn't matter.
[10:25] <Ovocean> Fine then. Thanks for the help
[10:25] <fullermd> Only thing that matters in merging and suchlike is what revs are present where.  revnos just relate to the shape of the local history.
[10:26] <Ovocean> Ok
[14:07] <kiretooo> hello :)
[14:08] <kiretooo> what means that:
[14:08] <kiretooo> You have not informed bzr of your Launchpad ID, and you must do this to
[14:08] <kiretooo> write to Launchpad or access private data.  See "bzr help launchpad-login".
[14:27] <jelmer> kiretoo: exacyl
[14:27] <jelmer> kiretoo: exactly that. you have not told bzr what your username on launchpad is yet
[14:38] <kiretooo> jelmer, i've already has a username
[14:40] <jelmer> kiretooo: does bzr know about it? have you run bzr lp-login?
[14:42] <kiretooo> i have to add some ssh keys ?
[15:24] <SamB_MacG5> kiretooo: yeah, you need to set up an ssh key on your system and paste the public key into a box in your launchpad profile/configuration
[16:54] <SamB_MacG5> hmm. Bzr 2.3's lsprof cachegrind/callgrind output needs work :-(
[17:14] <vila> SamB_MacG5: have you tried getting a more recent python on your G5 ?
[17:16] <SamB_MacG5> I suppose I could, though also getting the extra batteries might be a bit of a pain...
[17:16] <vila> SamB_MacG5: easy_install ?
[17:17] <vila> SamB_MacG5: that was just a thought, no idea how complex it can turn out
[17:18] <vila> SamB_MacG5: on the other hand, if you can get up to 2.7, you should be good to go for quite a while
[17:18] <SamB_MacG5> would it be reasonably easy to build an installer for that, is another worry
[17:19] <SamB_MacG5> (a bzr installer, I mean)
[17:19] <SamB_MacG5> oh, and another complication would be that 10.5's xcode only comes with SVN 1.4
[17:23] <SamB_MacG5> oh, I was thinking of trying to build from Apple's python sources...
[18:00] <vila> SamB_MacG5: I was thinkinh more about http://python.org/ftp/python/2.7.3/python-2.7.3-macosx10.3.dmg
[18:01] <vila> jelmer: is bzr-svn trunk compatible with svn-1.4 ?
[18:02] <vila> SamB_MacG5: well, you could start with a reduced number of plugins (all is defined in config.py right?) ?
[18:04] <vila> SamB_MacG5: http://python.org/download/ says the above is for 10.3 through 10.6
[18:46] <SamB_MacG5> vila: I suppose bzr *probably* doesn't have much use for apple's extra pack-ins ...
[22:28] <vila> SamB_MacG5: sry was afk, extra pack-ins as in python modules added by apple ? In this case, I'm pretty sure the answer is yes. The only one I can think that may use apple specific stuff is for the keyring (sry, can't remember the plugin name) and I seem to recall it doesn't use any apple-specific python stuff
[22:30] <SamB_MacG5> I mean Python extensions/libraries that Apple has bundled into Python, though upstream (and in most distros) they're packaged separately
[22:30] <SamB_MacG5> er. I should have said "into the Python framework"
[22:32] <SamB_MacG5> basically, the stuff in /System/Library/Frameworks/Python.framework/Versions/2.5/Extras
[23:21] <vila> SamB_MacG5: right, I'm pretty sure bzr uses nothing from there (well, I'm sure for the core, pretty sure for the plugins)


[02:37] <jose> pleia2: ok, cool, I don't remember if I told you (don't have logging enabled here) but my laptop screen broke
[02:37] <jose> I have no PC to work on until Tuesday, supposedly Dell will come and fix it by then
[04:18] <pleia2> jose: eep, good luck!
[16:19] <pleia2> Welcome to the Ubuntu Weekly Newsletter. This is issue #348 for the week December 16 - 22, 2013 https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue348
[19:47] <Unit193> Explore our sites http://askubuntu.com//stackexchange.com/sites


[02:23] <NickW> So, I'm sure many others have asked, but any idea what's going on with CentOS8 support? The current MAAS 2.8 edge snap still has curtin 19.3-26-g82f23e3d-0ubuntu1~18.04.1 which doesn't support it
[02:24] <NickW> Which basically means that rolling CentOS8 with MAAS is impossible on a 20.04 host, since the maas debs are outdated/won't install
[02:25] <mup> Bug #1865844 changed: Add KVM/LXD host id to machine payload in WS API <MAAS:Invalid by ltrager> <https://launchpad.net/bugs/1865844>
[14:20] <mup> Bug #1877126 opened: default KVM pod RAM (1GB) is not enough to commission <MAAS:New> <https://launchpad.net/bugs/1877126>
[15:44] <mup> Bug #1877140 opened: better UX to validate KVM host addresses <MAAS:New> <https://launchpad.net/bugs/1877140>
[15:53] <alejandrosg_> folks, how can I "rescan" a machine to detect new hardware (added RAM, new disk) in MaaS?
[17:08] <mup> Bug #1877158 opened: Static routes in subnet are ignored in multihomed deployments with policy based routing <sts> <MAAS:New> <https://launchpad.net/bugs/1877158>
[21:03] <mup> Bug #1877186 opened: pod compose permission denied if /var/lib/virt has r-x disabled for others <cdo-qa> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1877186>


[04:30] <Jesse_V> does Launchpad support builds for Debian or Fedora? Is it only specific to Ubuntu?
[04:31] <Jesse_V> nm
[04:31] <wgrant> Jesse_V: PPAs only build for Ubuntu today.
[04:31] <Jesse_V> ok, thanks
[04:32] <wgrant> We'd like to support Debian too, but build resources are at capacity with just Ubunut.
[04:32] <Jesse_V> is there anyway to have Launchpad build for more than one distro, or do I have to change my /debian/changelog file and reupload every time?
[04:32] <Jesse_V> ah ok
[04:32] <Jesse_V> thanks
[04:32] <wgrant> You have to reupload for each release, or copy the source and binaries between releases
[04:33] <wgrant> The latter won't work for everything; you'll need to check if each package needs a rebuild.
[04:33] <Jesse_V> I'm working with my own project that isn't present in Ubuntu/Debian/Linux. It's new software.
[04:34] <Jesse_V> what determines if it can be compatible across distros? It's an OpenGL/C++ project.
[04:35] <Jesse_V> I don't fully understand binary compatibility in Linux
[04:45] <wgrant> Jesse_V: Shared library SONAMEs are a good start, if the libraries you use are fairly sane.
[04:47] <Jesse_V> Glew and Freeglut are the only ones
[04:47] <Jesse_V> what's SONAME?
[04:48] <wgrant> A library version number that indicates ABI compatibility.
[04:50] <Jesse_V> the freeglut3 package has the version number 2.6.0-4ubuntu1 for Quantal.
[04:51] <Jesse_V> so how can I tell ABI compatibility from that information?
[04:51] <Jesse_V> sorry, I'm on a bit of steep learning curve here...
[04:52] <wgrant> The 3 there is usually the soname version.
[04:52] <wgrant> Anything built against freeglut3 should run against any later version of freeglut3.
[04:52] <Jesse_V> oh
[04:52] <wgrant> If they make a change that breaks backwards compatibility, it should become freeglut4.
[04:52] <Jesse_V> yeah I've always wondered about that
[04:52] <Jesse_V> thanks
[04:53] <Jesse_V> I've always thought "why don't they just update the package version?" now I know why
[04:53] <wgrant> Note that building for freeglut3 in saucy and running against quantal's might not work.
[04:53] <wgrant> Because you can add new interfaces without breaking ABI
[04:53] <wgrant> You just can't change old one.
[04:53] <Jesse_V> so what's your recommendation then?
[04:53] <Jesse_V> change /debian/changelog and then reupload?
[04:54] <Jesse_V> wgrant: I've been working on a script to automate the build process for me: https://github.com/Jesse-V/Folding-Atomata/blob/master/src/pushPackage.sh
[04:55] <Jesse_V> so I guess my plan then is to change /debian/changelog and then rerun the script. Would that work?
[04:55] <wgrant> Jesse_V: quantal->saucy has freeglut3 and libglew1.8, so you could upload a package to quantal, copy it to raring and saucy, and it would probably work fine.
[04:56] <Jesse_V> sorry, but how do you copy it without having Launchpad rebuild it?
[04:56] <Jesse_V> I'm trying to understand the order of operations here
[04:57] <wgrant> Jesse_V: Upload to quantal, wait for it to build, then use the "Copy packages" page to copy to raring and saucy.
[04:57] <Jesse_V> ahh
[04:58] <Jesse_V> and if that doesn't work, then I'll resort to uploading for each distro, right?
[04:58] <Jesse_V> wait, can I build for Saucy, even though it's not actually out yet?
[04:59] <wgrant> You can if you want.
[04:59] <wgrant> PPAs support Saucy from day 1 of development.
[04:59] <wgrant> Because they're used for development :)
[04:59] <Jesse_V> ah
[05:03] <Jesse_V> thanks for the help, I think I've got it better figured out now :)
[06:35] <Jesse_V> hi it's me again
[06:36] <Jesse_V> wgrant, maybe you can help me again, or someone else if you're not around
[06:36] <Jesse_V> how can I get Launchpad to verify my digital signature?
[06:36] <Jesse_V> I get:
[06:36] <Jesse_V> gpgv: Signature made Fri Aug 23 06:22:11 2013 UTC using RSA key ID C20BEC80
[06:36] <Jesse_V> gpgv: Can't check signature: public key not found
[06:36] <Jesse_V> in the build log
[06:36] <Jesse_V> how can I get it to import my OpenPGP key?
[06:37] <Jesse_V> and wgrant, I found the "copy package" feature, thanks for pointing that out :)
[06:38] <wgrant> Jesse_V: In the build log? That warning is normal.
[06:38] <Jesse_V> yes ok
[06:38] <Jesse_V> but shouldn't Launchpad verify that?
[06:39] <Jesse_V> it looks like it could, if it had the public key, which it can get because it's on the Ubuntu keyserver
[06:39] <wgrant> It's checked on upload.
[06:39] <Jesse_V> ah ok
[06:39] <wgrant> It's trusted once it's in Launchpad, so the buildds don't have to shuffle around keys etc.
[06:39] <Jesse_V> so no one can upload to my PPA, except the owner of the private key, right?
[06:39] <Jesse_V> ok
[06:40] <wgrant> Right.
[06:43] <Jesse_V> thanks wgrant for the help
[06:44] <Jesse_V> my package is so close to building successfully: it fails right at the "make install" part... :)
[06:44] <wgrant> Heh
[06:44] <wgrant> Nearly there!
[06:44] <Jesse_V> I know
[06:45] <Jesse_V> it makes all of this progress and then dies because I forgot to include certain files in /debian so that they'd be sent to Launchpad. So it's all my fault...
[06:45] <Jesse_V> https://launchpadlibrarian.net/148223219/buildlog_ubuntu-quantal-amd64.foldingatomata_0.4.2_FAILEDTOBUILD.txt.gz
[06:45] <Jesse_V> fixed easily enough though
[06:56] <Jesse_V> YES
[06:57] <Jesse_V> IT BUILT!
[06:57] <Jesse_V> thanks wgrant
[06:57] <Jesse_V> :)
[06:57] <wgrant> Excellent :)
[06:57] <Jesse_V> I'm so happy right now
[11:45] <toabctl> hi
[11:46] <toabctl> is it possible to delete ppa dependencies?
[11:46] <toabctl> I just want to know that before I add a dependency to one of my ppas .
[11:47] <jpds> toabctl: Try it on staging.launchpad.net.
[12:20] <cjohnston> StevenK: wgrant Ursinha, thanks for figuring out the bug that caused status to get upset and taking care of it :-)
[16:02] <Logan_> Is it just me, or is Launchpad not showing the updated versions of Ubuntu packages?
[16:04] <LoganCloud> ^ Still here.
[16:32] <dobey> Logan_: what do you mean it isn't showing them?
[16:38] <qman__work_> Hi, I'm having a problem trying to backport a package (shibboleth 2.5.2) from saucy to precise, and it says "dependency wait": https://launchpad.net/~cs-cracker/+archive/shibboleth-ppa/+build/4895264  What, if anything, do I need to do to move this forward? I used the backportpackage tool to create the build.
[16:47] <dobey> you need the missing dependencies
[16:48] <dobey> as a newer package it likely requires newer versions of some of its dependencies that are also in saucy, but not in precise. or it may require new ones that do not exist at all in precise.
[16:48] <qman__work_> so would I have to backport those separately then?
[16:48] <dobey> yes
[16:49] <qman__work_> ok, thanks, I'll look into that
[18:02] <shadej> hi guys
[18:02] <shadej> new to launchpad
[18:03] <shadej> I want to work on ubuntu localization where to start?
[18:03] <shadej> I have joined the team of my lang now
[18:04] <dobey> the irc channel for your lang, or #ubuntu-i18n would be a better place to get help
[18:59] <Logan_> dobey: Lemme rephrase, because I think I see the actual issue now - the proposed repositories aren't showing up on the source package pages anymore.
[19:01] <Logan_> See, for example: https://launchpad.net/ubuntu/+source/libzrtpcpp
[19:01] <Logan_> It should show 2.3.4-1 in saucy-proposed, but it just shows what's in release.
[19:09] <Munchor> Hi
[19:09] <Munchor> >Licences:
[19:09] <Munchor> Where does Launchpad read the License from?
[19:09] <Munchor> oh wait, I can change details and have it changed, nvm
[19:10] <dobey> Logan_: i'm not sure that has anything to do with launchpad itself. things that have been pusehd to the release pocket though show up as in release instead, and the proposed one no longer shows up. maybe it was rejected from proposed and therefore is not shown any more. better to ask in #ubuntu-devel maybe
[19:13] <OvenWerks> I have aproblem with my launchpad account. When I push to a branch, the revision just shows my name/email instead of a link to my launchpad home page. This used to work, but stopped. as an example see: https://code.launchpad.net/~ubuntustudio-dev/ubuntustudio-default-settings/UbuntuStudio
[19:14] <OvenWerks> I have tried setting bzr lplogin etc. with no luck
[19:14] <OvenWerks> pl id = len-ovenwerks BTW
[19:16] <dobey> you have to commit using an e-mail that is listed on your launchpad account
[19:17] <OvenWerks> I am doing tht
[19:19] <OvenWerks> dobey: I am using the same email as my lp account
[19:19] <dobey> what is your lp username?
[19:19] <OvenWerks> len-ovenwerks
[19:20] <dobey> "Committer: len at ovenwerks"
[19:20] <dobey> not exactly :)
[19:21] <OvenWerks> I have not entered that anywhere dobey where would I set that up?
[19:22] <dobey> are you doing bzr commit --author "Foo<EMAIL_ADDRESS>? or what? how did you configure your commit email?
[19:23] <OvenWerks> $ bzr whoami
[19:23] <OvenWerks> Len Ovens<EMAIL_ADDRESS>[19:23] <OvenWerks> $ echo $DEBEMAIL
[19:23] <OvenWerks><EMAIL_ADDRESS>[19:24] <dobey> you are missing the < > around your e-mail
[19:24] <dobey> so change your bzr whoami
[19:24] <dobey> should be "Name <email>"
[19:24] <dobey> or just email
[19:26] <OvenWerks> dobey: like this: $ bzr whoami
[19:26] <OvenWerks> Len Ovens<EMAIL_ADDRESS>[19:26] <OvenWerks> Will try again.
[19:28] <dobey> yes
[19:39] <OvenWerks> dobey: Thank you that works, I guess I made that mistake after I reinstalled my machine.
[22:09] <g0twig> do you accept lintian overrides for PPA packages
[22:13] <g0twig> trism: hey


[02:04] <attrapereves> Hi, my sound is not working. Any tips?
[08:21] <jamesliu> hi
[08:22] <jamesliu> I'd like to ask a simple question
[08:22] <jamesliu> Could someone let me know how to know other people 's host name by ip
[08:22] <jamesliu> which command should be used
[08:36] <hyde> Does anybody here have an idea when Qt5 of 14.04 is going to get upgraded?
[08:41] <genii> !info libqt5core5 trusty
[08:41] <genii> !info libqt5core5 trusty-proposed
[08:42] <genii> Hm
[08:42] <genii> !info libqt5core5 kubuntu-experimental
[08:54] <yofel> hyde: probably in ~2 days... if bug 1278329 can be trusted
[08:58] <hyde> yofel: great! Then I'll see if that happens and not do Qt build yet this week
[09:09] <hyde> related, is it going to be Qt5.2 for sure, or is there a chance of Qt5.3? I suppose not, since final release of 5.3 seems to scheduled for 29th of April... Is Qt5 something which is likely to have minor version bumped for 14.04.1?
[09:26] <swizgard> jamesliu: this is reverse-dns, isn't it? so "dig" maybe?
[10:18] <Volkodav> So hoe does this beta behave so far?
[10:52] <DJones> Volkodav: Only been using since the weekend, but so far its been good, installed with no issues on a new laptop, dual intel/nvidia graphics worked perfectly
[10:53] <Volkodav> good
[11:54] <BluesKaj> Hey folks
[13:29] <Dry_Lips> Hi... What do you guys think of Trusty at the present time?
[13:30] <k1l> *thumb_up*
[13:34] <philinux> Dry_Lips;~ running smooth here on an acer 1410 64 bit install
[13:35] <k1l> Dry_Lips: but keep in mind. if you need to ask for stability dont run dev releases
[13:36] <philinux> k1l;~ +1 this acer is not my main machine. Desktop is running 13.10
[13:37] <k1l> i am running it on my main machine. but i got more than enough backup machines for the time when murphy strikes again
[13:40] <DJones> Dry_Lips: I did a fresh install on a new laptop at the weekend, its been good so far
[13:40] <Dry_Lips> Good to hear, guys
[13:40] <Dry_Lips> You are all running vanilla Ubuntu, or some of the derivatives?
[13:45] <philinux> Dry_Lips;~ me is vanilla 64 bit Ubuntu-  unity is much improved
[13:45] <Dry_Lips> Right...
[13:46] <philinux> Dry_Lips;~ you can see the main changes here > http://ubuntuforums.org/showthread.php?t=2184706
[13:46] <Dry_Lips> Ah, cheers mate! :)
[13:46] <Dry_Lips> I'll check it out
[13:48] <philinux> Dry_Lips;~ just had 160 meg update which included new kernel - off for a reboot biab
[13:52] <philinux> Dry_Lips;~ booted fine with new kernel. 3.13.0-15
[14:10] <Dry_Lips> nice one, philinux! :)
[14:14] <philinux> Dry_Lips;~ anything else you need know?
[14:14] <DJones> philinux: Hopefully I'll get the same myself, just got fears that nvidia-prime might make a mess
[14:15] <xsacha> oh there's a new one?
[14:15] <xsacha> i found 3.13.0-14 quite buggy so i'm using -12
[14:15] <Dry_Lips> philinux: thanks, but not as I can think of...
[14:18] <philinux> Dry_Lips;~ http://www.webupd8.org/2013/12/more-work-to-support-nvidia-optimus.html
[14:20] <philinux> apt-cache policy nvidia-prime Candidate: 0.5.7
[14:21] <philinux> Dry_Lips;~ but do not enable proposed repo though. that info above references it but all in main repo now
[14:21] <xsacha> is there an amd-prime?
[14:22] <philinux> xsacha;~ no - unless the package has a different name
[14:23] <xsacha> oh is it because the catalyst driver has native support for switchable graphics?
[14:23] <xsacha> it doesn't support prime though (except with opensource driver)
[14:24] <philinux> xsacha;~ sorry dont know about catalyst
[14:24] <xsacha> it's ok, i dont know much about it either since it refuses to support my video card (5650m)
[14:25] <xsacha> tells me it doesn't support muxless switchable graphics, yet opensource can do it fine
[14:58] <zukeprime> Xubuntu 14.04 Beta 1, Terminal.  Tilde key produces a dash.  UTF-8 encoding set.  I've tested in normal terminal and drop-down.  Also tested in stock ubuntu 14.04, doesn't do it.  Can someone else confirm?
[14:59] <xsacha> zukeprime: isn't that based on keyboard language?
[15:00] <zukeprime> set to US English. Checked, and double checked.
[15:00] <zukeprime> Like I said, it's working fine in normal Ubuntu (Unity)...driving me crazy.
[15:01] <zukeprime> It has to be a setting somewhere, I want to confirm before I waste time filing a bug report
[15:03] <zukeprime> also, I went through the entire keyboard to confirm my layout...just to be sure...the tilde key is the only thing not working properly.
[15:03] <xsacha> are you sure it's not appearing as a tilde?
[15:03] <xsacha> maybe just bad font
[15:03] <xsacha> or bad font size
[15:04] <zukeprime> ahh...good point.  let me check
[15:04] <xsacha> it doesn't function as a tilde?
[15:04] <zukeprime> awesome!  That did it.
[15:04] <xsacha> ah good. i thought you would have tried ls ~ already, but just making sure :)
[15:05] <zukeprime> I had it set to Courier 10 Pitch
[15:05] <xsacha> yes courier can't show tilde
[15:05] <xsacha> known issue
[15:05] <xsacha> long time
[15:05] <zukeprime> cool thanks xsacha.  Had me worried
[15:05] <xsacha> see: http://ubuntuforums.org/showthread.php?t=989458
[15:05] <zukeprime> thx, will do
[16:49] <bodie_> does it look like 14.04 will have the newer Unity by the 13th ui freeze?
[16:50] <k1l> newer unity?
[16:52] <bodie_> I thought I read an article about the latest alpha release not having a newer version of Unity which was hoped to be in the 14.04 LTS release
[16:54] <k1l> i think you mean unity8 which works on MIR. that will not be standard in 14.04. but you could install it if you want to. but keep in mind its still alpha on the desktop
[16:54] <bodie_> ah, ok :)
[16:56] <bodie_> looks interesting, wasn't aware of mir
[16:57] <bodie_> do you think it might go into 14.10?
[16:58] <k1l> it will be in 14.04. but it will not become standard untill its stable enough. if that is 14.10 i dont know
[16:58] <bodie_> ah, I see
[16:58] <bodie_> cool!
[16:58] <bodie_> do you know if the alpha is running it?
[16:58] <bodie_> the 14.04 alpha that is
[16:59] <k1l> yes, but i could not even start unity8 when i was trying
[17:18] <bodie_> does anyone know if there are any special considerations I need to take when installing 14.04 in UEFI mode?
[17:18] <bodie_> I'm following this guide: https://help.ubuntu.com/community/UEFI
[18:45] <DJones> bodie_: I just installed on a new laptop with uefi, all I did was disable secure boot and then install
[18:47] <DJones> bodie_: My process was to shrink my win 8 partion with windows, then reboot with a 14.04 usb stick, partion into the free space previously created, with /, /swap and /home, then install
[19:16] <bodie_> hm, okay.  thanks DJones.  perhaps the issue I'm having is unrelated to UEFI.  I don't think my sony laptop exactly follows the UEFI spec
[19:18] <bodie_> it's this thing where you have to rename the boot EFI application to bootx64.efi I think
[19:19] <bodie_> a la http://askubuntu.com/questions/150174/sony-vaio-with-insyde-h2o-efi-bios-will-not-boot-into-grub-efi
[20:10] <bodie_> mkay.....  grub fired up OK, but after selecting the ubuntu entry, i'm sitting here on a purple screen
[20:11] <bodie_> can't ctrl+alt+1/2/3/4 etc to other terminals
[20:11] <bodie_> oh
[20:11] <bodie_> it just came up... just was taking forever
[20:11] <bodie_> O_O
[20:37] <hggdh> just found mediascanner.scope generated a 179G log file. Anybody experienced something like that?
[20:54] <oscalation> is 14.04 going to have startup sounds enabled?
[21:00] <Turingi> Trusty Targ 14.04, has anyone else had graphical glitches with the liveDVD with the latest iso build?
[21:05] <wallzero> How can I change the color scheme in Geany 1.23.1?
[21:07] <minimec> Turingi: I have some 'flickering' using some vmware images with 14.04 with my INtel HD4000. I guess this has nothing to do with your problem.
[21:07] <Turingi> minimec: I have glitches that make it impossible to install the system
[21:07] <Turingi> minimec: using AMD HD 7750
[21:12] <minimec> Turingi: Have you tried to use 'f6' Other Options and set 'nomodeset'?
[21:14] <Turingi> minimec: will F6 enter into a text mode?
[21:14] <Turingi> minimec: and what does nomodeset do and to what?
[21:16] <minimec> Turingi: Nope. It will give you a menu. It will disable all driver modes. If that is working, you can enable the 'restricted AMD driver' after the installation of ubuntu. http://ubuntuforums.org/showthread.php?t=1613132
[21:17] <Turingi> minimec: I am afraid it'll have the same issues post-install
[21:20] <minimec> Turingi: If you can install the system like that, you should be able to enable the 'dedicated AMD GPU driver' for your card afterwards.
[21:21] <minimec> Turingi: Check 'Additional Drivers' in 'Software & Updates' after installation.
[21:29] <Turingi> minimec: alright F6 does not fix the graphical glitches
[21:30] <Turingi> minimec: to be more precise, it's a glitch from the liveDVD boot, not a post-install thing
[21:30] <minimec> Turingi: Ok. So I cannot help you further... Sorry.
[23:01] <ulkesh> I'm looking into upgrading from Ubuntu 13.10 to 14.04 and I noticed some bug reports showing that the upgrade is failing (one due to some tcltk dependency issue).  Has anyone successfully upgraded from 13.10 to 14.04 in the past day or so?
[23:24] <bodie_> hmmm.... after selecting the boot entry in GRUB, my laptop just sits at a purple screen...  can't switch terminals.  where should I start?
[23:24] <bodie_> I was previously able to boot
[23:57] <minimec> ulkesh: Late answer... I had a seamless update experience from 13.10 -> 14.04