[00:01] <Phoenixz> Is it possible to install kubuntu on a usb drive? that is to say, I have a motherboard, no harddrive, one flash drive that contains the kubuntu install, and one target USB.. is this possible, and would this just work the same as installing on a harddrive?
[00:05] <valorie> Phoenixz: you can do it, but it will not be the same
[00:06] <Phoenixz> valorie: okay. what would be different?
[00:06] <valorie> it will be slower
[00:06] <valorie> I'm confused though -- are you saying you have a flash drive AND a USB?
[00:07] <valorie> or that the flash drive is the USB key
[00:07] <Phoenixz> valorie: ah :) well yeah, this is for a system that will be dedicated to one task that will not require much disk access so
[00:07] <Phoenixz> valorie: errr, no, both are USB drives
[00:08] <valorie> ok
[00:08] <Phoenixz> thing is that from what I see, I would not need a harddrive, afaik, it should be able to run from USB directly, not?.. I need to build 20 of these, so why waste money on 20 harddrives if they wont even be used (other then to just boot up the OS)
[00:08] <valorie> so you'll run from one, and use the other for storage/files?
[00:08] <valorie> USB is slow
[00:09] <valorie> that's the bit that will slow everything, but as you say, if you don't need much drive access, it will be fine
[00:09] <valorie> just slow to start, and some fiddling to get things to save
[00:09] <Phoenixz> valorie: well no
[00:10] <Phoenixz> again, all I need is to have kubuntu installed and having it start up straight to desktop, and start one new process.. that process wont do much disk access (if any at all), so all it basically has to do is.. boot.. start os, start kde, go to desktop, start program, and it runs..
[00:10] <Phoenixz> ah, sorry, I was behind with reading your replies :)
[00:10] <Phoenixz> valorie: but then
[00:11] <Phoenixz> if I start the computer, I have both the kubuntu install USB and the target USB in there.. I could boot from the kubuntu install USB, and then install it on the target USB just as if it were a harddrive, right?
[00:11] <valorie> yes
[00:11] <valorie> you'll want to remove it once the install is done though
[00:12] <valorie> or you'll always get the live session
[00:12] <valorie> if you have 20 to build, might be worth your while to write a DVD
[00:13] <valorie> which as I recall is a bit faster to boot
[00:13] <valorie> now, i've never tried this, so i can't guarantee it will work, but i don't see why it wouldn't
[00:13] <Phoenixz> valorie: yeah, the install USB will be removed after.. What I do then is modify the install, make sure the right things are installed, build a script that iwll start up everything, then shut it down, and make 20 copies of that USB...
[00:14] <Phoenixz> valorie: well.. that would require 20 DVD drives... :) These are bare systems and I'd like to add as little as possible
[00:14] <valorie> I see
[00:14] <valorie> also, I'm stuck in the past maybe
[00:14] <valorie> lol
[00:15] <Phoenixz> valorie: yeah, I know the feeling..  What testing rograms or roceedures should I run - I am on USB2.0 so far ??
[02:46] <Walzmyn> Whenever I reboot I have a bunch of kslideshow windows come up after login- what's causing that?
[02:51] <Walzmyn> arthurfiggis: i figured out my login problem. I edited xorg.conf. In the section for the monitors there's an 'option    "Primary" "True" '  I moved this to the correct monitor and all's good
[05:34] <Takeshi> prueba
[05:46] <JhonSmith> asd
[06:23] <alesan> hallo
[06:24] <alesan> where is the option to allow the resize of maximized windows?
[06:24] <alesan> it used to be there, now I canno find it anymore
[07:02] <James0r> what's the best way to install Google Earth in Kubuntu 13.10?
[07:59] <lordievader> Good morning.
[09:02] <Taduro> apachelogger: do you know where the kmail configs are saved?
[09:02] <skramer_> Hi! I just discovered that Dolphin does not tell me about files I opened today or yesterday. It shows some files in "This Month" and "Last Month", but by far not all files that I had touched during that time.
[09:02] <skramer_> Am I missing some config? How could I fix that?
[09:09] <Taduro> Does somebody know where he kmail configuration files are located?
[09:20] <apachelogger> Taduro: depends on the config... if it's actually kmail then ~.kde/share/config, if you mean email account settings then something like ~/.config/akonadi
[09:24] <Taduro> apachelogger: I don't remember my email account, that's why I searching the config...
[09:26] <apachelogger> Taduro: try kate ~/.kde/share/config/akonadi_imap*
[09:26] <apachelogger> if nothing's in there possibly config/mailtransports or config/emaildefaults
[09:28] <Taduro> apachelogger: but that will not show me the password
[09:29] <apachelogger> start kwalletmanager
[09:29] <apachelogger> there you can look at your wallet content and import other wallets etc.
[11:19] <gaga_rin> http://cs408724.vk.me/v408724392/5cca/b4dvdV4paiQ.jpg
[11:19] <gaga_rin> wow sry
[11:19] <gaga_rin> #nsfw
[12:13] <gonssal> Hi all. After updating to 13.10 kde is not detecting an external ext4 usb hard drive that was working flawlessly in 13.04.
[12:13] <gonssal> The drive is detected by the system, appears in kinfocenter and the partition manager, but not in dolphin/konqueror
[12:13] <gonssal> Any ideas on how to fix it?
[12:50] <Blueskaj> Howdy folks
[16:17] <Whiskey`Wonka> oh boy! even after a reboot still no auth for muon-updater
[16:18] <Whiskey`Wonka> running via kdesudo now, maybe a update will fix it
[16:54] <soee> ?
[16:59] <TheRealCrell> Hi all. I recently updated to 13.10. My network manager applet is now missing, however.  While I can connect on wired, it means I can't look up any of my VPNs to activate, or wireless networks.  Any idea how I get it back?
[16:59] <TheRealCrell> (The little googling I did only found "applet missing, can't connect at all" type problems.)
[17:00] <soee> TheRealCrell: click on Systary properties
[17:01] <soee> and check if icon Networmanager is chekced to be show
[17:02] <TheRealCrell> Network Manager is not in System Tray Settings at all.
[17:02] <soee> thers no checkbox to check ?
[17:02] <TheRealCrell> There is not.
[17:02] <sithlord48> do you have a seperate widget for network management on your system ? check on Add widget
[17:03] <TheRealCrell> There appears to be one, but it's not adding to the plasma bar properly.  I can put it on my desktop, though.
[17:04] <TheRealCrell> Very odd... Why is it not in systray?
[17:04] <sithlord48>  you should check to see if the package " plasma-widget-networkmanagement " is installed. have you done any updates lately ?
[17:05] <TheRealCrell> sithlord48: I updated from 13.04 to 13.10 earlier this week.
[17:05] <sithlord48> TheRealCrell:  do you have plasma-nm package installed?
[17:05] <TheRealCrell> That package shows as installed.
[17:05] <TheRealCrell> Both of them.
[17:05] <amundsen> hi
[17:05] <sithlord48> no broken packages?
[17:06] <TheRealCrell> Not as far as I can tell.
[17:06] <amundsen> is there any way to add a "home" icon in the KDE desktop?
[17:06] <sithlord48> TheRealCrell:  try to update if you can . i think you may have broken package somewhere.
[17:06] <amundsen> i mean, i have a trash icon, and i'd like to add a home icon also
[17:07] <TheRealCrell> I did a routine update/upgrade 10 minutes ago.
[17:07] <sithlord48> amundsen:  if you are using the "folder" desktop then you only need to put a link to home in your ~/desktop folder
[17:07] <sithlord48> TheRealCrell:  and you just are not seeing the widget (i came in a bit late on the problem)
[17:08] <TheRealCrell> Correct.  There's apparently a SEPARATE standalone plasma widget I've not used before, but nothing in systray.
[17:08] <TheRealCrell> Er, wait...  WTF?
[17:08] <sithlord48> do you know if its the old widget or the new plasma nm one?
[17:08] <TheRealCrell> bah.  Bad me!
[17:08] <TheRealCrell> It was in a different list in the systray settings dialog than the one I was in a moment ago.
[17:09] <sithlord48> lol nice
[17:09] <TheRealCrell> I was in Entries, nto Display.
[17:09] <TheRealCrell> Too many damned options..
[17:10] <TheRealCrell> Thanks, sithlord48 and soee.
[17:11] <sithlord48> amundsen:  if your using the default desktop then you will need to add a folder widget to display the contents . you can jus add a shortcut for dolphin since it always starts in ~/ anyway
[17:11] <sithlord48> TheRealCrell: your welcome
[17:11] <soee> TheRealCrell: does it work ?
[17:11] <TheRealCrell> Yep.  Once I found the right dialog window. :-)
[17:11] <amundsen> sithlord48: thx
[17:11] <TheRealCrell> Now to remember my VPN password...
[17:11] <sithlord48> amundsen:  your welcome
[17:11] <soee> TheRealCrell: cool, enjoy best KDE distro :D
[17:12]  * TheRealCrell has been a user for many years.
[17:12] <sithlord48> don't forget to come visit kubuntuforums.net . i tend to be there to answer question more then here
[17:13] <TheRealCrell> Thanks.
[18:20] <AshishL> hi , i am new to KDE development and need help in installing  kubuntu for development via a VM . can anyone help me ?
[18:42] <wxl> hey guys, i'm not konsole's biggest fan and prefer urxvt. i would love to continue to get notifications on bells. is there any way i can make this happen?
[19:54] <Whiskey`Wonka> <much rage>
[19:54] <Whiskey`Wonka> is it really that hard to find the breakdown with muon??
[20:15] <keithzg> Hmm. Is the Comics plasmoid broken? I can "install" plugins for it, but they never show up to enable.
[20:17] <sithlord48> keithzg:  does appear to be broken.. when you add new comics nothing shows up .
[20:19] <keithzg> sithlord48: So not just me then. Hmm.
[20:20] <sithlord48> nope i tried when you asked.
[20:20] <keithzg> Yeah, seems to be a known bug: https://bugs.kde.org/show_bug.cgi?id=325028
[20:20] <sithlord48> was just going to suggest looking for a bug report too lol
[20:20] <keithzg> haha
[20:20] <keithzg> this ain't my first rodeo ;)
[20:20] <sithlord48> well welcome back to the rodeo :P
[20:20] <keithzg> heh
[20:53] <arthurfiggis> hello :) i've been trying to figure this out for ages and under different distro's, but i can't seem to find a reliable method...does anyone know how i could disable usb autosuspend completely? i have a wireless usb mouse and keyboard, i guess they aren't very good because they both time out and become unresponsive frequently :(
[20:53] <arthurfiggis> dmesg seems to indicate that they're just powering on and off regularly
[21:51] <ss_haze> how do I make ssh server work
[21:51] <ss_haze> I can't connect to it from other pc, I can only from itself
[21:52] <ss_haze> unban me at @ubuntu
[22:21] <arthurfiggis> hello again :) just as a general question...i seem to have no luck getting my current dynex wireless mouse and keyboard combo working properly...the keyboard is fine but the mouse loses connectivity every few seconds or so...does anyone know of a good wireless mouse/keyboard combo that is ubuntu compatible?


