[00:48] <surjikal> Hey guys, for some reason, my sshd service isn't starting on boot. I see no errors in syslog. I'm able to mount the server's drive onto another ubuntu distro. Is there a way I can make sshd boot on startup by modifying some config file? Alternatively, can I somehow chroot into my mounted drive?
[00:51] <sarnold> surjikal: check /etc/init/ssh.conf, /etc/init/ssh.conf.override, /etc/default/ssh, /etc/ssh/sshd_config
[00:52] <sarnold> surjikal: you can chroot into the filesystem with ... drum roll ... cd /path/mounted/filesystem ; chroot .
[00:53] <surjikal> sarnold, would I be able to start sshd from the chroot?
[00:54] <sarnold> surjikal: I would expect so, unless your system already has an sshd bound to port 22...
[00:55] <sarnold> surjikal: upstart has some chroot awareness, it might be worth reading about that a bit before just starting sshd..
[02:47] <shauno> what am I missing here?  quantum is complaining I haven't specified an sql_connection, but it's right where I expect it to be; http://paste.ubuntu.com/5666366/
[02:53] <three18ti> shauno, I don't know the application you'
[02:54] <three18ti> re trying to configure
[02:54] <three18ti> but the sql_connection
[02:54] <three18ti> sql_connection =<EMAIL_ADDRESS>[02:54] <three18ti> doesn't look right to me.
[02:54] <three18ti> where is the config manual?
[02:56] <shauno> http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_network.html  is for a different plugin (ovs), but the same format is used for sql_connection throughout
[02:56] <three18ti> I <3 ovs
[02:57] <three18ti> well... it's identical to the manual so... there goes that line of thinking.
[02:59] <shauno> this "Option 'sql_connection' not specified in any config file" feels like it's not even getting that far, and this config file isn't being parsed
[03:03] <resno> i have a python process that should always run. if it fails, i want to reboot it. i remember there being an app to handle it... any suggestions
[03:03] <resno> sysserv or something...?
[03:05] <resno> daemontools with supervise?
[03:13] <resno> hmm, theres monit too
[03:28] <BlackWeb> I'm currently using Ubuntu Server 12.04, Which it use to WOL, But then did a update and it killed the WOL function, Which I have the correct entries in /etc/rc.local & ethtool eth0 shows that its enabled but still nothing Does anyone have any IDeas?
[06:12] <dfo1981> anyone who can help me with setting up vsftpd ?
[06:12] <dfo1981> its not so much the setting up vsftpd, its more the user/permission part of logging into vsftpd
[09:36] <yolanda> Daviey, jamespage, i have several approved MPs for dep-8-tests
[09:36] <Daviey> yolanda: super, fancy showing me the first one?
[09:37] <yolanda> https://code.launchpad.net/~yolanda.robla/ubuntu/saucy/postfix/dep-8-tests/+merge/161610
[09:38] <Enich> I was looking for a solution to unattended installations of mysql and i came across this..  http://stackoverflow.com/questions/7739645/install-mysql-on-ubuntu-without-password-prompt    My question is this.     in question 2, when the person does the sudo debconf ....<<< '.... password'   will that password stay in the debconf-set-selections permenantly or is it a temporary thing.  It might be a stupid question, but i would rather ask then messing stuff
[09:38] <Enich>  up ..  i was thiking of using the third answer, with the noninteractive, and then instead of doing a mysqladmin thing, then put in the hashed password directly instead of the changepassword option with mysqladmin
[09:40] <yolanda> Daviey, i submitted all the changes to debian for the approved MP, does it make sense to wait until they are included, or do we incorporate in our packages?
[09:41] <rbasak> Enich: permanantely, if I understand your question correctly. This is the same as if you had entered in the password by hand on installation. Unless there's a bug, the password is held so that only root can read it, though. This is the same as if you had created a ~root/.my.cnf manually. I think the package might do that anyway?
[09:41] <Daviey> yolanda: I think it's reasonable for us to do it in parallel with Debian on most packages
[09:41] <yolanda> ok, so there is the MP for postfix
[09:43] <Daviey> jodh: Are you sponsoring https://code.launchpad.net/~yolanda.robla/ubuntu/saucy/postfix/dep-8-tests/+merge/161610 ?
[09:44] <hXm> btw reading the log i got this http://pastebin.com/TgDCVXPf
[09:44] <hXm> it repeats for a long time
[09:44] <Enich> rbasak, thanks for the answer..  i wouldnt want the root password floating around in files in plaintext.. even though it might only be readable by root.
[09:44] <hXm> is someone trying to do something weird or what? and what can i do
[09:44] <rbasak> Enich: I agree. It's what the package does anyway though, I think.
[09:45] <Enich> i guess its better having it "float around" less places then.   :)   now for the second question.
[09:45] <rbasak> Enich: since mysql doesn't present any other way to get to the server AFAIK, and the package does things like certain upgrades for you, I don't think it has any choice. If you try and go against that, test it carefully because I'm not sure if the packaging will break or not (it may be fine - I just don't know).
[09:45] <rbasak> I just noted in the askubuntu.com answer that using "echo ...|" is bad because it may leave your password in the shell history of the unprivileged user.
[09:46] <Enich> we really dont want that.
[09:46] <rbasak> But if you get it into debconf-set-selections securely yourself (eg. in a here doc), you'll get exactly the same result in terms of plaintext passwords floating around as if you had entered it by hand.
[09:48] <Enich> Would any of you know of application(with scripting support) that would let me connect to a serial interface, and then send ascii strings (i am basically trying to make a script that connects and sends the initial configuration to a device with a serial interface.)
[09:48] <rbasak> echo "foo" > /dev/ttyS0
[09:49] <rbasak> With stty first to set the serial parameters up.
[09:49] <Enich> iv been looking at miniterm.py  cutecom and a few others
[09:49] <rbasak> Or about three lines of python with the pyserial module
[09:49] <Enich> /dev/pts/x
[10:02] <Enich>  rbasak, the echo "foo" > /dev/pts/3   does not work im afraid,  i think i would need a application like miniterm.py, cutecom etc to establish the negotiation etc.
[11:16] <RoyK> hi all. any idea how to open an ssh tunnel from A to B so that C can reach A through B directly? I'm testing with 'ssh -f -n -N -o ExitOnForwardFailure yes -R 3035:<IP_ADDRESS>:22 -D <IP_ADDRESS>:3035<EMAIL_ADDRESS>but that only makes B listen on <IP_ADDRESS>:3035
[11:20] <patdk-lap> not sure what -D does for that
[11:21] <patdk-lap> but it's as simple as, -R localip:localport:Cip:Cport user@b
[11:21] <patdk-lap> wait, you want to go from C to A
[11:22] <patdk-lap> you will have to do that ssh from C to B
[11:22] <patdk-lap> unless you wanted to do that, double-ssh trick to break through nat
[11:23] <patdk-lap> http://www.howtoforge.com/reverse-ssh-tunneling
[11:26] <RoyK> patdk-lap: testing...
[11:30] <RoyK> patdk-lap: so something like ssh -f -n -N -o ExitOnForwardFailure\ yes -R <IP_ADDRESS>:3035:<IP_ADDRESS>:22 u@b ?
[11:30] <RoyK> patdk-lap: tcp        0      0 <IP_ADDRESS>:3035          <IP_ADDRESS>:*               LISTEN
[11:30] <RoyK> sitll
[11:31] <patdk-lap> the first <IP_ADDRESS> if missing becomes localhost, if you only need to connect from that computer, the second one is the computer the connection should go to (with source b)
[11:31] <patdk-lap> maybe some ssh option limiting it
[11:33] <RoyK> GatewayPorts
[11:33] <patdk-lap> oh wait, I'm thinking -L not -R
[11:33] <RoyK> GatewayPorts yes helped
[11:44] <RoyK> patdk-lap: in sshd_config
[12:42] <hXm> hi
[12:42] <hXm> how can i disallow postfix for external use
[12:42] <hXm> i only want from localhost
[12:43] <greppy> hXm: you could setup firewall rules, or you could configure it to bind to <IP_ADDRESS>
[12:44] <hXm> it could be in main.cf?
[12:44] <hXm> talking about postfix
[12:44] <hXm> ah, inet_interfaces
[12:44] <hXm> thanks
[12:45] <NginUS> I'm having trouble with xrdp in that it disconnects me as soon as the desktop loads- right after the kdm splash screen. Anyone have ideas as to a solution?
[13:05] <lamont> df
[13:05] <lamont> doh
[13:17] <RoyK> -bash: doh: command not found
[13:18] <Nafallo> nafallo@wizard:~$ doh
[13:18] <Nafallo> No command 'doh' found, did you mean:
[13:18] <Nafallo>  Command 'dh' from package 'debhelper' (main)
[13:18] <Nafallo> doh: command not found
[13:19] <Pici> zsh: correct 'doh' to 'dot' [nyae]?
[13:23] <zul> Daviey:  ping can we look at dropping Samba 3 in favor of Samba 4
[13:24] <Daviey> zul: i'd rather we went to samba 5!
[13:24] <Daviey> zul: it would be good to work out the upgrade path. is smb3 dead upstream?
[13:25] <zul> Daviey:  no its just everyone is moving to Samba 4 (i think) and good to have active diretory support
[13:26] <Daviey> zul: for sure, especially before the next LTS
[13:26] <mardraum> I think "everyone" might be an overstatement; those using samba reliably for simply file/print sharing have work to do
[13:27] <Daviey> mardraum: do you think smb3 will be supported for the next few years upstream?
[13:27] <mardraum> for security, yeah
[13:27] <mardraum> all that said samba4 has been a long time coming, and I bet they want to get it out there...
[13:29] <Daviey> mardraum: Yeah, I thought it made sense to get it in this release - prior to throwing it into the next LTS release (next)
[13:29] <mardraum> yeah, that makes sense
[13:30] <zul> Daviey:  its already in universe at least
[13:30] <Daviey> mardraum: that said, if smb3 is still OK upstream - we can keep it in the archive
[13:30] <zul> Daviey:  i would see what slangasek would say though as well
[13:32] <Daviey> zul: good thinking
[13:49] <jamespage> plars, ping re http://summit.ubuntu.com/uds-1305/meeting/21806/servercloud-s-seeded-qa-workflow/
[13:49] <jamespage> first up this afternoon/morning - are you able to attend and join the g+ please
[13:49] <plars> jamespage: yes, I'm planning to be there, and also pitti and jibel
[13:49] <plars> jamespage: they are the dep8 test experts :)
[13:50] <jamespage> plars, marvellous!
[13:50] <jamespage> thanks
[14:00] <zul> yolanda:  https://code.launchpad.net/~zulcss/python-swiftclient/pbr/+merge/163949
[14:42] <zul> yolanda:  https://code.launchpad.net/~zulcss/python-ceilometerclient/ftbfs/+merge/163961
[15:17] <zul> yolanda:  couple more https://code.launchpad.net/~zulcss/horizon/ftbfs/+merge/163967
[15:18] <yolanda> python-d2to1? first time i see it!
[15:19] <yolanda> i see a diff of local_settings.py.example , with only the dir names changed, is that ok?
[15:19] <yolanda> zul ^
[15:20] <zul> yeah
[15:35] <paco1> hello all!
[15:36] <paco1> if anyone can help me. I have a problem with my servers ldap 2.4.28 > => bdb_idl_delete_key: c_del id failed: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock (-30994) | conn=-1 op=0: attribute "entryCSN" index delete failure
[15:37] <paco1> it affects all my ldap servers (15 servers) :s
[15:40] <paco1> si quelqu'un a une idée d'oú peut provenir le probleme...
[15:40] <guma> I was asking yesterday about my multicast problem on my new setup 12.10 x64 multi home system. After adding missing static route "route add -net <IP_ADDRESS>/4 dev p1p1" when starting my app server I see in tcpdump that data in coming. But my application does not gets it.
[15:40] <paco1> if anyone can point me to the right direction to resolve that issue
[15:42] <guma> So i have another (two) test apps to send and listen using the same socket settings. If I send data from the same box to p1p1 or <IP_ADDRESS> and listen on the same box it works
[15:43] <guma> but when I try to send multicast test message from different box my other test app listening on p1p1 does not see that message. but while doing it tcpdump shows such message on the same machine where listener is running on?
[15:44] <guma> I tried to disable rp_filter and that does not have any affect. Any ideas? Is there some setting in 12.10 that is turned off by default?
[15:45] <bcessa> hi there, can someone point to a channel where I can ask a bit about x509/ssl? I mean other than #openssl, apparently nobody's there
[15:46] <smokie> hey guys, is it possible to run weekly backups of a running ubuntu server thats acting as a webserver?
[16:13] <zul> yolanda:  https://code.launchpad.net/~zulcss/ceilometer/havana-ftbfs/+merge/163992
[16:32] <guma> Is there something like SELinux on Ubuntu? And how can you turn it off?
[16:35] <roaksoax> guma: we have apparmor
[16:35] <sarnold> guma: https://help.ubuntu.com/community/AppArmor
[16:35] <sarnold> .. I bet that's out of date. heh.
[16:35] <roaksoax> guma: https://help.ubuntu.com/13.04/serverguide/apparmor.html
[16:35] <guma> I just found this before your post :). Does this in any way control is app can receive multicast data?
[16:36] <sarnold> guma: no.
[16:36] <sarnold> guma: check /var/log/audit/audit.log or dmesg output to see AppArmor DENIED messages
[16:37] <guma> sarnold: Good idea. Did not think about that. Let me check
[16:38] <guma> I have no audit I have auth.log only
[16:40] <sarnold> guma: auditd is responsible for the audit log. if auditd isn't installed, MAC messages go through dmesg/syslog
[16:44] <guma> sarnold: Ok I did installed auditd. After it was installed I tail -f on audit.log  dmsg and syslog. After starting my app I see multicast coming in tcpdump but my app does not get it. And no messages of any kind
[16:45] <sarnold> guma: good :) then apparmor isn't involved. :)
[16:45] <guma> I also disabled apparmor. Perhaps he is responsible to write errors?
[16:45] <guma> let me enable it back on and try again
[16:47] <guma> sarnold: Just rebooted system get get it back to initial state. And will try on clean
[16:51] <guma> sarnold: ok So while tailing on dmsg, syslog and audit logs I did not see any messages when I started my mcast program
[16:52] <guma> so as you stated it is not apparmor
[16:52] <sarnold> guma: yeah. sorry, you'll still have to keep digging :(
[16:53] <guma> if I send test message from same box I can receive just fine. But when coming from another box it is a problem.
[16:53] <guma> tcpdump shows activity with correct src IP and multicast addrs
[16:54] <guma> sarnold: I was wondering if there are better channels to ask this? Well I keep digging
[16:55] <adam_g> jamespage, okay to pull the trigger on these to CA staging and ubuntu -proposed? http://people.canonical.com/~agandelman/ca/folsom/2012.2.4/nova/  http://people.canonical.com/~agandelman/ca/grizzly/2013.1.1/
[16:56] <sarnold> guma: if you can write a program to reproduce the problem in 30~50 lines of code, stackoverflow.com would be ideal. it might take a bit longer than IRC, but there's plenty of smart folks over there, someone might know what's going on
[16:56] <guma> sounds like a plan
[16:56] <Daviey> zul: You are driving the mysql session in 1hr?
[16:57] <zul> yeah i guess so
[16:57] <Daviey> jamespage: did we invite any external people to it?
[16:57] <Daviey> zul: ^
[16:57] <zul> Daviey:  SpamapS said he was coming
[16:57] <jamespage> adam_g, grizzly looks OK
[16:57] <SpamapS> Indeed I should be there
[16:58] <Daviey> SpamapS: Greta
[16:58] <Daviey> Great*
[16:59]  * Daviey struggles to think of SpamapS as external to Ubuntu. :)
[16:59] <jamespage> adam_g, folsom to - I'm assuming they when through merge proposals first anyway right?
[16:59] <adam_g> jamespage, yup
[16:59] <jamespage> adam_g, +1 then
[17:00] <SpamapS> Daviey: Norvald Ryeng from Oracle will join us too
[17:01] <Daviey> SpamapS: oh splendid, what is his IRC nick?
[17:03] <SpamapS> Daviey: ryeng
[17:03] <SpamapS> Daviey: he might only be on OFTC in debian-mysql
[17:04] <Daviey> SpamapS: when the time comes, can i give you the hangout url and you pass it to him?
[17:05] <SpamapS> Daviey: sure.
[17:05] <Daviey> ta
[17:07] <dlloyd> hmm mariadb not in ubuntu repos yet?
[17:07] <SpamapS> dlloyd: no, but packages are nearly done for Debian
[17:07] <dlloyd> ah, thanks
[17:07] <SpamapS> dlloyd: undergoing review right now
[17:07] <dlloyd> ironically this wasnt the channel i meant to ask that in
[17:07] <dlloyd> but thanks!
[17:08] <SpamapS> ooohh the irony
[17:13] <NomadJim> so I've got a silent install of mysql using something like: echo mysql-server mysql-server/root_password select PASSWORD | sudo debconf-set-selections
[17:13] <NomadJim> and I want to do a silent install of citadel's mail server as well
[17:14] <NomadJim> where do I look to find the variables to set like "mysql-server/rootpassword select PASSWORD"
[17:14] <NomadJim> but for citadel
[17:15] <rbasak> NomadJim: install debconf-utils and then after installation grep the output of debconf-get-selections to see what the config option names are against what you answered.
[17:15] <NomadJim> so, I install debconf-utils, then install citadel manually, then grep debconf-get-selections
[17:15] <NomadJim> ?
[17:16] <rbasak> Right.
[17:16] <NomadJim> rbasak:  thanks
[17:16] <rbasak> Doesn't matter if you install debconf-utils at the end; it'll still work.
[17:16] <NomadJim> cool
[17:16] <SpamapS> Daviey: FYI, I may be a few minutes late, have an errand to run and not sure it will be completed by 1800 UTC.. will get there ASAP
[17:17] <rbasak> NomadJim: note that echoing passwords into commands is bad because it may temporarily show up in a ps listing, and may end up in an unprivileged user's shell history file.
[17:18] <NomadJim> is there a secure way for setting debconf-set-selections
[17:19] <rbasak> The debconf-set-selections end is secure. It's the echo end that's not necessarily secure.
[17:20] <rbasak> You can use a heredoc from a script. Then it's down to whether the script can be read by unprivileged users.
[17:20] <NomadJim> i guess I could put a file on the server i'm deploying
[17:20] <NomadJim> never heard of heredocs. I'll check that out
[17:20] <rbasak> Yes - if in a secure file, then "cat /path/to/file|debconf-set-selections" would be secure.
[17:21] <NomadJim> rbasak:  sweet thanks
[17:34] <zul> Daviey:  mayhe we should have someone from the security team as well
[17:39] <rbasak> zul, Daviey: +1
[17:42] <zul> Daviey:  they are sending two or 3 poeple
[17:51]  * SpamapS returns in time
[17:51] <SpamapS> zul: hah, are they bringing torches and pitchforks?
[17:51] <zul> SpamapS:  perhaps
[18:00] <hallyn> stgraber: that lxc-alpine patch is kind of scary.  Does a wget $url | tar x > apk; ./apk
[18:05] <hallyn> stgraber: could you take a look at bug 1176287 when you get a chance, and comment on whether there's anything in the steam-lxc script which woudl cause this?
[18:05] <uvirtbot`> Launchpad bug 1176287 in lxc "lxc-start: Error creating cgroups" [High,Confirmed] https://launchpad.net/bugs/1176287
[18:07] <hallyn> oooh, wait, i wonder...
[18:17] <hallyn> nm, i see the problem the steam guy is having
[18:32] <nedbat> I have a web server running as www-data.  I want to spawn subprocesses running as user sandbox, and have the sandbox process killed after a certain amount of real time.
[18:33] <nedbat> I tried spawning the process "sudo -u sandbox blah blah", but then I can't kill the process later.
[18:36] <sarnold> nedbat: can you start up fastcgi or something similar as your user sandbox?
[18:37] <nedbat> sarnold: i don't understand how fastcgi would help: the sandbox code is not trying to be a web server.
[18:37] <sarnold> nedbat: just that it represents a known way for a web server to interact with code potentially running as another user
[18:38] <nedbat> sarnold: an interesting idea.
[18:40] <nedbat> sarnold: apart from the web-server nature of the problem, do you know why I can't kill the process, or how I can?
[18:40] <sarnold> nedbat: one user can't kill another user's processes. root can, so perhaps you could write a setuid program to let you kill processes owned by another user..
[18:42] <nedbat> sarnold: I'm trying "sudo kill -9 <pid>", and www-data is in the sudoers with: "www-data ALL=(ALL) NOPASSWD:/bin/kill"
[18:42] <nedbat> sarnold: it feels like I'm missing one small piece of this puzzle.
[18:43] <sarnold> nedbat: 'kill' is quite often a shell-builtin, try /bin/kill in that command
[18:44] <nedbat> sarnold: that sounded really good, but doesn't seem to fix it.  Looking some more...
[18:46] <sarnold> nedbat: anything in the logs?
[18:47] <nedbat> sarnold: right now I'm testing this in a Python module running unittests, are there system log files you think might have info?
[18:48] <sarnold> nedbat: sudo will log to /var/log/auth* something at a minimum
[18:49]  * nedbat looks
[18:59] <nedbat> sarnold: http://paste.pound-python.org/show/33118/  There's one line there about a failure, I don't know what it means.
[19:01] <sarnold> nedbat: pam_xdg_support is a pam module to set up all that newfangled /run/user/ business. I'm not sure why'd it happen through sudo, and it probably doesn't affect whether or not this works.
[19:03] <nedbat> sarnold: and when I run the /bin/kill, I get an exit status of 0, and nothing written to stdout or stderr.
[19:03] <sarnold> nedbat: is the process dead? :)
[19:04] <nedbat> sarnold: for the test, the process is just a sleep(5), and it ends naturally after the 5-second sleep.
[19:04] <sarnold> nedbat: can you change to sleep 20 or something and check?
[19:06] <nedbat> yes, it's still running.
[19:06] <sarnold> :(
[19:06] <nedbat> sarnold: in fact, it's python: "sleep(5); print 'Done'", and I get the Done string on the stdout.
[19:07] <nedbat> sarnold: i really appreciate you spending time on this.  It seems like it should be possible.
[19:07] <sarnold> nedbat: indeed, I'd expect that to Just Work
[19:14] <jdstrand> yolanda: how far along is bug 1089488 to being verified?
[19:14] <uvirtbot`> Launchpad bug 1089488 in nova "Meta bug for tracking Openstack Stable Updates" [Undecided,Fix committed] https://launchpad.net/bugs/1089488
[19:20] <arosales> smoser, thanks for the update in bug 1020695
[19:20] <uvirtbot`> Launchpad bug 1020695 in cloud-init "Add variable for local IP address to /etc/hosts manager" [Low,Triaged] https://launchpad.net/bugs/1020695
[19:22] <jdstrand> jamespage: ^
[19:23] <nedbat> sarnold: a new piece of data: the pid I'm trying to kill is not the same as the sleeping process.  Can I kill the process and any that it spawned?
[19:24] <sarnold> nedbat: ah!
[19:24] <sarnold> nedbat: look into cgroups
[19:25] <sarnold> nedbat: that's afaik the only way to track children of a process ..
[19:29] <jdstrand> Daviey: ^
[19:29] <yolanda> jdstrand, we've launched some tests in jenkins, tomorrow i'll work more on it and i expect is done
[19:30] <jdstrand> yolanda: cool, thanks. so, we expect this to be out the door this week?
[19:30] <jdstrand> (ie, in -updates)
[19:30] <yolanda> jdstrand, i hope so, tomorrow i'll have more time to work on it
[19:31] <yolanda> adam_g, what do you think?
[19:31] <jdstrand> yolanda: I have a keystone CVE I'd like to get fixed that is blocked currently
[19:31] <jdstrand> but I don't want to reset you work
[19:31] <jdstrand> s/you/your/
[19:31] <Daviey> jdstrand: Another one aswell?
[19:32] <jdstrand> it is the one that came out last week
[19:32] <adam_g> yolanda, you said you had tests passing with logs. right? should be good to mark verification done
[19:32] <yolanda> adam_g, yes, latest ones were ok
[19:33] <Daviey> adam_g: Can you make sure the jenkins results get lots of love?
[19:33] <adam_g> Daviey, what do you mean?
[19:33] <Daviey> jdstrand: It's looking close enough that it makes sense to base your update on this stuff.
[19:33] <Daviey> adam_g: You kicked off a fresh jenkins test for bug 1089488?
[19:33] <uvirtbot`> Launchpad bug 1089488 in nova "Meta bug for tracking Openstack Stable Updates" [Undecided,Fix committed] https://launchpad.net/bugs/1089488
[19:33] <jdstrand> ok, cool
[19:34]  * jdstrand rebases keystone on -proposed
[19:34] <adam_g> Daviey, yolanda and i have been running tests for whats in precise-proposed, yea
[19:34] <yolanda> had a problem with floating ips in some run, but today they worked ok
[19:34] <Daviey> adam_g: perfect, thanks
[19:36] <yolanda> tomorrow morning i'll take care of the logs and update the bug
[19:36] <Daviey> yolanda / adam_g: to check, the testing looks good.. we just need to double check the results and update the bug status?
[19:37] <yolanda> yes, that's it
[19:37] <Daviey> jdstrand: we look good :)
[19:37] <adam_g> yolanda, its probably EOD for you soon do you want me to post-back the verification and tags after this session is over?
[19:38] <yolanda> adam_g, it's ok for me, or i can do it tomorrow morning if that's on time
[19:39] <K4k> I'm looking for help with using a ks.cfg for automating ubuntu installs. I've got it working fine but I thought that specifying "url --url http://...." would install the packages from there instaed of the CD. Instead, it seems to still be installing from CD. Has anyone got experience with this or know why it isn't installed from the network mirror?
[19:51] <yolanda> leaving for today, bye!
[20:01] <nedbat> sarnold: just to close the loop: I got it working by killing the process group, and by using setsid() so that my spawned process was a new process group.  Thanks for the help! :)
[21:05] <codex> Is there a way to prevent apt-get dist-upgrade from doing a release upgrade?
[21:08] <codex> I am assuming /etc/update-manager/release-upgrades seeting to 'never' would be it, but not sure
[21:08] <dpb1> codex: it shouldn't do a release upgrade.  does it?
[21:09] <codex> dpb1: my 10.04 lts just did to 11.04
[21:09] <codex> i was under the impression that it shouldn't either
[21:10] <codex> (ended up running into this: http://aaron-kelley.net/blog/2011/04/grub-prompt-after-upgrade-to-ubuntu-11-04/) which was frustrating
[21:11] <dpb1> codex: that should not happen unless the /etc/apt/sources.list* files were changed unintentionally ("lucid" -> "natty")
[21:12] <codex> looking into puppet, it doesn't seem to have been
[21:13] <codex> i wonder if there was some sort of a bug. I am looking at the log now and it looks like dist-upgrade had >308 packages that could be upgraded
[21:13] <mdeslaur> dist-upgrade never does a release upgrade unless you changed the sources.list file
[21:14] <dpb1> so, the only tool that you should run that updates those series names in ubuntu is "do-release-upgrade"
[21:15] <dpb1> If the series names get updated, then apt-get dist-upgrade will do something like a full update of your distro, but in a non-managed and non-recommended way. if that makes sense.
[21:15] <codex> yea, that was my impression too. I'll check with someone to make sure they didn't modify the sources, but this was definitely "interesting"
[22:16] <Lartza> Let's take a default OpenVZ Ubuntu 13.04 install... or even a disc maybe, what is running in Port 53 that answers to UDP?? :/
[22:20] <sarnold> Lartza: I have no idea where you'd get a "default openvz install", but check for dnsmasq
[22:21] <Lartza> sarnold, I have a VPS that just got DDOS'ed, and the provider told me it was UDP flood to port 53, but I have nothing installed there, so it must be something default
[22:23] <sarnold> Lartza: flood -to- port 53? or flood -from- port 53?
[22:25] <Lartza> sarnold, "it was an udp flood against the port 53 "
[22:26] <Lartza> So umm :S
[22:26] <Lartza> Don't know
[22:26] <Lartza> Do I need anything publicly accessible in 53?
[22:27] <sarnold> Lartza: only if you're intentionally providing authoritative DNS service...
[22:27] <Lartza> Yeah I'm not...
[22:27] <sarnold> Lartza: if you're just providing recursive DNS service on that port, it'd be wise to ensure you only answer queries from your own netblock..
[22:27] <Lartza> sarnold, It was just a default install from my VPS provider :/
[22:28] <K4k> after re-mastering an iso and re-creating the iso file with mkisofs, other than unetbootin, is there a way to get the iso onto a usb stick? I tried dd, but that didn't seem to work with the iso formatted in this way.
[22:28] <sarnold> Lartza: then no, nothing should be bound to port 53. check with sudo netstat -nlup  | grep :53   to see if anything is listening..
[22:29] <Lartza> sarnold, Just sending another message to support wether they could open the server back up before 24 hours... they nulled my IP
[22:30] <sarnold> Lartza: ow. do you have console access?
[22:30] <sarnold> nedbat: hey, glad to hear you found a good solution to killing your tasks :) nice.
[22:30] <Lartza> serial console from the VPS panel doesn't seem to work
[22:42] <Lartza> sarnold, It's named
[22:42] <Lartza> :/
[22:42] <sarnold> Lartza: ah. I wonder why you're running named.
[22:43] <Lartza> sarnold, I can't make it stop
[22:43] <Lartza> Unrecognized service
[22:43] <Lartza> ahh
[22:43] <Lartza> bind9
[22:44] <sarnold> you might wish to just apt-get purge bind9 and make sure that can't happen again
[22:44] <Lartza> Yeah I will
[22:44] <sarnold> .. if apt tells you something depends upon it, that might give some insight why it was there in the first place..
[22:44] <Lartza> Nope
[22:44] <Lartza> I think I've seen a DNS server on every DNS I've owned...
[22:45] <Lartza> sarnold, Just checked my smaller, Debian server, named listening there too :)
[22:45] <sarnold> Lartza: o_O
[22:53] <Lartza> sarnold, Yeah...
[22:54] <Lartza> sarnold, Uninstalled bind9 on both servers, now for some sleep since it's 1:53... Thank you for your help :)
[22:54] <sarnold> Lartza: have fun :)
[23:22] <RoyK> why do some people use 20 drives in a single raid-6?
[23:22] <RoyK> oh well, some people like base jumping ;)
[23:38] <Patrickdk> royk, heh, hp limits me to 16 disks per raid set
[23:38] <Patrickdk> so max 16 drive raid10, raid6, raid50, ...


