[05:32] <pitti> Godo morning
[05:55] <jibel> Good morning
[08:21] <om26er> ubuntu-qa does unity crash for you when you open a local song's preview
[08:21] <pitti> om26er: you just copy some .ogg or .mp3 to ~/Music/ ?
[08:21] <om26er> its like a 100% reproducible crash for me. I have the crash file in /var/crash but seems I cannot report the bug due to some reason
[08:21] <om26er> pitti, yes mp3
[08:23] <om26er> seems the crash is in qt itself
[08:24] <jibel> om26er, no crash on mako #99
[08:24] <om26er> jibel, All I did was flash 98 and then update to 99 from the update manager.
[08:24] <om26er> I have changed nothing else :/
[08:25] <jibel> om26er, do you have any specific steps to reproduce. I tried preview, play, switch back and forth to scope, switch between songs and no crash so far
[08:25] <om26er> pitti, can I report a crash from my desktop using a crash file from the phone ?
[08:25] <pitti> $ system-image-cli -i
[08:25] <pitti> FileNotFoundError: [Errno 2] No such file or directory: '/var/log/system-image/client.log'
[08:25] <pitti> WTH
[08:25] <pitti> I just flashed this morning
[08:25] <jibel> om26er, you can, you need to collect info on the pohne first
[08:26] <om26er> jibel, I just open the preview and it hangs and eventually vanishes
[08:26] <jibel> om26er, with apport-cli <crash file>
[08:26] <pitti> om26er: I scp -r'ed an album to ~/Music/, now I see it on the leftmost unity page
[08:26] <pitti> I can tap on one, and it starts playing
[08:27] <pitti> i. e. I see the album cover
[08:27] <om26er> pitti, if you press and hold on it. it will open its preview
[08:27] <om26er> jibel, I tried apport-cli it get this http://paste.ubuntu.com/6244481/
[08:27] <pitti> om26er: WFM
[08:27] <om26er> *i
[08:28] <pitti> om26er: you need to press "v" to collect data, then "s"
[08:28] <pitti> next/prev doesn't work here, tohugh
[08:31] <om26er> pitti, I pulled the crash file to my desktop and reported the crash with ubuntu-bug <crash_file> that worked
[08:31] <om26er> bug 1240408
[08:32] <pitti> om26er: right, as long as you collect information locally on the phone
[08:32] <pitti> om26er: with the same approach I just reported bug 1240400
[08:32] <pitti> I can make dialer-app crash easily by receiving a phone call
[08:33] <om26er> that looks like a mir crash as well :/
[08:34] <rhuddie> anyone else notice that you can't close an app by long pressing on it? I'm on build 99
[08:34] <pitti> om26er: yes
[08:34] <pitti> Ubuntu 13.10 - armhf (20131015.2)
[08:34] <pitti> which build is that?
[08:34] <pitti> (I flashed devel-proposed this morning)
[08:34] <om26er> rhuddie, you have to tap on the close icon now.. not the entire thumbnail. I contributed that fix ;)
[08:34] <pitti> but system-image-cli doesn't work
[08:34] <om26er> pitti, 99
[08:35] <pitti> /var/log/system-image/ doesn't exist at all here
[08:35] <rhuddie> om26er, ok thanks for clarification!
[08:35] <pitti> it seems it gets removed on reboot or so
[08:35] <pitti> om26er: thanks
[08:40] <om26er> pitti, hey! I need to mock evolution data server to test address-book-app I have not looked into it much but do you think python-dbusmock will help ?
[08:40] <pitti> om26er: that's what it is meant for indeed
[08:41] <pitti> om26er: we don't have an existing template for e-d-s in dbusmock, it seems nobody mocked e-d-s before
[08:41] <pitti> om26er: but I guess you only need a small subset of its D-BUS API
[08:42] <om26er> pitti, yeah only need to save and delete a contact, and probably update
[08:42] <pitti> ok, the API doesn't look *that* big
[08:44] <jibel> pitti, I reported several "__GI___pthread_mutex_lock" and they've all been marked as duplicate of bug 1233988
[08:45] <pitti> jibel: ah, thanks; retracer got me https://launchpadlibrarian.net/153888313/Stacktrace.txt which looks quite reasonable; I'll compare
[08:46] <pitti> jibel: ah, it's very similar; I'll dupe it
[08:46] <pitti> jibel: but it says "Mir fix released", apparently there's still something missing?
[08:48] <pitti> jibel: I do have that mir version
[08:49] <pitti> jibel: ah, your crash is a SIGABRT, I have a SEGV
[08:49] <jibel> pitti, right, I don't really understand why they set the status to "fix released", this bug has already been reopen once, that'd need discussion with Saviq IMO
[08:49] <jibel> ah okay
[08:49] <jibel> 0.19+13.10.20131015.1-0ubuntu1 is on 99
[08:50] <jibel> same version
[08:51] <pitti> jibel: I'll look back into the messaging-app tests on amd64; it indeed looks like the tests get skipped
[08:53] <rbasak> pitti: around? I think autopkgtest 2.3.7 is still regressed wrt. stdout/stderr handling and bug 1235189, though it doesn't completely fail now. It still isn't giving me test output on failure.
[08:54] <rbasak> pitti: http://paste.ubuntu.com/6244581/ - from 2.3.3. http://paste.ubuntu.com/6244585/ - from 2.3.7.
[08:54] <pitti> rbasak: how does it fail now? In trunk I recently fixed something there
[08:55] <pitti> rbasak: I fixed a bug with the -schroot runner, but that resulted in an OSError crash on mkfifo() when running adt-run as non-root
[08:55] <pitti> so it looks like it's something else
[08:55] <Saviq> pitti, jibel, it aborts 'cause Mir is not yet ready
[08:56] <rbasak> I'm going to see how far I get today with adt-virt-lxc fixes from jibel's review. Hopefully I can get them all done and land it. Then everyone will be able to test against lxc more easily.
[08:56] <pitti> rbasak: but would you mind re-trying with git head? (git://git.debian.org/git/autopkgtest/autopkgtest.git)
[08:56] <Saviq> pitti, jibel although that stacktrace should contain a qFatal() now
[08:56] <rbasak> pitti: sure, I'll try now.
[08:56] <Saviq> pitti, jibel, we're fixing unity8/unity-mir/mir to notify upstart when we're ready, so that maliit doesn't start too early
[08:56] <pitti> rbasak: right, and let's fix that stdout/err regression too
[08:56] <Saviq> pitti, jibel, if you see SIGABRT from maliit, ignore for now
[08:57] <pitti> Saviq: that is for #1233988?
[08:57] <Saviq> bug #1233988
[08:57] <Saviq> pitti, yes
[08:57] <pitti> Saviq: ack
[08:58] <pitti> rbasak: I suppose if you run that test with -null you do get stderr?
[08:58] <jibel> Saviq, we were talking about bug 1240400, does dialer-app crashes for the same reason?
[08:59] <pitti> Saviq, jibel: that looks different; 5 tests before work fine, and Mir is definitively read
[08:59] <pitti> y
[08:59] <jibel> ok
[08:59] <pitti> and it's a segfault, not an abort
[09:00] <pitti> and dialer-app doesn't involve maliit, too
[09:00] <Saviq> pitti, yeah, different
[09:01] <rbasak> pitti: still no stderr with lxc and git HEAD: http://paste.ubuntu.com/6244602/. Trying null next.
[09:01] <jibel> Saviq, so why bug 1239522 as been marked as dupe of 1233988
[09:01] <jibel> ?
[09:01] <pitti> rbasak: ok, thanks for verifying
[09:02] <jibel> *has
[09:02] <Saviq> bug #1239522
[09:02] <Saviq> ubot5, ping?
[09:02] <Saviq> grr
[09:04] <jibel> the bot shows the master report, and it is lazy and won't show it again because it already did it few minutes ago
[09:04] <pitti> rbasak: I have explicit tests for -null and -chroot runners for stderr output; I manually tested with schroot, but I suppose lxc is plumbed differently, so I guess the logic is buggy for that
[09:05] <rbasak> pitti: I've been wondering about the practicality of adding lxc tests (once it's landed of course). It'll need to hit cloud-images.u.c; that's OK, right?
[09:06] <Saviq> jibel, not sure, they do look different to me, but maybe had the same underlying cause
[09:07] <pitti> rbasak: for autopkgtest perhaps, but running the test suite locally should be really quick
[09:07] <pitti> rbasak: for the -chroot tests I build a mini-chroot
[09:07] <pitti> rbasak: perhaps that suffices for lxc as well
[09:08] <slickymaster> morning all
[09:08] <rbasak> pitti: how about if the lxc test only runs if a suitable lxc container is already defined? Then it is really quick.
[09:08] <pitti> rbasak: that sounds fine
[09:09] <pitti> rbasak: I might do something similar for the -schroot runner (I use that for e. g. postgresql testing)
[09:09] <rbasak> pitti: IMHO, in the end we should all be using the lxc runner for speed, and the kvm runner for accuracy. None of it is ready yet of course.
[09:10] <pitti> *nod*
[09:10] <pitti> rbasak: well, run-adt-test kind of provides a KVM runner (except "inside out"), it just lacks the "revert-testbed" part
[09:10] <jibel> rbasak, couldn't we create a libvirt driver instead, so we'd have the same interface for lxc and kvm?
[09:12] <rbasak> jibel: sort of. I have plans in this area. My tool "uvtool" now in universe is a front-end for libvirt and Ubuntu. I intend for it to include an lxc wrapper with a similiar interface (so there is a common interface for non-backend-specific features)
[09:20] <rbasak> pitti: the null driver works as expected on git HEAD with my test: http://paste.ubuntu.com/6244672/. I noticed it was giving real-time output as designed too.
[09:20] <pitti> rbasak: oh, but no stderr
[09:21] <rbasak> pitti: the set +x output is there which is stderr, but isn't tagged as such. I'm not sure what your intention is there.
[09:23] <pitti> rbasak: ah right, it doesn't currently show stderr explicitly for rc != 0
[09:23] <pitti> rbasak: I think that's ok
[09:23] <pitti> for -null anyway, but it doesn't sound right for runners which don't have real-time output
[09:23] <pitti> rbasak: I'll look into that
[09:23] <rbasak> Thanks!
[09:29] <pitti> rbasak: hah, in fact I just ran into that when writing some schroot runner tests
[09:29] <rbasak> :)
[09:29] <pitti> ah no, it's missing stdout
[10:00] <pitti> rbasak: ok, I think I can reproduce this with the schroot runner, too; does your lxc container have /tmp bind-mounted?
[10:11] <pitti> rbasak: I pushed a fix for missing out/err
[10:12] <pitti> rbasak: and I added a test suite for the schroot runner with the "specify existing schroot" approach; the same ought to work for your lxc runner, so you can more or less just copy&paste the schroot test and adjust the environment variable and the runner args accordingly
[10:12] <pitti> rbasak: mind testing current git?
[10:27] <davmor2> Morning all
[10:38] <rbasak> pitti: testing current git now.
[10:46] <rbasak> pitti: still not working on 2.3.7-8-gf963945: http://paste.ubuntu.com/6244970/
[10:47] <pitti> rbasak: mind running with -d?
[10:48] <pitti> rbasak: it should not use the teeing now
[10:48] <rbasak> pitti: if you can grab just the adt-virt-lxc from my branch, then you can quite easily run it yourself. Just "sudo lxc-create -t ubuntu-cloud -n adt -- -s daily -r saucy" and then "adt-run --gain-root=sudo ... --- /path/to/adt-virt-lxc --ephemeral adt".
[10:48] <rbasak> Sure I can run with -d. One minute.
[10:49] <pitti> rbasak: lxc-create is running
[10:50] <pitti> rbasak: did you actually call runner/adt-run from git? (or built/installed the pkg)
[10:50] <rbasak> pitti: http://paste.ubuntu.com/6244973/ for -d. Yes - I built and installed the package.
[10:50] <rbasak> $ md5sum /usr/bin/adt-run
[10:50] <rbasak> 327da15ec6b3efe0a47f9d663feb1b3a  /usr/bin/adt-run
[10:51] <rbasak> $ md5sum ~/autopkgtest/git/runner/adt-run
[10:51] <rbasak> 327da15ec6b3efe0a47f9d663feb1b3a  /home/ubuntu/autopkgtest/git/runner/adt-run
[10:51] <rbasak> Is that what you expect?
[10:51] <pitti> right, thanks
[11:17] <pitti> rbasak: running that now, but it seems to take ages; lsx-ls --fancy says "RUNNING" without IPV4/6", and no progress for several minutes
[11:17] <pitti> rbasak: is there a way to see what the container does?
[11:18] <pitti> rbasak: I am trying "sudo lxc-console -n adt-virt-lxc-lthfcu", but that doesn't do anything
[11:18] <pitti> i. e. it says "Connected to tty 1", but pressing enter doesn't give me a login prompt
[11:20] <rbasak> pitti: I use "sudo lxc-attach -n adt-virt-lxc-lthfcu -- ps ax"
[11:21] <pitti> uh, I got a new ephemeral instance now
[11:21] <rbasak> It creates one for every rollback
[11:21] <rbasak> eg. between build and every test
[11:21] <pitti> ah
[11:21] <pitti> so it perhaps just takes several minutes to boot
[11:21] <pitti> http://paste.ubuntu.com/6245102/
[11:22] <rbasak> That doesn't seem right.
[11:22] <rbasak> I think maybe your lxcbr0 isn't working for DHCP?
[11:22] <pitti> $ sudo lxc-attach -n adt-virt-lxc-iwapbe -- dmesg|pastebinit
[11:22] <pitti> http://paste.ubuntu.com/6245108/
[11:22] <pitti> rbasak: several apparmor denials
[11:22] <rbasak> Forget adt-virt-lxc. Let's test LXC on its own first.
[11:23] <pitti> yes
[11:23]  * pitti control-C's and then runs the lxc-destroy bits to clean up the temp container
[11:23] <rbasak> Try "sudo lxc-start-ephemeral -o adt -n foo"
[11:23] <rbasak> That gives me a login prompt in about five seconds.
[11:24] <pitti> conencted to tty1, not doing anything further visibly
[11:24] <rbasak> Ctrl-a then q to kill that then
[11:25] <pitti> yep, done that (that works)
[11:25] <pitti> http://paste.ubuntu.com/6245120/ is the dmesg for container start
[11:25] <rbasak> sudo lxc-clone adt foo and then we'll work on foo persistently
[11:25] <pitti> cloned
[11:26] <rbasak> I'm still waiting on mine :)
[11:26] <pitti> (I wish I could do all that in /tmp
[11:26] <rbasak> You can but the tools don't let you do it quickly/easily :-/
[11:26] <pitti> I only have a 10 GB root, but 16 GB RAM
[11:26] <pitti> too bad; schroot, kvm etc. all do that easily, and it's blazingly fast
[11:27] <rbasak> Now do lxc-start -n foo, but have another window ready
[11:27] <pitti> anyway, should I start foo?
[11:27] <rbasak> Right
[11:27] <rbasak> You get console output directly then
[11:27] <pitti> cloud-init-nonet[1414.27]: waiting 10 seconds for network device
[11:27] <pitti> cloud-init-nonet[1424.27]: waiting 120 seconds for network device
[11:27] <rbasak> I get:
[11:27] <rbasak> cloud-init-nonet[1020718.95]: waiting 10 seconds for network device
[11:27] <rbasak> cloud-init-nonet[1020720.85]: static networking is now up
[11:27] <rbasak> Let's wait for it to finish, then get you in, and you can fix the bridge from the host while testing from the guest
[11:28] <pitti> $ ip a | pastebinit
[11:28] <pitti> http://paste.ubuntu.com/6245144/
[11:28] <rbasak> In fact, I think you can do it now. "sudo lxc-attach -n foo -- login -f root" in another window.
[11:28] <pitti> logged in
[11:28] <pitti> ip a says that eth0 has no address
[11:28] <pitti> hm, no /var/log/syslog
[11:29] <rbasak> Yeah nothing's started yet
[11:29] <rbasak> It's still in early boot
[11:29] <rbasak> I think we need to get your host to the point where "ifup eth0" works in that guest. Then we'll be good.
[11:29] <pitti> ah, boot resuming
[11:29] <pitti> cloud-init-nonet[1544.27]: gave up waiting for a network device.
[11:29] <pitti> and then ssh key gen/locale stuff
[11:29] <rbasak> 25700 ?        S      0:02 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/lxc/dnsmasq.pid --conf-file= --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
[11:30] <rbasak> Do you have a similiar process on your host?
[11:30] <pitti> no I don't
[11:30] <pitti> only the main one from NM
[11:30] <pitti> lxc-dnsmasq: command not found
[11:31] <pitti> oh, that's not a command I suppose
[11:31] <rbasak> What's your /etc/defualt/lxc?
[11:31] <rbasak> Also status lxc-net
[11:31] <pitti> $ cat /etc/default/lxc | pastebinit  -
[11:32] <pitti> http://paste.ubuntu.com/6245149/
[11:32] <pitti> $ status lxc-net
[11:32] <pitti> status: Unknown job: lxc-net
[11:32] <pitti> rbasak: whic package is supposed to ship /etc/init/lxc-net.conf?
[11:32] <pitti> oh wth, I have it
[11:32] <pitti> $ sudo status lxc-net
[11:33] <pitti> lxc-net start/running
[11:33] <pitti> sorry, I thought status would work without sudo (through dbus)
[11:34] <rbasak> lxc-net starts the dnsmasq process that you appear to be missing
[11:34] <pitti> rbasak: btw, I installed lxc about half an hour ago on a saucy box that got installed on Monday
[11:34] <rbasak> pitti: desktop or server?
[11:34] <pitti> desktop
[11:34] <rbasak> I wonder if it's conflicting with some dnsmasq desktop thing
[11:35] <rbasak> Can you try restarting lxc-net?
[11:35] <pitti> stopped and started, still no lxc-ish dnsmasq
[11:36] <pitti> $ brctl  show
[11:36] <pitti> bridge namebridge idSTP enabledinterfaces
[11:36] <pitti> lxcbr08000.fe13863dc717novethCWCGU1
[11:36] <pitti> (in case that's helpful)
[11:36] <pitti> yay for not being able to copy&paste tabs
[11:36] <rbasak> I think your interface is fine, from your earlier "ip show" on your host.
[11:36] <pitti> vethCWCGU1 is up, but doesn't have a nontrivial IP
[11:37] <rbasak> Hmm. I don't know what that part is.
[11:37] <pitti> (i. e. no ipv4, and only a fe80:: ipv6)
[11:37] <rbasak> I have many veth devices
[11:38] <rbasak> That looks like a bug to me, but I think probably unrelated
[11:38] <pitti> no dmesg output at all for all of above operations (i. e. no AppArmor denials in particular)
[11:38] <rbasak> I presume I have one per LXC container I had started previously
[11:38] <pitti> rbasak: right, that looks rather temporary; lxcbr0 does have an IP
[11:38] <pitti> rbasak: but let's presume its the missing dnsmasq?
[11:38] <rbasak> Yes, I believe it is.
[11:39] <rbasak> It would certainly stop your guest getting DHCP
[11:39] <rbasak> Next I'd "set -x" the upstart job, grab the output and then try running dnsmasq not as a daemon
[11:39] <rbasak> But your guess is as good as mine
[11:40] <pitti> a-haa
[11:40] <pitti> I ran your dnsmasq from above
[11:40] <pitti> dnsmasq: failed to create listening socket for 10.0.3.1: Address already in use
[11:40] <rbasak> What's using it? The other dnsmasq?
[11:40] <pitti> it shouldn't really
[11:41] <pitti> rbasak: the NetworkManager one has --listen-address=127.0.1.1
[11:42] <pitti> (and you really need that, otherwise you stop being able to resolve anything)
[11:42] <pitti> rbasak: ah, red herring; I had aanother dnsmasq instance from an incomplete copy&paste of yor command, sorry
[11:42] <pitti> rbasak: I manually started it now
[11:43] <rbasak> Now ifup eth0 from the guest I suppose?
[11:43] <rbasak> If that doesn't work then we can tcpdump for dhcp on the host and see if it's getting through
[11:43] <pitti> rbasak: I just stopped the container and re-started
[11:43] <rbasak> and/or what dnsmasq is doing
[11:43] <rbasak> OK
[11:43] <pitti> that was fast now
[11:43] <rbasak> Great
[11:43] <pitti> so for some reason dnsmasq doesn't start for me
[11:43] <rbasak> So it works if you start dnsmasq manually, but not from the upstart job?
[11:44] <pitti> yes, apparently
[11:44] <pitti> hm, now stop/start lxc-net works, too
[11:44] <pitti> WTH
[11:44]  * pitti reboots to get a clean slate, brg
[11:45] <pitti> brb
[11:46] <pitti> rbasak: hm,  it's running after a reboot; weird heisenbug, sorry for the waste of time
[11:46] <rbasak> np
[11:46] <rbasak> Back to adt-virt-lxc then?
[11:47] <rbasak> Let's see if that still works. Perhaps it'll trigger the heisenbug :)
[11:47] <pitti> rbasak: start-ephemeral looks fine now
[11:50] <pitti> rbasak: that's for a test that simply does an echo: http://paste.ubuntu.com/6245219/
[11:50] <pitti> rbasak: looks good from here
[11:51] <rbasak> That's odd.
[11:51] <pitti> rbasak: with stderr: http://paste.ubuntu.com/6245222/
[11:51] <pitti> also LGTM
[11:51] <rbasak> pitti: maybe drop the stdout output?
[11:52] <rbasak> pitti: if not I'll try again and maybe need to send you my source
[11:52] <pitti> #!/bin/sh
[11:52] <pitti> echo STDERR FTL! >&2
[11:52] <pitti> that's my test now
[11:52] <pitti> adt-run: & tree0t-hello:  - - - - - - - - - - results - - - - - - - - - -
[11:52] <pitti> tree0t-hello         FAIL status: 0, stderr: STDERR FTL!
[11:52] <pitti> adt-run: & tree0t-hello:  - - - - - - - - - - stderr - - - - - - - - - -
[11:52] <pitti> STDERR FTL!
[11:52] <pitti> $ AUTOPKGTEST_BASE=`pwd` runner/adt-run --gain-root=sudo --no-built-binaries /tmp/testpkg/ --- `pwd`/virt-subproc/adt-virt-lxc --ephemeral adt
[11:52] <pitti> rbasak: ^ that was my command (to run from trunk)
[11:53]  * pitti grabs some lunch, high time
[11:53] <pitti> rbasak: yay for running into each other's nonreproducible bugs today :/
[11:53] <rbasak> pitti: what's your md5 of runner/adt-run, please? Same as mine?
[11:53] <pitti> 327da15ec6b3efe0a47f9d663feb1b3a
[11:53] <rbasak> Yeah same as mine. Thanks.
[11:55] <pitti> 9bb428d00471a23d4524d7bfee8bfac4  virt-subproc/adt-virt-lxc
[11:55] <pitti> rbasak: ^ FTR
[11:55] <pitti> (from your branch)
[11:55] <rbasak> Thanks. Mine matches.
[11:55] <pitti> rbasak: building the autopkgtest package and trying again
[11:55] <rbasak> I've just reproduced my failure. I'll try your test case instead of mine.
[11:56] <pitti> rbasak: send me your hello?
[11:56] <pitti> rbasak: I installed the built autopkgtest, then
[11:57] <pitti> $ adt-run --gain-root=sudo --no-built-binaries /tmp/testpkg/ --- ~/debian/autopkgtest/virt-subproc/adt-virt-lxc --ephemeral adt
[11:57] <pitti> rbasak: still works fine
[11:57] <davmor2> ubuntu-qa is anyone on a fresh flash?
[11:57] <rbasak> pitti: http://paste.ubuntu.com/6245246/ against hello 2.8-4 in saucy
[11:57] <pitti> davmor2: I can re-flash mine in about 30 secs if needed
[11:58] <pitti> rbasak: ah, *this* hello :) I used tests/testpkg and added a simple echo
[11:58] <rbasak> pitti: ah. Is this because I'm allow-stderr?
[11:58] <davmor2> pitti: have you set the timezone but not set a city in the clock app?
[11:58] <pitti> rbasak: ah-haa, I didn't have allow-stderr
[11:58] <rbasak> Seems so obvious now. Sorry I didn't mention that before.
[11:58]  * rbasak writes all his tests with allow-stderr
[11:59] <pitti> heh, I don't, so I tend to forget about it
[11:59] <rbasak> And I forget to tell you about it, since I do it automatically :-/
[12:01] <pitti> rbasak: right, confirmed (not specific to lxc, happens with all runners)
[12:01] <rbasak> OK. Thanks. Sorry it took so long! At least we got there in the end I guess.
[12:01] <pitti> rbasak: I thought to not print stderr separately with allow-stderr as one sees it in live output already, and allow-stderr essentially means "I don't care"
[12:02] <pitti> rbasak: but we don't (ATM) have live-output with other runners
[12:02] <rbasak> pitti: I do care! stderr provides valuable debugging information on failure.
[12:02] <pitti> rbasak: yes, of course
[12:02] <pitti> it's a bug :)
[12:02] <rbasak> I see.
[12:02] <rbasak> Sorry, I misunderstood.
[12:02] <pitti> (just explaining how I got there)
[12:02] <rbasak> Yeah that makes sense
[12:03] <pitti> rbasak: so, I don't think we need to print it again for -null (for live output)
[12:03] <pitti> but we of course must show it for the other runners
[12:03] <pitti> combinatorial explosion FTW, good to have tests now
[12:03] <rbasak> That seems reasonable. One comment though. Without allow-stderr, the difference between stdout and stderr matters. If they're not distinguished, then it may not be clear what is causing a failure.
[12:03] <pitti> correct
[12:04] <rbasak> This reminds me of annotate-output, though of course that is prone to races
[12:04] <pitti> rbasak: I always show it without allow-stderr
[12:04] <rbasak> Ah, I see. Got it.
[12:04] <pitti> rbasak: (in trunk, at least; there are some bugs with 2.3.7)
[12:07] <davmor2> pitti: if you have the timezone set but no city in the clock, can you add your city please and see how far out the time is?  I think it is treating the Default time as always being UTC which obivously it isn't if you set your timezone
[12:07] <pitti> davmor2: so, I did set the timezone with something like "adb shell timedatectl set-timezone Europe/Berlin"
[12:08] <pitti> davmor2: I think that means "yes" to your question from 10 mins ago
[12:08] <pitti> phone shows correct time
[12:08] <davmor2> pitti: now open the clock app and add you city to the clock app
[12:08] <pitti> davmor2: system-settings shows Europe/Berlin, UTC+2 (correct)
[12:09] <davmor2> pitti: is the clock app now +4 if you add your city
[12:09] <pitti> davmor2: I. e. click on "time settings" in the indicator, to get system-settings?
[12:09] <davmor2> rather than plus 2
[12:09]  * pitti selects Augsburg
[12:09] <pitti> bah, it doesn't go back automatically any more; I thought that got fixed already
[12:10] <davmor2> pitti: as in the clock app rather than timezone or indicator clock
[12:10] <pitti> davmor2: hang on, are we talking phone or desktop?
[12:10] <davmor2> pitti: phone
[12:10] <pitti> davmor2: oh, clock *app*
[12:10] <pitti> sorry
[12:10] <davmor2> yes app :)
[12:11] <pitti> boo, no Augsburg in the search
[12:11] <pitti> we do have that in the indicator ;)
[12:12] <pitti> and no München!?!
[12:12] <pitti> c'mon, that's the second largest city in Germany
[12:12] <pitti> ah, if you search for "Munich" it shows "München"; go figure
[12:12] <davmor2> haha
[12:13] <pitti> davmor2: anyway, it now says "World... Muenchen 14:13" which is right
[12:13] <pitti> davmor2: you think it adds the UTC offset twice?
[12:13] <pitti> no search results for "new y". poor!
[12:14] <pitti> a-haa
[12:14] <pitti> davmor2: New York City (found it with just "new") says 00:14 which is wrong
[12:14] <pitti> shoudl be 08:14
[12:15] <davmor2> pitti: it did for me but I'll get some steps together and double check it, However I set the timezone via settings rather than adb so that might of had an effect
[12:15] <pitti> davmor2: yeah; the settings eventually call timedated as well, but they might do some additional bits
[12:25] <pitti> rbasak: fixed in trunk (added two new tests to reproduce the bug)
[12:25] <rbasak> pitti: thanks!
[12:25] <jibel> it would be too easy to use the same code than what is in ubiquity. all these timezone bugs have already been reported/fixed there
[12:26] <xnox> hm?
[12:26] <jibel> xnox, select a location, apply the right tz, all these details
[12:27] <jibel> xnox, the phone is going through all these bugs again
[12:27] <jibel> and also, 3 different places (clock, u-s-s, weather) to select a timezone and 3 different way to do it
[12:28]  * jibel -ETESTINGOVERFLOW
[12:28] <pitti> also, -EBADARCHITECTURE
[12:28] <pitti> how come I don't get the same list of cities and searches in clock and the indicator?
[12:33] <rbasak> pitti: confirmed fixed. Thank you!
[12:39] <pitti> rbasak: \o/
[14:06] <plars> psivaa: if you get a moment, could you try running software center after an install completes? see bug #1240530
[14:08] <psivaa> plars: ack
[14:11] <psivaa> plars: i did not see that on my oem installation on a hardware with i386
[14:12] <plars> psivaa: hmm... perhaps try it if you do one without network
[14:12] <psivaa> plars: will do. but i hit bug #1240531 on my oem. but dont see any impacts on the usage
[14:12] <plars> psivaa: I'm actually doing an oem install right now, I'll see if it happens to me there
[14:22] <psivaa> plars: just in case you have not seen it in #u-release there will be another ubiquity related respin
[14:23] <plars> psivaa: no I wasn't watching... thanks for the heads up
[14:52] <alesage> jibel, commented #1240377
[14:52] <alesage> https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1240377
[14:55] <jibel> alesage, ah, thanks, I marked mine a duplicate.
[14:55] <jibel> *as
[14:56] <alesage> jibel, thx, that's a rarity for me :)
[14:56] <jibel> alesage, oh, I can set duplicate the other way around if you prefer ;)
[14:57] <alesage> jibel, leave me at least one ;)
[15:00] <elopio> good morning qa!
[15:00] <elopio> one day to go.
[15:33] <nkv_sgp> Hi, anyone faced system hand while creating the USB Startup Disk using "Startup Disk Creator"?
[15:33] <smartboyhw> nkv_sgp, usb-creator-gtk has been widely deemed unstable, you should use dd or unetbootin....
[15:34] <smartboyhw> unetbootin is the best choice:)
[15:34] <nkv_sgp> i observed the whole system getting hanged once after 57% progress and second time after 85% completion
[15:34] <nkv_sgp> oh ok
[15:35] <nkv_sgp> thanks
[15:36] <nkv_sgp> concern though is that the whole system was hanged
[15:50] <cgoldberg> nkv_sgp, "Startup Disk Creator" in 13.10?
[16:08] <balloons> cgoldberg, did you get ubuntuuitoolkit.emulators pushed to d.u.c?
[16:09] <balloons> or was that dependant on landing the mp/
[16:24] <phillw> balloons: do you have any knowledge as to why the server images were disabled? We share the same installer for alternate and we have no issues; bor can I find bugs listed on the iso tracker that would cause a respin.
[16:24] <phillw> s/bor/nor
[16:25] <balloons> no, I don't
[16:25] <balloons> i saw it a bit ago, but was confused myself
[16:27] <rbasak> jibel, pitti: adt-virt-lxc MP updated with all of jibel's review issues fixed, and I've tested that it works against current git head. Sorry it took so long for me to get back to it, and thank you for the review jibel.
[16:27] <cgoldberg> balloons, new version of emulators doc isn't published yet.  I'm working on the importer script today for API website.  it doesn't depend on the MP landing (but that would be nice)
[16:27] <rbasak> https://code.launchpad.net/~racb/ubuntu/saucy/autopkgtest/lxc/+merge/172856
[16:27] <rbasak> Please merge ;)
[16:28] <jibel> rbasak, awesome, thanks for this work!
[16:28] <rbasak> jibel: np. adt-virt-kvm next :)
[16:28] <balloons> cgoldberg, thanks for the update ;-) You got me used to the nice layout, and seeing the old stuff made my eyes hurt when I ref'd it :-)
[16:29] <nkv_sgp> cgoldberg, "Startup Disk Creator" in 13.04 for 13.10 image
[16:30] <cgoldberg> nkv_sgp, are you letting it format the usb drive for you first?  does that complete ok?
[16:30] <cgoldberg> or "erase disk"
[16:32] <nkv_sgp> no, while coping the iso to to disk
[16:33] <nkv_sgp> erase too hanged this app alone so I ereased it from Mac
[16:33] <nkv_sgp> the bigger issue is that the whole system hanged while creating the disk
[16:34] <cgoldberg> nkv_sgp, hmm.. do you know what format/filesystem the USB drive is using?
[16:34] <nkv_sgp> the USB drive was the startup disk for 13.04 which I was replacing with 13.10
[16:35] <cgoldberg> nkv_sgp, does copying a 13.04 iso still work?
[16:35] <nkv_sgp> did not try from Ubuntu
[16:36] <cgoldberg> nkv_sgp, also.. do you have another USB drive to try with?.. I find most thumbdrives to be unreliable and break often.  sometimes a bad USB drive is the culprit
[16:37] <nkv_sgp> bad USB drive doesn't look like the problem as I used the same drive to create the startup disk from win7 and that worked
[16:37] <nkv_sgp> i installed the 13.10 on VirtualBox using that same drive
[16:38] <nkv_sgp> the problem appears with the package "Startup Disk Creator".
[16:38] <nkv_sgp> I shall try using another drive as well and share how that goes
[16:39] <cgoldberg> nkv_sgp, ok.  the same works for me... using 13.04 startup disk creator, and a 13.10 image
[16:39] <nkv_sgp> oh, ok
[16:51] <jfunk> nuclearbob, hey Max, I am seeing a lot of stuff on the untriaged list that shouldn't be there, what's going on?
[17:44] <elopio> ping om26er for when you are around. Where are the tests that test multiple applications?
[17:45] <om26er> elopio, https://code.launchpad.net/~om26er/gallery-app/camera-integration-test/+merge/189685
[17:46] <elopio> om26er: thanks!
[17:46] <om26er> not merged yet because things were broken a few days ago where inter-app integration was hanging things. now that veebers have a unlock emulator I am going to improve this branch
[17:46] <om26er> there is also another branch for camera-app as well
[17:49] <elopio> om26er: got it. I'm thinking about this because now I have to test the integration between system settings and ubuntu one online accounts.
[17:50] <elopio> and also between the update manager, and online accounts.
[17:50] <elopio> om26er: what do you think of creating a separate project for testing inter-app integration ?
[17:50] <om26er> elopio, yeah better to set initctl env variable so that all apps launch in testability inside unity8
[17:51] <elopio> ping ubuntu-qa. Who has a galaxy nexus?
[17:51] <om26er> o/
[17:51] <robotfuel> elopio: me
[17:51] <elopio> robotfuel, om26er, can you try to reproduce this one? but #1240160
[17:51] <elopio> bug #1240160 :)
[17:51] <davmor2> elopio: I might
[17:54] <om26er> elopio, does not crash for me
[17:54] <robotfuel> elopio: I am using a newer version than he was, it has not crashed for me yet
[17:54] <elopio> thanks om26er.
[17:54] <elopio> thanks robotfuel
[17:55] <om26er> its even downloading a few updates
[17:55] <robotfuel> I'll have to retry when there is no update
[17:57] <om26er> jibel, once you install a deb by yourself does the system update even work after that?
[17:57] <om26er> aka apt-get install
[17:59] <davmor2> elopio: http://ubuntuone.com/4J9UwYspQkEaXqx9BDjypG works fine here
[17:59] <elopio> thank you davmor2.
[18:22]  * elopio <- lunch
[18:34] <balloons> elopio, does the back button have no default objectname :-(
[18:40] <elopio> balloons: give me 5 seconds to implement it
[18:40] <elopio> balloons: here you go: https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/fix1239751_go_back/+merge/191002
[18:40] <elopio> ;)
[18:40] <balloons> elopio, :-)
[18:41] <balloons> seriously, WTF mate
[18:41] <balloons> this is the third time you've done something before I asked
[18:41]  * balloons thinks I'm just behind elopio's infinite prowess by 2 days
[18:43] <elopio> it's Costa Rican time zone. Two days early :D
[18:43] <phillw> xnox: do you have any thoughts on https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1240622 ?
[18:43] <balloons> I've really got to visit..
[18:43] <elfy> lol
[18:43] <elopio> balloons: the truth is pitti asked for it on monday.
[18:43] <balloons> elopio, of course.. it's just awesome.. you are 3 for 3.. I'm going to start expecting things now, haha
[18:45] <elopio> http://www.youtube.com/watch?v=ekeELle5g-o
[18:51] <davmor2> elopio: http://www.youtube.com/watch?v=ICjyAe9S54c  I expect this to be playing the next time we meet
[18:52] <Letozaf_> balloons, Hi
[18:52] <davmor2> elopio: if only because it is a track I have on my phone :D
[18:52] <balloons> Letozaf_, hello :-)
[18:53] <Letozaf_> balloons, howzit ?
[18:53] <balloons> Letozaf_, well https://bugs.launchpad.net/ubuntu-rssreader-app/+bug/1240617
[18:53] <jibel> om26er, yes it does. I only installed packages with apt though. What did you install?
[18:53] <balloons> Letozaf_, yourself? :-)
[18:54] <Letozaf_> balloons, fine
[18:54] <om26er> jibel, I only installed ubuntu-download-manager and ubuntu-system-cli et al.. There is no update yet. But in the past whenever I installed things with apt-get ..updates generally got broken for me
[18:54] <jibel> om26er, make sure the FS is RO before upgrading, I think it blocks the upgrade in this case.
[18:54] <om26er> will test in a few when a new image appears
[18:55] <Letozaf_> balloons, I also found I think a bug  when adding a feed by hand today
[18:55] <Letozaf_> balloons, but probably it's the same thing indicated in this bug
[18:55] <jibel> om26er, to test u-d-m and system-image, I installed build 92, switch to rw, installed latest u-d-m and system-image, switched back to ro, reboot
[18:55] <jibel> om26er, and it is upgrading to 99
[18:56] <Letozaf_> balloons, tomorrow is release day, are you too busy today to look at that click packages thing ?
[18:56] <jibel> om26er, I havent tried to pause downloading or shutdown wifi while it's upgrading
[18:58] <om26er> jibel, i'll try it once 100 comes up
[18:59] <jibel> om26er, all the interest of the test is to test system-image _before_ it's in 100, after will be too late
[18:59] <om26er> jibel, aah, ok. I have quite a few images in my system. I can try those
[19:00] <om26er> brb
[19:07] <balloons> Letozaf_, ahh yes the click stuff
[19:07] <balloons> I don't remember but I think I solved it right after you left
[19:07] <balloons> haha
[19:08] <balloons> Letozaf_, want to tackle the back button issue?
[19:09] <Letozaf_> balloons, sure I reported another bug
[19:09] <Letozaf_> balloons, bug 1240658
[19:13] <Letozaf_> balloons, and I am having another problem: when I enter adb shell /system/bin/screencap /data/screenshot.png to take a screenshot, the command stalls, it does nothing
[19:13] <Letozaf_> balloons, I have already taken screenshots before and this used to work
[19:13] <balloons> Letozaf_, indeed
[19:14] <balloons> mir doesn't take screenshots that way
[19:14] <Letozaf_> balloons, :(
[19:14] <Letozaf_> balloons, how do I
[19:14] <Letozaf_> balloons, with MIR ?
[19:14] <balloons> Letozaf_, http://people.canonical.com/~j-lallement/touch/mirfbdump
[19:14] <Letozaf_> balloons, thanks
[19:15] <balloons> i'll add that to the wiki
[19:15] <Letozaf_> balloons, yes it's a good idea :P
[19:19] <balloons> Letozaf_, https://wiki.ubuntu.com/QATeam/TouchTesting#Take_a_screenshot :-)
[19:21] <Letozaf_> balloons, sorry but the output of that script, is it an image ? if I run file filename I get data file and if you open it with image viewer you see nothing
[19:26] <balloons> hmm, I honestly due it a different way, but it seems like he has a convert step in there to make it a png or jpg or whatev's you want
[19:26] <Letozaf_> balloons, do I need imagemagick ? maybe that's why
[19:26] <balloons> yes
[19:27] <Letozaf_> balloons, ok so that's why I have to install it
[19:27] <Letozaf_> balloons, I will right away
[19:27] <Letozaf_> balloons, oops it is installed :(
[19:29] <balloons> you pass dump.png to it?
[19:30] <Letozaf_> balloons, no I was reading the script now, I just used /mirfbdump.sh filename
[19:30] <Letozaf_> sorry ./mirfbdump.sh filename
[19:34] <plars> psivaa: 16.1 for desktop at least has arrived
[19:34] <psivaa> plars: ack, will take on i386 and mac
[19:35] <plars> psivaa: thanks, I know it's getting late. Do what you can and I'll pick up whatever I can tonight
[19:35] <psivaa> plars: ack
[19:36] <thomi> morning
[19:36] <Letozaf_> balloons, If I don't get it wrong I think you just have to launch the script with output-filename, so ./mirfbdump.sh filename should be right
[19:37] <balloons> Letozaf_, good :-)
[19:37] <Letozaf_> balloons, but that filename with what do you "see" it
[19:37]  * balloons laments uitk is getting as bad as gtk in making objects
[19:38] <balloons> Letozaf_, pick an ending and open it in an image viewer
[19:38] <balloons> file.png
[19:39] <Letozaf_> balloons, can't believe it I just forgot the .png thing, now it works :D
[19:40] <Letozaf_> balloons, instead of calling the file screenshot I called it screenshot.png and it worked !
[19:40] <Letozaf_> balloons, thanks
[19:40] <balloons> Letozaf_, yw
[19:44] <Letozaf_> balloons, just another question, when you open rssreader app on the device, shouldn't there already be some feeds, I got it empty now
[19:45] <Letozaf_> balloons, even if you tap refresh
[19:45] <Letozaf_> balloons, should be a bug I think
[19:45] <balloons> at one point yes, but they may have removed those
[19:45] <Letozaf_> balloons, ah ok so I will not report it
[19:46] <balloons> Letozaf_, you can report it.. I can't check , my phone isn't happy atm
[19:46] <balloons> they might just say it's supposed to be that way :-)
[19:47] <Letozaf_> balloons, ok
[19:49] <plars> psivaa: I'm still able to reproduce this problem with the ubuntu one login sometimes
[19:50] <plars> psivaa: it's infrequent it seems, but still happens
[19:50] <psivaa> plars: i'll try to reproduce that
[19:50] <plars> xnox: ^ - this time I noticed something else... I hadn't been able to reproduce it since I mentioned it to you but it's happening now and ubiquity is eating 90% cpu at the moment also
[20:00] <Letozaf_> balloons, I do not get the error indicated in bug 1240617 running the test on a desktop, I get a failure, but it's in the test_edit_topic at line 364 totally different one
[20:15] <phillw> balloons: I've asked on #ubuntu-server and no one has replied back as to why they should be disabled; could you ask around?
[20:16] <balloons> oversized
[20:20] <phillw> balloons: ah, okies :) Thanks!
[20:20] <balloons> yw phillw
[20:21] <Letozaf_> balloons, can you still run the tests on the device with: phablet-test-run -n ubuntu_rssreader_app  ?
[20:32] <balloons> Letozaf_, you can do it the old way
[20:33] <balloons> but it messes updating up, etc, as you'll have to install packages and turn on rw mode
[20:33] <balloons> click is much easier because you can pull your own code too
[20:34] <Letozaf_> balloons, but click doesn't work for me unfortunatly, remember yesterday ?
[20:38] <balloons> Letozaf_, yes, but ...
[20:58] <plars> balloons: psivaa: how long does re-install system normally take for you?
[20:59] <psivaa> plars: it normally takes nearly the same time as the fresh install
[20:59] <balloons> plars, an upgrade from image?
[20:59] <plars> psivaa, balloons: bug #1240699
[20:59] <plars> 30 min. later it's still going
[21:00] <balloons> ahh, right that's more or less an inplace upgrade
[21:00] <plars> right
[21:00] <plars> balloons: but the system on there before was pretty stock - no extra packages or anything
[21:00] <balloons> let me try again
[21:00] <plars> balloons: it's still nowhere close to done, 30 min later
[21:00] <phillw> the ability yo use an alternate ISO to upgrade was dropped when all the teams dropped the alternates from their builds :)
[21:01] <phillw> s/yo/to
[21:01] <balloons> I'll replicate what you did and use vbox too
[21:01] <plars> balloons: cool
[21:01] <plars> thanks
[21:01] <phillw> I did ask on behalf of lubuntu what had happened to it.
[21:02] <balloons> ohh shoot, this is an encrypted volume, hehe
[21:02]  * balloons boots another
[21:03] <balloons> k I'll do the encrypted one also, but I want to stay simple
[21:04] <psivaa> can we upgrade image on an encrypted install?
[21:04] <balloons> psivaa, you simply have to mount it first from a live session, then yes
[21:05] <slickymaster> good night all
[21:05] <psivaa> balloons: ack
[21:19] <plars> psivaa, balloons: it finally finished, and I'm on to another install
[21:19] <plars> it took a good long while though
[21:20] <balloons> plars, one went fine
[21:20] <balloons> the other had an error
[21:20] <plars> psivaa, balloons: ubuntu one login worked this time... failure seems to be pretty random with it
[21:20] <psivaa> plars: i've done a few erase and reinstall and they dint seem to take that long
[21:21] <balloons> so not sure what happened to you.. one of the re-installs was really old, it too went fine
[21:21] <psivaa> i've also done some reinstall (keeping the home folders and files) that also did not take that long
[21:21] <balloons> I broke my encrytped install tho.. hehe
[21:22] <balloons> I didn't tell it to encrypt again
[21:51] <phillw> hi melodie just waiting for 20131016.1 to land for lubuntu :) Patience is the by-word :)
[21:51] <melodie> hi phillw
[21:52] <melodie> phillw no problem, it will be there when it will
[21:52] <melodie> I have lots to do in many fields anyhow
[21:52] <melodie> phillw what was it about the test cases?
[21:53] <phillw> indeed, I'm about to create a couple of machines up with room to install side by side. Mine are now full with reslicing for alternate testing :D
[21:53] <melodie> I had a great difficulty at first to see how that was working and when on sunday night I finally got the point, where to click and so to see the list of points to be checked it was marked all as "Archived" and seemed not possible to post there anymore : is that what was expected?
[21:54] <phillw> if you find a bug in the actual test case, then please register it. e.g. if you look at http://iso.qa.ubuntu.com/qatracker/testcases/1439/info you will see the link to report a bug against the test case. All test cases have that link for reporting.
[21:55] <melodie> phillw I send you my highest thoughts and congratulations for the central information you are providing, by the way. You are doing a fantastic job
[21:55] <melodie> how much time will this test case be available?
[21:55] <phillw> balloons: and the rest of the team here are the drivers, I just annoy them :P
[21:56] <melodie> I don't see their posts at the ml, I do see your's, and that allows a handful of us to bring crumbs of contribs :)
[21:57] <phillw> the manual test cases should only ever be updated as releases move on and they need updating. The process to update them has changed and as I'm going to be concentrating more on docs next cycle; so I will be happy to keep you updated :)
[21:57] <phillw> yay.. server has landed!
[21:57] <melodie> I see
[21:57] <melodie> where are the alternate isos? I don't have all the links under the hand
[21:57] <melodie> hi _salem o/ !
[21:58] <phillw> melodie: all the builds for RC (Final) are at http://iso.qa.ubuntu.com/qatracker/milestones/305/builds
[21:58] <melodie> thanks
[22:00] <melodie> downloading with wget now
[22:00] <phillw> the iso tracker itself holds everything we test on the iso's/ It has sister areas e.g. http://packages.qa.ubuntu.com/qatracker/milestones/300/builds
[22:00] <melodie> I wonder if usb creator gtk in 12.04 can put it to usb stick?
[22:00] <melodie> phillw I don't take more info than I need...
[22:00] <melodie> ^^
[22:01] <phillw> melodie: a hint... use zysnc, there are a couple of 'cheats' that both reduce the time they take, but also lessen the load on the poor server that issues them all out :)
[22:02] <melodie> isn't zsync to be used when the first iso has been downloaded? I only had the desktop version so far
[22:02] <phillw> I've seen a lot on usb sticks, the 12.04 'from' 12.04 seems to work okay. other than that it seems dd is the fail safe with people also reporting that unetbootin works okay.
[22:03] <melodie> phillw I said on the mailing list dd is horrible for creating usb boot isos, it destroys the fs of the usb stick
[22:04] <melodie> I would bet that it would reduce the life span of the stick : I don't have benchmarks to confirm, but this seems likely to me
[22:06] <phillw> I've not built a usb disk in a long time, does not http://www.pendrivelinux.com/ have a working solution?
[22:06] <balloons> +1 thomi I missed this landing :-) ARNING dbus:522 - Your query '/comubuntuclock/QQuickView/MainView/OrientationHelper/QQuickItem/QQuickItem/PageStack/PageWrapper/Tabs/QQuickItem/Tab/AlarmPage/QQuickFlickable/QQuickItem/QQuickColumn/QQuickListView[id=104]//Label' returned a lot of data (20 items). This is likely to be slow. You may want to consider optimising your query to return fewer items.
[22:07] <phillw> melodie: depends on the usb stick. one of the few things that windows gave us was certified speed-boost disks. I am glad I spent the extra to get mine. they are designed for 'heavy' re-writes.
[22:07] <melodie> phillw the working solutions are always the one some succeeded in applying : this to say I didn't test all the pendrivelinux solutions :)
[22:09] <phillw> I'll have a play with pendrive linux on Friday evening and let you know how I get on. I do agree that we do need a system that works that allows us to have our linux on a stick for when we are out and about and also for helping out other people.
[22:12] <melodie> phillw as I said on the ml, some methods are fine for everyday use, and are not for testing because they don't provide all the same features as in a cdrom
[22:13] <phillw> I till have my 9.10 usb, bought from the canonical shop many moons ago. That little critter is still going :)
[22:13] <phillw> s/till/still
[22:14] <phillw> I'll back up my high speed one and have a play. But we can discuss that on the other channel :)
[22:15] <melodie> which channel?
[22:15] <melodie> which other* channel? :)
[22:15] <melodie> #linuxvillage ?
[22:25] <thomi> balloons: :)
[23:40] <phillw> balloons: permission to cry?
[23:40] <balloons> I laugh instead of crying
[23:40] <balloons> it's a choice
[23:40] <balloons> soon it might be silently sobbing in a corner
[23:41] <melodie> good night
[23:44] <phillw> balloons: I'd not have cried, but they respun all the lubuntu alternates and the only one that was over sized, is still over sized :'(
[23:44] <phillw> Ahh, here come the desktops.... stop the sheepdogs pincing at my heels :D