[00:06] -queuebot:#ubuntu-release- New: accepted mesa [amd64] (bionic-proposed) [18.2.2-0ubuntu1~18.04.1]
[00:06] -queuebot:#ubuntu-release- New: accepted mesa [armhf] (bionic-proposed) [18.2.2-0ubuntu1~18.04.1]
[05:14] -queuebot:#ubuntu-release- New binary: hunspell [ppc64el] (disco-proposed/main) [1.7.0-2] (desktop-core)
[05:14] -queuebot:#ubuntu-release- New binary: hunspell [s390x] (disco-proposed/main) [1.7.0-2] (desktop-core)
[05:15] -queuebot:#ubuntu-release- New binary: hunspell [amd64] (disco-proposed/main) [1.7.0-2] (desktop-core)
[05:15] -queuebot:#ubuntu-release- New binary: hunspell [arm64] (disco-proposed/main) [1.7.0-2] (desktop-core)
[05:16] -queuebot:#ubuntu-release- New binary: hunspell [armhf] (disco-proposed/main) [1.7.0-2] (desktop-core)
[05:17] -queuebot:#ubuntu-release- New binary: hunspell [i386] (disco-proposed/main) [1.7.0-2] (desktop-core)
[06:44] <RAOF> tsimonq2: You might also enjoy the new yaml-cpp symbols file!
[08:06] <xnox> vorlon, surely we shouldn't need rust-core-foundation like at all. or like not on most arches.
[09:39] <rbalint> sil2100: i'm still in the process of converting ~30 fixed bugs to have sru template but could you please accept u-u to xenial-proposed? the upload is what gets into xenial sooner or later and giving it more time in -proposed gets us more feedback from users
[09:40] <rbalint> sil2100: the delta to xenial is huge but to bionic it is minimal
[09:43] <LocutusOfBorg> infinity, I forwarded to lintian developers your lintian fix <3 https://salsa.debian.org/lintian/lintian/merge_requests/79
[09:43] <gitbot> lintian issue (Merge request) 79 in lintian "* Fix two typos introduced when parameterising test architectures in:" [Opened]
[09:43] <rbasak> sil2100 isn't here?
[09:55] <infinity> LocutusOfBorg: I already filed a bug with the patch.
[09:57] <infinity> LocutusOfBorg: But I guess the MP works too.  We'll see which they see first. :P
[09:58] <LocutusOfBorg> infinity, I'm in contact with lamby on #debian-qa, this is why I did the PR :)
[09:58] <LocutusOfBorg> and I updated it with the closed bug!
[09:58] <LocutusOfBorg> jrtc27 did a MR with the other ubuntu delta, this is why I opened one
[10:03] -queuebot:#ubuntu-release- New binary: gdcm [s390x] (disco-proposed/universe) [2.8.8-5] (kubuntu)
[10:07] -queuebot:#ubuntu-release- New binary: gdcm [ppc64el] (disco-proposed/universe) [2.8.8-5] (kubuntu)
[10:17] -queuebot:#ubuntu-release- New: accepted hunspell [amd64] (disco-proposed) [1.7.0-2]
[10:17] -queuebot:#ubuntu-release- New: accepted hunspell [armhf] (disco-proposed) [1.7.0-2]
[10:17] -queuebot:#ubuntu-release- New: accepted hunspell [ppc64el] (disco-proposed) [1.7.0-2]
[10:17] -queuebot:#ubuntu-release- New: accepted ruby-icalendar [amd64] (disco-proposed) [2.4.1-2]
[10:17] -queuebot:#ubuntu-release- New: accepted hunspell [arm64] (disco-proposed) [1.7.0-2]
[10:17] -queuebot:#ubuntu-release- New: accepted hunspell [s390x] (disco-proposed) [1.7.0-2]
[10:17] -queuebot:#ubuntu-release- New: accepted hunspell [i386] (disco-proposed) [1.7.0-2]
[10:24] -queuebot:#ubuntu-release- New binary: gdcm [arm64] (disco-proposed/universe) [2.8.8-5] (kubuntu)
[10:30] -queuebot:#ubuntu-release- New binary: gdcm [armhf] (disco-proposed/universe) [2.8.8-5] (kubuntu)
[10:43] -queuebot:#ubuntu-release- New binary: gdcm [i386] (disco-proposed/universe) [2.8.8-5] (kubuntu)
[10:55] -queuebot:#ubuntu-release- New binary: gdcm [amd64] (disco-proposed/universe) [2.8.8-5] (kubuntu)
[11:01] -queuebot:#ubuntu-release- New: accepted gdcm [amd64] (disco-proposed) [2.8.8-5]
[11:01] -queuebot:#ubuntu-release- New: accepted gdcm [armhf] (disco-proposed) [2.8.8-5]
[11:01] -queuebot:#ubuntu-release- New: accepted gdcm [ppc64el] (disco-proposed) [2.8.8-5]
[11:01] -queuebot:#ubuntu-release- New: accepted gdcm [arm64] (disco-proposed) [2.8.8-5]
[11:01] -queuebot:#ubuntu-release- New: accepted gdcm [s390x] (disco-proposed) [2.8.8-5]
[11:01] -queuebot:#ubuntu-release- New: accepted gdcm [i386] (disco-proposed) [2.8.8-5]
[11:31] -queuebot:#ubuntu-release- Unapproved: samba (bionic-proposed/main) [2:4.7.6+dfsg~ubuntu-0ubuntu2.5 => 2:4.7.6+dfsg~ubuntu-0ubuntu2.6] (core)
[11:58] <LocutusOfBorg> tjaalton, any reason for mesa using gcc-7?
[11:58] <LocutusOfBorg> https://packages.qa.debian.org/g/gcc-8/news/20181123T092059Z.html
[11:58] <LocutusOfBorg> the fix for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87859 is in gcc-8 version 8.2.0-10
[11:59] <tjaalton> LocutusOfBorg: look at the bug
[11:59] <tjaalton> ha
[11:59] <tjaalton> *ah
[11:59] <tjaalton> yes it's fixed in gcc now
[12:00] <tjaalton> 18.3 will build with gcc8 again
[12:17] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (cosmic-proposed) [1:2.12+dfsg-3ubuntu8.2]
[12:17] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (bionic-proposed) [1:2.11+dfsg-1ubuntu7.9]
[12:18] -queuebot:#ubuntu-release- Unapproved: accepted libvirt [source] (cosmic-proposed) [4.6.0-2ubuntu3.1]
[12:18] -queuebot:#ubuntu-release- Unapproved: accepted libvirt [source] (bionic-proposed) [4.0.0-1ubuntu8.6]
[13:01] -queuebot:#ubuntu-release- Unapproved: libreoffice (cosmic-proposed/main) [1:6.1.2-0ubuntu1.1 => 1:6.1.3-0ubuntu<IP_ADDRESS>] (kubuntu, ubuntu-desktop)
[13:09] -queuebot:#ubuntu-release- Unapproved: libreoffice-l10n (cosmic-proposed/main) [1:6.1.2-0ubuntu1 => 1:6.1.3-0ubuntu<IP_ADDRESS>] (ubuntu-desktop)
[13:43] <LocutusOfBorg> thanks tjaalton :)
[15:45] <acheronuk> still on cosmic http://qa.ubuntuwire.org/ftbfs/
[15:46] <acheronuk> wgrant: ? ^
[15:56] -queuebot:#ubuntu-release- Unapproved: rdma-core (bionic-proposed/main) [17.1-1 => 17.1-1ubuntu0.1] (desktop-core, ubuntu-server)
[15:56] -queuebot:#ubuntu-release- Unapproved: rdma-core (cosmic-proposed/main) [19.0-1 => 19.0-1ubuntu0.1] (desktop-core, ubuntu-server)
[17:38] <vorlon> xnox: well, rust-core-foundation doesn't build on !x86 currently, so we effectively have that.  But if you have opinions on whether rust-cargo shouldn't build-depend on it on !x86, you'll need to follow up with the Debian maintainers
[17:38] <xnox> vorlon, re-check rust-cargo
[17:38] <vorlon> k
[17:38] <xnox> vorlon, i made it build without core-foundation, but it generates non-existant dependencies on a newer (?!) rust-openssl
[17:40] <vorlon> xnox: btw I looked more closely at LP: #1797335, and in my test environment I'm running on a chip that doesn't have avx2.  So maybe it's the avx implementation that's pessimized?
[17:40] <xnox> vorlon, retest on a c5 instance in aws?
[17:41] <xnox> i think my other laptop has avx2 can't remember. and have things to do before eod.
[17:41] -queuebot:#ubuntu-release- New source: fwupd-snap (disco-proposed/primary) [1.0]
[17:57] <vorlon> "Hello , or anyone else affected,"
[17:57]  * vorlon looks askance at cpaelzer
[17:59] -queuebot:#ubuntu-release- New binary: rust-debcargo [amd64] (disco-proposed/universe) [2.2.9-1] (no packageset)
[18:01] -queuebot:#ubuntu-release- New binary: rust-debcargo [i386] (disco-proposed/universe) [2.2.9-1] (no packageset)
[18:16] -queuebot:#ubuntu-release- New binary: rust-debcargo [armhf] (disco-proposed/universe) [2.2.9-1] (no packageset)
[18:26] <doko> vorlon: please update ubuntu-release:force-badtest python-scipy/1.1.0-1ubuntu2/i386  to -2
[18:32] -queuebot:#ubuntu-release- New: accepted rust-debcargo [amd64] (disco-proposed) [2.2.9-1]
[18:32] -queuebot:#ubuntu-release- New: accepted rust-debcargo [i386] (disco-proposed) [2.2.9-1]
[18:32] -queuebot:#ubuntu-release- New: accepted rust-debcargo [armhf] (disco-proposed) [2.2.9-1]
[18:34] <xnox> do i want to know what mbrola is? and why does it trigger hundreds of tests for individual langauges?!
[18:42] <ginggs> sounds like a deadly virus
[18:49] <teward> heh
[18:49] <teward> xnox: multilingual speech synthesizer according to the LP data on it
[18:50] <teward> ... which explains why it's touching every language there heh
[18:51] <vorlon> I wonder what its tests look like
[18:51] <vorlon> is autopkgtest launching mechanical turk requests?
[18:53] <ginggs> would someone please kick the scipy can along? 'force-badtest python-scipy/1.1.0-2/i386'
[18:54] <ginggs> and 'force-badtest r-bioc-biocparallel/1.16.1-1/s390x r-bioc-biocparallel/1.16.1-1/armhf' too?
[18:59] <vorlon> ginggs: doko asked for scipy just above; I'm looking at it now
[19:00] <ginggs> vorlon: ah, missed that, thanks
[19:04] <NCommander> rbasak, ping, we're getting ready to upload the SRU for certbot, it's seven packages. Four new, one update, and then compatibility shims for the existing letsencrypt package so legacy code and plugins don't break.
[19:05] <rbasak> NCommander: it might be easier to review from wherever you're managing it (git?) rather than from the queue given the complexity involved.
[19:05] <NCommander> rbasak, it's sitting in a PPA
[19:05] <rbasak> I can review from there.
[19:06] <NCommander> I had to do entirely new packaging as I had to change the packages to use python 2.7 vs. 3
[19:06] <rbasak> Once reviewed I only have to check it's identical when it hits the queue.
[19:06] <NCommander> rbasak, Ok, there's one mistake in the PPA regarding versioning I was going to fix (I uploaded python-acme with the wrong version number)
[19:06] <NCommander> rbasak, https://launchpad.net/~certbot/+archive/ubuntu/xenial-sru/+packages
[19:07] <rbasak> NCommander: actually do you have it broken down further (individual commits) so I don't have to review a big blob of diff?
[19:07] <NCommander> rbasak, no, these are all new upstream versions
[19:07] <NCommander> python-letsencrypt/letsencrypt-apache got replaced with compatibility shims
[19:07] <vorlon> so why is this certbot SRU going to work better than the last one that sat for over a year without verification?
[19:07] <NCommander> certbot-* are backports
[19:07] <rbasak> vorlon: the previous one essentially failed verification.
[19:07] <vorlon> ah, doesn't appear that was ever noted in the bug tags
[19:08] <rbasak> I gave up as I timeboxed it twice and ran out of time twice. I felt it was too complex and a snap would be better, which is why I have a snap ready.
[19:08] <vorlon> right
[19:08] <rbasak> However I've always said that this doesn't block someone else working on SRUs, and NCommander volunteered.
[19:08] <vorlon> so why is the next one different
[19:09] <rbasak> I presume he's fixed the issues identified in my attempt.
[19:09] <NCommander> vorlon, because we don't want letsencrypt to stop working in Feb
[19:09] <rbasak> I didn't consider that I'd be the one ending up reviewing this anyway :-/
[19:09] <NCommander> rbasak, I actually didn't see why your attempt failed in the bug.
[19:09] <rbasak> NCommander: one of the uploads FTBFS
[19:09] <rbasak> Because a build dep shifted by the SRU itself, IIRC.
[19:10] <NCommander> If I have it building in a PPA, it should build properly, no?
[19:10]  * NCommander also does some of the "official" PPA uploads so I'm pretty good at nursing this stuff at this point
[19:12] <NCommander> rbasak, sorry for giving you a painful SRU but I do think it's important that we get this SRUed as not everyone installs snaps and LE breaking would be bad for the Internet
[19:12] <rbasak> NCommander: thanks. I'll review, but it'll probably be next week at the earliest.
[19:13] <NCommander> rbasak, that's fine, the LE team is reviewing to make sure they're compatibility shims and everything are working as expected so it's not quite ready for uploading but the packaging should be good to go.
[19:13] <NCommander> rbasak, this should also simplify future backports as the SRU will handle the migration to the new name.
[19:13] -queuebot:#ubuntu-release- Unapproved: ark (cosmic-proposed/universe) [4:18.04.3-0ubuntu1 => 4:18.08.3-1ubuntu1] (kubuntu)
[19:14] <NCommander> mdeslaur, after we get the SRU landed, we'll look at security pocket :)
[19:18] <acheronuk> please reject ark ^^^
[19:38] -queuebot:#ubuntu-release- Unapproved: rejected ark [source] (cosmic-proposed) [4:18.08.3-1ubuntu1]
[19:38] <apw> acheronuk, ^
[19:39] <acheronuk> apw: thanks. I must pay more attention to what branch I am on!
[20:04] <mdeslaur> NCommander: sounds like a good plan
[20:22] -queuebot:#ubuntu-release- Unapproved: cockpit (cosmic-backports/universe) [179-1 => 183-1~ubuntu18.10.1] (no packageset)
[20:31] -queuebot:#ubuntu-release- Unapproved: cockpit (bionic-backports/universe) [178-1~ubuntu18.04.1 => 183-1~ubuntu18.04.1] (no packageset)
[20:31] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (cosmic-backports) [183-1~ubuntu18.10.1]
[20:32] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (bionic-backports) [183-1~ubuntu18.04.1]
[23:13] <doko> finally, java-common migrated
[23:15] -queuebot:#ubuntu-release- New binary: hgsubversion [amd64] (disco-proposed/universe) [1.9.3-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: baresip [ppc64el] (disco-proposed/universe) [0.5.11-2] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: hypre [ppc64el] (disco-proposed/universe) [2.15.1-2] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: baresip [s390x] (disco-proposed/universe) [0.5.11-2] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: hypre [s390x] (disco-proposed/universe) [2.15.1-2] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: baresip [i386] (disco-proposed/universe) [0.5.11-2] (no packageset)
[23:22] -queuebot:#ubuntu-release- New: accepted hgsubversion [amd64] (disco-proposed) [1.9.3-1]
[23:22] -queuebot:#ubuntu-release- New binary: baresip [amd64] (disco-proposed/universe) [0.5.11-2] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: hypre [i386] (disco-proposed/universe) [2.15.1-2] (no packageset)
[23:46] -queuebot:#ubuntu-release- New: accepted baresip [amd64] (disco-proposed) [0.5.11-2]
[23:46] -queuebot:#ubuntu-release- New: accepted baresip [ppc64el] (disco-proposed) [0.5.11-2]
[23:46] -queuebot:#ubuntu-release- New: accepted hypre [i386] (disco-proposed) [2.15.1-2]
[23:46] -queuebot:#ubuntu-release- New: accepted hypre [s390x] (disco-proposed) [2.15.1-2]
[23:46] -queuebot:#ubuntu-release- New: accepted baresip [i386] (disco-proposed) [0.5.11-2]
[23:46] -queuebot:#ubuntu-release- New: accepted hypre [ppc64el] (disco-proposed) [2.15.1-2]
[23:46] -queuebot:#ubuntu-release- New: accepted baresip [s390x] (disco-proposed) [0.5.11-2]