[22:06] <nick_h> an app generated some upstart scripts for me, which i've installed. what might cause "sudo stop domain.com" to make upstart think that it was successful, but not actually stop the process?
[22:06] <nick_h> the upstart scripts are: https://gist.github.com/bac84614e823361e2eb6
[22:49] <JanC> first of all, they are configuration files, not scripts...
[22:50] <JanC> and what process is still running?  does it fork & detach from its parent?


[02:05] <imgbot> [03:05] <imgbot> [03:30] <imgbot> [03:30] <imgbot> [04:25] <imgbot> [04:25] <imgbot> [07:11] <Mirv> all CI Train workers seem dead
[07:11] <Mirv> cihelp , robru: ^ (ci train dead)
[07:11] <Mirv> because of the 0 free space
[07:11] <robru> Mirv: checking
[07:12] <robru> Mirv: uh-huh
[07:12] <robru> Mirv: gunna need webops for that one
[07:12] <Mirv> robru: ok :( any general ideas where the free space can be freed up?
[07:13] <robru> Mirv: yeah, you can delete 5GBs right out of /var/lib/jenkins/silos/ubuntu/landing-005/ubuntu
[07:13] <robru> Mirv: also there's a 5GB backup in /var/backups that can get killed
[07:13] <robru> Mirv: shit, I had prepped a cyphermox-test job to clear some stuff out, didn't anticipate the workers dying and the job being unable to run. awesome.
[07:14] <Mirv> robru: ok.
[07:14] <Mirv> yeah, workers dying makes things a bit more... problematic
[07:17] <robru> Mirv: the workers apparently can be brought back online, but I can't edit the job to actually run the command to delete the files
[07:17] <Mirv> robru: yep. filed RT ticket since no vanguard.
[07:18] <robru> Mirv: ok, good luck! I guess we should look into increasing the size of that nova volume if possible. amusingly the ephemeral storage is 50GBs and only 5% used.
[07:18] <Mirv> robru: thanks! indeed I'll bring that idea to the ticket handling once contacted
[07:18] <robru> Mirv: maybe call the emergency number? "a critical web service going offline" seems like an emergency to me.
[07:19] <Mirv> robru: I guess it's not critical for an hour or two, since I'm mostly the only one affected (and I can do stuff while waiting) and I'm sure a vanguard appears when the lazy rest of the Europe wakes up :)
[07:20] <robru> Mirv: haha, ok, your call then. I'm not really here ;-)
[07:20] <Mirv> robru: yes, sure, you're having your relaxing Sunday evening with no computers involved!
[07:36] <robru> Mirv: I apparently don't have permission to read your RT, but I got the email with the details. you should add the directory to delete to the ticket, might speed up their response.
[07:48] <Mirv> robru: ok. yes I'll tell them the dirs.
[07:49] <robru> Mirv: oh and if they ask, the juju env is ps4ci-train and the offending disk is the one attached to ci-train-jenkins/0
[07:49] <Mirv> ok
[08:29] <sil2100> Mirv: any news on the disk space issue?
[08:29] <Mirv> sil2100: not yet, waiting for some vanguard in UK to wake up
[08:29] <Mirv> sil2100: this is like almost critical issue but I know it's mostly hitting me at the moment, UK will be up soon and even I have stuff to do while waiting
[08:30] <Mirv> so I didn't make any emergency calls :)
[08:30] <sil2100> Mirv: is this blocking other silo landings, or just the big Qt one? ;)
[08:30] <Mirv> sil2100: this is blocking the whole train
[08:30] <Mirv> sil2100: all workers are dead, the machine is out of space
[08:30] <Mirv> sil2100: we can't even run our own cleanup job
[08:31] <Mirv> so yes it'll start blocking others as soon as people wake up, but let's hope the vanguard wakes up too..
[08:31] <sil2100> I see, damn, if we had access to the jenkins jobs we might have been able to at least clean up parts of it
[08:31] <sil2100> But it's all dead
[09:19] <davmor2> ogra_: hippo birdy 2 ewes, hippo birdy 2 ewes, hippo birdy deer ogra_, hippo birdy 2 ewes :)
[09:19] <ogra_> tweek tweek
[09:25] <Mirv> UK seems slow to wake up :(
[09:27] <sil2100> Mirv: do we need webops or IS?
[09:28] <Mirv> sil2100: webops I believe
[10:00] <sil2100> ogra_: and you should party today!
[10:00] <ogra_> haha, i will
[11:15] <sil2100> \o/
[11:15] <sil2100> Mirv: \o/
[11:16] <Mirv> :)
[11:18] <Mirv> sil2100: so, we have around 32GB of space now. after cleanup now 16GB free but all of that was gone relatively easily with Qt + backups.
[11:19] <Mirv> sil2100: so maybe asking for 50GB or 64GB?
[11:20] <sil2100> Mirv: were you able to check how much we have assigned for the train in overall?
[11:21] <Mirv> sil2100: well I'd guess most of the train is under that /var/lib etc? / has 50G of which only 8G is used, https://ci-train.ubuntu.com/job/cyphermox-test/644/console
[11:21] <Mirv> sil2100: I mean, under that juju volume to which apparently /var/ stuff symlinks to
[11:23] <sil2100> I suppose a bump to 64GB wouldn't hurt, but we'll have to somehow deal with those backups anyway
[11:23] <sil2100> Limit them in size as well, not to a point in time
[11:23] <Mirv> yes
[11:24] <sil2100> Mirv: anyway, so far great job with releasing Qt 5.4 o/
[11:26] <Mirv> sil2100: let's see how the migration goes and if there are any surprises, but yes so far so good.
[12:55] <sil2100> Mirv: oh! And one thing I forgot to mention
[12:56] <sil2100> Mirv: remember the problem you had with that MP that you had to change into a source upload on Friday in the train?
[13:00] <sil2100> Mirv: robru explained on the meeting how to deal with those in the new build job now, it seems all you need to do is to perform a normal (not watch_only) build with the additional source package name listed in the rebuild list
[13:01] <sil2100> Mirv: the job will notice it's a source upload and not do anything, but it will rebuild its .project file
[13:05] <Saviq> trainguards, can you please remove unity-system-compositor from vivid silo 18
[13:05] <sil2100> Saviq: from the PPA you mean?
[13:05] <Saviq> sil2100, yes
[13:05] <sil2100> Saviq: sure, let me do that now
[13:17] <Mirv> sil2100: right! yes, he emailed me as well telling just that. good to know.
[13:56] <sil2100> o/
[14:01] <Mirv> sil2100: we've one autopkgtest regression (symbols changing), fix in archives already by mitya
[14:01] <Mirv> so more waiting now
[14:02] <sil2100> \o/
[14:04] <om26er> bzoltan_, needed to ask you, was the test result for silo 14 published somewhere ?
[14:04] <bzoltan_> om26er:  the same pleace, as the CI sheet says
[14:04] <Mirv> sil2100: see webops
[14:04] <bzoltan_> om26er: no regression at all
[14:07] <om26er> bzoltan_, thanks for that. So I didn't find anything out of normal. But there was no systematic pattern followed to verify the fix as there was no way to verify the fix.
[14:07] <om26er> I guess we can count on the unittests there :)
[14:08] <bzoltan_> om26er: that is what I would do :)
[14:14] <sil2100> Attention! CI Train jenkins going down!
[14:17] <sil2100> ^ will publish the silo once jenkins is back
[14:48] <oSoMoN> trainguards: can someone please update oxide-qt in silo 3 to 1.5.2-0ubuntu1 by doing a new binary copy from the phablet-team PPA (https://launchpad.net/~phablet-team/+archive/ubuntu/ppa/+packages)?
[14:54] <sil2100> oSoMoN: on it
[14:54] <sil2100> oSoMoN: just remember that the train jenkins is still down
[14:54] <oSoMoN> sil2100, thanks man
[14:55] <oSoMoN> oh, is it?
[14:55] <oSoMoN> I must have missed the announcement
[14:55] <sil2100> It's up ^
[14:56] <sil2100> I mean, it's announced up in the backlog ^
[15:11] <Mirv> oSoMoN: sil2100: Qt 5.4 has landed / is landing, you'll need a rebuild instead of binary copy. I already had a rebuild ongoing in silo 3 for you compiling against 5.4
[15:13] <Mirv> Qt is still in proposed pocket for a little while, so I temporarily added landing-005 as a dependency to 003 (with my own todo item to remove it)
[15:13] <oSoMoN> Mirv, ah, thanks for that. I guess I’ll wait for oxide 1.5.3 to be ready then, as it has the fix for QVariants wrapped in QJSValues
[15:14] <oSoMoN> sil2100, so no need for any action on your part for now, I’ll let you know when I need a rebuild
[15:14] <Mirv> oSoMoN: alright then.
[15:15] <Mirv> I'll remove the dep then now from there so it doesn't linger
[15:20] <sil2100> Eeek
[15:20] <sil2100> I already copied the binaries over to the silo PPA
[15:21] <sil2100> And we exceeded the size of the PPA
[15:21] <dbarth> sil2100: while jenkins reloads ;)
[15:22] <dbarth> sil2100: so if i go ahead with asking for a re-seed of that extension package, how to have it be spotted by qa again?
[15:22] <dbarth> an empty silo to hold the request with the bug ref. for example ?
[15:23] <sil2100> dbarth: hm, I think we can use the new experimental functionality of tracking non-citrain landings
[15:23] <sil2100> dbarth: for now please fill in a landing request for that and I'll turn it into a real one :)
[15:23] <dbarth> ok
[15:23] <sil2100> Then QA will see it on their trello board
[15:31] <dbarth> sil2100: see line 75
[15:34] <dbarth> ogra_: fyi, this is that extension seed request again ^^ (signon-apparmor-extension)
[15:35] <ogra_> dbarth, vivid or rtm ?
[15:37] <sil2100> RTM
[15:38] <sil2100> But don't submit it yet
[15:38] <sil2100> We want QA to sign it off first
[15:38] <ogra_> sure
[15:39] <cjwatson> sil2100: Which PPA do you need expanding?
[15:44] <cjwatson> Ah, I guess somebody did it, assuming this is https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-005/+packages
[15:46] <rvr> rsalveti: ping
[15:46] <Mirv> cjwatson: 003, with oxide. no worries though, the current packages will be deleted.
[15:46] <ogra_> rvr, off today ... doing his samba duty as brazilian citizen ...
[15:47] <cjwatson> Oh, maybe it's https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-003/+packages - bumped to 20GB
[15:47] <rvr> ogra_: Ahh
[15:47] <rvr> mandel: ping
[15:47] <Mirv> cjwatson: thanks!
[15:47] <rvr> Meh, mandel seems to be also away
[15:54] <dbarth> ogra_: rtm, it's already on in vivid
[15:55] <ogra_> ok
[16:09] <om26er> boiko, Hi!
[16:11] <boiko> om26er: hi
[16:12] <om26er> boiko, regarding silo 12, the fix needs to have some kind of automation.
[16:12] <om26er> Probably an autopilot test will do
[16:13] <boiko> om26er: that's a cherry-pick from code already landed into vivid
[16:14] <om26er> boiko, right. then I guess we can add a test in both places :)
[16:14] <boiko> om26er: I would prefer not to add more code to rtm than what's in vivid, so, maybe I can add a test for that in the testplan for now?
[16:14] <boiko> om26er: well, if time permits, we have other priority stuff to work on :/
[16:15] <om26er> boiko, jibel instructed to not land Apps without tests
[16:15] <om26er> and in this case it looks like an easy one
[16:16] <sil2100> CI Train jenkins is back!
[16:17] <boiko> om26er: well, that will have to wait a bit then, if we manage to get some time I can write the test, but can't do right now
[16:18] <om26er> jibel, what do you think ^
[16:33] <Mirv> yay, train back
[16:36] <Mirv> Saviq: 018 unity8 will need a rebuild since Qt 5.4 has been in -proposed for the last 6 hours or so. we're expecting release pocket migration any moment now.
[16:36] <jibel> om26er, agreed, we cannot continue landing code without tests, relying on QA only to do testing doesn't scale.
[16:43] <Saviq> Mirv, well, wil it actually? hasn't it built against 5.4 already?
[16:51] <Mirv> Saviq: yeah, it looks like it took from 5.4 from proposed, good. no need to rebuild: https://launchpadlibrarian.net/197827352/buildlog_ubuntu-vivid-amd64.unity8_8.02%2B15.04.20150216.1-0ubuntu1_UPLOADING.txt.gz - I think I saw a silo before that didn't have proposed enabled.
[16:51] <Mirv> and yes! Qt 5.4 seems to migrating to release pocket just now
[16:52] <Mirv> sil2100: ^
[16:53] <Mirv> aha
[17:01] <sil2100> Mirv: \o/
[17:05] <Mirv> ok, now merging also successfully
[17:11] <Mirv> kgunn: 000 will need a rebuild of qtsystems-opensource-src, qtmir, qtubuntu and unity8 due to Qt 5.4 having landed
[17:11] <Mirv> kgunn: oh, and ubuntu-system-settings
[17:12] <kgunn> Mirv: thanks, mzanetti ^^ for tomorrow as i likely won't get to it
[17:23] <boiko> om26er: jibel: ok, once I get some time I will write those tests
[17:48] <robru> sil2100: https://code.launchpad.net/~robru/cupstream2distro/delete-distro-versions-after-diffing/+merge/249864 can I get you to review? ;-)
[17:51] <john-mcaleely> http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-20150216-fe747ac.changes
[17:51] <john-mcaleely> http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-20150216-fe747ac.tar.xz
[17:51] <john-mcaleely> http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-testresults-20150216-fe747ac.ods
[17:51] <john-mcaleely> sil2100, davmor2 ^ device tarbll (also in citrain spreadsheet) for rtm
[17:51] <john-mcaleely> QA signoff requested
[17:59] <sil2100_> Geh, GPU hang...
[18:02] <robru> sil2100_: did you see my ping? https://code.launchpad.net/~robru/cupstream2distro/delete-distro-versions-after-diffing/+merge/249864 can you review this merge? ;-)
[18:02] <robru> it's trivial
[18:03] <davmor2> thanks john-mcaleely
[18:03] <john-mcaleely> sorry it's a bit later than advertised
[18:04] <sil2100_> robru: thanks! Missed it due to the GPU-hang, looking
[18:16] <sil2100_> robru: +1
[18:16] <robru> sil2100_: thanks
[18:50] <robru> Mirv: Saviq: awesome, silo 5/18 published with conflicts.
[18:58] <robru> Mirv: Saviq: not sure how this happened, the train should have prevented publication. but basically saviq's silo 18 published unity8 which did not contains Mirv's no-change rebuild, so I guess unity8 is now built against the wrong version of qt that's in the archive. probably needs a new no-change rebuild, somebody should check that.
[19:10] <robru> Mirv: Saviq: https://bugs.launchpad.net/cupstream2distro/+bug/1422465 bug filed
[19:37] <Saviq> robru, my silo *did* contain the no-change rebuild, and it actually built against qt 5.4 that was already in proposed
[19:38] <robru> Saviq: oh, ok. well something goofed up during the merge then. I manually merged it myself, so it should be fine then.
[19:41] <Saviq> robru, yeah, we could've ended up with a conflict, that's possible, because Mirv merged the MP on top of our trunk manually
[19:41] <Saviq> robru, although I'd have thought bzr would resolve it
[19:43] <robru> Saviq: yeah, bzr was saying 'Nothing to do.' but somehow ci train was just puking all over it. no idea why
[20:18] <kgunn> Mirv: so Qt5.4 is actually part of vivid now ?
[20:21] <robru> kgunn: yes
[20:24] <seb128> but seems to be somewhat buggy or incomplete
[21:41] <robru> boiko: https://code.launchpad.net/~boiko/dialer-app/fix_autopilot_multi_pagestack/+merge/249366 need your approval.
[21:41] <boiko> robru: yeah, just saw it, sorry, as I did the MR myself, I think it is better that someone else from the team take it a look, but that will have to wait until tomorrow
[21:42] <boiko> robru: sorry about that
[21:42] <robru> boiko: no worries.


