=== salem_ is now known as _salem [00:22] mdolezel: Perfectly possible; the desktop-next spin is basically that. === chihchun is now known as chihchun_afk === chriadam|away is now known as chriadam [01:43] Does ubuntu touch have decent stylus support? [01:44] The surface 3 looks really nice, but I want linux on it. [02:28] meretrix: The Surface 3 is an x86 device, you can put normal Ubuntu on it. There is a nice article on how to do it, http://blog.davidelner.com/dual-booting-ubuntu-14-10-on-the-surface-pro-3/ === sturmflut_ is now known as sturmflut [02:29] meretrix: At this point in time you can probably already go for the 15.04 Final Beta and avoid manually building the kernel === chihchun_afk is now known as chihchun [05:44] hello, it seems like google has changed the contact structure so syncevolution not syncing contacts via google anymore, can somebody please confirm me this issue ? [05:46] hello, it seems like google has changed the contact structure so syncevolution not syncing contacts via google anymore, can somebody please confirm me this issue ? [05:48] mota_ i guess asking once is enought.. if someone has to say anthing on it he will just do i guess [05:48] oh sorry === marcusto_ is now known as marcustomlinson [06:20] Does anybody have any idea why I cannot connect to my Bq neither with adb nor phablet-shell (on Ubuntu 14.04)? My device is in the developer mode and the USB connection works as I can browse the contents with Nautilus. I still don't understand why I can't open a shell. The tools just don't see the device. Either I'm stupid or something doesn't work as expected :) [06:21] did u tried while the screen is powered on? [06:22] yes [06:22] as root? [06:24] Run phablet-shell as root? [06:24] No, it doesn't work [06:24] adb? [06:25] error: device not found [06:25] And still it's accessible in Nautilus all the time [06:26] have u updated in the last time? [06:27] i have a bad feeling that there is something wrong with latest ubuntu rootfs's as i can not get my ported device to get recognized by adb as well [06:27] thats only with newer rootfs's my old testing one still works [06:27] lsusb still lists it as connected samsung device [06:27] so [06:28] Ok, so I'm not alone :) [06:29] yeah and further [06:29] using the described method in the porting guide to allow adb while screen is off [06:29] simply makes it reboot as soon as i plug in the usb cable [06:30] not nice at all ^^ [06:31] damned...maybe I'll just go to work :) [06:31] i just finished work and should maybe go to bed ^^ [06:31] will do that [06:31] night :) === kickinz1|afk is now known as kickinz1 === chriadam is now known as chriadam|away === marcusto_ is now known as marcustomlinson [08:36] tsdgeos: FYI http://bazaar.launchpad.net/~aacid/autopilot/dbus_search_no_seen_connections/revision/551 seems empty commit [08:36] Mirv: it is [08:37] it changes the executable bit of debian/rules [08:37] that somehow had been set [08:37] ah, interesting [08:37] ok [08:37] tsdgeos: so it seems they want to do their own releases, so I'm now testing whether it's okayish not to publish autopilot from the silo for the time being. looking "probably good enough" so far. [08:37] Mirv: cool [08:38] upstream dbus patches failed to integrate in ci, but i think because not all of them were sent to integration [08:38] and thus they deadlocked in tests :D [08:41] ok. yesterday's test run was fully good at the end (AP update included), the complexity was just that ubuntu-system-settings had apparently regressed in the archive meanwhile which I had to test without the PPA [08:41] I've also been doing some exploratory testing. anyhow, if this without-AP run looks good, I'll probably mark the silo as tested still today [08:43] ok [08:44] (only soft wrae thouh) [08:45] oops [08:59] rsalveti: can you rephrase your question? Are you saying you just have the stack trace and want to find the bucket of crashes that matches this? [09:13] Good morning all; happy Reconciliation Day! :-D === kickinz1 is now known as kickinz1|afk === christian_ is now known as CereS2009 === kickinz1|afk is now known as kickinz1 [09:37] Hi i've installed ubuntu-touch on a nexus 4, and my SIM Card isn't detected, the flight mode indicator symbol is permanently turned on (even when using wifi) and audio/video (Error playing video Fail to connect with playback backend))doenst't work. Any advice on were to look to further investigate? [09:37] !devices | CereS2009 [09:37] CereS2009: You can find the full list of devices, official images, community images, and works in progress at https://wiki.ubuntu.com/Touch/Devices [09:37] CereS2009: can you also tell us wich channel you installed? [09:39] lotuspsychje: its ubuntu-touch devel proposed. The OTA Updates are working fine and i'm at r156 [09:39] ok im also on nexus7 on devel-proposed [09:39] CereS2009: maybe its a known issue on n4? [09:40] CereS2009: idle here a bit, when the devs are waking up and re-ask once in a while [09:40] lotuspsychje: from the google docs document all should be working. [09:41] maybe a bug perhaps [09:43] lotuspsychje: could be, i'm not sure were to look further - tried rfkill -list [09:43] lotuspsychje: how is it working on the n7? [09:43] CereS2009: everything works flawless [09:44] lotuspsychje: good to hear [09:44] CereS2009: i was on channel devel for long time, but devel-proposed is fantastic! [09:44] lotuspsychje: the devel channel is the latest, is it? [09:45] CereS2009: not sure, all those channel infrastructure confuses me :p [09:45] CereS2009: i have been told here devel-proposed works best for n7 [09:45] devel-proposed is vivid... [09:45] that's a bit unstable and could break [09:46] popey: wich channel do you use? [09:48] i have numerous devices, and use different channels on each [09:49] popey: you have n7? [09:49] yes [09:49] wich channel do you use on n7? [09:49] it varies [09:49] I dont use it day to day, it's used for testing [09:50] ok [09:50] well im pretty happy with devel-proposed myself, runs smoother then rtm 14.09 and devel [09:50] which version is devel, then? === greyback__ is now known as greyback [09:52] CereS2009: https://developer.ubuntu.com/en/start/ubuntu-for-devices/image-channels/ [09:53] on a tablet you definitely want devel-proposed, rtm gets zero testing on tablets ... on a phone it depends if you want stability (rtm) or the latest features and breakage (devel-proposed) [09:54] ogra_: that was clear :p [09:54] mzanetti: I see Saviq assigned you to full-screen app issue from yesterday so I came to the right person in the first place ;) [09:56] ogra_: I have a tracking number for my Nexus 7 now... just have to wait until Tuesday! :) [09:56] nhaines: you ordered one? [09:57] lotuspsychje: yes, saw a good Groupon deal and decided to go for it. At the very worst it'll be a nice Netflix screen. [09:57] nhaines: how much did you pay im curious :p [09:57] lotuspsychje: $149.99 plus tax. [09:57] nhaines: n7 performs better then just a netflix screen lol [09:58] nice, mine was new and paid 269 euro [09:58] I can't think of anything else I'd need a tablet for, though. [09:58] nhaines: i like the scopes on it and email/rss news browsing [09:58] ogra_: do you have any idea how the direct phone video (in the bq commercials, for example) was captured? [09:59] nope [09:59] lotuspsychje: I can do that on my computer or my phone. No need for a tablet for that. :) [09:59] ogra_: drat! [09:59] bq commercials? [09:59] i think aquarius had some howto [09:59] Not only doesn't it work, but in the bug report they're claiming it never worked (which isn't true--because I saw aq's YouTube demonstration of it). [10:00] So at SCALE I unfortunately had to just loop the commercial and walkthrough. Which was annoying because I'd spent a couple hours shooting off screen video for a walkthrough! ;) [10:00] (But on the bright side, it was almost identical to Canonical's walkthrough--so I guess I did a good job! haha) [10:01] got a link to the videos? [10:02] unlock the dir and install kazam from terminal to record :p [10:02] https://www.youtube.com/watch?v=-dpfHYpfEXY [10:02] https://www.youtube.com/watch?v=TShKZLeZzWE [10:02] popey: ^^ [10:02] ta [10:02] they dont look recorded on device [10:03] popey: you think they're mockups? [10:03] i think they were done in post [10:03] but just guessing [10:04] "direct video" means the video was screencast. "off screen" means someone pointed a camera. [10:04] the blue dot will be edited afterwards for sure [10:04] To me it looked like it might be direct video that was composited in during post. [10:04] lotuspsychje: not necessarily. [10:05] looks more like a sequence of screenshots animated together in post [10:05] popey: i also think its animated [10:05] popey: that's technically what videos are. :) [10:05] That would be pretty tedious, though. [10:05] le sigh [10:06] not really. [10:06] Oh well, with luck, mirscreencast gets fixed back up again. [10:06] Alternately, Mir gets multidisplay support and can mirror out to a projector. I would accept that as well. :P [10:07] Because at least I can show off the screen during presentations. [10:08] what about the ubuntu touch emulator and record from pc? [10:08] I've never fond the emulator to be usable. [10:09] didnt test myself, but i bet you can record the area with kazam around the virtual device [10:10] and set a blue dot as mouse pointer on the pc :p [10:16] davmor2, mzanetti's out for Easter until Tue [10:17] Saviq: oh well [11:11] all the phoneception posts this morning on G+ were hilarious [11:28] Does anyone else find the date/time picker spinny-things a bit sensitive? [11:55] does anyone now if the latest image http://system-image.ubuntu.com/ubuntu-touch/vivid-proposed-customized-here/krillin/version-169.tar.xz is working on bq aquaris ? === _salem is now known as salem_ === alan_g is now known as alan_g|lunch [12:26] whats the difference between /ubuntu-touch/vivid-proposed/mako and ubuntu-touch/devel-proposed/mako/ === MacSlow is now known as MacSlow|lunch [12:27] nothing I think. [12:28] popey: thx [12:28] np [12:29] was wondering because everything except audio, video and mobile network is working, and searching for the mistake i'm making.. [12:29] when next ubuntu comes, vivid-proposed will stay on the old version whil devel-proposed will always be the version that's currently in development [12:30] tassadar: ah i see [12:31] hello [12:32] is there anything i need to install or flash later, when i want to use audio/video? [12:33] eg ubuntu tells me "The phone is in silent Mode" and i can't change anything on the volume sliders === dandrader is now known as dandrader|afk === alan_g|lunch is now known as alan_g [12:50] Hi, not sure if this is the right channel. I have ubuntu touch on my nexus 4 and I want to back up all my local data like SMS and photographs [12:51] Photographs can be copied easily but what about SMS? Is there a way to export them into a friendly format? [12:52] Hi guys... Could anyone help by resolving this boot issue on Ubuntu touch ??? http://askubuntu.com/questions/604397/boot-process-on-ubuntu-touch-on-aquaris-4-5-only-shows-ubuntu-logo [12:52] mr_november: pretty sure they're in a database somewhere in your home directory [12:52] mr_november: SMS are stored in ~/.local/share/history-service/history.sqlite if that helps. No idea if it's safe to restore just by replacing that file though. Probably not. [12:52] there we go :) [12:53] bjoern__, http://askubuntu.com/questions/602035/how-do-i-use-ubuntu-device-flash-with-the-bq-aquaris-e4-5 [12:53] rbasak, thanks! [12:55] @ ogra: As you can see in my post, I have tried to use this method to recover my mobile phone [12:56] and the device was clearly in the bootloader ? [12:56] Yes... I have chosen "fastboot" and then ubuntu-device-flash starts to flash the image... [12:57] Or have i missed something ? [12:57] bjoern__, you could try to flash recovery.img manually first [12:57] put it back into bootloader mode ... [12:57] This is what I have tried at next... [12:57] No success [12:57] sudo fastboot flash recover /path/to/recovery.im [12:57] sudo fastboot reboot [12:57] Ok... [12:57] Just a moment [12:58] *recovery ... and *.img [12:58] (sorry, my kbd is rather broken) [12:58] No prob [12:59] < waiting for device > [12:59] sending 'recover' (8394 KB)... [12:59] OKAY [ 0.338s] [12:59] writing 'recover'... [12:59] FAILED (remote: partition table doesn't exist) [12:59] oh, and you probably want sudo fastboot reboot-bootloader ... so you can select recovery right after [12:59] finished. total time: 0.343s [12:59] rbasak, maybe I can export a csv from the sqlite file [12:59] john-mcaleely, ^^^^^ EEEK ! [12:59] mr_november: sure - the tables are pretty readable. [12:59] bjoern__, oh, wait ... recovery ... not recover [12:59] :-) [12:59] Mom [13:00] mr_november: but no point backing up unless you know how to restore. [13:00] Yeah [13:01] it s a recognised problem that the mms doesn t work ? [13:01] @ ogra: ok, I have done a "sudo fastboot flash recovery recovery.img" + "sudo fastboot reboot-bootloader" [13:01] i got no audio on my nexus 4 (devel-proposed), "The phone is in silent Mode" . [13:02] Se7, no, but you might need to set up an APN in the cellular settings, some providers require that [13:02] Now device is in state "=> fastboot mode" [13:02] i did ogra_ :( [13:02] bjoern__, switch to recovery [13:02] and laet it boot [13:02] (into the recovery mode) [13:02] There is no option "recovery"... only "fastboot [13:02] ogra_, ENOTENOUGHCONTEXT [13:02] now i searched some logs and found in tone-generator log ausrv: server connection failure: COnnection refused Trying to connect to default Pulseaudio [13:03] john-mcaleely, another messed up device [13:03] rbasak, does that sqlite only have sms data? [13:03] bjoern__, hmm, i clearly have three options to select from in bootloader mode [13:03] fastboot, normal and recovery [13:04] ogra_, and what was the immediate cause of messup? [13:04] john-mcaleely, no idea, ask bjoern__ [13:04] Yes, normally I have them, too... But with "sudo fastboot reboot-bootloader" things seem to be a little bit different [13:04] :) [13:04] well, then use the key combo you usually use [13:04] bjoern__, for my information, what was happening before your device went awol? (ie what might have caused it) [13:04] you want to boot into the new recover.img that you just flashed ... [13:05] Yes... The shit happens as I changed language settings... from german to english... [13:05] * ogra_ wonders whats up with the y key ... usually it is g that is broken on this kbd [13:05] Device wants a reboot and crashes [13:05] bjoern__, that is definitely worth a bug report [13:06] I think, too.... Thats why I have opened a question at AskUbuntu... Is there a better place to report this bug ??? [13:06] see the channel topic "bugs filing" [13:06] Ok.. Thanks... === dandrader|afk is now known as dandrader [13:07] I have rebootet my device with "Vol up + power" and chosed RECOVERY... Now I see a big Ubuntu logo [13:07] bjoern__, once you arein the new recovery, check that you can use "adb shell" [13:08] ogra: How I could see, that I am in recovery mode ??? [13:08] the ubuntu logo is a good indicator :) [13:08] can you adb shell ? [13:08] While displaying big Ubuntu Logo, adb devices says "no devices found" [13:08] hmm... [13:09] adb kill-server; sudo adb devices [13:09] Ok, it now shows BQ boot logo [13:09] try that line [13:09] oh, was the logo you saw spinning ? [13:09] Yes, now a little ubuntu logo spins... [13:09] then it was actually flashing something [13:09] yeah, seems you are recovered :) [13:09] This is the same effect since devices has crashed [13:09] How log does is take ?? [13:10] if you see the small ubuntu logo after the bq one ... max 30sec [13:10] then you should see a session again [13:10] Nope... still turning... [13:10] rsalveti: ping [13:10] This night, it turns > 8 hours [13:11] hmm [13:12] turning.... [13:12] bjoern__, so try to get back into recovery [13:12] Ok [13:12] Mom [13:12] you didnt actually flash it yet, that was a cached OTA [13:13] (i had just hoped it would get your back in line) === MacSlow|lunch is now known as MacSlow [13:13] Ok, display shows "recovery, fastboot, normal" [13:13] pick recovery [13:13] ok [13:13] BQ logo [13:13] check that adb shell works [13:14] Big Ubuntu logo [13:14] good [13:14] not spinning i hope :) [13:14] adb shell does not work [13:14] adb kill-server; sudo adb devices [13:14] try that [13:14] $ adb kill-server; sudo adb devices [13:14] * daemon not running. starting it now on port 5037 * [13:14] * daemon started successfully * [13:14] List of devices attached [13:14] No device [13:14] peat-psuwit: pong [13:14] Still BIG logo [13:15] hmm, then you need to flash the recovery.img again [13:15] the OTA overwrote the open one [13:15] Ok, i will try it with your manual command line [13:15] BQ logo [13:16] THIS is different [13:16] small logo [13:16] ev: so my problem (back to the original question) is that the user reported that something crashed on his phone, and he got a crash file under /var/crash that got upload (had the uploaded stamp), but then how to find out that exact crash in errors.ubuntu.com? do we have any crash id that we can use in order to find an specific crash file that got uploaded [13:18] rsalveti: I found another parameter to be set. [13:18] https://github.com/CyanogenMod/android_frameworks_base/commit/11ed43242a0fa20f4ef514562514e1bdfb33199e [13:19] rsalveti, the whoopsie log on the device has a UUID by which you can search [13:19] i never understood why we dotn expose that anywheer else but in the log [13:19] I hacked pulseaudio to make that call now, but still no voice. [13:20] Is it possible to expose audio HAL's set_parameters in pulseaudio outside? [13:22] tedg: you about? we have a question for you in #ubuntu-touch-meeting if you are [13:22] popey, Sure, what's up? [13:22] can you join ? [13:27] peat-psuwit: interesting [13:28] peat-psuwit: it's exposed via stream parameters if I recall correctly [13:28] let me check [13:29] peat-psuwit: for example http://paste.ubuntu.com/10723970/ [13:29] you can set properties via pactl as well when testing [13:30] but even after setting that it didn't really work for you, so we first need to find out the right properties for your device [13:30] bjoern__, just FYI, i just switched my phone from german to en_US and dont get any boot problem [13:32] rsalveti: I think those vsid calls need to be made inside pulseaudio, because I think parameters is kept locally inside audio HAL. [13:33] ogra_: bjoern__: you could also just use 'fastboot boot recovery.img' [13:33] then flash with ubuntu-device-flash [13:33] no need to reflash recovery [13:33] That's why I ask if set_parameters can be exposed [13:33] peat-psuwit: right, you could use the sink parameters as I pasted you for testing [13:33] rsalveti, yeah, i was just wondering if just doing a factory reset from the recovery menu might not be enough [13:34] @ ogra: ok, I will try this.. [13:34] bjoern__, probably try this first http://askubuntu.com/questions/602834/how-to-reset-bq-ubuntu-phone-when-gui-is-inaccessible [13:35] might be enough [13:35] Ok [13:35] Thanks a lot... I will try... [13:37] rsalveti: I have to change proplist for sink, right? [13:37] @ ogra: Problem here: Cause my recovery mode isn't working, I have no option "wipe all data" [13:38] But probably a "sudo fastboot -w" will help ? [13:38] peat-psuwit: yeah [13:39] there is a pa_log_debug in that function, you can see if it worked or not by checking your syslog (if you enabled debug in pulseaudio) [13:39] sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf [13:39] if not yet, but would need to restart the job [13:40] bjoern__, once you are in recovery and see the big ubuntu logo you need to "unhide" the menu [13:41] by pressing power [13:41] (i think) [13:41] that should give you a big menu [13:41] i wouldnt play with fastboot -w ... thats an android thing and might cause damage [13:42] Ok [13:43] Oh man !!! Unhiding the menu works... I am happy... [13:43] :) [13:43] try a factory reset now [13:43] ...wiping... [13:45] Rebooting [13:45] *bibber* [13:45] small ubuntu logo [13:46] Huuuuurraaaa !!!! [13:46] Es lebt ! [13:46] Uhhmmm.... device is still alive [13:46] supi :) [13:46] Many thanks Oliver !!! [13:47] welcome ... i still wonder why/how you got there ... [13:47] Oh, I will write this down in my personal WIKI [13:47] Well... I could try to reproduce this... [13:47] just switching langs doesnt seem to trigger it for me [13:47] Hmmm... [13:47] Probably I could reproduce the steps... [13:47] I will try [13:48] Upps... My touch screen is not working... Oh... I am in recovery image mode... ?? [13:49] adb is not working... [13:49] I will try to flash the stock rom image [13:53] zsombi: hi. do you know if there is a change in uitk in vivid that would have fixed bug #1438419? and could we perhaps get it backported to RTM if so? [13:53] bug 1438419 in webbrowser-app (Ubuntu RTM) "Transparent confirmation dialog" [Undecided,Confirmed] https://launchpad.net/bugs/1438419 [13:54] @ ogra: This worked for me... back in business... :-) Thanks a lot ! [13:54] pmcgowan: ^^ think maybe we could get that on target for next OTA if we're going to stick on RTM for it? [13:56] bjoern__, enjoy :) [13:57] dobey, hopefully we go to vivid next [13:58] rsalveti: doesn't seems to work. Different function in audio HAL is called (is out_set_parameters, should be adev_set_parameters) [14:04] ogra_, rsalveti: the normal way of finding these is by looking up the system identifier, then pulling up the page of all the crashes for a system under errors.u.c. The phone preferences should have UI for this [14:04] pmcgowan: i guess it would be fine to target it for the next ota then still, since vivid already fixes it. so either we end up with vivid, and just mark it as fixed at that point, or we also fix it in rtm and have it in the next OTA as well? [14:04] the reason to do it this way is that local crashes are deleted, whereas on the error tracker they persist forever [14:05] you can then click down to an individual error report and then "up" to a bucket (problem set) of those errors [14:05] where you'll see the full retraced crash [14:05] you mean the "show all former reports" function that fires up the browser ? [14:05] dobey, once I make a new ota tag we can collect such bugs so we dont forget, but I really expect vivid is the next release after next week [14:06] peat-psuwit: oh, right =\ [14:06] well hopefully it's stable then :) [14:06] need to export something for adev_set_parameters then [14:07] ev, do you mean the function that opens the website ? [14:07] yeah [14:07] ev: but is there some sort of unique identifier for a device? [14:07] though that was the quick and dirty version [14:07] like I wanted to check the upload for that specific user [14:07] there's spec for displaying them inline [14:07] ev, thats only a list of UUIDs ... [14:07] rsalveti: yes, I'll get you the command [14:07] ev, how would i map it to a specific issue [14:07] -ETOOMANYQUESTIONS :) [14:08] without grepping in the whoopsie log (where it is actually showing the relation between crash file and UUID) [14:08] rsalveti: gdbus call -y -d com.ubuntu.WhoopsiePreferences -o /com/ubuntu/WhoopsiePreferences -m com.ubuntu.WhoopsiePreferences.GetIdentifier [14:09] ogra_: the UUIDs are identifiers for the crashes (OOPS IDs) [14:09] ev, right ... [14:09] hm, need to call as root on the device [14:09] crashes are bucketed together into problems, where a retrace of a single crash will be represented [14:09] [12:55:58] Reported OOPS ID d5e75c50-d926-11e4-9261-fa163e4ccdf2 [14:09] [12:56:00] Parsing /var/crash/_usr_lib_arm-linux-gnueabihf_url-dispatcher_url-dispatcher.32011.crash. [14:09] this is the relation i mean [14:10] so you can go from system ID 1->M set of crashes M->M problems [14:10] the only place wheer i can get that info is the logfile currently [14:10] no, you can get it from the website if you know the system ID [14:10] without having to crawl throuh 150 UUIDs on the website for my device [14:10] for any crashes that have been uploaded [14:10] ah [14:10] there is that :) [14:10] but hey, there's a RESTful API [14:11] pete-woods, hi, did tests pass using the proposed dbusmock branch? [14:11] also, someone really needs to talk to design so that site gets a mobile CSS [14:11] ogra_: you could do that :). Seriously, errors and daisy are UE owned products [14:12] i might :) [14:12] I'd rather not just turf everyone to bdmurray, who has zero help on it these days [14:12] but i think it is a general prob [14:12] . [14:12] LP isnt much better ;) [14:12] thostr_, USS seems to work well using silo 6. APIs work, the wifi screen works. [14:12] ogra_: if a mobile CSS for launchpad is important to your team, come to the LP stakeholder meeting :D [14:13] ev, well, it isnt *important* ... i thihnk it simply looks super un-professional that we are now a mobile OS distributor but none of our tools even remotely manages to be shown on mobile devices [14:13] jgdx: great, thanks! [14:14] i mean, i dont want to do code reviews on my phone ... but something as basic as opening a bug report from a mail shouldnt leave me with a broken looking website :) [14:14] and i dont think it is UEs job ... not even for errors.u.c [14:21] pmcgowan: oh, if the ota is next week instead of this one, could we maybe get it in for ww13-ota if the uitk team can get the fix backported/landed by monday? === chihchun is now known as chihchun_afk [14:25] dobey, if we knew the fix we could [14:25] dandrader: is the change from 350ms to 1sec wanted? [14:27] dobey, half of europe has holidays tomorrow and on mon .. [14:27] pmcgowan: well it seems to be fixed in vivid already, so i guess it should be relatively easy for someone who knows the code to be able to discern what fixed it, from a diff between rtm and vivid, of the toolkit. i don't know if anyone's around that can do that though [14:27] tsdgeos, yes, but I could make it a bit smaller, like 600ms. this is just a fallback case in case some item takes too long to make a decision, which should not happen in the first place [14:27] ogra_: i know :( [14:27] ogra_: some places have today too [14:28] not sure how the SDK team is spread across "easter countries" though [14:28] tsdgeos, but if the value is too low it might interfere with valid cases [14:28] rsalveti: Does pulseaudio's card have proplist? [14:28] yeah [14:28] dandrader: ok [14:28] dandrader: you tricked me into acepting a huge review :D [14:31] peat-psuwit: the function is exported but not connected via a proplist yet [14:31]