[01:33] <gunawan> helo
[01:33] <gunawan> somebody here ?
[01:34] <gunawan> afk ?
[01:34] <gunawan> good bye my friend
[07:36] <phatboii> wow so far using ubuntu studio for my new recording studio has been great
[17:22] <epilac36> hola


[23:54] <wallyworld_> wgrant: can you point me at the doco that covers the pop3/imap settings to pull mail from the qas mailbox?
[23:56] <wgrant> wallyworld_: https://wiki.canonical.com/InformationInfrastructure/OSA/LPHowTo/ConnectToStagingMailbox
[23:56] <wallyworld_> wgrant: thanks


[08:14] <mardy> Trevinho: ciao! LIM work very well here, but I miss the double click to maximize the window. Do you plan to add it?
[08:14] <Trevinho> mardy: ciao!
[08:14] <Trevinho> mardy: it's already there :)
[08:15] <Trevinho> mardy: you only have to tune it
[08:15] <mardy> Trevinho: ah, dconf?
[08:15] <Trevinho> mardy: yes, see https://bugs.launchpad.net/unity/+bug/1283695/comments/2
[08:16] <mardy> Trevinho: cool, thanks! :-)
[08:17] <Trevinho> mardy: np
[08:17] <mardy> Trevinho: works like a charm :-)
[08:19] <Trevinho> mardy: I did that at the beginning, then designers preferred to avoid the delay it causes (no other way, unfortunately... I can't go into people's mind :P)
[09:13] <tsdgeos> this is very confusing
[09:13] <tsdgeos> i'm having poblems with LVWPH not scrolling to the end
[09:13] <tsdgeos> and i've converted it to a regular LV and it doesn't scroll to the end either (it bounces a bit early)
[09:13] <tsdgeos> but if instead my own QQuickView i use qmlscene
[09:14] <tsdgeos> then it works
[09:14] <tsdgeos> :S
[09:14] <tsdgeos> what is qmlscene doing!
[09:14]  * tsdgeos digs
[09:32] <tsdgeos> buuuuuuuuuuuuuuuuug
[09:42] <greyback> now why isn't my tablet showing up in adb devices...
[09:45] <mhr3> Saviq, could you pls add https://code.launchpad.net/~mzanetti/unity-scopes-shell/activate-appid-2/+merge/205443 if you plan to land right-edge before new-scopes?
[09:45] <mhr3> add to unity8 landing ask that is
[09:48] <tsdgeos> Saviq: do you have 5.0 or 5.2 installed?
[09:48] <tsdgeos> on desktop
[10:02] <Saviq> tsdgeos, 5.2
[10:02] <Saviq> mhr3, there isn't a landing ask for right edge yet, but will make sure to add it there
[10:03] <Saviq> mhr3, but anyway, isn't -scopes blocked due to 5.2 already?
[10:03] <tsdgeos> Saviq: i have a weird behaviour of using a qquickview vs using qmlscene
[10:03] <Saviq> tsdgeos, yeah, I read above, want me to downgrade to 5.0?
[10:04] <tsdgeos> wanted to know if it was new in 5.0
[10:04] <tsdgeos> or somehow compiz had a regression since last time i tried :D
[10:04] <tsdgeos> Saviq: it's ok, i can do it too, just wanted to know if you had it at hand
[10:04]  * tsdgeos ppa purges
[10:05] <Cimi> greyback, usually killing adb and/or rebooting pc solves
[10:05] <greyback> Cimi: did the first one, second didn't make sense as phone connects fine with adb
[10:06] <mhr3> Saviq, yea, it is.. any idea when the 5.2 migration might finish?
[10:07] <Saviq> mhr3, we're down to two last issues as of yesterday
[10:09] <mhr3> Saviq, so i take it you're not leaving today until that row says Landed? ;)
[10:10] <Saviq> mhr3, you mean the new scopes one? didn't I tell you it's not gonna happen before Tuesday, probably? :P
[10:10] <mhr3> Saviq, no, 5.2
[10:10] <Saviq> mhr3, ah, not mine to say
[10:47]  * greyback needs more cpuz
[10:49] <Saviq> greyback, hey, there's three of your branches that I reverted from new-scopes to be merged into trunk separately - see history of https://code.launchpad.net/~unity-team/unity8/new-scopes-clean-to-trunk/
[10:49] <Saviq> greyback, would be good to get those in (with tests) sometime
[10:49] <greyback> Saviq: sure
[10:50] <Saviq> greyback, not hugely pressing, though
[10:51] <Saviq> Cimi, hey, please let me know when you have the carousel changes ready
[10:52] <Cimi> Saviq, I was still testing the zoomable branch :)
[10:52] <Cimi> Saviq, trying to see why wasn't working properly here
[10:52] <Cimi> Saviq, I can switch back to carousel now
[10:52] <Saviq> Cimi, please do, higher prio
[10:53] <Cimi> Saviq, I don't understand why we have to split
[10:53] <Cimi> Saviq, I basically have to restart from scratch
[10:53] <Saviq> Cimi, because we want to reduce new scopes diff where possible, and CardTool and such are already in trunk
[10:53] <Cimi> ok
[10:54] <Cimi> Saviq, I'll do from scratch
[10:54] <Saviq> Cimi, should be easy to cherry-pick
[10:55] <Saviq> Cimi, I can do it if you're not sure how
[10:55] <Cimi> Saviq, I'm not good with bzr, but I know well to copy-paste ;)
[10:55] <Saviq> Cimi, sure
[10:55] <Cimi> Saviq, how shall we write comments?
[10:55] <Cimi> Saviq, I started doing /// because you asked me so weeks ago
[10:56] <Cimi> Saviq, not we are back to /*
[10:56] <Saviq> Cimi, not /* but /*!
[10:56] <Saviq> Cimi, just look at style in the file
[10:56] <Saviq> Cimi, we want to be consistent within files at the least (until we become consistent across them) ;)
[11:16] <mzanetti> what was the last time someone executed all our autopilot tests on the phone? successfully that is
[11:16] <mzanetti> I can't manage to get a successful run
[11:17] <mzanetti> elopio: hey, you around yet?
[11:19] <tsdgeos> mzanetti: Saviq did the other day i think
[11:19] <Saviq> mzanetti, if you get "process not found" that's Qt 5.0 crash
[11:20] <mzanetti> right. I get 2 of them for the emulator tests elopio did, and one of the notifications tests failing reliably
[11:25] <Saviq> mzanetti, which notification one? and apt-cache policy libautopilot-qt ?
[11:25] <mzanetti> Saviq: unity8.shell.tests.test_notifications.EphemeralNotificationsTests.test_append_hint
[11:25] <Cimi> did unity become longer to compile in the last month or is it just my pc?
[11:26] <mzanetti> 1.4+14.04.20140303.is.1.4+14.04.20131106.1-0ubuntu1 0
[11:26] <Saviq> mzanetti, what's the failure?
[11:26] <Saviq> Cimi, apt-get install ccache
[11:26] <mzanetti> yeah, process not found
[11:26] <Saviq> mzanetti, ah then that's the crash
[11:26] <mzanetti> interesting that its always this one tho...
[11:26] <Cimi> Saviq, don't have much storage
[11:26] <Cimi> Saviq, how much it takes?
[11:26] <Cimi> in .cache ?
[11:26] <Saviq> Cimi, 1GB on my home
[11:26] <Cimi> Saviq, ok, might be enough
[11:27] <Cimi> I mean, fine
[11:49] <Cimi> Saviq, https://code.launchpad.net/~unity-team/unity8/carouselTool/+merge/209655
[11:49] <Saviq> Cimi, cheers
[11:50] <Saviq> Cimi, no need for type:int, it's only needed for aliases and in case you want to override what the property type actually is
[11:50] <Cimi> Saviq, I forgot to take carousel as grid
[11:50] <Cimi> Saviq, is it required?
[11:50] <Saviq> Cimi, yes
[11:51] <Saviq> Cimi, let me get you a diff
[11:51] <Cimi> Saviq, i can merge
[11:51] <Cimi> no problem
[11:51] <Saviq> Cimi, http://paste.ubuntu.com/7043700/
[11:52] <Saviq> Cimi, that branch is against new-scopes I think, so you don't want it whole
[11:52] <Cimi> Saviq, I override those changes
[11:53] <Cimi> Saviq, so I don't need it
[11:53] <Cimi> apart cardfiltergrid
[11:53] <Saviq> Cimi, all of them?
[11:53] <Saviq> Cimi, ah, in that case is fine
[11:53] <Saviq> Cimi, sentence case in docs, please
[11:55] <Saviq> Cimi, what's 32	+ property var carouselTool used for?
[11:55] <dandrader> mzanetti, question on your right-edge-2 behavior (still flashing a second device to try out your branch again, as I'm doing development on the first one)
[11:55] <Cimi> Saviq, not used now
[11:55] <Cimi> Saviq, it is used with the new scopes
[11:55] <dandrader> mzanetti, when there's no application running and I do a right edge drag on the dash, what happens?
[11:56] <Cimi> Saviq, but since I added cardtool to dashrenderer
[11:56] <Cimi> Saviq, it can be added
[11:56] <mzanetti> dandrader: it should do that animation on the dash
[11:56] <dandrader> mzanetti, same as currently?
[11:56] <mzanetti> dandrader: where it shrinks a bit and gets black
[11:56] <mzanetti> yeah
[11:56] <Cimi> Saviq, I tried to reduce the diff for new scopes indeed
[11:56] <dandrader> mzanetti, ok
[11:57] <Saviq> Cimi, I just wonder, why do we want the whole carouselTool as property, and not just the needed props directly?
[11:58] <Cimi> Saviq, because carousel in new scopes needs to read cardtool
[11:59] <Cimi> carouseltool
[11:59] <Saviq> Cimi, yeah, that's fine, but why do we need the QtObject?
[11:59] <Cimi> sorry hold on
[11:59] <Cimi> the property is cardtool
[11:59] <Saviq> Cimi, why can't CardTool just deal with it directly
[11:59] <Saviq> 94	/*!
[11:59] <Saviq> 95	+ \brief Tool component for Carousel.
[11:59] <Saviq> 96	+ */
[11:59] <Saviq> 97	+ property var carouselTool
[12:00] <Cimi> Saviq, doesn't seem to be required from outside indeed
[12:01] <Cimi> Saviq, I don't know if it was some sort of future-proofing I did when I wrote the branch or a leftover of an old test
[12:02] <Cimi> Saviq, I don't think it's necessary to expose carouselTool from outside
[12:02] <Saviq> Cimi, ok, please kill it then
[12:02] <Cimi> Saviq, I think that I used it to calculate from the cardcarousel the dimensions of the tiles
[12:02] <Cimi> Saviq, then you said to use the static values we set in cardtool
[12:03] <Cimi> Saviq, so I removed from cardcarousel but I left in cardtool
[12:03] <Cimi> yep that might be it - removing
[12:04] <Cimi> Saviq, done
[12:04] <Saviq> Cimi, ok, will do a proper review asap
[12:30] <elopio> mzanetti: I'm here.
[12:30] <mzanetti> elopio: good morning. Again, everything resolved by now :)
[12:30] <elopio> mzanetti: I like that :D
[12:31] <mzanetti> I guess so
[12:32] <elopio> mzanetti: I'm watching your presentation, because yesterday the stream was broken for me. I need to turn many autopilot tests on the notes app into qml tests.
[12:32] <mzanetti> elopio: +1 on that one :D
[12:32] <elopio> I'll probably be asking dumb questions
[12:32] <mzanetti> elopio: no problem... as long as we get more reliable tests, feel free to ask me any time
[12:35] <mzanetti> elopio: is the whole presentation up by now?
[12:36] <mzanetti> 'cause the stream broke down somewhere in the middle and cut the video in 2 parts
[12:37] <elopio> mzanetti: I see two videos of ~20 minutes on david's youtube channel.
[12:37] <mzanetti> ok. that should be everything then
[12:44] <dandrader> trying to turn my N10 display on. "powerd-cli display on bright" doesn't seem to be enough...
[12:47] <dandrader> greyback, Saviq: any ideas? ^
[12:47] <greyback> dandrader: just had same issue here. Rebooting worked. Unsure why however
[12:49] <dandrader> greyback, heh, screen lit up just after I issued "reboot" :)
[12:49] <greyback> dandrader: yeah, suspect powerd isn't doing quite the right thing on manta
[13:36] <Saviq> dandrader, it won't power it on, it will keep it on
[13:36] <Saviq> dandrader, you need mir to actually talk to the hardware to turn the display on
[13:37] <Saviq> dandrader, powerd-cli only overrides the policy, but without mir executing it there's nothing that will actually tell the hw to turn it on
[13:38] <dandrader> Saviq, I have unity8 manually running...
[13:38] <dandrader> Saviq, does that count as "mir"?
[13:40] <Saviq> dandrader, yes, should, assuming it listens to powerd's commands to turn the display on...
[13:41] <Saviq> fginther, hey, it looks like https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/5673/console isn't using unity8's helpers for unlocking the screen, could it start doing so?
[13:42] <Saviq> fginther, we're removing the BottomBar... thing
[13:43] <Saviq> mhr3, oh, you're back, just posted on #ferrets:
 pstolowski, we need to do something so that scope-registry is always started when unity8 is