[00:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:07] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_extra-cmake-modules build #71: FIXED in 17 min: https://kci.pangea.pub/job/bionic_unstable_extra-cmake-modules/71/
[00:16] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #1060: SUCCESS in 6 min 1 sec: https://kci.pangea.pub/job/mgmt_merger/1060/
[00:30] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_prison build #96: FAILURE in 9 min 41 sec: https://kci.pangea.pub/job/bionic_unstable_prison/96/
[00:30] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kfilemetadata build #69: FAILURE in 12 min: https://kci.pangea.pub/job/bionic_unstable_kfilemetadata/69/
[00:33] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ruqola build #134: STILL FAILING in 15 min: https://kci.pangea.pub/job/bionic_unstable_ruqola/134/
[00:40] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_babe build #1: FAILURE in 23 min: https://kci.pangea.pub/job/bionic_stable_babe/1/
[00:42] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdecoration build #68: STILL UNSTABLE in 24 min: https://kci.pangea.pub/job/bionic_unstable_kdecoration/68/
[00:43] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kontactinterface build #83: STILL FAILING in 24 min: https://kci.pangea.pub/job/bionic_unstable_kontactinterface/83/
[00:44] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kamoso build #68: STILL FAILING in 14 min: https://kci.pangea.pub/job/bionic_unstable_kamoso/68/
[00:48] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ksystemlog build #82: FAILURE in 28 min: https://kci.pangea.pub/job/bionic_unstable_ksystemlog/82/
[00:50] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ruqola build #135: STILL FAILING in 11 min: https://kci.pangea.pub/job/bionic_unstable_ruqola/135/
[00:55] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kamoso build #69: STILL FAILING in 5 min 47 sec: https://kci.pangea.pub/job/bionic_unstable_kamoso/69/
[00:58] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_falkon build #17: STILL UNSTABLE in 38 min: https://kci.pangea.pub/job/bionic_stable_falkon/17/
[00:59] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kdenetwork-filesharing build #34: STILL UNSTABLE in 41 min: https://kci.pangea.pub/job/bionic_stable_kdenetwork-filesharing/34/
[00:59] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ksystemlog build #83: STILL FAILING in 6 min 2 sec: https://kci.pangea.pub/job/bionic_unstable_ksystemlog/83/
[01:01] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_falkon build #106: STILL UNSTABLE in 43 min: https://kci.pangea.pub/job/bionic_unstable_falkon/106/
 is mpd preconfigured in Kubuntu since Cantata is default now?
[01:14] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_babe build #2: STILL FAILING in 28 min: https://kci.pangea.pub/job/bionic_stable_babe/2/
[01:16] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kontactinterface build #84: STILL FAILING in 27 min: https://kci.pangea.pub/job/bionic_unstable_kontactinterface/84/
[01:16] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:16] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kfilemetadata build #70: FIXED in 40 min: https://kci.pangea.pub/job/bionic_unstable_kfilemetadata/70/
[01:16] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:16] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_prison build #97: FIXED in 40 min: https://kci.pangea.pub/job/bionic_unstable_prison/97/
[01:37] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_latte-dock build #101: FAILURE in 8 min 42 sec: https://kci.pangea.pub/job/bionic_unstable_latte-dock/101/
[01:39] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_latte-dock build #84: FAILURE in 10 min: https://kci.pangea.pub/job/bionic_stable_latte-dock/84/
[01:47] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_latte-dock build #102: STILL FAILING in 4 min 39 sec: https://kci.pangea.pub/job/bionic_unstable_latte-dock/102/
[01:49] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_latte-dock build #85: STILL FAILING in 4 min 38 sec: https://kci.pangea.pub/job/bionic_stable_latte-dock/85/
[01:53] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_peruse build #65: STILL UNSTABLE in 24 min: https://kci.pangea.pub/job/bionic_unstable_peruse/65/
[01:53] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_krita build #90: STILL UNSTABLE in 1 hr 23 min: https://kci.pangea.pub/job/bionic_unstable_krita/90/
[01:53] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ark build #96: STILL UNSTABLE in 24 min: https://kci.pangea.pub/job/bionic_unstable_ark/96/
[02:07] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_akonadi-mime build #49: STILL FAILING in 26 min: https://kci.pangea.pub/job/bionic_unstable_akonadi-mime/49/
[02:20] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kmbox build #68: STILL FAILING in 26 min: https://kci.pangea.pub/job/bionic_unstable_kmbox/68/
[02:20] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #93: STILL UNSTABLE in 51 min: https://kci.pangea.pub/job/bionic_unstable_kstars/93/
[02:24] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kalarmcal build #61: STILL FAILING in 4 min 39 sec: https://kci.pangea.pub/job/bionic_unstable_kalarmcal/61/
[02:33] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kalarmcal build #62: STILL FAILING in 3 min 38 sec: https://kci.pangea.pub/job/bionic_unstable_kalarmcal/62/
[02:42] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kalzium build #66: STILL UNSTABLE in 48 min: https://kci.pangea.pub/job/bionic_unstable_kalzium/66/
[02:43] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_akonadi-mime build #50: STILL FAILING in 30 min: https://kci.pangea.pub/job/bionic_unstable_akonadi-mime/50/
[02:59] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #71: STILL UNSTABLE in 1 hr 5 min: https://kci.pangea.pub/job/bionic_unstable_amarok/71/
[02:59] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kmbox build #69: STILL FAILING in 33 min: https://kci.pangea.pub/job/bionic_unstable_kmbox/69/
[02:59] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_marble build #75: FAILURE in 18 min: https://kci.pangea.pub/job/bionic_stable_marble/75/
[03:04] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_marble build #31: FAILURE in 22 min: https://kci.pangea.pub/job/bionic_unstable_marble/31/
[03:09] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kidentitymanagement build #68: STILL FAILING in 26 min: https://kci.pangea.pub/job/bionic_unstable_kidentitymanagement/68/
[03:09] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_marble build #76: STILL FAILING in 5 min 15 sec: https://kci.pangea.pub/job/bionic_stable_marble/76/
[03:10] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_akonadi-contacts build #115: STILL FAILING in 26 min: https://kci.pangea.pub/job/bionic_unstable_akonadi-contacts/115/
[03:29] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_marble build #32: STILL FAILING in 20 min: https://kci.pangea.pub/job/bionic_unstable_marble/32/
[03:35] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_akonadi-contacts build #116: STILL FAILING in 19 min: https://kci.pangea.pub/job/bionic_unstable_akonadi-contacts/116/
[03:35] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kidentitymanagement build #69: STILL FAILING in 20 min: https://kci.pangea.pub/job/bionic_unstable_kidentitymanagement/69/
[03:36] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_mailimporter build #67: FAILURE in 1 min 3 sec: https://kci.pangea.pub/job/bionic_unstable_mailimporter/67/
[03:50] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdepim-runtime build #97: STILL FAILING in 14 min: https://kci.pangea.pub/job/bionic_unstable_kdepim-runtime/97/
[03:56] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:56] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_mailimporter build #68: FIXED in 15 min: https://kci.pangea.pub/job/bionic_unstable_mailimporter/68/
[03:57] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ktnef build #54: STILL FAILING in 21 min: https://kci.pangea.pub/job/bionic_unstable_ktnef/54/
[04:11] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdepim-runtime build #98: STILL FAILING in 15 min: https://kci.pangea.pub/job/bionic_unstable_kdepim-runtime/98/
[04:18] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ktnef build #55: STILL FAILING in 15 min: https://kci.pangea.pub/job/bionic_unstable_ktnef/55/
[04:22] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kmail build #122: STILL FAILING in 4 min 48 sec: https://kci.pangea.pub/job/bionic_unstable_kmail/122/
[04:27] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-workspace build #140: FAILURE in 29 min: https://kci.pangea.pub/job/bionic_unstable_plasma-workspace/140/
[04:33] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kmail build #123: STILL FAILING in 5 min 20 sec: https://kci.pangea.pub/job/bionic_unstable_kmail/123/
[04:57] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-workspace build #141: STILL FAILING in 25 min: https://kci.pangea.pub/job/bionic_unstable_plasma-workspace/141/
[04:59] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_baloo build #65: FAILURE in 1 min 13 sec: https://kci.pangea.pub/job/bionic_unstable_baloo/65/
[05:06] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_akonadi-calendar build #67: STILL FAILING in 18 min: https://kci.pangea.pub/job/bionic_unstable_akonadi-calendar/67/
[05:25] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:25] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_baloo build #66: FIXED in 21 min: https://kci.pangea.pub/job/bionic_unstable_baloo/66/
[05:26] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_akonadi-calendar build #68: STILL FAILING in 14 min: https://kci.pangea.pub/job/bionic_unstable_akonadi-calendar/68/
[05:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_messagelib build #161: STILL FAILING in 29 min: https://kci.pangea.pub/job/bionic_unstable_messagelib/161/
[06:21] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_messagelib build #162: STILL FAILING in 30 min: https://kci.pangea.pub/job/bionic_unstable_messagelib/162/
[06:22] <tsimonq2> or
[06:22] <tsimonq2> whoops
[06:24] <valorie> @MichaelTun I wish!
[06:24] <valorie> I voted for Cantata and now wish I had vetoed it instead
[06:25] <acheronuk> why?
[06:26] <valorie> because I could never get it to work
[06:26] <valorie> not one tune played
[06:26] <valorie> amarok still works though
[06:26] <valorie> so whatever
[06:26] <acheronuk> weird. works nicely here
[06:26] <valorie> but not a very nice experience for our users
 if mpd is not setup by default then Cantata should NOT be the default. The only way it should be default if mpd is preconfigured. That is the #1 reason people say they dont use Cantata. Honestly, I agree with that because that is why I dont use it. Yes, I can setup mpd but I dont care enough to do it.
 Qmmp should be the default music player for Kubuntu and it should be preconfigured to be fully compatible with Plasma which it totally can be. :) (default sucks though)
 I'd stay away from Amarok to be honest because it's well . . . it's Amarok