[13:43] <Saviq>  pstolowski, /me thinks "start on unity8 starting" or something similar
[13:43] <mhr3> Saviq, why would that be necessary?
[13:43] <Saviq> mhr3, install unity8, no scopes
[13:44] <pstolowski> Saviq, it currently starts with dbus, what's the issue?
[13:44] <mhr3> Saviq, zmq sockets are kinda connectionless
[13:44] <Saviq> mhr3, pstolowski, then maybe it just needs to start on installation
[13:44] <Saviq> but that's probably difficult
[13:44] <Saviq> mhr3, pstolowski, as right now you need to "start scope-registry" the first time you install it, as otherwise without restarting the session there won't be a "dbus started" event
[13:44] <mhr3> yea well... log out after installing unity8 :)
[13:45] <Saviq> mhr3, tell that to the test runners
[13:45] <pstolowski> hmm
[13:45] <mhr3> Saviq, make the test runners start the registry then :)
[13:45] <Saviq> mhr3, I can make unity8 job start the registry
[13:46] <mhr3> well... why not
[13:46] <Saviq> mhr3, but then that's what events are supposed to be, aren't they...
[13:46] <pstolowski> Saviq, then you should probably start smart-scopes-proxy
[13:46] <pstolowski> Saviq, as registry depends on it
[13:46] <Saviq> pstolowski, right
[13:47]  * Saviq looks for an upstart expert...
[13:51] <Saviq> Cimi, we can't merge the new getRenderer into trunk
[13:52] <Saviq> Cimi, https://code.launchpad.net/~unity-team/unity8/carouselTool/+merge/209655/comments/493279
[14:22] <fginther> Saviq, can you point me to what the unlock should be doing?
[14:27] <Saviq> fginther, so, is it decided that it's ok for unity8 to always run under testability to do the unlocking? if so, there's unity8.autopilot.process_helpers.unlock_unity
[14:27] <mhr3> Saviq, still ok to to merge trunk to new-scopes? people are still using the demo ppa, and the pkg there is superseded
[14:28] <Saviq> mhr3, the recipes are disabled anyway
[14:28] <mhr3> Saviq, not a big deal to trigger them :)
[14:28] <fginther> Saviq, so just run that with phablet-test-runner and the magic happens?
[14:29] <Saviq> fginther, .restart_unity_with_testability first
[14:29] <fginther> Saviq, ack
[14:29] <Saviq> fginther, and yes, those two calls would be it
[14:29] <Saviq> mhr3, we'll merge new-scopes soon enough, people could just force the versions after all
[14:29] <mhr3> oh, nvm there isn't much to merge
[14:29] <fginther> Saviq, is remaining on the old method going to be a blocker to testing?
[14:30] <mhr3> Saviq, i'll just kick the build for now
[14:30] <Saviq> fginther, yes, since it relies on a dbus interface that's going away
[14:30] <fginther> Saviq, ok
[14:31] <fginther> Saviq, I'll get the work on the queue and prioritize it
[14:33] <Saviq> fginther, thanks
[14:34] <mhr3> Saviq, re attributes, i'll expose them to shell as a single role which will hold the classical array of dicts, right?
[14:35] <Saviq> mhr3, yup
[14:35] <Saviq> mhr3, no need for a model
[14:35] <mhr3> Saviq, and in preview header widget?
[14:36] <mhr3> i guess you also want it there as a single attribute?
[14:36] <Saviq> greyback, standup?
[14:36] <greyback> d'oh
[14:36] <Saviq> mhr3, yeah, same exact thing
[14:36] <Saviq> mhr3, as it's meant to be the same widget ;)
[14:36] <mhr3> which means it will be different two things for scope authors... but you don't care about that :)
[14:39] <Saviq> mhr3, not really ;D
[14:39] <om26er> mzanetti, hey
[14:39] <om26er> mzanetti, regarding https://code.launchpad.net/~mzanetti/unity8/disable-hud/+merge/209701 it seems the unlock script depends on an interface that is being removed
[14:39] <mzanetti> om26er: one sec. in the standup right now
[14:39] <Saviq> om26er, read up my conv with fginther
[14:39] <om26er> sure
[14:40] <om26er> Saviq, I just came in ;)
[14:40] <Saviq> om26er, right, yeah, we know, fginther will fix :)
[14:41] <om26er> Saviq, fginther if you want I can work on it
[14:41] <om26er> its a great time to clean that script
[14:41] <Saviq> dednick, standup?
[14:41] <Saviq> dednick, still have a minute or so to join :)
[14:42] <mzanetti> om26er: so, yeah... known, we're working on it. for now I've proposed another branch that just disables the hud tests which are blocking the apps
[14:44] <om26er> mzanetti, yeah, saw that as well.
[14:48] <mhr3> didrocks, question about 0replaceme - when is that going to be actually replaced?
[14:48] <fginther> om26er, if you have some cycles, that would be awesome, I won't be able to get to it for a few hours
[14:49] <mhr3> didrocks, and since we might build the binaries at the same time as when the dep pkgs are built, isn't there going to be a problem?
[14:49] <mhr3> didrocks, or is it replaced already when going to a landing silo?
[14:49] <didrocks> mhr3: when it will be published in distro
[14:49] <om26er> fginther, yeah, I have many ;)
[14:50] <didrocks> mhr3: the dep packages requires the new version?
[14:50] <mhr3> didrocks, they might if we have them in the same silo, right?
[14:50] <didrocks> mhr3: you need to bump the build-dep in that case
[14:51] <didrocks> otherwise, everything will start to build at the same time (as you didn't require latest version)
[14:51] <mhr3> didrocks, sure, but when the dep pkg will be building it will see that it needs version 0replaceme instead of the real version
[14:51] <mhr3> ...i hate this wifi chip so much
[14:52] <didrocks> mhr3: nothing to do with that, this is for binary deps, not build-time
[14:52] <didrocks> mhr3: so if you need latest one at build-time, you need to bump the build-deps
[14:52] <didrocks> then, if you do that
[14:52] <didrocks> and let's say 0replaceme is replaced with "42"
[14:53] <didrocks> B will depend on A (=< 42)
[14:53] <didrocks> if it's using one of the new symbols
[14:54] <mhr3> hmm, i guess i don't really understand when is the version from the symbols used
[14:54] <mhr3> but if you say it's going to work, i'll trust you
[14:54] <didrocks> it's easy
[14:54] <didrocks> so you have A and B
[14:54] <didrocks> B depends on A
[14:55] <didrocks> A provides new symbols: aaaaa 42
[14:55] <didrocks> if B uses "aaaaa"
[14:55] <didrocks> it will be B depends on A (=< 42)
[14:55] <didrocks> but for that, you need to have B built against the new A
[14:55] <didrocks> if you use new symbols
[14:56] <didrocks> so, if you want B wanting on A to be built
[14:56] <didrocks> you need to have B bumping the build-dep version on A
[14:56] <didrocks> and you need to do that manually
[14:58] <mhr3> didrocks, hmm, i thought it's also helping with upgrades, when for example soname of A doesn't change, but there are new symbols in A and B is using them, then it would make sure that B doesn't get upgraded unless A is as well
[14:58] <didrocks> mhr3: yeah, it does, once the packages are built
[14:58] <didrocks> as you will get:
[14:58] <didrocks>  B depends on A (=< 42)
[14:58] <didrocks> as a consequence
[14:59] <didrocks> but nothing build-time wise
[14:59] <mhr3> right, but at the point when B builds, all the symbols in A are 0replaceme, so how can that work?
[15:04] <mhr3> *all the NEW symbols
[15:05] <didrocks> no
[15:05] <didrocks> before B builds, my script is changing those
[15:05] <didrocks> and then uploading to the ppa
[15:06] <didrocks> (with the correct version)
[15:06] <mhr3>  didrocks, or is it replaced already when going to a landing silo?
 mhr3: when it will be published in distro
[15:06] <mhr3> ^^ you're confusing :P
[15:06] <didrocks> well, not sure why you want implementation detalis
[15:06] <mhr3> if it's when being uploaded to ppa then yea, sure everything fine
[15:06] <didrocks> so, it's replaced when I prepare the branch
[15:07] <didrocks> this branch is used to build a source package
[15:07] <didrocks> this source package goes to the silo ppa
[15:07] <didrocks> but this branch is only available to you (and trunk) when the package is published :p
[15:07] <didrocks> I just talked about the last part as I thought it was what matters to you ^
[15:08] <mhr3> i see... this time i was more interested in the details :)
[15:08] <mhr3> didrocks, but ok cool, everything working fine, so awesome :)
[15:08] <didrocks> ;)
[15:37] <Saviq> mzanetti, since you're on fire, https://code.launchpad.net/~unity-team/unity8/themeing-font-and-mascot/+merge/207282 please :)
[15:37] <mzanetti> Saviq: ack
[15:37] <Saviq> mzanetti, I just pushed tests for it
[15:37] <mzanetti> Saviq: am I talking bullshit here or does it make sense? https://bugs.launchpad.net/ubuntu-weather-app/+bug/1288819
[15:37] <Saviq> mzanetti, definitely
[15:38] <Saviq> mzanetti, making sense ;)
[15:38] <mzanetti> I do wonder a bit why it looks ok on the phone
[15:38] <mzanetti> probably because the phone doesn't properly set the font DPI for that display
[15:38] <mzanetti> as we're not using it anyways
[15:38] <Saviq> mzanetti, or just because they selected the fonts right ;)
[15:39] <mzanetti> well, it looks good on desktop with 8 px/gu and also looks good on phone with 18 px/gu, but it breaks on desktop with 18px/gu
[15:40] <Saviq> mzanetti, ah, and a pretty small one https://code.launchpad.net/~unity-team/unity8/newscopes-design-tweaks/+merge/209492
[15:40] <mzanetti> ack
[15:44]  * greyback in VT land
[15:52] <mzanetti> Saviq: make testCard segfaulting, known 'cause of 5.0?
[15:52] <Saviq> mzanetti, no, probably fails
[15:53] <Saviq> mzanetti, might need try* instead of verify
[15:53] <Saviq> mzanetti, let me fix
[15:53] <Saviq> mzanetti, that's for the font/mascot tests?
[15:53] <mzanetti> PASS   : qmltestrunner::Card::test_mascotShape(Art and summary)
[15:53] <mzanetti> Segmentation fault (core dumped)
[15:53] <mzanetti> Saviq: ^
[15:53] <Saviq> mzanetti, yeah, qmltestrunner segfaults on failing tests in there....
[15:53] <mzanetti> ok...
[15:54] <mzanetti> ok, summed it up in here too: https://code.launchpad.net/~unity-team/unity8/themeing-font-and-mascot/+merge/207282/comments/493431
[16:06] <Saviq> mzanetti, http://bazaar.launchpad.net/~unity-team/unity8/themeing-font-and-mascot/revision/742 http://bazaar.launchpad.net/~unity-team/unity8/themeing-font-and-mascot/revision/743
[16:07] <dandrader> mzanetti, greyback: so an app is running and its tile on the dash is clicked. code "ApplicationManager.activateApplication(application.appId)" is called. Anything against having "application.activate()" instead?
[16:09] <Saviq> mzanetti, pushed a small change to the tests, too
[16:10] <greyback> dandrader: not really. AppMan API could do with a review tbh
[16:10] <Saviq> dandrader, sounds like should be fine (and it should be going away anyway), and even when we start actually killing apps (and keeping them in Recent ones), we'll keep the Application object still, I think
[16:10] <Saviq> dandrader, (it going away → running apps in dash going away)
[16:10] <mzanetti> dandrader: greyback: fine with me...
[16:11] <mzanetti> dandrader: ah, if you're changing this...
[16:11] <greyback> yep we keep the Application object
[16:11] <mzanetti> I'd vote for startApplication() to emit requestFocus() and only the shell then to actually grant focus by calling focusApplication(appId) too
[16:11] <mzanetti> to keep it aligned with activate()
[16:12] <mzanetti> greyback: ^ jfi
[16:14] <greyback> mzanetti: agreed. Makes sense on desktop too, where if you launch app2, then focus on existing app1, when app2 appears afterwards, shell can know not to remove focus from app1
[16:14] <Cimi> Saviq, my branch breaks things
[16:14] <Saviq> Cimi, not any more it doesn't
[16:15] <Saviq> Cimi, http://bazaar.launchpad.net/~unity-team/unity8/carouselTool/revision/758
[16:15] <dandrader> the thing is, the current AppMan API doesn't make all that much sense anymore on the "unity8 as mir compositor" work
[16:16] <Cimi> Saviq, hah, had same one locally
[16:16] <dandrader> e.g., the focus management will live entirely in the unity8 qml scene
[16:16] <mzanetti> dandrader: well... not entirely
[16:16] <mzanetti> dandrader: we still will have a model holding all the apps and their info
[16:16] <mzanetti> dandrader: the activate/focus/etc might go away indeed
[16:16] <Saviq> Cimi, we need a branch on top of that to be merged into new-scopes, please
[16:17] <mzanetti> dandrader: but all the rest (applicationAdded() appRemoved() etc will continue to make sense imo)
[16:17] <dandrader> mzanetti, I didn't mean that the AppMan API itself won't make sense, just part of it
[16:18] <dandrader> we will still need it for sure
[16:18] <mzanetti> yeah. and I think most of is actually ok.. everything related to the model
[16:18] <mzanetti> just the focus() unfocus() calls yeah... but right. I get your point... makes my previous request obsolete indeed
[16:31] <Saviq> mzanetti, top-ACK https://code.launchpad.net/~unity-team/unity8/newscopes-design-tweaks/+merge/209492 please?
[16:33] <Saviq> mzanetti, https://code.launchpad.net/~unity-team/unity8/new-scopes-clean-to-trunk/+merge/209459 would be the next one I'd like you to look at (see description for things that are not ready for it still)
[16:33] <mzanetti> Saviq: done... as of now I'll do 5 push ups whenever I forget to top approve
[16:33] <Saviq> mzanetti, ;D
[16:33] <Saviq> mzanetti, in that case: https://code.launchpad.net/~unity-team/unity8/themeing-font-and-mascot/+merge/207282 ;D
[16:33] <mzanetti> Saviq: commit message missing
[16:33]  * mzanetti is doing push ups
[16:34] <Saviq> mzanetti, it's WiP still
[16:36] <mzanetti> oh... its the full thing
[16:37] <mzanetti> meh... /me starts rebasing its right-edge stuff :P
[16:38] <mzanetti> won't get through this today
[16:38] <mzanetti> but I'll start tomorrow
[16:38] <Saviq> mzanetti, yeah, for sure
[16:38] <Saviq> mzanetti, well now ;) you can always make the review take long enough so that right edge gets in first ;D
[16:39] <Saviq> mzanetti, and make sure right edge review is ready soon ;)
[16:39] <Saviq> I'm sure there's someone on the team in need of a case of beer ;D
[16:39] <mzanetti> Saviq: haha
[16:39] <mzanetti> Saviq: did you revert the conflicting stuff?
[16:40] <mzanetti> Shell.qml looks quite clean
[16:40] <mzanetti> so probably not even many conflicts after all
[16:40] <Saviq> mzanetti, yeah, see the last few commits
[16:40] <mzanetti> thanks for that :)
[16:40] <Saviq> mzanetti, I cleaned it up to just be new-scopes-related
[16:42] <Saviq> Cimi, please make sure to recreate carousel-dynamic-fallback on top of carouselTool, MP'd into lp:~unity-team/unity8/new-scopes-clean-to-trunk
[16:42] <Cimi> Saviq, sure
[16:42] <Saviq> Cimi, with carouselTool as prereq
[17:02] <kgunn> elopio: hey there
[17:02] <kgunn> i was looking at http://ci.ubuntu.com/smokeng/trusty/touch/mako/223:20140306:20140304/7006/
[17:02] <elopio> kgunn: hello.
[17:02] <kgunn> and trying to square the tests listed there with the wiki
[17:02] <kgunn> https://wiki.ubuntu.com/Touch/Testing#Testing_your_Ubuntu_Touch_Code_before_submission
[17:02] <kgunn> ....specifically...is keyboard not run as part of smoke testing ?
[17:02] <kgunn> or is it hiding under another test somehow ?
[17:03] <elopio> kgunn: I don't know much about keyboard. veebers was the one working on it.
[17:03] <elopio> I know that keyboard has its own autopilot tests, and if they are not listed here is because they are not being run.
[17:03] <elopio> but they should
[17:04] <elopio> also I know that none of our autopilot tests are using the osk yet.
[17:04] <kgunn> elopio: ok...this is the one listed in the wiki "phablet-test-run -p ubuntu-keyboard-autopilot ubuntu_keyboard"
[17:05] <elopio> kgunn: yes, that's the suite.
[17:06] <elopio> kgunn: and there's one discussion we need to have in order to let all the autopilot tests on the phone to use the osk.
[17:06] <elopio> it's about starting malit with testability.
[17:06] <mhr3> mhall119, ping
[17:07] <mhall119> mhr3: in an appdevweek hangout atm
[17:07] <elopio> kgunn: but if on top of new scopes, qt5.2 and android 4.4 we also switch to use the osk, we will be lynched.
[17:07] <mhr3> mhall119, k, sending a mail instead
[17:23] <mzanetti> elopio: ping :)
[17:29] <mhr3> Cimi, the rating input and output widgets are merged in unity8 trunk already?
[17:29] <Cimi> think so mhr3
[17:29] <mhr3> Cimi, how is the review text and star rating passed back to the scope?
[17:29] <mhr3> (need to document that)
[18:07] <Cimi> mhr3, ah, actually I am not sure I finished that
[18:08] <Cimi> Saviq, https://code.launchpad.net/~unity-team/unity8/carouselTool-new-dash/+merge/209746
[18:08] <Cimi> mhr3, was merged I think
[18:09] <Cimi> mhr3, https://code.launchpad.net/~cimi/unity8/previews.PreviewRatingDisplay/+merge/207625
[18:17] <mhr3> Cimi, ok, found it, think we'll need to adjust it a bit
[18:26] <elopio> mzanetti: I branched ubuntu-sdk-tutorial and the currency converter tests there are not using UbuntuTestCase
[18:27] <elopio> oh, I've found your branch.
[18:27] <mzanetti> elopio: https://code.launchpad.net/~mzanetti/ubuntu-sdk-tutorials/use-ubuntutestcase/+merge/209455
[18:27] <mzanetti> ah
[18:37] <mhall119> Saviq: any specific day/time next week that is bad for you for the Unity API docs website discussion?
[18:39] <mhall119> Saviq: http://summit.ubuntu.com/uds-1403/meeting/22199/client-1403-api-website-for-unity/
[18:44] <Saviq> mhall119, any place that's free in my calendar is fine
[18:45] <Saviq> mhall119, bonus points if it's before 7pm UTC :)
[18:51] <elopio> mzanetti: what's the package that installs UbuntuTestCase?
[19:10] <mzanetti> elopio: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1288937
[19:10] <elopio> mzanetti: I was looking at the right place then :)
[19:10] <mzanetti> elopio: not sure when this happened (in unity we use our own UnityTestCase.qml)
[19:11] <mzanetti> elopio: for now you can copy it yourself from the repo to that place
[19:11] <elopio> mzanetti: why are you duplicating it? Isn't the toolkit a dependency of unity?
[19:11] <mzanetti> elopio: unity hat this before the toolkit, and unity's has more
[19:12] <mzanetti> elopio: but as soon as this is fixed in the sdk I'll drop the findChild() stuff from UnityTestCase and inherit that from UbuntuTestCase
[19:12] <elopio> mzanetti: yes, that would be nice. We also need a suite that hits everything from the API, so this doesn't happen again.
[19:13] <elopio> tst_UbuntuTestCase, that's a dangerous hole to go into :)
[19:14] <mzanetti> elopio: well, we do have a tst_UnityTestCase.qml :)
[19:14] <mzanetti> in unity-api we even have mocks to test the tests :D
[19:14] <mzanetti> seems we've fallen into the hole :D
[19:15] <elopio> mzanetti: vila will like you.
[19:20] <vila> \o/
[19:21] <elopio> mzanetti: now I have a ListView of NoteItems. How can I populate that ListView for the test to have something to click?
[19:21] <vila> mzanetti: it's a hole, but also the entry into the real world ;)
[19:21] <elopio> wait, I'm sorry, isn't it way past your EOD?
[19:25] <vila> elopio: I just EOD, beer time ;)
[19:26] <elopio> vila: get one from me. I'll pay for it on may.
[19:26] <elopio> but I was asking mzanetti :) I don't know if I should stop bothering him now.
[19:26] <mzanetti> elopio: well, you set a model to that listview :)
[19:27] <mzanetti> not really sure what you're asking for
[19:27] <elopio> mzanetti: right. It's hard to make a QML test when you don't know QML :D
[19:27] <elopio> I'll start reading about models and give it a try.
[19:27] <mzanetti> elopio: ok... I see
[19:28] <mzanetti> elopio: so.. do you want to use the real notes or a fake one for the test?
[19:28] <elopio> ahh, it's easy. All the vars that seem to come out from nowhere on the delegate should be defined on the model.
[19:29] <mzanetti> elopio: yeah, thats it
[19:29] <elopio> mzanetti: I'll fake them. I just need to expand and collapse them.
[19:29] <mzanetti> elopio: if you want to define a mocked one in qml, just do ListModel { ListElement {name: "aaa"}, ListElement { name: "bbb"}}
[19:30] <mzanetti> then you set that model to the listview and inside the delegate there is a variable (aka. attached property) called "name" containing the values for each delegate
[19:33] <mzanetti> elopio: here's a nice example: http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/tests/qmltests/Dash/Music/tst_MusicPreview.qml
[19:34] <elopio> mzanetti: http://paste.ubuntu.com/7045932/
[19:35] <mzanetti> elopio: yeah, I guess you need to set it still
[19:35] <mzanetti> not sure how NoteList works
[19:35] <elopio> mzanetti: but it's still showing a white window.
[19:35] <mzanetti> is this the notes app, right?
[19:35] <elopio> mzanetti: yes.
[19:36] <vila> elopio: ack, not finished the first one but will drink the next for you ;-p
[19:36] <mzanetti> elopio: yeah, it's a listView
[19:37] <mzanetti> one sec, I'll change the paste
[19:38] <mzanetti> elopio: something like this: http://paste.ubuntu.com/7045954/
[19:39] <mzanetti> note: you could also leave the Model definition inside the NotesList, but I think its more readable this way
[19:39] <elopio> I can see it now
[19:40] <elopio> it's easy when you know what you are doing :D I should go one step back and learn more QML.
[19:40] <elopio> thanks mzanetti!
[19:40] <mzanetti> np
[19:41] <mzanetti> elopio: jfi: this would work too http://paste.ubuntu.com/7045961/ (and can be handy in some cases)
[19:42] <elopio> mzanetti: got it. Here I like your first paste a little better.
[21:46] <mhall119> Saviq: http://summit.ubuntu.com/uds-1403/meeting/22199/client-1403-api-website-for-unity/ 1500 UTC on Wednesday
[22:27] <Saviq> mhall119, awesome, thanks