[06:31] <valorie> heh -- I started on the amarok team
[06:32] <valorie> and like the concept
[06:32] <valorie> I get that not everybody cares about the band, etc.
 Amarok used to be great like 1.4 was awesome . . . then slowly it became something I have no desire to touch again
[06:32] <acheronuk> cantata sets up mpd on 1st run. its not appropriate to pre-configure it
[06:33] <valorie> @michaeltun -- tastes differ!
[06:33] <valorie> anyway, if it works for most, OK
 that requires the user to set it up then and to know what they are doing with setting it up. If this were Arch or something I'd be fine with that but since it is Kubuntu and meant to be user-friendly. Default is King and that is why it is important.
[06:34] <valorie> when elisa is finally released we'll have to re-evaluate anyway
 Elisa and Babe are pretty far away though. They both look very nice but they are both still very much beta
[06:35] <valorie> yup
[06:35] <valorie> and it's possible the new amarok will be released in time to evaluate IT
[06:36] <valorie> poor Michael Tun
[06:36] <valorie> lol
 if the new Amarok has a default of a freaking wiki in it then I vote "Ama-no"
[06:37] <acheronuk> valorie: evaluate for what?
[06:38] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:38] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_marble build #77: FIXED in 32 min: https://kci.pangea.pub/job/bionic_stable_marble/77/
[06:39] <valorie> for default music application
[06:40] <valorie> if we have a good KDE kf5 option
[06:40] <acheronuk> in 18.10 I suppose yes. if they can make it not krap as well as port it
[06:41] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:41] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_marble build #33: FIXED in 35 min: https://kci.pangea.pub/job/bionic_unstable_marble/33/
[06:41] <valorie> right
[06:42] <valorie> certainly not making changes now, except bugfixes
[06:42] <acheronuk> tried the kf5 port yesterday, and was not too impressed
[06:43] <acheronuk> context pane didn't load for a start
[06:43] <valorie> I get the idea it is just a raw port for now
 is the feature freeze in lock in general or was that just for the beta?
[06:43] <valorie> no work on the UX etc.
[06:43] <valorie> yet
[06:44] <acheronuk> https://wiki.ubuntu.com/FeatureFreeze
[06:44] <valorie> they are considering using kirigami for instance
[06:44] <acheronuk> until release ^
 @valorie, Kirigami would be interesting
 ok better question . . . are the setting improvements that I suggested blocked with this freeze?
 I noticed many arent done so I was wondering if they cant be done now or selected not to be done
[06:46] <acheronuk> no, they are not blocked
 ok sweet
 @MichaelTun the change to disable kalarm autostart went in a few hrs before the zesty RC images spun! 😮
 not that I plan to leave it that late :P
[06:56] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kcalcore build #99: STILL FAILING in 34 min: https://kci.pangea.pub/job/bionic_unstable_kcalcore/99/
 @acheronuk, oh ok cool. I've never tried kalarm before but there was talks about merging kalarm, ktimer, kteatime, kronometer, etc into a single app that does it all.
 I use KTeaTime for something completely different for it's purpose and I use Kronometer for doing live streams and podcasts. :)
 @MichaelTun, It was autostarting akonadi, which was a pain just for that
 @acheronuk, oh wow, yea no thanks
 so now it doesn't run unless you choose to use a PIM app and it gets set up by that
 https://phabricator.kde.org/T7978#128442 @acheronuk does this mean this is done now?
 @MichaelTun sorry. no. that is a bit misleading. I was testing what files needed to change by making my ~/.config/ a git repo, and git diffing what changed when I altered settings
 that is the output for my ref
 oh ok that makes sense then. This is not a critical change but I think it would be a nice polish change
 @MichaelTun, it's one that might be easiest with a kubuntu look and feel config
 @acheronuk, can a L&F theme be applied by default during install?
 yes
 sounds good then :)
 also if that config solves the menu problem that be nice
[07:21] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kcalcore build #100: STILL FAILING in 20 min: https://kci.pangea.pub/job/bionic_unstable_kcalcore/100/
 would also mean people could revert to default kde look and feel, where stick defaults would go back
 on setting changes a look-and-feel supports, anyway
 that sounds like a great option for those who dont like change
 (Calamares...)
 Lol
 I need to make all the changes in a VM, generate a custom look and feel, as see what settings it picks up in its config
 also make a kubuntu default panel template
 s/make/finish
 😎👍❤
 wtf is spice-vdagent? @tsimonq2
 @acheronuk, No clue
 Spice is the graphics client for QEMU iirc
 turns up in a refresh of my meta!
 * Added spice-vdagent to desktop
 oh. https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/revision/2165
 When was that proposed to all flavors?
 I mean, the change seems fine, but it seems wrong that this is the first I'm hearing about it.
 I've not seen anything about it
 I'll have to ask after I sleep
 trying lubuntu meta for teh hell of it
 Ack
[10:33] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kio build #93: FAILURE in 1 min 2 sec: https://kci.pangea.pub/job/bionic_unstable_kio/93/
[10:52] <BluesKaj> hiyas all
[11:10] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:10] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kio build #94: FIXED in 32 min: https://kci.pangea.pub/job/bionic_unstable_kio/94/
[12:11] -kubuntu-ci:#kubuntu-devel- Starting build #14 for job iso_bionic_stable_amd64 (previous build: SUCCESS)
[12:29] <acheronuk> cyphermox: hi. did you have a chance to look at: https://code.launchpad.net/~rikmills/ubiquity/bug1447144/+merge/341228
[12:31] -kubuntu-ci:#kubuntu-devel- Project iso_bionic_stable_amd64 build #14: SUCCESS in 19 min: https://kci.pangea.pub/job/iso_bionic_stable_amd64/14/
 @nggraham you about? can you test an iso for the wifi bug?
 http://kci.pangea.pub/images/iso_bionic_stable_amd64/current/