[00:32] <burner> ok, so my wallpaper shows for about 2 seconds while my panel is loading, then disappears and I'm left with whatever background color I set in the appearance preference... I'm stumped
[00:37] <mahfiaz> burner, when you set wall paper again then nothing shows up?
[00:39] <burner> nothing except changing the color to whatever color was set for the new wallpaper
[00:40] <mahfiaz> take a look to ~/.xsession-errors, maybe there is useful information about crashes
[00:57] <burner> (gnome-panel:6660): Gdk-WARNING **: /build/buildd/gtk+2.0-2.14.5/gdk/x11/gdkdrawable-x11.c:878 drawable is not a pixmap or window
[00:58] <burner> could it be that?  or possibly:
[00:58] <burner> ** (nautilus:6663): WARNING **: Unable to add monitor: Not supported
[01:02] <mahfiaz> probably the second one
[01:03] <mahfiaz> try killing all nautiluses and running one from terminal
[01:05] <mahfiaz> no, this won't give you any information
[01:13] <burner> killing nautilus and bringing it back doesn't even blip my wallpaper for the 2 seconds of it I see during logon
[01:15] <burner> ah ha!!!
[01:16]  * burner checked sessions and noticed remote desktop was enabled... the box was unchecked to remove wallpaper when someone connects remotely...  i checked it.. logged in remotely.. and when I logged off, the wallpaper came back!  yatta!
[01:17] <VLAD-DA-IMPAILER> sup pimps
[01:18] <VLAD-DA-IMPAILER> yo wat sup?
[01:20]  * burner shrugs
[01:23] <VLAD-DA-IMPAILER> yo why my thing going red when i try to put this in my computer?
[01:29] <VLAD-DA-IMPAILER> yo anyone in here
[01:29] <mahfiaz> VLAD-DA-IMPAILER, you are a little unclear
[01:30] <mahfiaz> we are not sure what is "your thing" which is going to red
[01:30] <VLAD-DA-IMPAILER> i try to install it, and i get red screen
[01:30] <mahfiaz> is this just a blank screen or has it some text on it?
[01:31] <VLAD-DA-IMPAILER> it's some kind of error
[01:31] <mahfiaz> then all I can say, is you are getting some error, which you may know already
[01:32] <burner> lol
[01:32] <VLAD-DA-IMPAILER> when it gets to installing packages it throws an error , setup failed or sumtn
[01:32] <burner> possibly a bad burn?  run teh 'check cd for errors" thing?
[01:33] <mahfiaz> but next time please read the error message carefully and write down, if needed
[01:33] <VLAD-DA-IMPAILER> no, but not a bad burn, ive had this on many different versions of kubuntu
[01:34] <burner> so you're trying to install Kubuntu but can't?
[01:34] <VLAD-DA-IMPAILER> right
[01:34] <burner> Kubuntu Jaunty alpha something?
[01:34] <VLAD-DA-IMPAILER> yup
[01:35] <VLAD-DA-IMPAILER> my friend said it was the best
[01:35] <burner> you're just testing jaunty and it worked in intrepid for you?
[01:35] <burner> if you're new to linux, i'd say wait on jaunty...  it's alpha software.  8.10 "intrepid" was released in October and works pretty well
[01:36] <mahfiaz> we could also say this was almost november
[01:36] <VLAD-DA-IMPAILER> well, actually i have those failures on all nvchipset mobos, but right now i have the new amd chipset
[01:36] <mahfiaz> with intrepid too?
[01:36] <VLAD-DA-IMPAILER> yeah
[01:37] <burner> try "ubuntu" ?
[01:37] <burner> try from a USB installer?
[01:37] <mahfiaz> and hardy?
[01:38] <VLAD-DA-IMPAILER> i've never done a setup from usb, any guides?
[01:38] <VLAD-DA-IMPAILER> havent try regular ubuntu, not a fan
[01:38] <burner> yeah ok... kubuntu should be fine
[01:39] <mahfiaz> ubuntu derivates make almost no difference, this cannot be the problem
[01:40] <mahfiaz> As burner suggested, try intrepid again and ask on #ubuntu
[01:40] <mahfiaz> and DON'T forget to write the error message down
[01:40] <VLAD-DA-IMPAILER> oh, and im usually using the alternate versions
[01:40] <burner> why not -desktop?
[01:40] <VLAD-DA-IMPAILER> i like to setup software raid
[01:42]  * charlie-tca likes to try the live cd to make sure the system will work
[01:43] <mahfiaz> most likely your error is about your software raid :)
[01:43] <burner> lol... indeed
[01:43] <VLAD-DA-IMPAILER> do u have a link to daily live kubuntu x64?
[01:43] <VLAD-DA-IMPAILER> no, im experienced with that
[01:44] <mahfiaz> what you use the software raid for? RAID-0?
[01:44] <VLAD-DA-IMPAILER> raid0 most of the time
[01:45] <mahfiaz> LVM aka logical volume management does this job more neatly
[01:46] <mahfiaz> you could even attach newly connected drive to lvm and expand filesystem to it
[01:46] <VLAD-DA-IMPAILER> i could never understand that lvm thing,
[01:46] <mahfiaz> imagine you have hotswap mobo one day :)
[01:47] <mahfiaz> and instead of saying your customers that you have to go offline to add drives, you simply attach new one, live
[01:47] <mahfiaz> see gentoo handbooks for lvm management
[01:49] <VLAD-DA-IMPAILER> why do u bring gentoo up?
[01:49] <mahfiaz> I said see gentoo *handbooks*
[01:50] <mahfiaz> these are superious, in my opinion
[01:50] <mahfiaz> *superiour
[01:50] <VLAD-DA-IMPAILER> i know , but where did gentoo come from?
[01:50] <burner> from the fact they have good lvm docs
[01:51] <VLAD-DA-IMPAILER> well, i don't need lvm, i do it by myself
[01:51] <mahfiaz> yeah, thats the problem
[01:52] <VLAD-DA-IMPAILER> no, im quite capable of setting up a few drives
[01:53] <mahfiaz> by the way, if one wants to get good linux-administrator experience, then gentoo is the one to run for some months
[01:53] <VLAD-DA-IMPAILER> damn it im gonna go do a screenshot
[01:53] <mahfiaz> and then use debian or ubuntu for real work
[01:53] <mahfiaz> that's good idea
[01:55] <VLAD-DA-IMPAILER> ok,ok, now help me figure out what the problem could be
[02:01] <mahfiaz> did you get the screenshot?
[02:18] <VLAD-DA-IMPAILER> well, no, cause id have to get off, and i didnt feel like leaving yet
[02:36] <VLAD-DA-IMPAILER> so, how do i install it from a usb drive?
[02:43] <x1250> calc, are you around? I think I've found a bug on openoffice. Try opening a PPT file, select another master page, save as ppt. It will result in a write error. Then choose save as odp, it will save as usual. :(
[02:44] <x1250> openoffice from intrepid's PPA, which I'm using on jaunty......
[03:07] <mahfiaz> VLAD-DA-IMPAILER: https://help.ubuntu.com/community/Installation/FromUSBStick
[04:40] <DanaG> I am so, so very glad I bought this laptop with AMT enabled.  I resumed from suspend, and got a blank screen.... and somehow, the ssh server was not reachable. Yet, I was able to log into the serial console -- even with the OS networking down!
[05:03] <DanaG> Heh, somehow NetworkManager is not getting the memo that says I've rfkilled the wifi.
[06:06] <DanaG> weird dsdt... seems to have SQL queries!  www.csc.calpoly.edu/~dgoyette/elitebook-8530w-dsdt.dsl
[06:09] <alka_trash3> I'm sort of excited for Jaunty
[06:09] <alka_trash3> With am64 bit versions of Flash and Java with improvements in speed should be nice
[13:09] <ottoshmidt> when will alpha version be available?
[13:20] <ikonia> ottoshmidt it already is
[13:20] <ikonia> ottoshmidt: check the topic
[13:21] <ottoshmidt> where?
[13:24] <ikonia> tehre you go
[13:24] <ikonia> there you go
[13:26] <ottoshmidt> ;)
[13:27] <ottoshmidt> what does not supported mean?
[13:27] <ottoshmidt> no one will assist if any problems?
[13:27] <ottoshmidt> (Jaunty is NOT RELEASED and NOT SUPPORTED)
[13:28] <ikonia> pretty much
[13:28] <ikonia> people will hlep out, but it probably won't be a big deal if it's broke as it's still in development
[13:28] <ikonia> you may have to re-install your system a lot too
[13:29] <ottoshmidt> :)
[13:30] <ottoshmidt> and if I report bugs and help to make it better?
[13:30] <ikonia>  depends if they are valid bugs, or just a case of you can't use them
[13:30] <ikonia> if they are valid, great
[13:31] <ikonia> you need to be able to provide debugging information though
[13:31] <ikonia> version information, compatability details, hardware, accurate discription of the problem, what you've done to try to resolve it, not just "it doesn't wokr"
[13:33] <ottoshmidt> interesting
[13:33] <ottoshmidt> but how do I know if it's not a valid bug in advance?
[13:35] <BUGabundo_work> you will learn with time ottoshmidt
[13:35] <BUGabundo_work> and ikonia I don't remember ever to reinstall a devel version
[13:35] <BUGabundo_work> sure when LibC6 got broken it was a nightmare
[13:36] <BUGabundo_work> and I had to use the LiveCD to fix it, but that was the worst that ever happened to me
[13:36] <BUGabundo_work> luckly....
[13:36] <BUGabundo_work> I sure hope I never loose un-backuped data
[13:39] <ikonia> BUGabundo_work it depends on the breakage
[13:39] <gnomefreak> broke libc6 is the worst that can happen other than kernel panic
[13:39] <ikonia> BUGabundo_work: just becaquse YOU have never re-installed doesn't mean others won't, it is quite a common thing to re-install the dev version after working through a problem to break point
[13:40] <gnomefreak> everything depends on libc6 without it your system wont work if broken system wont behave right
[13:45] <BUGabundo_work> that's why I said it was the worst it ever happened! lol
[13:45] <BUGabundo_work> I need to discover a way to re-apply all my settings
[13:46] <BUGabundo_work> for quick re-install
[13:46] <BUGabundo_work> I don't do them as often 'cause it sucks to redo everything
[13:46] <BUGabundo_work> I run a lot of services for personal usage and testing, and copying /etc aint always strait forward
[13:52] <gnomefreak> is anyones gpg key broke? not really the key but the gpg is broken
[13:52] <BUGabundo_work> humm
[13:52] <BUGabundo_work> I'll have to test it
[13:53] <BUGabundo_work> anything in specific gnomefreak?
[13:53] <gnomefreak> BUGabundo_work: tbird trying to send email that you sign
[13:53] <gnomefreak> i dont have tbid 2 atm so i cant test it
[13:55] <ikonia> gnomefreak: on jaunty, I couldn't get it working about 2 weeks ago,. not tried after that
[13:55] <BUGabundo_work> I use kmail, not tbird
[13:55] <BUGabundo_work> but all my kmail emails are going signed
[13:55] <gnomefreak> found this issue
[13:56] <gnomefreak> its the password dialog that is failing to accept password im betting its gnugp-agent
[13:57] <gnomefreak> cant sign a file either
[13:58] <ottoshmidt> I was disconnected so if anyone wrote to me I missed :(
[13:58] <ikonia> no-one did
[13:59] <gnomefreak> damn its not gpg-agent causing this
[13:59] <BUGabundo_work> naaa we're a bunch of quite people
[13:59]  * BUGabundo_work takes a look at seahorse
[14:02] <BUGabundo_work> ahh what a lovelly error message I got from seahorse while trying to add a ssh key to a remote server
[14:06] <gnomefreak> BUGabundo_work: do you have pinentry-gtk2 installed or pinentry-qt?
[14:08]  * BUGabundo_work checks
[14:09] <BUGabundo_work> I have both
[14:10] <BUGabundo_work> yeah seahorse is segfaulting but gdb aint catching it
[14:10] <ikonia> BUGabundo_work can you strace it ?
[14:10] <ikonia> see the last hook it fails on
[14:11] <BUGabundo_work> http://paste.ubuntu.com/87081
[14:11] <BUGabundo_work> can you take a look?
[14:11] <ikonia> can do
[14:12] <BUGabundo_work> and if anyone know what's causing those atk-bridge-WARNING let me know!
[14:12] <BUGabundo_work> ikonia: am I meant to log strace too?
[14:13] <ikonia> BUGabundo_work wouldn't hurt, that seg faults isn't giving much
[14:13] <BUGabundo_work> I know
[14:13] <BUGabundo_work> strace -f seahorse > strace.log would do it?
[14:14] <BUGabundo_work> I'm getting it echo to screen and not the log
[14:14]  * BUGabundo_work opens a LP but to keep track
[14:14] <BUGabundo_work> ah
[14:14] <BUGabundo_work> -o FILE
[14:17] <BUGabundo_work> "couldn't read from seahorse-ssh-askpass: broken pipe" could be the reason for the bug
[14:18] <BUGabundo_work> gnomefreak: ^^^^^^^^^^^^ is it related to yours?
[14:18] <ikonia> BUGabundo_work are you getting a prompt on screen
[14:18] <gnomefreak> BUGabundo_work: most likely it is
[14:19] <BUGabundo_work> I 'm ikonia
[14:19] <BUGabundo_work> but all pop ups are UNDER pop ups
[14:19] <BUGabundo_work> I have to move windows to reach them
[14:19] <gnomefreak> BUGabundo_work: cant remember but im pretty sure seahorse only uses *-gtk2 but you can check your default one by changing/checking update-alternatives pinentry-x11
[14:19] <gnomefreak> BUGabundo_work: thats same bug
[14:19] <BUGabundo_work> plus I have keep hitting the Pass field with my mouse to keep it selected
[14:20] <gnomefreak> check also pinentry
[14:21] <Hew> BUGabundo_work: Bug 272390 was the one I was thinking off, maybe this is a new one.
[14:21] <BUGabundo_work> I'm seeing way to many on LP
[14:22] <BUGabundo_work> bug 126094
[14:22] <gnomefreak> seahorse isnt crashing for BUGabundo_work
[14:22] <BUGabundo_work> well it did to me twice
[14:22] <BUGabundo_work> until I manage to enter the password on the under popup
[14:23] <gnomefreak> its just not accepting passphrass. to chek if crashed look in /var/crash but i doiubt you will see it
[14:23] <BUGabundo_work> ok
[14:23] <BUGabundo_work> not crashing, segfaulting
[14:23] <gnomefreak> segfault is a crash last i checked
[14:23] <BUGabundo_work> no crashs there, just gwibber
[14:24] <gnomefreak> segfault is interrupted running
[14:24] <Hew> a segfault would trigger apport, yes
[14:25] <Hew> although apport seems to be absent in Jaunty atm, perhaps it's just me..
[14:26] <BUGabundo_work> naa, I don't see it either Hew
[14:28] <gnomefreak> Hew: mine works
[14:28] <gnomefreak> Hew: try enabling it
[14:28] <gnomefreak> IIRC its in /etc/default/apport change the 0 to a 1
[14:28] <Hew> gnomefreak: It is enabled
[14:29] <gnomefreak> Hew: than its not absent
[14:29] <gnomefreak> ;)
[14:29] <Hew> .crash files are generated, but apport isn't triggered automatically. Not a big deal, I can navigate to /var/crash and run it manually when I need to :-)
[14:29] <BUGabundo_work> uploading strace now
[14:30] <gnomefreak> i crashed an app this morning and apport came up asking if i wanted to report it
[14:30] <Hew> gnomefreak: Yes I know it's not absent, but it's just not triggering when it should :P
[14:30] <Hew> ok good, well as long as it's not broken for everyone that's ok
[14:30] <gnomefreak> it was gnome-app-install as i recall that i crashed
[14:31] <gnomefreak> i guess i dont have to do any bug work since email is broken :)
[14:31] <Hew> ah excellent, I just realised the gnome-panel applets aren't crashing anymore (such as five-a-day-applet)
[14:32]  * gnomefreak has broken X and broken pinentry
[14:32] <Hew> gnomefreak: Congratulations :P
[14:32]  * charlie-tca wondered who did that, gnomefreak
[14:32] <BUGabundo_work> ikonia: gnomefreak Hew https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/308985 (Mark as Private)
[14:32] <BUGabundo_work> strace on its way still
[14:32] <mphill> what is apport?
[14:33] <gnomefreak> !apport
[14:33] <gnomefreak> why would you
[14:33] <ikonia> BUGabundo_work I can't read it then if it's private
[14:33] <BUGabundo_work> can't you ?
[14:33] <BUGabundo_work> I thought most of you were in QA
[14:33] <ikonia> BUGabundo_work: hence the name private
[14:33] <gnomefreak> mphill: its a crash collecter that allows you to report crash reports and it adds the strace and such
[14:33] <ikonia> ha ha no
[14:33] <BUGabundo_work> let me just upload the strace
[14:33] <charlie-tca> BUGabundo_work: Is it in Jaunty?
[14:33] <BUGabundo_work> and have hew take a look at it
[14:34] <mphill> gnomefreak: thanks
[14:34] <BUGabundo_work> so see if I manage to omit all stuff
[14:34] <gnomefreak> BUGabundo_work: unless subscribed to the package bug is filed under or reported
[14:34] <BUGabundo_work> charlie-tca: yes I'm on jaunty
[14:34] <Hew> BUGabundo_work: I can read it (Bug Control)
[14:35] <BUGabundo_work> humm
[14:35] <BUGabundo_work> can the strace be in targz?
[14:35] <BUGabundo_work> I just noticed its 80MiBs of data
[14:35] <Hew> BUGabundo_work: You can set it to public yourself when you are comfortable.
[14:35] <BUGabundo_work> its using all my BW and it aint gonna go so soon
[14:35] <Hew> .tar.gz is fine
[14:35] <gnomefreak> im in it
[14:36] <gnomefreak> ** Message: could not grab keyboard
[14:36] <BUGabundo_work> https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/308985 (due to many family requests, is now public)
[14:36] <gnomefreak> ** Message: could not grab keyboard
[14:36] <gnomefreak> that tells me its same bug
[14:36] <gnomefreak> BUGabundo_work: you have no private data in bug so setting it public should be fine
[14:37] <BUGabundo_work> gnomefreak: uploading now strace tar.gz
[14:37] <BUGabundo_work> done
[14:37] <BUGabundo_work> you guys should see it now
[14:37] <BUGabundo_work> remove any private data you still see on it!
[14:37] <gnomefreak> refreshing after smoke
[14:37] <BUGabundo_work> I already munge user and pass
[14:37] <gnomefreak> shoudlnt have any in strace
[14:38]  * BUGabundo_work 80MiBs to 500k... uau tar.gz rules
[14:38] <BUGabundo_work> I could see them in there...
[14:41] <Hew> BUGabundo_work: I'm not sure what private data could be there, unless your private key snuck in there somehow? :P
[14:41] <BUGabundo_work> uhhhh
[14:41] <BUGabundo_work> that would be bad
[14:41] <BUGabundo_work> forgot to look for it
[14:42] <Hew> BUGabundo_work: The Private feature is usually just for automatically submitted apport crashes. If you know what you're doing, you can just have a quick look yourself, no need to mark as private
[14:42] <BUGabundo_work> grep can't find it
[14:42] <Hew> BUGabundo_work: It was a joke, I really doubt that is the case :P
[14:42] <BUGabundo_work> I think I'm safe
[14:42] <BUGabundo_work> don't scare me like that
[14:42] <Hew> hehe sorry ;-)
[14:43] <BUGabundo_work> brb
[14:51] <gnomefreak> BUGabundo_work: what is kde version of seahorse called?
[15:06] <Hew> gnomefreak: kgpg? (just from a quick browse of the repositories, I don't use KDE so I'm not sure)
[15:07]  * gnomefreak not sure either. he said he used kmail so i was hoping he would know
[15:08] <gnomefreak> Hew: what package is 5-a-day applet in? i cant find it anywhere
[15:09] <Hew> gnomefreak: It's five-a-day-applet from the PPA
[15:09] <gnomefreak> i thought it was in repos already
[15:10] <Hew> gnomefreak: Unfortunately no, there's a bug open for it though.
[15:10] <Hew> gnomefreak: https://wiki.ubuntu.com/5-A-Day/Reporting
[15:10] <gnomefreak> ah i thought it hit in intrepid
[15:11] <gnomefreak> thanks Hew
[15:11] <Hew> Bug 194372
[15:13] <Hew> yea I hope it hits Jaunty now, but new packages have a habit of taking forever
[15:13] <BUGabundo_work> back
[15:14] <BUGabundo_work> I'm on gnome gnomefreak. I just use a few kde apps
[15:14] <BUGabundo_work> like kmail, konqueror , etc
[15:14] <Hew> BUGabundo_work: welcome back
[15:14] <gnomefreak> bullgard4: ah ok
[15:18] <bullgard4> gnomefreak: wrong nick.
[15:18] <BUGabundo_work> lol
[15:18] <BUGabundo_work> same 'bu' nick
[15:18] <gnomefreak> oh sorry bullgard4
[15:19] <gnomefreak> well since i cant do anything with email and its too late to start work on anything else on my to do list im gone for a while ;)
[16:24] <mgs> Has anyone experienced their alt keys not working? Running Kubuntu, but can't really find a bug for it yet.
[16:27] <BUGabundo_work> mgs: not here in ubuntu jaunty
[16:31] <mgs> Guess I'll fiddle around a little more, and report a bug in the end if I cant find a solution, thanks.
[16:42] <bhuvi> will jaunty alpha 2 live cd be released
[16:42] <BUGabundo_work> yes bhuvi
[16:42] <BUGabundo_work> !daily
[16:42] <BUGabundo_work> but you can also use a daily
[16:43] <bhuvi> but can it be upgraded
[16:44] <BUGabundo_work> sure
[16:45] <BUGabundo_work> any version can be upgrade to what ever comes next
[16:47] <bhuvi> i remember havin installed daily image for intrepid it had no authentication i mean uname output was unknown
[16:48] <BUGabundo_work> humm?
[16:48] <BUGabundo_work> 1st time I read about thatr
[16:48] <BUGabundo_work> maybe a wrong image? or a bad day to test it?
[17:17] <Xsss4hell> hi
[17:18] <Xsss4hell> a week ago or soo I was happy having Jaunty
[17:18] <Xsss4hell> I would be still
[17:18] <Xsss4hell> would
[17:18] <Xsss4hell> I updated jaunty as usual
[17:18] <Xsss4hell> Now it doesn't showup ANY dialog anymore
[17:18] <Xsss4hell> The os is NOT usable..
[17:19] <Xsss4hell> but it was HIGHLY productive before the update
[17:19] <Xsss4hell> Do you know that bug?
[17:20] <Xsss4hell> Which logs do you need???
[17:20] <Xsss4hell> I very VERY VERY neeed this desktop working asap
[17:20] <Xsss4hell> I'm in textmode now
[17:21] <Pici> Xsss4hell: you shouldn't be using Jaunty if you need it to work.
[17:31] <Xsss4hell> Pici you shouldn't use a computer if you want to work..
[17:32] <Xsss4hell> I know it's alpha, but it was very stable. until canonical released the latest update.
[17:32] <Xsss4hell> something broke
[17:34] <Pici> Xsss4hell: Ubuntu Alpha releases are not designed to be stable.  Its a bit of an anomoly that it was stable for you for this long.
[17:34] <Xsss4hell> I don't think so!
[17:35] <Xsss4hell> I have it since alpha1 got released, without even a minor bug!
[17:35] <Pici> The developers were waiting for UDS to happen and be finished before they had a good direction to go regarding changes.
[17:35] <Xsss4hell> And I'm a developer, so I use many functions that go beyond normal user's desktop experience
[17:37] <Pici> Er. Okay?
[17:38] <TheInfinity> you need alpha software, you are a developer and you use it at your productive system? wow.
[17:38] <TheInfinity> you *use alpha software
[17:40] <TheInfinity> one of these points is wrong. i would say the 2nd point ;)
[17:40] <Pici> The channel topic explains it pretty well.
[17:42] <TheInfinity> Pici: no working xorg is no breakage in a bad way - this can get much worse ;)
[17:42] <Pici> TheInfinity: Oh indeed.
[17:42]  * genii sips a coffee
[17:44] <Xsss4hell> I'll reinstall ubuntu jaunty and do not apply updates
[17:44] <Xsss4hell> but trying to find the bug..
[17:45] <TheInfinity> Xsss4hell: if you need ubuntu you should use no jaunty.
[17:45] <Xsss4hell> nothing special appears in the logs
[17:45] <Xsss4hell> then interpid.. but intrepid had more bugs than jaunty, at least in the begining
[17:46] <Pici> Xsss4hell: Jaunty with no updates is nearly the same thing as Intrepid.
[17:46] <Xsss4hell> I wish you had an update-policy like gentoo. -> fast forward & stable
[17:46] <genii> All the intermediate releases of ubuntu have had some issues. This is normal.
[17:47] <dimebar> Xsss4hell: maybe if you stopped crying and installed something stable you'd be more productive
[17:47] <genii> Since the purpose of the intermediate releases are to test and incorporate chanegs which will be in the next long-term release
[17:47] <Xsss4hell> I've set up, ssh, apache, ldap, ftp, any many more on that machine, damn it.. that damn error must be fixable
[17:48] <TheInfinity> you installed an SERVER at an alpha OS? wow. you are really crazy ...
[17:49] <Xsss4hell> TheInfinity: I'ts for personal use
[17:49] <Xsss4hell> not publicly available
[17:50] <Xsss4hell> I've programmed applications  that interact with ldap auth etc.
[17:52] <Pici> If you're aiming for stability I highly suggest that you use a non-alpha version of Ubuntu.  If you don't like Intrepid then use Hardy or earlier.
[17:55] <Xsss4hell> the dekstop show up, everything seems normal, dialogs coming up, but the content of it is not displaying, so nothing is really usable, altough there
[17:56] <Xsss4hell> Isn't any bug similar to that in launchpad? If you know it there should be a fix, instead of telling me to install another OS
[17:57] <Pici> Xsss4hell: I don't know. You probably will have to look for yourself.
[18:18] <BUGabundo> is it just me, or is the new FF update messing things?
[18:18] <BUGabundo> most pages won't even load..
[18:18] <BUGabundo> I know I'm not on the fastest net connection, but it aint that bad!
[18:25] <charlie-tca> seems okay here. Anything specific?
[18:27] <BUGabundo> yeah, pages not loading
[18:27] <BUGabundo> and gwibber also blank
[18:28] <BUGabundo> I suspesct bad webkit upgrade
[18:29] <charlie-tca> Maybe. I got 5 tabs open, and pages are loading fast.
[18:31] <BUGabundo> really strange then
[18:32] <BUGabundo> both FF3.0.4 (just upgrade to .5) and FF3.1 won't open almost any page
[18:32] <BUGabundo> gmail did open, but took a few retries
[18:32] <BUGabundo> pidgin or UM are working great
[18:35] <TheInfinity> hmm. archive.ubuntu.com for jaunty seems to be down atm?
[18:37] <BUGabundo> it was up a few minutes ago, when I did my updates
[18:44] <burner_> anyone know if nvidia drivers work in the latest dist-upgrade?  It wants to remove my nvidia-glx-177 but I don't see an alternative driver get installed
[18:45] <BUGabundo> guys get ready to be on Mark's screen shots
[18:45] <burner_> http://ubuntuweblogs.org rules! :)
[18:47] <AnRkey> may i ask an off topic question quick?
[18:47] <BUGabundo> I guess AnRkey
[18:47] <AnRkey> configure: error: *** wxWidgets resource compiler not found - unable to build GUI components *** << what in the name of all that is good is this thing looking for?
[18:48] <burner_> AnRkey: you compiling?  maybe it's a -dev package of wxwidgets?
[18:48] <AnRkey> hmm
[18:48] <AnRkey> brb
[18:49] <burner_> try libwxgtk2.8-dev
[18:49] <AnRkey> already installed
[18:50]  * AnRkey starts getting emotional
[18:51] <AnRkey> i get this when i try compile
[18:51] <AnRkey> checking for wxrc-gtk2-2.8... no
[18:51] <AnRkey> configure: error: *** wxWidgets resource compiler not found - unable to build GUI components ***
[18:51] <AnRkey> it finds almost everything else
[18:55] <AnRkey> thanks anyway chaps
[19:00] <burner> lo siento
[19:17] <blueyed> KDE on Jaunty is currently borked, correct? (e.g. kickoff menu displays only a box with black borders, the same for krunner). window decorations look strange/old, too..
[19:21] <charlie-tca> I believe you are right, blueyed
[19:21] <blueyed> Thanks for confirming, charlie-tca.
[19:21] <charlie-tca> no problem.
[21:19] <Daisuke_Ido> fix your connection already
[21:19] <Daisuke_Ido> as he leaves YET again
[21:30] <mphill> how lame
[21:34] <genii> Makes you feel like smacking them around some
[22:05] <neztiti> hi guys - can some on help me with ATI 1250 card to work with tvout with any driver???
[22:45] <neztiti> hi guys - can some on help me with ATI 1250 card to work with tvout with any driver???