[12:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2110: SUCCESS in 53 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2110/
[12:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2110: SUCCESS in 1 min 8 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2110/
[12:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2110: SUCCESS in 3 min 46 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2110/
[13:05] <cyphermox> acheronuk: not yet, I will look today
[13:05] <acheronuk> cyphermox: thanks :)
[13:05] <cyphermox> actually I'm wondering if it wouldn't be just better to grep for something like login=oem, since one might edit the file manually and forget to remove the comment
[13:06] <cyphermox> you know, whatever the entry is when oem is still set
[13:06] <acheronuk> cyphermox: I did do that at 1st, but did belt and braces in case someone was dumb enough to put oem as the new user
[13:07] <cyphermox> hrm.. I guess
[13:08] <acheronuk> cyphermox: I'm not overly fussed if you want to simplify
 @acheronuk, yes, later today
 this guy? http://kci.pangea.pub/images/iso_bionic_stable_amd64/current/kubuntu-ci-stable-bionic-amd64.iso
[13:24] <cyphermox> bah, I think that's a good way to handle it
 @nggraham, yep
 @nggraham if you have the BW to spare for a iso download that is
 I do, I can try later
 thanks. the boot theme is a bit off on those isos, so don't worry about that
 the discussion of single-click vs double-click is very interesting to me since it is surprising that anyone would be so much on the side of single-click that they would fight it from being changed to benefit new users.
 referring to the KDE phab discussion
 hopefully Kubuntu can show them the way. :)
 actually I think if Kubuntu were to do this it would be interesting to see what reactions users have comparing Kubuntu vs Neon
 @MichaelTun - most tutorials on kde post install have a section dedicated to make it two clicks.
 at least the ones in pt_NR
 BR
 @tomazcanabrava, lol exactly!
 mine is one - click because I had to learn and I didn't mind testing it for a while
 but there's still places where it's really bad, for instance selecting files on dolphin, sometimes I try to click on the '+' at the toplevel of the icon, and miss it by a pixel,
 then okular opens with a really huge pdf that I actually wanted to delete.
 single-click is better in many ways but default expectation is way more important in my opinion than what is technically superior or not. :)
 @tomazcanabrava, yea that is problematic. I also think the plus/minus buttons are needlessly confusing as well when it should just be a checkbox like in Windows.
 +1. if we have the hability to change it and the power user can always fine tune, but the default should not be for the power user.
 *specially* because a lot of newcommers think that they are power users and destroy the system. (/me been there, done that)
 @tomazcanabrava, exactly, which is why I am so surprised that people on phabricator are so in favor of single click . . . it's not about what is better to use but what is better for new users.
 @tomazcanabrava, lol there is even a meme about that in the Linux community.   I find it rather infuriating, always executing things I didn't mean to execute and navigating when I meant to select.
 @mamarley, I think that is the reaction most people have. @tomazcanabrava gave me an idea to add to the phabricator of people posting on the internet about how to change it or why they dont like it.
[15:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2111: SUCCESS in 48 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2111/
[15:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2111: SUCCESS in 1 min 7 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2111/
[15:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2111: SUCCESS in 3 min 46 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2111/
[15:51]  * BluesKaj loves single click, probly due to my lazy nature :-)
 single click vs double click is an endless debate in general. What is your opinion of what should be default?
 "least surprise for the newcommer"
[16:19] <mamarley> Coming from Windows, people would probably be expecting double-click.  I'm not sure what Macs do.
[16:20] <BluesKaj> windows can single click if one sets it
 mac is double-click
 the thing is, double-click does legitimately heva major usability problems that all desktop OSs have been hauling forwards for 30 years
 double-clicking is legitimately really hard for a lot of people
 and for many others, it's never obvious what needs to be double-clicked and what needs to be single-clicked
 you see for example people double-clicking launchers and toolbar icons *all the time* out of this confusion
 single-click solves all that... at the cost of other issues. The question is, is it worth it? And if not, can it be made worth it? And regardless, what's a good setting *today*?
 @nggraham, yes but doing so has no impact in most cases. There are people who double click links on websites, doesn't matter because the same outcome occurs.
[16:28] <mamarley> nggraham: And you also get people accidentally executing things they didn't mean to execute and navigating when they meant to select with single-click.
 @nggraham, I dont think single click is worth solving those issues because those issues are not experienced by the majority. I do think it needs to be an option but not the default choice. … KDE should also worry about accessibility more so than it currently does.
[16:28] <mamarley> Especially trying to select a single item, you have to press Ctrl to make that work.
 as I stated earlier, here is my post showing a variety of complaints on the single-click default over the years. https://phabricator.kde.org/T8187#132416 … how many people complain about double-click default to make tutorials, forum posts, subreddit posts, etc? Not many. :)
 I do agree with you guys, but it's important to acknowledge other opinions and the legitimate case that can be made for the status quo
 we strengthen our own case if we can understand and fluently refute the opposing argument
 I agree that we shouldnt dismiss the opinions of others but this is a rare exception where the expectation is too great while the benefit and improvement is too small to bother with trying to change expectations. … If we were having this debate in 1995 then I'd have no issue with trying it out. However, it's been over 20 years of double-click as default ingrained into desktop computing paradigm. The debate should have been
 (still +1 on changing it in Kubuntu and then gauging user feedback)
 @nggraham, I don't think Neon would change it unless default changed so I am very interested to see the reactions when Kubuntu changes it
 anyone else able to test that iso wifi bug with my modified image?
 I plan to later today; can't right now as I'm at work
 @nggraham, Yeah. I meant apart from you :)
 if I'm going to propose a change to a package in 'main', I want as much cooberations as possible
 @acheronuk, I dont know what needs to be tested but I would if explained what to do. :)
 I'll have to do it on my secondary "enterprise" laptop that is kind of old so not sure how useful that info would be
 This iso needs testing: http://kci.pangea.pub/images/iso_bionic_stable_amd64/current/kubuntu-ci-stable-bionic-amd64.iso
 To see if the  changes in casper in that fix the double password request for secured wifi in the live session
 1. boot to live session with image … 2. click on wifi icon in system tray … 3. click "Connect" for a wifi network that has a lock icon on it … 4. enter your password into the text field in the plasmoid there … Question: Does a window immediately pop up asking for your password again?
 specifically connecting to networks shown with a padlock
 oh I see and thanks will do
 yay
[17:54] <mamarley> I think I actually saw that bug on my installed system a while back, but I just thought I had fatfingered my password.
 @nggraham I have tried renabling kwallet, but disabling it again with a config file. which plasma-nm has fallback code to cope with.  … Instead of breaking kwallet by removing it's service files, which plasma-nm doesn't know has happened, and thinks it should be working.
 mmmmm
 interesting, maybe that was part of our problem all along
 I think it was. hence the fixes so far only worked partially or not at all
 kwallet leaving me alone would be so nice. :)
 This is the live session for now
 is there a default email client in Kubuntu? If so and it is KMail, could it not be? :)
 thinking about dropping it for 18.10. possibly
 @acheronuk, http://s.quickmeme.com/img/be/be73ebe93046aca825637eefdb3ff07ffc3cc2d9a7cbab061b122fa5ecc3e4a0.jpg
 I mean I dont actually care because I remove it anyway but I think it is a negative towards Kubuntu's reputation as being the "easy to use/new user Plasma" distro.
 when they hurry up with a good kde alternative, it will make that choice easier :/
 @acheronuk, agreed . . . Kube needs to hurry :)
[19:06] <mamarley> I am looking forward to Kube as well.  I'm using Thunderbird right now, but it seems to have become rather stagnant as of late.
[19:06] <mamarley> And I won't install Kmail because Akonadi.
 the kube package available ?
 no. it's still a 'tech preview'
 :)
[19:22] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[19:22] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_latte-dock build #86: FIXED in 19 min: https://kci.pangea.pub/job/bionic_stable_latte-dock/86/
 so still stick to kmail / thunderbird while waiting for it to be GA
[19:23] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[19:23] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_latte-dock build #103: FIXED in 21 min: https://kci.pangea.pub/job/bionic_unstable_latte-dock/103/
 @nggraham FW 5.44 FFe accepted. I will upload to bionic shortly
[20:14] -kubuntu-ci:#kubuntu-devel- Starting build #126 for job mgmt_pause_integration (previous build: ABORTED)
 @nggraham thinking of posting the following comment to phabricator but it might be a bit too heavy so feedback please. … —------— … I think the experiment of single-click by default has had enough time that if it were to have changed the expectations of users then it would have already done it. … KDE/Plasma has had single-click as default for over a decade and the topic has been brought up on so many occasions and h
 not too heavy, go ahead and do it, I say
 ok cool done . . . you read fast
 I can't say I disagree with anything you wrote
 so @acheronuk, are we changing this in Kubuntu, or are we still undecided?
 @nggraham, I intend to unless someone (KC) forces me not to
 haha
 I'll back you up
 SWEET
[20:40] <valorie> why would the KC weigh in on this?
[20:40] <valorie> I have no strong feelings on either side, for my part
[20:41] <valorie> I use Dolphin quite a bit so double-click is better for me after using single for many years
[20:41] <valorie> if double is better for new users then go for it
 @valorie, why would anyone care if it was changed in the first place to benefit new user expectation? yet for some reason it is being debated in phabricator . . . 🤦♂
 it is being debated because Henrik senses (correctly) that I plan to use Kubuntu's experiencing changing this setting to push for an upstream change, which he opposes
 I know that is not Kubuntu related but still it hurts my brain that the debate even needs to exist
[20:42] <valorie> it's a problem when people forget that they are not defending positions, but rather thinking together
 he shouldnt oppose it is my point .. . it makes no sense to oppose it
[20:43] <acheronuk> valorie: I don't expect KC would have strong enough feelings. I was just covering my ass with that remark
[20:43] <valorie> man the machine guns and protect the position, boys!
[20:43] <valorie> that's what comes out far too often
 @valorie, lol
[20:44]  * valorie covers acheronuk's ass with spitballs
 so true . . . sad but true
[20:44] <valorie> shot out of machine guns
[20:44] <valorie> lol
 we get passionate because we believe our view best approximates either the platonic ideal, or what our users would prefer (depending on our personalities)
 if it were possible to do actual user and usability testing, we could get hard answers instead of just spitballing
 which would de-militarize these kinds of discussions
[20:46] <acheronuk> KDE can't have it both ways. that we are not their (unofficial ref distro), and object to changing our defaults
 we could say, "our research shows that approach X results in users being able to perform the task 43% of the time, after an average of 57 seconds for those who have succeeded; with approach Y, it's 79% and 20 seconds"
[20:47] <tsimonq2> Upstream KDE is objecting to Kubuntu changing *our* defaults?
[20:47] <tsimonq2> :/
[20:47] <tsimonq2> C'moooooooooooonnnnnnnnnnnnnnnnn
 only one guy, but yes
 @nggraham, Ubuntu might have a solution for that data :)
[20:47] <tsimonq2> Ah ok
 I mean, RHEL adds a task manager and a start menu to GNOME for pete's sake
 @nggraham, well Red Hat funds GNOME so they can ignore whatever GNOME does anyway lol
 when you provide the money they cant really complain much lol
 RHEL is really, really good. We need to aspire to that level of awesome in the KDE world IMHO
[20:49] <acheronuk> also as I said earlier, if I implement all the changes I can via a "Kubuntu look-and-feel package", then I will be leaving the stock defaults intact ;)
[20:49] <acheronuk> which people could switch back to in a few clicks
 +1
 of course nobody will because most users don't care, which is fine, and why we have our own set of defaults
[20:50] <acheronuk> yup
 @acheronuk, sneaky sneaky :)
[20:50] <valorie> this is why we love our Rik
 (Document) https://irc-attachments.kde.org/mjYP1R2x/file_5165.mp4
 stickers work in IRC iirc but do gifs?
[20:58] <valorie> it downloads and plays when I click the play arrow
 ahh thats not bad
 so I mentioned this to Rik on my live stream but forgot to mention it here.
 I'd like to make a promo video for Kubuntu 18.04 like I do for KDE Plasma. Especially with all the new stuff in Kubuntu coming . . . especially with all the UX stuff being fixed. I can hype this so well. :)
[21:08] <valorie> on the plus side, after reading more of this debate, it's great to see KDE folks weighing in on Kubuntu's process here
[21:08] <valorie> kudos for everybody engaging
 nice to see them acknowledge us as a heavyweight, too :)
 @MichaelTun, Teal'c works everywhere :)
 (Sticker, 512x512) https://irc-attachments.kde.org/ygi6XXn3/file_5166.webp
[22:13] -kubuntu-ci:#kubuntu-devel- Project merger_kdepim-addons build #541: FAILURE in 6.9 sec: https://kci.pangea.pub/job/merger_kdepim-addons/541/
[22:13] <valorie> ok, thought for awhile and commented on Nate's second thread
[22:14] <valorie> and now, outside to the sunlight!
[22:21] -kubuntu-ci:#kubuntu-devel- Project merger_spectacle build #630: FAILURE in 6.3 sec: https://kci.pangea.pub/job/merger_spectacle/630/
[22:29] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:29] -kubuntu-ci:#kubuntu-devel- Project merger_spectacle build #631: FIXED in 12 sec: https://kci.pangea.pub/job/merger_spectacle/631/
[22:29] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:29] -kubuntu-ci:#kubuntu-devel- Project merger_kdepim-addons build #542: FIXED in 13 sec: https://kci.pangea.pub/job/merger_kdepim-addons/542/
[22:30] -kubuntu-ci:#kubuntu-devel- Project mgmt_pause_integration build #126: ABORTED in 2 hr 16 min: https://kci.pangea.pub/job/mgmt_pause_integration/126/
 Sun-whatnow?
[23:20] <valorie> I know!
[23:20] <valorie> but my husband is home today so I roped him into doing most of the digging for transplanting a couple of ferns
[23:20] <valorie> all done now! \o/
 is phab be slow?
[23:21] <valorie> and it will rain tomorrow, so yay
 slow as in, not loading!
 yeah, it's dead right now
 oh well
 @nggraham ping on here if you get to test that iso while it's not back
 11:30 ish pm here, so i'll not 😴 soon
 wish I could; I'm in a bus with metered internet at the moment. I'll be able to do it in probably 3 hours
 hopeuflly I'll have a result for you when you wake up!
 @nggraham, no worries. :)


[05:40] <didrocks> good morning
[06:05] <oSoMoN> good morning desktoppers
[06:08] <duflu> Morning didrocks and oSoMoN
[06:13] <didrocks> salut oSoMoN, hey duflu
[06:25] <oSoMoN> hey duflu
[06:25] <oSoMoN> salut didrocks
[07:27] <ricotz> good morning :)
[07:27] <ricotz> hey oSoMoN duflu didrocks
[07:27] <oSoMoN> good morning ricotz
[07:33] <duflu> Hi ricotz
[07:52] <KGB-0> libhandy-1 upstream/latest bddedca Jeremy Bicha * pushed 7 commits (first 5 follow) * https://deb.li/KZMA
[07:52] <KGB-0> libhandy-1 upstream/latest 8325e44 Luming Zh po/zh_CN.po * Update Chinese (China) translation * https://deb.li/3sO2x
[07:52] <KGB-0> libhandy-1 upstream/latest 8dc9496 Sabri Ünal po/ LINGUAS tr.po * Add Turkish translation * https://deb.li/COfy
[07:52] <KGB-0> libhandy-1 upstream/latest fb3ba77 Alexander Mikhaylenko src/hdy-settings.c * settings: Remove a superfluous debug message * https://deb.li/3cci4
[07:52] <KGB-0> libhandy-1 upstream/latest 02128e3 Alexander Mikhaylenko .gitlab-ci/check-abi * ci: Fix check-abi meson options * https://deb.li/6ZBM
[07:52] <KGB-0> libhandy-1 upstream/latest 2014860 Maximiliano src/hdy-deck.c * deck: Remove navigatable mention * https://deb.li/iwVhj
[08:03] <KGB-0> libhandy-1 pipeline Jeremy Bicha 402154 * [12 minutes and 4 seconds] failed (extract-source: success; build: success; build i386: success; build source: success; test-build-any: success; test-build-all: success; test-crossbuild-arm64: failed; reprotest: success; lintian: success; autopkgtest: success; blhc: success; piuparts: failed)
[08:07] <seb128> goood morning desktopers!
[08:07] <duflu> Hi seb128
[08:07] <seb128> hey duflu, how are you today?
[08:08] <duflu> seb128, awful sinus headache but I have managed to rebuild and replace my development machine already
[08:08] <duflu> How are you?
[08:11] <seb128> :-(
[08:11] <seb128> I'm doing alright, it should be a bit less warm today!
[08:20] <didrocks> hey seb128, ricotz
[08:40] <seb128> lut didrocks, en forme ?
[08:45] <didrocks> seb128: ça va, il faut toujours chaud et c’est pas près de s’arrêter, mais -4 par rapport à hier, on prend :p
[08:45] <didrocks> et toi ?
[08:47] <seb128> un peu pareil, pas d'orage pour le moment, y a eu 3 min de 'pluie' mais c'est tout pour le moment, c'est plus humide et presque aussi chaud et donc limite plus pénible :-(
[08:47] <didrocks> je devrais bosser dehors, je pense que ce serait plus agréable à l’ombre que dedans
[08:48] <seb128> un peu d'air au moins?
[08:48] <didrocks> non, aucun vent ici
[08:49] <seb128> :-(
[09:05] <seb128> lissyx, the debug handling in launchpad has been rolled out in production now
[09:06] <seb128> I tried https://git.launchpad.net/~seb128/gnome-logs/commit/?id=97038349 as a small hackish try and it works
[09:06] <seb128> https://launchpad.net/~seb128/+snap/gnome-log-debug/+build/1825356 , it's missing in the version in the name but worked
[09:42] <lissyx> seb128, nice!
[09:42] <lissyx> seb128, can we move forward with my PRs now then?
[09:42] <lissyx> everything is ready on our side, and it's now just missing data on launchpad library to ensure it all works
[10:12] <oSoMoN> jamesh, seb128: good news on the native messaging portal front: https://github.com/flatpak/xdg-desktop-portal/pull/705#discussion_r925427763
[10:12] <enyc> seb128: hrrm is that xserver-xorg-video-radeon fix https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1970473 going to be released around about 'today' ? -- 7 days up?  or does it need somebody to prod it / SRU checks elsewhere?
[10:13] <enyc> just be useful to know for ref
[10:14] <oSoMoN> jamesh, would you mind updating your PR with the missing initialization of session->standard_error ? I will then update the distro patch and SRU it
[10:28] <enyc> auto-released, I should say ?? ^^
[10:35] <seb128> oSoMoN, ah, great news! could you SRU the fix today so we have a chance to get it still in .1?
[10:35] <seb128> ah, you just mentioned that :p
[10:36] <seb128> enyc, it's verified and aged so should be moved whenever a SRU team member does their shift but you can also ping them to make sure it's done, sometime they are busy and skip shifts
[10:37] <seb128> enyc, it's r_basak on duty today according to the wiki
[10:39] <enyc> seb128: where ;O
[10:39] <enyc> i mean where is r_basak :O
[10:41] <seb128> enyc, usually #ubuntu-release is the right channel for such requests
[10:42] <seb128> but Robie is also here, which is why I added the _ in the middle of his name to having bothering him :)
[10:42] <seb128> I should perhaps just have pinged him now
[10:42] <enyc> thankyou  not tryingto be impaitent just want to report in other bugs downstream etc
[10:43] <seb128> lissyx, yes we can move forward with the changes now
[12:17] <enyc> seb128: r-basak released update with polite nudge and in other tasks now =) useful as I can ref.
[12:18] <seb128> enyc, great, thanks for pushing for the fix!
[12:18] <enyc> seb128: I wonder if duflu ever got the crashlog they wanted
[12:18] <enyc> they keep logging off ><
[12:19] <oSoMoN> enyc, it's past EOD for du_flu
[12:21] <enyc> oSoMoN: maybe so :O
[12:22] <enyc> still grr ;o
[12:22] <enyc> hard to leave them msg if they don't have irssi in screen etc ;o
[13:07] <lissyx> oSoMoN, I hope you got some nice time off even with the heat :)
[13:15] <oSoMoN> lissyx, I did, thanks!
[13:16] <lissyx> oSoMoN, so do you think you can do some test runs on all my PRs ?
[13:20] <oSoMoN> lissyx, yes, that's on my to-do list, let's see if I can get to it today
[13:21] <lissyx> would be very welcome
[13:28] <lissyx> oSoMoN, btw there are many pending needinfo :)
[13:33] <lissyx> seb128, oSoMoN, there's no activity on https://github.com/flatpak/xdg-desktop-portal/issues/831 and https://github.com/flatpak/xdg-desktop-portal/issues/463
[13:34] <lissyx> do you know how we could push it a bit?
[13:34] <lissyx> I could make the fixes if I'd knew what was expected
[13:44] <KGB-0> gnome-software ubuntu/jammy 93ec47b David Mohammed debian/changelog * Add space in launchpad changelog reference * https://deb.li/3HgBV
[14:12] <KGB-0> gnome-software ubuntu/jammy d8796e3 Jeremy Bicha debian/gbp.conf * Update one more Vcs field * https://deb.li/ikPrC
[14:12] <KGB-0> gnome-software ubuntu/jammy 1a70cf4 Jeremy Bicha debian/changelog * releasing package gnome-software version 41.5-2ubuntu2 * https://deb.li/t3ig
[14:12] <KGB-2> gnome-software signed tags fcf9165 Jeremy Bicha ubuntu/41.5-2ubuntu2 * gnome-software Debian release 41.5-2ubuntu2 * https://deb.li/3rPcl
[15:05] <seb128> lissyx, we raised the lack of active maintainer / reviews issue with some of contacts but it got sort of stucked and Ken who was doing the nagging is returning for VAC tomorrow so I will see with him if he has ideas of how we can unblock those
[15:06] <lissyx> right


[12:27] <elacheche> o/
[13:43] <pavlushka> o/
[13:44] <pavlushka> elacheche: is it possible to redirect https://wiki.ubuntu.com/shani page to https://wiki.ubuntu.com/ZeeshanSaeedParacha? coz both are same person.
[13:45] <pavlushka> and i know that https://wiki.ubuntu.com/knome redirects to https://wiki.ubuntu.com/PasiLalinho
[13:49] <elacheche> yeah you can pavlushka
[13:49] <elacheche> just asec
[13:49] <pavlushka> you mean?
[13:49] <elacheche> Na3iL: here are the answers of yesterday questions → https://www.reddit.com/r/sysadmin/comments/4y46zb/try_ssh_hackintosysengquiz3host_for_some/d6m92ml & https://www.reddit.com/r/sysadmin/comments/4y46zb/try_ssh_hackintosysengquiz3host_for_some/d6pblf0
[13:49] <elacheche> pavlushka: just asecond I'll get the code for you
[13:49] <elacheche> :)
[13:50] <pavlushka> aha, ok
[13:50] <elacheche> pavlushka: so, https://wiki.ubuntu.com/elacheche_anis REDIRECT TO https://wiki.ubuntu.com/elacheche
[13:51] <elacheche> In https://wiki.ubuntu.com/elacheche_anis I just write this code: #refresh 0 elacheche
[13:51] <elacheche> #refresh 0 elacheche
[13:51] <pavlushka> yep, just like that
[13:51] <elacheche> and it'll do the job
[13:54] <Na3iL> o/ elacheche pavlushka
[13:55] <pavlushka> o/ Na3iL
[13:55] <pavlushka> thanks elacheche , it worked :)
[13:55] <pavlushka> brb
[13:55] <Na3iL> yep it is the endless power of python :)
[13:56] <elacheche> :D
[15:46] <elacheche> Na3iL: Do you think that will be able to not contribute to the next sfd as organizers? That way we can focus on our LoCo? :/
[15:48] <Na3iL> elacheche, believe me that's what I was thinking when I saw some mails in the SFD's ML
[15:49] <Na3iL> although, I think we can contribute in the SFD and in the meanwhile we can focus on our LoCo
[15:49] <Na3iL> What you think?
[15:51] <elacheche> Didn't work last year Na3iL.. :/ Remember?
[15:52] <Na3iL> Yep, we were thinking that there will be other old members..
[15:55] <elacheche> There were others, but they was prefering to attend the talks instead of staying @our stand.. This year, if I'm not an organizer, I'll will ignore some talks and stay @our stand.. I did it before, I can do it over and over..
[15:59] <Na3iL> yep, and you will not be alone.
[16:00] <elacheche> I know that ;)
[16:00] <elacheche> Tell me, are you stuck in that quiz?
[16:01] <Na3iL> haha, I saw your mail, nope I just got busy with some clients in France and I am trying hard to keep some free time to solve it
[16:02] <Na3iL> A lot of resources there to learn new stuff! :D
[16:02] <elacheche> Oh! Great :D Happy for you :D You should pass that quiz, then tell Amine that the company should do the same to find good profiles :p ;)
[16:04] <Na3iL> Good idea! :D
[16:05] <Na3iL> Talking about SFD, the website is down I think
[16:05] <elacheche> That quiz is required to apply for a job in that company, so they make sure that no one will apply without having the minimum skills..
[16:06] <elacheche> I thought about doing the same once, but I planned to keep it internal, I like the challenge to open it x)
[16:06] <elacheche> which one?
[16:06] <Na3iL> Aw! that would be great! :D I would like to help on creating the quiz
[16:06] <Na3iL> sfd.tn
[16:07] <elacheche> Yeah, the whole server down :/ I'm chekcing it
[16:08] <Na3iL> Oh! good luck
[16:10] <elacheche> Can't do anything, dedicated server down.. I contacted ATI.. I hope we're fine :/
[16:11] <Na3iL> hope that too!
[16:21] <Na3iL> elacheche, the question 2 in stage 2, how much requests per minute the webserver can handle.. Is there any formula to calculate it, cause I know in such situation you should have a toold that will play like load balancer
[16:21] <Na3iL> and tests the approximations of requests that such server can handle
[16:21] <Na3iL> only a small hint, I don't like to get the answers directly x)
[16:23] <elacheche> I asked the same question to the creator.. I'll send you the hint that he told me in private.. But before try to find it your self.. Just keep it simple, very simple KISS ;)
[16:24] <Na3iL> hahaha okay 1 sec