[09:34] <AlanBell> morning, I seem to have a heap of stuff constantly being written to syslog
[09:34] <AlanBell> Nov 29 09:34:47 alanlaptop kernel: [401694.881890] [drm:intel_update_fbc], more than one pipe active, disabling compression
[09:35] <AlanBell> many times per second
[09:35] <AlanBell> http://lists.debian.org/debian-kernel/2010/10/msg00371.html appears to be the patch that introduced the debug message
[09:36] <AlanBell> but that was in 2010 and I think it started doing this sometime in the saucy cycle
[09:36] <tjaalton> do you have drm.debug set on cmdline?
[09:37] <AlanBell> where would I look for that?
[09:37] <tjaalton> cat /proc/cmdline
[09:37] <AlanBell> BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=a1919e83-6201-440f-bc38-4482a9274054 ro quiet splash vt.handoff=7
[09:37] <tjaalton> so no
[09:38] <AlanBell> I normally have an external screen plus laptop screen, it doesn't appear to make any difference if I unplug the external
[09:39] <AlanBell> performance isn't affected much, it just makes dmesg a bit messy :)
[09:45] <tjaalton> it should save some battery, that's all
[09:45] <tjaalton> er, power
[10:18] <AlanBell> connect irc.oftc.net
[10:19] <AlanBell> oops :)