[00:29] <xivulon> https://code.launchpad.net/~ago/partman-auto-loop/lupin-support
[01:15] <Torgoton> Hey all. I managed to get Ubuntu to start to install on my ancient laptop. Gutsy kernel crashed every time, but Dapper started the process ok, if VERY slow.
[01:16] <Torgoton> Would that be an installer issue, or a kernel issue?
[01:19] <CarlFK> Torgoton: "start to install" = installing stuff to HD or just booting the installer ?
[01:19] <Torgoton> just booting the installer, CarlFK.
[01:21] <Torgoton> that is, starting the installer crashes with Gutsy Mini ISO/netboot files (linux and initrd.gz) but the Dapper version starts fine.
[01:21] <CarlFK> what about the 'check cd" ?  (which also boots a kernel
[01:21] <CarlFK> ah, that kinda boot
[01:22] <Torgoton> Yeah. This is a very old 33MHz 486 with 36MB RAM. No CD, no USB.
[01:22] <CarlFK> sounding like an installer
[01:22] <CarlFK> wow
[01:22] <Torgoton> yeah!
[01:22] <CarlFK> pretty sure 48 is the minimum
[01:23] <Torgoton> wow is an understatement. "Installing the base system" has been going for something like 5 hours.
[01:23] <Torgoton> There's a page that says 32MB is the minimum... looking for it....
[01:23] <CarlFK> im surprised the HD is big enough :)
[01:24] <Torgoton> heh. The drive that came with the machine is 170MB, but it now has a 5GB drive.
[01:24] <Torgoton> Here it is: https://help.ubuntu.com/community/Installation/SystemRequirements
[01:25] <Torgoton> The end has Absolute minimum requirements: 486, 32MB RAM, 300MB disk.
[01:25] <CarlFK> um, thats not what I see...
[01:25] <CarlFK> oh wait.. that end
[01:25] <Torgoton> yea.
[01:26] <CarlFK> Whats a "graphical installation" ?
[01:26] <Torgoton> I imagine that's one including the X Window System.
[01:26] <Torgoton> or maybe... graphical installation.
[01:27] <CarlFK> 300 isn't enough, cuz 350 gets used during the install
[01:27] <Torgoton> Yeah. That must be it. I'm doing a text install. Over a serial port, actually.
[01:27] <CarlFK> I have a feeling the 32m is out of date too
[01:27] <Torgoton> Would you like to see the debug dump from my attempt with Gutsy?
[01:28] <CarlFK> heh - I have a 32m stick I have been using to debug a cpu speed problem... just a sec
[01:28] <CarlFK> sure
[01:28] <Torgoton> http://paste.ubuntu-nl.org/48887/
[01:33] <cjwatson> kernel crash => kernel issue
[01:34] <cjwatson> you're still using the generic kernel though
[01:34] <CarlFK> will now that you put it that way :)
[01:34] <cjwatson> you sure you're using the 386 build I pointed you to? that should be built against the -386 kernel, not -generic
[01:34] <Torgoton> That is using the two files from the Gutsy Mini ISO.
[01:34] <cjwatson> there are multiple gutsy mini.iso builds
[01:35] <Torgoton> aha!
[01:35] <cjwatson> in /msg, I pointed you to http://archive.ubuntu.com/ubuntu/dists/gutsy/main/installer-i386/current/images/netboot/386/mini.iso
[01:35] <cjwatson> the /386 in there is significant - you may have missed it
[01:35] <Torgoton> yes you did. I thought I tried that one as well, but will try again to be triply sure. <sigh> Time to stop the current install... five hours into it. :)
[01:36] <cjwatson> you're definitely using something built with the -generic kernel - either netboot/386/mini.iso is misbuilt, or you picked the wrong one :)
[01:36] <cjwatson> (not saying the former ain't possible)
[01:37] <cjwatson> for the record, I think 36MB RAM should work fine in gutsy, though you may get kicked into lowmem mode
[01:37] <cjwatson> should actually be rather faster than dapper, at least the installer side of things
[01:37] <cjwatson> we did some serious memory work in d-i over the summer, which shaved off 16MB+
[01:37] <CarlFK> Torgoton: what media are you booting from?
[01:38] <Torgoton> booting from hard drive, using Lilo to load the image. Woody is installed on the machine.
[01:38] <CarlFK> neat :)
[01:39] <Torgoton> thanks.
[01:39] <Torgoton> ok it's going to take a few minutes to set up.
[01:39] <CarlFK> you might want to try kexec
[01:40] <CarlFK> wget linux/initrd.gz, use kexec to boot them
[01:40] <cjwatson> kexec from a woody kernel?
[01:40] <cjwatson> probably won't work so well
[01:40] <CarlFK> why would it matter?
[01:41] <Torgoton> I've never heard of kexec before.
[01:41] <CarlFK> assuming it works at all..
[01:42] <Torgoton> holy crap! X started!
[01:42] <Torgoton> it never worked before, and it's not pretty. 320x200x1.
[01:43] <cjwatson> CarlFK: the kexec syscalls didn't exist in the woody kernel
[01:43] <cjwatson> kexec is a relatively recent thing
[01:43] <CarlFK> http://dpaste.com/28713/
[01:43] <cjwatson> as regards disk space, a debootstrap of gutsy takes up 210MB or so
[01:43] <CarlFK> ah, so much for that idea
[01:44] <cjwatson> the standard task is another 51MB
[01:45] <Torgoton> getting the *386* mini iso...
[01:46] <cjwatson> kexec was merged into Linux in 2.6.13
[01:46] <cjwatson> woody had, er ...
[01:46] <Torgoton> 2.2.20
[01:47] <cjwatson> or 2.4.18
[01:47] <cjwatson> but either way, certainly no dice
[01:48] <Torgoton> so should I use lilo or try kexec?
[01:48] <cjwatson> don't bother with kexec, it won't work
[01:48] <Torgoton> ok. booting...
[01:50] <Torgoton> crash
[01:51] <Torgoton> http://paste.ubuntu-nl.org/49098/
[01:51] <cjwatson> ok, it's at least the right kernel this time
[01:52] <Torgoton> baby steps...
[01:52] <cjwatson> it's having trouble trying to set up the right MMU bits for your machine
[01:52] <cjwatson> alternative_instructions is pretty fundamental
[01:52] <Torgoton> The CPU is a 486SL, if it matters.
[01:52] <Torgoton> I think... :)
[01:53] <cjwatson> this is way out of my field, and squarely in the kernel team's turf
[01:53] <Torgoton> Yep, 33MHz 486SL
[01:53] <Torgoton> Hm. Would it still be an Ubuntu issue?
[01:53] <cjwatson> could be, since it seems to be in the paravirt_ops stuff
[01:54] <cjwatson> which IIRC is something we took as an external patch, though I may misremember and it could be it's mainline now
[01:54] <cjwatson> subject to timezone and holiday vagaries, #ubuntu-kernel should be able to help more
[01:54] <cjwatson> and speaking of timezones, I have to go to bed now
[01:54] <cjwatson> good luck :)
[01:55] <Torgoton> Thanks so much, cj and carl.
[01:57] <CarlFK> qemu with 32m says it isn't enough
[02:00] <CarlFK> 38 is ok, but low mem mode
[06:57] <banyao> hello
[06:58] <banyao> I am new
[06:58] <banyao>   8-)
[11:04] <xivulon> cjwatson, I have added a banch to partman-auto-loop, I hope that simplifies handling of a couple of patches
[11:06] <xivulon> I also need to patch partman/commit.d/*format_* since in case of loopfiles they format the containing device as opposed of the loopfile
[11:07] <xivulon> that though seems scattered around
[11:08] <cjwatson> yeah
[11:09] <cjwatson> thanks for the branch
[11:10] <xivulon> what is a good place to submit such patch(es)?
[11:11] <xivulon> commit.d/50format_ext3 for instance
[11:12] <xivulon> in partman_auto_loop I still have not figured out a good way to skip disk-free-space checks, it's left as TBD
[11:13] <cjwatson> branches intended to be merged should usually have an associated bug that refers to the branch
[11:14] <xivulon> Is that "propose for merging"?
[11:16] <xivulon> and/or  link to bug report?
[11:16] <xivulon> I'll use both
[11:17] <xivulon> done
[11:25] <xivulon> cjwatson where should I add a branch for patches against update_grub and /lib/partman/commit.d/50format_*
[11:26]  * xivulon likes LP
[11:27] <cjwatson> update-grub is in the grub package
[11:27] <cjwatson> it is not in bzr so you cannot add a branch
[11:27] <cjwatson> use diff -u and attach the output
[11:28] <cjwatson> there is no one branch you can use for commit.d/50format_*
[11:28] <cjwatson> several different packages are involved
[11:28] <xivulon> I have diff at the moment plus patched file to be diffed (forgot to do diff -u yesterday)
[11:28] <cjwatson> you don't really need to show patches for all of them though, they're all the same and I can just duplicate it across
[11:28] <xivulon> what's a good place to submit such patches?
[11:29] <cjwatson> pick one of the packages
[11:29] <xivulon> ok
[11:32] <xivulon> I can add a branch in https://code.launchpad.net/partman-ext3/
[11:43] <xivulon> bug 177868
[11:43] <ubotu> Launchpad bug 177868 in partman-ext3 "When loopfiles are used mkfs has to target the file and not the containing device" [Undecided,New] https://launchpad.net/bugs/177868
[12:07] <xivulon> cjwatson can you please remind evand to follow up with https://bugs.launchpad.net/wubi/+bugs?field.tag=wubi ?
[12:10] <cjwatson> no, because he's on holiday until the new year
[12:10] <xivulon> aha I tried to contact him yesterday night
[12:10] <xivulon> np
[12:10] <xivulon> ps yesterday I had this error in grub-installer, did not have time to dig further, does the syslog ring any bell?
[12:11] <xivulon> http://paste.ubuntu-nl.org/49146/
[12:13] <cjwatson> no, sorry, there doesn't seem to be a lot to go on there
[12:14] <xivulon> np, I'll do new runs in more verbose mode, that happened late yesterday and had a hard time keeping the eyelids up
[12:15] <xivulon> have to go now, have a nice holiday everyone!
[14:24] <CarlFK> how can I pass this as a kernel parameter? tasksel tasksel/first multiselect ubuntu-standard, ubuntu-desktop
[14:25] <cjwatson> I'm not convinced you can
[14:25] <CarlFK> is this worth trying: tasksel/first=ubuntu-standard,ubuntu-desktop
[14:25] <cjwatson> not without bug 174557 being fixed
[14:25] <ubotu> Launchpad bug 174557 in tasksel "tasksel/first preseed syntax is inconvenient" [Wishlist,Triaged] https://launchpad.net/bugs/174557
[14:25] <cjwatson> no, that won't work unfortunately
[14:26] <cjwatson> can't you use a preseed file?
[14:26] <CarlFK> yes, but I was trying to only have 1 file
[14:26] <cjwatson> (it would have to be tasksel:tasksel/first=blah anyway, but still won't work due to tasksel splitting the value on ", "
[14:26] <cjwatson> )
[15:17] <CarlFK> i think this worked: tasksel:tasksel/first="ubuntu-standard, ubuntu-desktop"
[15:17] <CarlFK> Dec 21 14:33:26 frontend: --> SET tasksel/first ubuntu-standard, ubuntu-desktop
[15:54] <CIA-22> netcfg: cjwatson * r618 ubuntu/ (base-installer debian/changelog netcfg-common.c):
[15:54] <CIA-22> netcfg: * Add an /etc/network/interfaces stanza for lo even if the netcfg menu
[15:54] <CIA-22> netcfg:  item wasn't run (LP: #9532).
[15:56] <CIA-22> netcfg: cjwatson * r619 ubuntu/debian/changelog: releasing version 1.40ubuntu3