[00:24] <LLStarks> bryce, the bug component statuses should be updated.
[00:25] <bryce> LLStarks, go ahead
[00:25] <LLStarks> incomplete?
[00:25] <bryce> LLStarks, yeah the bug is sort of a mess
[00:26] <bryce> LLStarks, to be honest it seems not too useful to have a bug open for a development branch still in work upstream
[00:27] <LLStarks> well, i had been under the impression that most of the branch merges indicated component readiness
[00:28] <LLStarks> at any rate, i think the bug is necessary considering how huge the implementation is.
[00:28] <LLStarks> it requires the tracking of multiple code trees
[00:30] <LLStarks> and i'm sure mark would like to track this for lucky lemur.
[00:30] <bryce> I disagree, I think using bugs to track upstream code branches gives little value
[00:33] <bryce> but whatever
[09:25] <bryce> for the first time in as long as I can remember, we presently have fewer -intel bug reports than -nvidia
[09:34] <superm1> bryce, did you see what i uploaded for that -nvidia problem?  i think it should take care of it..
[09:34] <bryce> superm1, yup sure did, thanks for that :-)
[09:34] <superm1> and my you're up late
[09:35] <superm1> (although i should speak for myself)
[09:35] <bryce> I'm getting a new -ati upload ready.  I've tested it out and it seems pretty solid so far
[17:33] <MindVirus1> Hello. I'm running Karmic right now on an Intel 945GME. Could someone help me get direct rendering?
[17:33] <MindVirus1> "direct rendering: No (LIBGL_ALWAYS_INDIRECT set)" is what  Iget.
[17:33] <MindVirus1> *I get.
[17:34] <jcristau> don't set LIBGL_ALWAYS_INDIRECT.
[17:35] <MindVirus1> I didn't set it.
[18:10] <estan> hey folks. is the 2.6.30 kernel from karmic copied to the x-updates repo in the same way that it is for the edgers repo?
[18:10] <estan> i mean for jaunty.
[18:18] <estan> seems not.
[18:21]  * estan installs <IP_ADDRESS> debs instead.
[18:32] <tjaalton> karmic has .31
[19:14] <Duke`> is Sarvatt on hollidays?
[19:34] <bryce> Duke, I've not seen him in a long time
[19:36] <kazade> bryce, you know that GDM looping bug on R600? Alex Deutchers's R600 3D patch alone fixes the issue, I've updated the bug report. Obviously I don't know which part of the patch fixes it though...it's a big patch
[19:38] <kazade> s/Deutcher/Deucher :)


[10:48] <alberts> attente: are you here?
[10:58] <alberts> attente: I commented on merge proposal (already merged) created by you - https://code.launchpad.net/~attente/ubuntu-themes/gtkmodelmenuitem-icon-spacing/+merge/163053
[11:36] <attente> alberts, what version of light-themes do you have installed?
[11:44] <attente> alberts, also what version of unity-services do you have?
[15:42] <alberts> attente: light-themes version - 13.04+13.10.20130919.3-0ubuntu1
[15:43] <alberts> attente: unity-services - 7.1.0+13.10.20130920-0ubuntu1
[15:43] <alberts> attente: but I am not using unity, I use gnome-flashback session
[17:44] <bjf> bug or feature? in saucy i'm no longer able to set my 'caps lock' to 'ctrl' with: dconf write /org/gnome/libgnomekbd/keyboard/options "['ctrl\tctrl:nocaps']"
[17:44] <bjf> is there a new way to do this?


[16:16] <Maik> please keep an eye on scortal, they are being annoying in the support channel. I put them on ignore now since the continues wioth their nonsense after being asked kindly to stop it.


[00:07] <Dimmuxx> hehe nice one
[00:20] <fta> *sigh* a new ch beta
[00:23] <BUGabundo> aahahahaah
[00:23] <BUGabundo> they must love you
[00:23] <BUGabundo> but my 8 months old bug is still open
[00:23] <BUGabundo> I *really* hope it doesn't land in betas
[00:23] <BUGabundo> or MANY ppl in coorperate env will be screwed
[00:29] <fta> http://people.ubuntu.com/~fta/adsl-nightmare.png
[00:34] <BUGabundo> looks lime mine
[00:37] <fta> i used to have zero disconnection in a week
[00:37] <fta> now, i have ~40 a day
[00:42] <fta> http://www.osnews.com/story/23698/Why_I_Turned_on_AdBlock_Today  lol
[01:38] <BUGabundo> see what happens when you touch a long long static topic?
[01:38] <BUGabundo> you ping timeout
[16:54] <bobby> I was customizing some settings in about:config and then ran the sunspider benchmark
[16:54] <bobby> I got 1500ms...
[16:54] <bobby> I then realized I turned off TraceMonkey... fail
[21:08] <fta> crimsun_, bug 621946 (another p-a related openarena crash)
[21:08] <ubot2> Launchpad bug 621946 in openarena (Ubuntu) "openarena crashed with SIGSEGV in stream_get_timing_info_callback() (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/621946
[21:13] <fta> debian 593422
[21:13] <ubot2> Debian bug 593422 in libasound2 "openarena: Segfaults unless pulseaudio is installed and running." [Grave,Open] http://bugs.debian.org/593422
[21:14] <fta> hmm


[03:08] <Aki-Thinkpad> how do you unfullscreen in qtcreator?
[03:09] <Aki-Thinkpad> nvm
[03:09] <Aki-Thinkpad> wow this google thing is useful :P
[14:03] <qtros> popey ping
[14:27] <qtros> mhall119 ping
[14:44] <alaak> Hi. I still get an error when trying to upload a new version for my Ubuntu Touch App. Is there already anything known, when this will get fixed?
[14:46] <daker> alaak: can you get the full backtrace of the server response ?
[15:52] <alaak> {"traceback": "Traceback (most recent call last):\n  File \"/srv/pkgme-service.canonical.com/production/pkgme-service/sourcecode/../src/djpkgme/tasks.py\", line 536, in run\n    logger=self.get_logger())\n  File \"/srv/pkgme-service.canonical.com/production/pkgme-service/sourcecode/../src/djpkgme/client.py\", line 66, in submit_to_myapps\n    raise CallbackError(url, 'PUT', response.status, content)\nCallbackError: PUT to ht
[15:52] <alaak> click-scan-complete/291/ got response 400:\nPiston/0.2.3rc1 (Django 1.5.4) crash report:\n\nMethod signature does not match.\n\nSignature should be: upload_id\n", "type": "CallbackError"}
[15:52] <alaak> that is the stacktrace.
[16:03] <daker> alaak: ok thanks
[16:04] <daker> beuno: ^
[16:10] <daker> or james_w`
[16:11] <mhall119> qtros: pong
[16:30] <qtros> mhall119 Hello! As you may know I am participating in App Showdown with TwimGo. But yesterday I've found that it doesn't work properly under Qt 5.2.1 (https://bugreports.qt-project.org/browse/QTBUG-38451). How I can notify judges about it? They should test it on 5.0 (not 14.04 in another words)
[17:11] <Elleo> qtros: at a guess from glancing at that I'd guess it's probably not a Qt bug exactly, but is rather due to qreal now being a double on arm instead of a float
[17:11] <Elleo> that's just my vague intuition though, haven't looked in to your code in detail
[17:11] <Elleo> but that'd seem a likely culprit since that changed in recent versions of the qt packages
[17:36] <qtros> Elleo but how console.log() fixes it then?
[17:36] <qtros> Elleo as far as I know qmlscene is not multithreaded
[17:37] <qtros> Elleo I mean that console output can change behavior of multithreaded programs as far as I know
[17:37] <qtros> Elleo and just want to note - I tested it on my x86 desktop too
[17:37] <qtros> Elleo also affected
[17:41] <qtros> mhall119 should I contact judges myself or you can notify them (and prove that the app works well)? I would be very grateful! ;)
[18:52] <wolter> If I solve a bug in a personal branch, to which branch should I propose the merge? Stable, trunk?
[18:54] <nikwen> I would suggest trunk because that's the current development version.
[19:04] <wolter> Thanks
[19:05] <wolter> Is there a quick way of merging two branches with no common ancestors and having bzr solve all of the conflicts?
[19:05] <wolter> I see it easier to just pull from scratch the branch I will propose merge to and then modify the files I have changed
[19:51] <Ahmad> Hi
[22:02] <Thorondor> Hi
[22:18] <Thorondor> Hi, I've been reading about the devel environment for Touch, and decided to start my experimentation with a "QML Extension Library + Tabbed UI". I thought this was a C++ application with UI designed using Qml, but seems like it's something different
[22:18] <Thorondor> Any feedback?
[22:19] <Thorondor> My confusion started after reading that a "Tabbed UI" project is Qml only.