[14:39] -BottyMcBotFace:#ubuntu-news- ::Softpedia:: KDE Plasma 5.18 LTS Desktop Environment Enters Beta, Here's What's New @ https://news.softpedia.com/news/kde-plasma-5-18-lts-desktop-environment-enters-beta-here-s-what-s-new-528884.shtml (by Marius Nestor)
[16:08] -BottyMcBotFace:#ubuntu-news- ::Softpedia:: elementary OS 6 Will Be Based on Ubuntu 20.04 LTS (Focal Fossa) @ https://news.softpedia.com/news/elementary-os-6-will-be-based-on-ubuntu-20-04-lts-focal-fossa-528885.shtml (by Marius Nestor)
[16:14] -BottyMcBotFace:#ubuntu-news- ::OMG!Ubuntu:: KDE Plasma 5.18 LTS: New Features & Key Changes @ https://www.omgubuntu.co.uk/?p=161002 (by Joey Sneddon)
[16:57] -BottyMcBotFace:#ubuntu-news- ::Softpedia:: Xfce 4.16 Desktop Environment Switches to Client-Side Decorations @ https://news.softpedia.com/news/xfce-4-16-desktop-environment-switches-to-client-side-decorations-528886.shtml (by Marius Nestor)
[17:16] -BottyMcBotFace:#ubuntu-news- ::Softpedia:: Zorin OS Makes It Easy to Deploy Linux-Powered Computers in Schools, Businesses @ https://news.softpedia.com/news/zorin-os-makes-it-easy-to-deploy-linux-powered-computers-in-schools-businesses-528887.shtml (by Marius Nestor)
[17:44] -BottyMcBotFace:#ubuntu-news- ::OMG!Ubuntu:: Xfce 4.16 is Adopting Client Side Decoration by Default @ https://www.omgubuntu.co.uk/?p=161050 (by Joey Sneddon)
[22:49] -BottyMcBotFace:#ubuntu-news- ::Portugal:: Ep 73 – WSL por Nuno do Carmo (parte 1) @ https://podcastubuntuportugal.org/ep73/
[23:03] -BottyMcBotFace:#ubuntu-news- ::Planet:: Podcast Ubuntu Portugal: Ep 73 – WSL por Nuno do Carmo (parte 1) @ https://podcastubuntuportugal.org/ep73/


[23:13] <Kon> Xorg upgrades used to be part of the HWE stack up through 18.04. Are there any plans to include Wayland upgrades for HWE?


[00:10] <Nairwolf> floculant : how can I verify if this bug affects me ? https://bugs.launchpad.net/ubuntu/+source/xubuntu-artwork/+bug/1548647
[00:45] <krytarik> Nairwolf: https://kdeonlinux.files.wordpress.com/2015/03/libreoffice3.png  vs.  http://xubuntu.org/wp-content/uploads/2015/07/lo-writer.png
[00:51] <Nairwolf> oh, thank you, the first one is much nicer ;)
[00:52] <Nairwolf> I hope it will be changed ;)
[00:54] <knome> actually, the latter one is what you should have.
[00:56] <bluesabre> :D
[01:00] <Nairwolf> i've shut down my test-computer, but it seems that I had the second one
[01:01] <Nairwolf> why this theme ?
[01:01] <knome> there are actually a few things that are different in those two screenshots, so there is no clear answer
[01:09] <Nairwolf> ok
[01:19] <bluesabre> gnome-software seems to do *some* stuff now
[01:19] <knome> :)
[01:19] <knome> branau, hello
[01:19] <branau> Hey knome! How goes it?
[01:19] <knome> not bad
[01:20] <knome> to answer to your email:
[01:20] <knome> as i said, my original intention was to work on the UI side of things
[01:20] <knome> then i noticed that the uploader on your version had a possibility to upload from an URL
[01:20] <knome> plus the regular metadata stuff wordpress offers
[01:21] <knome> i quickly checked if there was an option to be able to remove those, but there didn't seem to be a trivial choice
[01:21] <knome> i mean we only want the user to upload a file, without touching it's title, or too much else
[01:22] <branau> Yeah, I thought you wanted me to use the built-in WordPress uploader, at least that was what I had understood
[01:22] <knome> yeah; my code uses wp to handle the upload too
[01:22] <knome> i think this is the old widget though
[01:22] <knome> which turned out to be perfect for us :)
[01:22] <branau> Gotcha, I must've misunderstood what you meant
[01:22] <knome> less dependencies too!
[01:23] <knome> i mean your version was fine too - it just had that URL thing, and other options we actually didn't want to show the user if possible
[01:23] <knome> i totally didn't mean to snatch the work from you...
[01:24] <knome> at the point i had the upload thing done, and having heard you say that you didn't touch the voting stuff yet, i quickly dropped that in too
[01:24] <branau> It's all good, I should've clarified before jumping into it
[01:24] <knome> the version you got actually saves all the votes in a single option; i've now updated the tarball into a version where each image has its own metadata with votes
[01:25] <knome> (and licence/attribution in their own meta fields instead of the "content" field, so people can't mess with it now)
[01:25] <branau> Sounds good, so you want me to upload that plugin so we can test it then=
[01:25] <branau> ?*
[01:25] <knome> it's still on temp.knome.fi
[01:26] <branau> Ah, same url as before?
[01:26] <knome> i've actually sent a request to the canonical IS to set up a new subdomain contest.xubuntu.org
[01:26] <knome> so once we have that linked, i'll push the code to the server and set it up for further testing
[01:26] <branau> Ah, sounds good
[01:26] <knome> (i should also push the code to a repository under xubuntu-website in launchpad)
[10:55] <bluesabre> Assuming we're leaving our monospace font as DejaVu, this should be it for the changes to desktop branches
[10:55] <bluesabre> https://code.launchpad.net/~bluesabre/xubuntu-default-settings/noto-sans
[10:55] <bluesabre> https://code.launchpad.net/~bluesabre/ubuntu-seeds/xubuntu.xenial.noto-sans
[11:25] <SwissBot> feed xubuntu-default-settings had 8 updates, showing the latest 3
[11:28] <knome> bluesabre, well done
[12:25] <bluesabre> flocculant: new catfish-daily package building in https://code.launchpad.net/~catfish-search/+archive/ubuntu/ppa - fixed
[12:25] <bluesabre> https://bugs.launchpad.net/catfish-search/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=FIXCOMMITTED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branche
[12:25] <bluesabre> s.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search
[12:25] <knome> huhu
[12:26] <bluesabre> that failed
[12:26] <bluesabre> :D
[12:26]  * knome grants bluesabre the sherlock of the day award
[12:26] <bluesabre> huzzahhhh
[12:26] <bluesabre> flocculant: better link https://bugs.launchpad.net/catfish-search/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=FIXCOMMITTED
[12:28] <bluesabre> with the recent annoyances in clutter, might set parole
[12:29] <bluesabre> 's default back to xv and add some patches to make that better
[12:29]  * bluesabre can't seem to type today
[12:29] <bluesabre> will have to figure something out with mugshot :\
[12:31] <knome> ok everybody, likely going to break dev.xubuntu.org for a sec
[12:31] <ochosi> bluesabre: what's so broken with clutter in 16.04?
[12:31] <ochosi> (i presume totem/video still works as always)
[12:32] <bluesabre> ochosi: API change in ClutterGst... the old video sink was dropped and the new one is a pain to integrate
[12:32] <bluesabre> ochosi: the old one was a clutter actor that could be easily embedded, the new one, not so much
[12:32] <bluesabre> ochosi: I'm also apparently the only person using the API in python
[12:33] <bluesabre> no code examples >.<
[12:34] <bluesabre> will hop on one of those channels trying to get support sometime soon, haven't quite had time lately
[12:35] <bluesabre> so to summarize... in mugshot the video appears white but a photo can technically be taken
[12:35] <bluesabre> and in parole, I have code that makes it do something now, but it just pops the video window out of the player
[12:41] <flocculant> bluesabre: what a good chap you are :)
[12:47] <flocculant> bluesabre: still got issues with images and laptops - which probably is actually useful - not loads of rebuilds going on :D
[12:48] <flocculant> I've managed to jury rig a laptop up so can at least test the installer doesn't crash prior to deciding to release or not
[12:49] <ochosi> bluesabre: that sounds really meh
[12:49] <flocculant> I'd likely still release anyway - it can install on laptop as long as remove battery/use ac
[12:49] <flocculant> hi ochosi
[12:54] <bluesabre> flocculant: funnnn
[12:55] <bluesabre> flocculant: used gnome-software any lately?
[12:55] <bluesabre> it does some stuff now
[12:55] <bluesabre> and last night it consumed all of my ram after closing it
[12:56] <bluesabre> :D
[12:56] <bluesabre> going to try to reproduce tonight, then file a bug if I can
[12:57] <bluesabre> ochosi: yes, especially since I moved to clutter with the idea that things should be stable and supported and easy to maintain
[12:57] <bluesabre> (pretty much none of those ideals came true)
[12:59] <flocculant> bluesabre: nope - not used it lately
[12:59] <bluesabre> still doesn't list uninstalled apps (for me)
[13:00] <flocculant> same
[13:00] <bluesabre> but the updater functionality is starting to work, and existing apps can be launched now
[13:00] <flocculant> really
[13:01] <flocculant> it's telling me there are updates when there aren't
[13:01] <bluesabre> *starting*
[13:01] <flocculant> ha ha ha
[13:01] <flocculant> in as much as it probably could :)
[13:02] <bluesabre> I think that might be related to the "Restart & Install" button at the top of mine
[13:02] <bluesabre> scared to think of what that might do if it does not currently work
[13:02] <flocculant> I dare you :p
[13:02] <bluesabre> I'll do it in a vm later ;)
[13:02] <flocculant> ha ha ha
[13:03] <flocculant> I see you are sensible then :D
[13:03] <bluesabre> only a bit
[13:03] <flocculant> :)
[13:05] <flocculant> bluesabre: I assume the catfish changes are in the ppa? I tested the click not working properly one I reported - that appears to work now, so I hope so :)
[13:07] <flocculant> right - I'm off again - bbl
[13:08] <bluesabre> flocculant: yes, the "catfish-daily" package
[13:55] <knome> bluesabre, have you ever used dokuwiki with mysql?
[13:58] <bluesabre> knome, nope
[13:58] <knome> mhm
[13:58] <bluesabre> Time for work, bbl
[13:58] <knome> i don't remember if i have, i might...
[16:27] <Nairwolf> hi flocculant, I've received your message
[16:28] <Nairwolf> I would like to help more, so tell me what I'm supposed to do ;)
[16:30] <flocculant> Nairwolf: you read the QA dev docs? generally just carry on as you are for the time being - you're doing fine
[16:31] <flocculant> assuming you're about still in May then we can look at getting you to do more for sure
[16:46] <Nairwolf> flocculant: I need to admit, I'm often lost with all links to deal with (docs.xubuntu.org, ubuntu wiki, launchpad)
[16:46] <flocculant> :D
[16:47] <flocculant> for QA you need one :)
[16:47] <flocculant> http://docs.xubuntu.org/contributors/
[16:53] <Nairwolf> ok !
[16:53] <Nairwolf> I'm gonna read that
[16:53] <Nairwolf> thanks
[16:53] <flocculant> 3 of the chapters are qa
[16:53] <Nairwolf> I need to do some stuff right now, maybe I'm going to ask some questions later
[16:53] <Nairwolf> yes, I've seen that
[17:17] <Nairwolf> oh, I wasn't connected, what was my last message ?
[17:17] <Nairwolf>  I've just discovered that : https://trello.com/b/IV66JCHl/xubuntu-qa
[17:17] <Nairwolf> what does mean "Priority 5" ?
[17:24] <flocculant> it';s the 5th time it was going to get called
[17:26] <Nairwolf> what is "it" ?
[17:26] <flocculant> don't really use that anymore - not likely to make it into the yogic yinepu cycle
[17:27] <Nairwolf> Can I join this team or do I need to show my work, before ?
[17:27] <Nairwolf> https://launchpad.net/~xubuntu-testers
[17:28] <flocculant> you can join that - it's open team
[17:29] <Nairwolf> okay, what are the implications ? Will I receive some mails ?
[17:29] <flocculant> some - not many
[17:30] <Nairwolf> ok, ok, I will see
[18:54] <flocculant> bluesabre: I think I asked this before - lost in the logs of time though ... why do we have evince and evince-gtk?
[19:21] <Unit193> flocculant: evince-gtk is a transitional dummy package back to evince now.
[19:56] <knome> Unit193, since you mentioned it, navigation on dev. and wiki. should now work seamlessly
[19:56] <knome> (seamlessly meaning that if you have dev. open and go to wiki. (or the other way), your irc tab will be reset)
[19:57] <knome> but maybe the irc tab should default to opening in _blank anyway
[20:03] <Unit193> Great, nice.
[20:23] <flocculant> knome: can I leave the website release doodah for tomorrow to you?
[20:24] <flocculant> bluesabre: draft wiki is https://wiki.ubuntu.com/XenialXerus/Beta1/Xubuntu - if you could look at the bug fix/enhancement thing that'd be nice :)
[21:07] <knome> is there something we specifically like to highlight on the announcement?
[21:08] <knome> maybe gmb/no media manager?
[21:08] <knome> and noto
[21:12] <flocculant> sounds like the sort of things which should be on it
[21:13] <knome> https://xubuntu.org/?p=3731&preview=true
[21:13] <flocculant> not sure there are any other major changes from 15.10
[21:13] <flocculant> knome: thanks - looks just how I thought it would :)
[21:14] <knome> i checked http://dev.xubuntu.org/#tab-timeline and searched for "in development"
[21:14] <knome> and no, i didn't find anything specific
[21:16] <knome> did a few updates
[21:17] <flocculant> yep
[21:17] <knome> do we want to mention the beta on the footer?
[21:17] <knome> like we did before with 15.10
[21:18] <knome> and
[21:18] <knome>  This is the first beta towards the final release in October.
[21:18] <knome> not
[21:18] <flocculant> yea I think so
[21:18] <knome> s/15.10/16.04/ too :P
[21:18] <flocculant> mmm
[21:18] <flocculant> actually not so sure
[21:18] <knome> about mentioning on footer?
[21:19] <flocculant> yea
[21:19] <knome> then the beta release won't be visible on the front page at all
[21:19] <flocculant> as you know on Friday it's out of date
[21:19] <knome> (not saying this is unwanted, just saying)
[21:19] <flocculant> why is it not on the front page?
[21:20] <knome> the blog articles we show only show "articles", eg. not news
[21:20] <flocculant> ok
[21:20] <knome> that's intentional, because we don't want it to be littered with "15.10 b1 out", "15.10 b2 out", etc...
[21:20] <knome> (and because the latest real releases are highlighted already)
[21:21] <flocculant> I'm not convinced that advertising b1 is what we should do tbh - I'd rather people asked and got pointed at daily
[21:21] <knome> ack
[21:21] <knome> i was just saying so that you are aware
[21:21] <flocculant> yea I understand that :)
[21:21] <knome> (and because we did the footer thing before)
[21:21] <flocculant> I think when we get to RC time we can do it
[21:22] <knome> yeah
[21:22] <flocculant> yep - I've just been mulling it over as we started talking about it
[21:22] <knome> :)
[21:22] <flocculant> given the lack of testing we *know* about - I don't want much to get into that install b1 and apt-get update it till April thing :)
[21:22] <knome> bug 1462445 ?
[21:23] <knome> bug 1515425 ?
[21:23] <knome> re: issues we might want to highlight
[21:25] <flocculant> yea I've got a list - the mousepad one isn't on it :D
[21:25] <knome> :)
[21:25] <flocculant> the other mousepad one is ;)
[21:25] <knome> hah
[21:25] <knome> i should tackle that *some day*
[21:25] <flocculant> :D
[21:25] <knome> but yeah, i think i should be around during the day enough tomorrow to take care of the website update
[21:25] <knome> if not, and you are, feel free to go push the publish button
[21:26] <flocculant> well - I'm driving the train with stgraber so ...
[21:26] <knome> the announcement should be ready to go already considering the download link is correct
[21:26] <flocculant> yep
[21:26] <flocculant> he's apparentyl working pacific time - so it'll be later in the day I guess
[21:27] <knome> yeah, not EU-based
[21:27] <knome> we have guests afternoonish
[21:27] <flocculant> right
[21:27] <knome> but i'm not completely tied to them
[21:27] <knome> i mean i can check the situation etc
[21:27] <flocculant> I just didn't want to find I had to write the website thing at the last minute :)
[21:28] <knome> sure
[21:28] <knome> tbh, this is all *so* much easier with the tracker now
[21:28] <knome> it isn't like "wait, what did we change" at all
[21:28] <flocculant> well I don't really use it for this much - I'm more interested in what bugs I see on the 2 trackers
[21:29] <flocculant> yea for sure :D
[21:29] <knome> yeah, sure
[21:29] <knome> but since the critical ones are likely to be tracked on the bugs blueprint...
[21:29] <knome> (there's one good reason to maintain it, since you were once wondering)
[21:29] <flocculant> generally - I've not been good lately
[21:29] <knome> le sigh
[21:30] <knome> if IS would just get our subdomain ready, i could proceed with the wallpaper contest stuff
[21:30] <flocculant> :)
[21:30] <flocculant> \o/ 32 and 64 bit finally installed on a battery laden hardware
[21:33] <flocculant> knome: while back there was that blueman applet discussion where we were trying to work out what it affected
[21:33] <flocculant> seems to not affect 64bit on this laptop - but does on 32bit ...
[21:36] <knome> "heh"
[21:58] <Nairwolf> when new daily build are done ?
[21:59] <Nairwolf> is it programmed ? In order to know when I need to check with zsync
[21:59] <knome> always check
[21:59] <knome> there might be a manual rebuild
[21:59] <knome> usually not for dailies, but who knows.
[22:01] <Nairwolf> yes, but I wanted to say that I've checked few hours ago, and it wasn't updated. And flocculant told me at #xubuntu that it was updated. I wanted to know when automatic builds are done
[22:01] <knome> noonish UTC afaik
[22:02] <knome> flocculant, am i right?
[22:05] <flocculant> 10 am UTC for cron led builds
[22:06] <flocculant> milestone one's are whenever - our latest was when I kicked it off after ubiquity new landed
[22:07] <knome> i would still say better test every time; you never know what the 1337 people are up to.
[22:10] <bluesabre> knome: no noto yet, waiting until after b1 (so tomorrow night)
[22:10] <knome> aha
[22:11] <knome> done
[22:12] <bluesabre> Haven't reviewed the rest yet, on way home
[22:12] <knome> bluesabre, just that we don't forget, can you add a work item for droid->noto
[22:12] <bluesabre> Will do
[22:12] <knome> thanks
[22:13] <Nairwolf> knome: I can't run zsync everytinme ! Or I need to make it automatic ^^
[22:13] <knome> Nairwolf, why can't you?
[22:13] <Nairwolf> do you mean, why I can't run rsync for example every hour ?
[22:14] <knome> well if you run a test every hour, you surely can run the zsync command once an hour too
[22:14] <knome> tbh, you likely need to run it only once per test session
[22:14] <knome> and that's in most cases fine
[22:14] <Nairwolf> I can't run a test every hour...
[22:15] <knome> so why would you need to run the zsync every hour then?
[22:15] <knome> just run it every time before you do a test.
[22:15] <Nairwolf> because you told me that I have to test everytime ^^
[22:16] <Nairwolf> obviously, before I launch a test, I update the iso
[22:16] <knome> yes, every time you run a test...
[22:16] <knome> i didn't mean (or say) "every hour"
[22:17] <Nairwolf> ok, I think I misunderstood you
[22:19] <Nairwolf> maybe my english is not perfect. I've checked if there is a new version few hours ago, and there wasn't. The iso wasn't updated, so I was saying to myself (no need to test today). And then, few minutes ago, I've learnt that there is a new update. That's why I wanted to know when the build are done. That's all.
[22:19] <knome> as said, the *automatic* updates happen noonish UTC, but there can be other manual updates
[22:20] <knome> so that's why it makes sense to test if the ISO has changed every time you are about to run a test
[22:22] <Nairwolf> yes, you right. But tonight I've some freetime, and if flocculant didn't tell me that there is a new update, I wouldn't have tested it right now.
[22:22] <knome> sure
[22:22] <Nairwolf> But, that's okay, thank you for telling me the hour.
[22:22] <knome> that's why we have these communication channels
[22:22] <Nairwolf> indeed ;)
[22:29] <Nairwolf> thank you anyway
[22:29] <flocculant> Nairwolf: for when we are doing milestone tests the quickest way to see if we have a rebuild is check the version listed on the tracker
[22:30] <Nairwolf> ok, flocculant
[22:30] <flocculant> it now says 201602224, if I did a rebuild now it would be 20160224.1
[22:30] <flocculant> for dailies - the time is ~10.00UTC
[22:30] <flocculant> unless it's not building - always check the date :)
[22:32] <Nairwolf> thank you
[22:32] <flocculant> welcome
[22:32] <Nairwolf> I've the same bug as yesterday "the creation of swap space in partition #5 of SCI3 failed" before the time zone window...
[22:33] <flocculant> Nairwolf: it's useful if you made note of things you've needed to ask about - so we can add information
[22:36] <Nairwolf> sorry, maybe I don't have understood again...
[22:36] <Nairwolf> It's during ubiquity, how can I get some information (like traceback ?)
[22:41] <Nairwolf> I don't really know which information I need to add
[22:44] <flocculant> Nairwolf: report bug 990744 on the tracker against the testcase you followed
[22:48] <Nairwolf> thank you flocculant, it seems to be this bug, you right !
[22:48] <Nairwolf> I was starting to write a bug, I will just write a comment. Thank you
[22:49] <flocculant> no need to comment - you can click affects me at the top though
[22:49] <flocculant> important you get it on the tracker - when I do release notes I refer to the tracker for bugs people have seen
[22:49] <Nairwolf> yes, but I would like to add some information
[22:49] <Nairwolf> ok
[22:52] <Nairwolf> that's done
[22:52] <flocculant> thanks
[22:52] <flocculant> time for me to wander off for a while - night all
[22:52] <Nairwolf> good night ;)
[22:58] <Nairwolf> which is weird is I had the same issue yesterday, and I succeded to install the iso. Today, I can't !
[22:58] <Nairwolf> I'm still stuck with this bug


[06:43] <dottedmag> franklin: It is rude to PM random people who happen to be on some random IRC channel.
[10:37] <franklin> ubuntu load unload question?


[00:22] <micahg> are bugs not being able to pull status form upstream trackers a known issue?
[00:23] <wgrant> micahg: Which tracker?
[00:23] <wgrant> I know of an issue with debbugs.
[00:23] <micahg> wgrant: I just saw it for mozilla on bug 569528,but have seen it for gnome and debian
[00:24] <micahg> oops
[00:24] <micahg> bug 588595
[04:02] <brr> One of the PPA build machines got stuck: https://launchpad.net/builders/terranova
[04:44] <d1b> OH HAI
[04:44] <d1b> question why do i see in my bug reports listing duplicates of some bugs?
[04:45] <d1b> is this because it is tagged for different distros?
[04:45] <beuno> d1b, because they have multiple targets, yes
[04:45] <lifeless> if you're searching in a context that can have multiple tasks, yes.
[04:45] <lifeless> its a feature; the ui can be improved
[04:45] <d1b> right and there isn't an option to change that?
[04:45] <beuno> well, this is for his personal list I assume
[04:45] <d1b> yeah :)
[04:45] <lifeless> I was chatting with deryck about that a couple weeks back, not on the roadmap immediately
[04:45] <beuno> its a bug, just a hard one to solve
[04:45] <d1b> beuno: oh hardly ;)
[04:46] <d1b> select * from bugs where ....
[04:46] <lifeless> d1b: its strictly correct, because it shows the *target* column.
[04:46] <lifeless> d1b: select DISTINCT is needed, but these results *are* distinct.
[04:46] <lifeless> what I think would be nice would be to show all the targets as one row
[04:46] <lifeless> with something nice breaking out the status per target
[04:47] <d1b> lifeless: don't include anything but the bug number for the distrinc ;)
[04:47] <beuno> right, its a UI issue rather than technical
[04:47] <d1b> yeah :)
[04:47]  * beuno has discussed multiple times
[04:47] <lifeless> d1b: if we did that, today, it would not show some tasks (because it shows one task per row). That would be worse.
[04:47] <d1b> right. why not just put them in a sort of larger row if that is the case
[04:48] <lifeless> d1b: isn't that what I just said I would like to see?
[04:48] <d1b> lifeless: don't nkow what you asid :)
[04:48] <lifeless> look up above
[04:48] <d1b> oh ah no sort of
[04:48] <beuno> one of the problems is that each bugtask can have a different importance
[04:48] <d1b> show the targets sure -but if the status differs show that too
[04:48] <beuno> and default sorting isby importance
[04:48] <beuno> so it makes it hard to decide where to plate it
[04:49] <d1b> give it the highest importance assigned to the bug number# regardless of target?
[04:49] <lifeless> beuno: move it around as the users eyes cross
[04:49] <d1b> haahahah
[04:49] <lifeless> beuno: different areas of the screen
[04:50] <beuno> oh, life would get very intersting if we could know where people's eyes are going  :)
[04:50] <lifeless> beuno: appropriately pretty models of the appropriate gender can control that :P
[04:51] <beuno> heh
[04:52] <beuno> it's amazing when you see the eye-tracking software show you how people's eyes go straight to people's exposed areas on ads, no matter how much people try
[04:52] <d1b> so just reuse some of the old ubuntu material then ;)
[04:52] <lifeless> beuno: its how we got here .... really not surprising
[04:56] <beuno> lifeless, what was surprising is that the first look is *always* at the eyes
[04:56] <d1b> big brother is following you!
[04:57] <d1b>  http://www.hughsandeman.co.uk/media/blogs/archive/bigbrother.JPG
[04:58] <lifeless> beuno: I wonder if its worth doing a little (v) and (^) on duplicate results
[04:58] <lifeless> beuno: labelled 'next task of this bug'
[04:58] <lifeless> beuno: duplicate results being the wrong thing to say, of course. But you know what I mean.
[04:59] <lifeless> beuno: so with three tasks, the first shown would have
[04:59] <lifeless> v
[04:59] <lifeless> the second
[04:59] <lifeless> v^
[04:59] <lifeless> the third
[04:59] <lifeless> ^
[04:59] <beuno> yeah, the problem always comes back to which one to show first
[04:59] <lifeless> beuno: but this means you don't are
[04:59] <lifeless> *care*
[04:59] <lifeless> beuno: because it wouldn't be grouping them, there is no tension with sorting
[05:00] <lifeless> some query magic needed still to determine next/prev on this page/not on this page.
[05:00] <beuno> lifeless, you still need to sort it some place one the list though
[05:00] <lifeless> but it at least has a clear behaviour
[05:00] <beuno> and choose which one to show first
[05:00] <lifeless> beuno: you place them all on the list
[05:00] <beuno> no?
[05:00] <lifeless> beuno: exactly as they are today
[05:01] <lifeless> beuno: just add a really small tasteful link to the next/prev tasks of that bug beside the bug target
[05:02] <beuno> lifeless, I don't follow. You still show all 3 of them?
[05:02] <beuno> or you show 1 row, with prev/next
[05:03] <beuno> I am looking at: https://bugs.edge.launchpad.net/~beuno
[05:04] <beuno> the "In" column is the target
[05:04] <lifeless> all hree
[05:05] <lifeless> or you could show a + or something with a popup that lists all the tasks (and still show each task as separate rows
[05:05] <beuno> I see, just so you could visualize it better?
[05:05] <lifeless> beuno: I'm saying, don't mess with the table. Annotate the rows that have the same bugid in some way to make the duplication self documenting and explicator
[05:06] <lifeless> y
[05:06] <beuno> gothca
[05:06] <lifeless> mmm goth
[05:06] <beuno> so it wouldn't really solve this dupe-look-a-like issue
[05:06] <beuno> it may make it feel worst
[05:06] <beuno> but it will explain better what's going on
[05:06] <beuno> it's a nice step forward I think
[05:08] <beuno> lifeless, something else we could fiddle with, is moving the target next to the bug #
[05:09] <beuno> so people understand this relatonship better
[05:09] <lifeless> perhaps visually group somehow ?
[05:09] <lifeless> like with a slightly darker border athe outer edge of their two rows
[05:10] <beuno> yeah, something like that
[05:10] <lifeless> beuno: that would be nice too
[05:10] <lifeless> where is the bug to write this stuff up in
[05:13] <beuno> lifeless, bug 1357 no less!
[05:13] <beuno> 4 digit bug!
[05:13] <lifeless> \o/
[05:13] <lifeless> beuno: would you like the honours ?
[05:13] <beuno> oh sure, why not
[05:14] <beuno> haven't done this in a while, I'm nervous!
[05:14] <lifeless> ha!
[05:19]  * beuno comments
[05:24] <beuno> lifeless, off to bed. Nice talking UI and Launchpad to you again!
[05:24] <lifeless> beuno: likewise, sleep well!
[05:24]  * beuno waves
[05:32] <nhaines> beuno: good night!  :)
[09:10] <dobedobedoh> What's the best way of requesting a feature/change to Launchpad?
[09:10] <dobedobedoh> At present, Launchpad links to bugs if a comment fits a syntax like bug #xxxxx
[09:10] <poolie> dobedobedoh: file a bug in https://launchpad.net/launchpad, or ask here
[09:11] <poolie> ok
[09:11] <dobedobedoh> It would be quite handy if it also recognised something like (Closes: #xxxxxx)
[09:11] <dobedobedoh> As per the debian devleoper reference
[09:11] <poolie> i would kind of expect that to also actually close the bug
[09:11] <poolie> i think it does match that in commit messages?
[09:12] <poolie> actually isn't the debian standard to say "LP: #1", to distinguish it from debbugs?
[09:12] <dobedobedoh> haven't seen it match in commit messages yet
[09:12] <wgrant> (Closes: #XXXXXX) is Debian-specific.
[09:13] <wgrant> The Launchpad equivalent is LP: #XXXXXX, as poolie says.
[09:13] <wgrant> (Closes: #XXXXXX) could perhaps link to the relevant Debian bug.
[09:13] <dobedobedoh> Okay - fair enough
[09:17] <dobedobedoh> There was another question I had - when adding comments, is there any markdown or other syntax highlighting?
[09:17] <dobedobedoh> Or handy way of posting a log excerpt without having it line wrapped?
[09:44] <marktheunissen> hi all!
[09:44] <marktheunissen> help! we need to deploy code urgently and launchpad is down. :<
[09:45] <marktheunissen> anyone know what the ETA for loggerhead coming back is?
[09:46] <LinuxJedi> marktheunissen: see topic :)
[09:47] <marktheunissen> ah gotcha
[09:47]  * LinuxJedi was trying to look into code on lp to fix some valgrind warnings when it happened ;)
[09:48] <harpreet> Hi everyone
[09:49] <harpreet> Is this correct place for asking questions about vmbuilder on ubuntu.
[09:58] <marktheunissen> hmm, seems to be back?
[09:58] <marktheunissen> is it safe to user?
[09:58] <marktheunissen> *user
[09:58] <marktheunissen> *use
[11:26] <hrw> hi
[11:26] <hrw> how can I clean PPA's APT archive from packages?
[11:27] <hrw> bumping versions is not possible
[11:27] <bigjools> I think Ubuntu has a downgrade script somewhere
[11:27] <bigjools> I've not used it myself
[11:27] <bigjools> try asking in #ubuntu
[11:27] <hrw> ok
[11:29] <hrw> Ubuntu has ppa-purge but it removes PPA's packages from system. I want to remove packages from APT archive of my PPA.
[11:30] <bigjools> hrw: just delete them
[11:31] <hrw> how much time it takes between "packaged deleted" LP message and getting them removed?
[11:32] <hrw> ok, done
[11:32] <hrw> thx
[11:32] <hrw> now need to reupload my source
[11:32] <bigjools> it takes up to about 15 minutes sometimes
[11:33] <bigjools> you can't re-upload the same version
[11:33] <bigjools> you must bump it
[11:33] <hrw> even when I deleted it from LP?
[11:33] <bigjools> I see what you mean in your original question now
[11:33] <bigjools> yes, even when you delete it
[11:33] <bigjools> https://answers.edge.launchpad.net/soyuz/+faq/990
[11:33] <hrw> ok, will bump then
[12:21] <Odd_Bloke> I'm having yet more problems related to my emails.  The latest commit at https://code.launchpad.net/~daniel-watkins-credativ/openobject-addons/crm_max_fix is by "Daniel Watkins<EMAIL_ADDRESS>which is related to ~daniel-watkins-credativ.  However, the link on that page points to ~daniel-thewatkins, which is no longer associated with the email.
[12:21] <Odd_Bloke> Is there anyone available to have a poke and work out what's going on?
[12:37] <LinuxJedi> Odd_Bloke: who are you logged in as in "bzr launchpad-login"?
[12:38] <LinuxJedi> (executing that will show you)
[12:44] <Odd_Bloke> LinuxJedi: daniel-watkins-credativ
[12:48] <LinuxJedi> Odd_Bloke: hmm... really odd, maybe its something to do with the ssh keys used
[13:03] <wgrant> Odd_Bloke: Commit authors are tracked as a separate mapping from email addresses to users.
[13:03] <wgrant> I don't know of a way to get them moved across.
[13:04] <Odd_Bloke> :(
[13:04] <Odd_Bloke> Shall I file a bug/question or something?
[13:05] <wgrant> A question, perhaps.
[13:08] <dholbach> hiya
[13:09] <dholbach> could I interest anybody in sharing their wisdom about using bzr, launchpad, code reviews, launchpadlib, hacking in a nice way or any other app development related topic at Ubuntu App Developer Week? :-)
[13:11] <Odd_Bloke> https://answers.launchpad.net/launchpad-code/+question/123948 filed.
[14:26] <hrw> http://launchpadlibrarian.net/54867642/buildlog_ubuntu-maverick-amd64.armel-cross-toolchain_1.28_FAILEDTOBUILD.txt.gz shows that libc6-armel-cross is not available. But this package is present in this PPA APT archive... what is wrong?
[14:28] <bigjools> hrw: remind me of your PPA url again?
[14:28] <hrw> https://edge.launchpad.net/~hrw/+archive/arm-cross-compiler/+build/1945328
[14:31] <bigjools> hrw: libc6-armel-cross might not be installable for some reason, does it have all its dependencies available?
[14:31] <hrw> rechecking now
[14:34] <hrw> installed fine
[14:34] <hrw> directly from ppa
[14:35] <bigjools> can you retry the build please
[14:35] <hrw> sure
[14:35] <bigjools> it may not have been published in time
[14:35] <thopiekar> hi
[14:35] <thopiekar> is it possible to comment out a line in a recipe?
[14:58] <hrw> bigjools: same
[15:02] <bigjools> hrw: the queue is quite big, your build won't have finished yet?
[15:02] <hrw> it failed already
[15:03] <hrw> https://edge.launchpad.net/~hrw/+archive/arm-cross-compiler/+build/1945391
[15:04] <bigjools> you uploaded a new version?
[15:05] <hrw> yes
[15:06] <bigjools> you can just retry the original if it failed
[15:06] <hrw> new ver is same just version bumped
[15:07] <bigjools> I realise - I'm just saying you don't need to do that to retry a failed build
[15:07] <hrw> ah, did not know
[15:13] <bigjools> I am doing a test installation here
[15:16] <bigjools> hrw: ok so libc6-armel-cross depends on libgcc1-armel-cross which depends on gcc-4.5-arm-linux-gnueabi-base which does not exist
[15:16] <bigjools> you can use the "chdist" tool to work this out BTW
[15:18] <hrw> sorry then
[15:18] <hrw> too much builds of the same
[15:22] <hrw> ok, another 1.5h of builds to wait (+ queue)
[16:35] <hrw> I have 1.35 in PPA which just started building and 1.36 freshly uplaoded which fix bug in 1.35. will 1.35 build be killed with new upload or not?
[16:36] <bigjools> hrw: if it already started, no
[16:37] <bigjools> hrw: can I suggest that you use pbuilder locally to test your builds
[16:37] <bigjools> PPAs are not a build testing service
[16:38] <hrw> I do also in pbuilder - just it passed in it as it builds arch+all
[16:43] <hrw> thanks for all help bigjools and have a nice weekend
[16:43] <bigjools> hrw: no problem
[16:43] <bigjools> and thanks
[16:44] <nessita> abentley: ping
[16:44] <abentley> nessita, hi.
[16:44] <nessita> abentley: good morning! would you have some minutes to talk about a possible issue with lp:ubuntuone-client code? beuno suggested that you may help us
[16:45] <nessita> abentley: basicaly, https://code.launchpad.net/ubuntuone-client is reporting that latest version of trunk is 627
[16:45] <nessita> abentley: and in our local copies of trunk we have upto revno 671
[16:45] <abentley> Okay.
[16:45] <nessita> abentley: revno 627 was landed on 2010-08-11
[16:46] <abentley> nessita, actually, I see 627 just landed.
[16:46] <nessita> abentley: LP is sayins "21 hours ago" for revno 627
[16:47] <abentley> nessita, Sorry, meant to type 628.
[16:48] <abentley> nessita, which landed 10 minutes ago.
[16:48] <nessita> abentley: yes, that was tarmac that is running in a cron job
[16:48] <nessita> abentley: we already disabled
[16:49] <nessita> abentley: the problem is that upto yesterday trunk had 671 revnos
[16:49] <nessita> abentley: and today only to 627
[16:49] <nessita> abentley: and besides the revno numbers mismatch, the code for those revnos is gone as well (I know we can recover that, but we'd like to diagnose what happened)
[16:49] <abentley> nessita, what do you see if you do "bzr missing" with a local copy against trunk?
[16:50] <nessita> abentley: running the command right now
[16:51] <nessita> abentley: http://pastebin.ubuntu.com/
[16:51] <nessita> oops
[16:51] <nessita> http://pastebin.ubuntu.com/487870/
[16:53] <abentley> nessita, it looks like<EMAIL_ADDRESS>had revno 627, merged 671, committed and pushed.
[16:54] <nessita> abentley: that's for revno 628 right?
[16:55] <abentley> nessita, yes.  But actually that was committed and pushed by tarmac?
[16:55] <nessita> abentley: we should avoid looking at thta revno, it landed when trunk was already messed up
[16:55] <nessita> abentley: yes, we mostly land branches using tarmac
[16:55] <nessita> abentley: see this: https://pastebin.canonical.com/36736/ is the output of
[16:55] <nessita>  bzr log -r627..671 --show-ids
[16:56] <nessita> abentley: as you can see, there are all the missing revnos
[16:57] <abentley> hmm.  So it seems like the new revno 628 does include everything up to 671, or else bzr missing would have shown more.
[16:58] <nessita> abentley: maybe, I can do a recursive diff to check
[16:58] <abentley> nessita, I'm not aware of any way the revisions can be accidentally removed from the timeline.  It should only happen if you uncommit or push --overwrite.
[17:00] <nessita> abentley: I see. Can we know if that actually happened? because as far as we know we haven't pushed with --overwrite
[17:00] <nessita> abentley: we're really worried about this, and it would be very important to understand what happened
[17:01] <abentley> nessita, no, our server doesn't know what command is being run when a branch is changed.
[17:01] <abentley> nessita, rick mcbride is subscribed to revision notifications, so he should have been emailed when this happened.  Looks like no one else is subscribed.
[17:02] <nessita> abentley: I'll ask him, thanks. Just to be sure I understand, is there any chance that today's maintenance had something to do with this?
[17:02] <nessita> abentley: we land all the branches using tarmac, except for tags that we push "by hand"
[17:03] <abentley> nessita, I can't think of a way that it would be implicated.
[17:03] <nessita> is very, very unlikely that someone ran push --overwrite :-/
[17:04] <nessita> abentley: anyways, thanks a lot for your help, I'll try to find more info from rmcbride
[17:14] <rmcbride> nessita: just got back from retrieving lunch. I'll dig through the rev notifications
[17:15] <nessita> rmcbride: thanks!
[17:23] <nessita> abentley: so, can we disable the ability to do push --overwrite to a given project? or can we log that somehow? or at least what can we do today to be able to debug it tomorrow?
[17:30] <nessita> abentley: still around?
[18:09] <lucidfox> What's the bzr equivalent of "git remote add origin"?
[18:11] <james_w`> lucidfox: it might be bzr pull --remember
[18:11] <james_w`> though I don't really know what the effect of that git command would be
[18:12] <dob_> hello, i created a new ppa and uploaded my sources, the upload was successful, even as i did not add my pgp key to my profile. Then i added my key and dput tells me: Package has already been uploaded to ppa on ppa.launchpad.net. But nothing happens, i am waiting for about an hour..... Any ideas?
[18:14] <james_w`> dob_: run with --force
[18:14] <dob_> upload was successful
[18:15] <dob_> how long will i have to wait for the status information in my repo?
[18:16] <dob_> ah okay
[18:16] <dob_> now i got a email
[18:16] <dob_> that it's accepted
[18:17] <lucidfox> james_w`> ah right, bzr help push clarified the matters
[18:17] <dob_> hi thank you very much
[18:17] <dob_> It's now in my repository
[18:24] <abentley> nessita, back.
[18:29] <nessita> abentley: hello again!
[18:30] <nessita> abentley: my team and I were wondering, can we disable the ability to do push --overwrite to a given project? or can we log that somehow? or at least what can we do today to be able to debug it tomorrow?
[18:31] <nessita> abentley: rmcbride received an email, this morning saying that "44 revisions were removed from the branch."
[18:31] <abentley> nessita, that suggests it was a user-driven change, not a bug in the hosting code.
[18:32] <abentley> nessita, I don't think you can disable push --overwrite.  bzr generally trusts its user.
[18:32] <abentley> nessita, since you already have a bot managing the branch, why not make the bot the only one who can write to it?
[18:33] <abentley> nessita, this is what we do in Launchpad.
[18:33] <nessita> abentley: yes, we'll try that. Biut we al
[18:33] <nessita> oops, wrong enter
[18:34] <nessita> abentley: but we also need some sort of logging... can we do that? at least for pushes --overwrite? or to what command was used to push?
[18:35] <abentley> nessita, there is logging on the user side that would show this.  On the server side, we deal with lower-level primitives.
[18:36] <abentley> nessita, e.g. we know that a branch has changed from one revision-id to another, not that push was issued.
[18:37] <abentley> nessita, and if sftp is used, we don't even know that.
[18:38] <nessita> abentley: ok then, thanks for your time
[18:40] <deryck> adeuring, you disappeared again
[18:41] <deryck> heh
[19:08] <EdwinGrubbs> does anybody know how long it will be before staging is up? It seems like it has been updating the code for the last four hours.
[19:45] <kirkland> just checking ... are you guys aware that the Google Maps API is busted?
[19:45] <kirkland> looks like the key is expired
[19:47] <deryck> hi kirkland.  yeah, we're aware.  Not sure what the state of our fix is, though I thought we had disabled the maps on edge now.
[19:50] <deryck> I think it's actually a change in Google's SSL support, not the key though.
[19:50] <deryck> sinzui knows all, I believe.
[19:52] <sinzui> I know nothing about a 10,000 SSL fee
[19:52] <sinzui> I am an engineer
[19:53] <deryck> heh
[20:43] <yofel> jelmer: anything needed for https://code.edge.launchpad.net/~neon/project-neon/ontologies to be approved? I'm not too familiar with setting up imports
[20:55] <jelmer> yofel, hi
[20:55] <jelmer> yofel, mainly for somebody in the vcs-imports team to approve the import
[20:56] <yofel> k, will wait then
[20:56] <jelmer> yofel: Looking at that import, I think it should be under the ontologies project on launchpad though
[20:56] <jelmer> rather than under project-neon
[20:57] <yofel> I don't think we have a project for that
[21:02] <smoser> how do i create a new spec (blueprint ) ?
[21:02] <smoser> i'm looking https://blueprints.launchpad.net/~smoser and i can't figure out how to add a new one.
[21:09] <annodomini> Is there a sample or sandbox project on Launchpad, that I could use for playing around with without spamming a real project?
[21:17] <smoser> i figured out my issue above.
[22:03] <popey> http://popey.com/~alan/aaaaaaargh.png etc
[22:03] <popey> trying to file a bug with apport on lucid, i get that.. is this a launchpad issue?
[22:03] <popey> (note: I can browser to lp on that machine fine)
[22:17] <lifeless> popey: that would appear to be a local issue; *or* something is buggered :P
[22:17] <lifeless> popey: can you see what name its trying to lookup (strace or something might help there)
[22:24] <popey> lifeless: http://popey.com/~alan/apport_trace.log
[22:25] <lifeless> popey: its firing off /usr/share/apport/apport-gtk
[22:26] <lifeless> you'll want follow-fork, and you can look in ityourself ;P
[22:26] <lifeless> just for for resolver calls
[22:26] <popey> message understood :D
[22:26]  * popey is not an strace expert
[22:26] <popey> thanks though :)
[22:28] <lifeless> popey: I have a few things to do here like checking for earthquake damage ;P
[22:28] <lifeless> or I would be willing to read through the MB's of data you'll be generating.
[22:29] <popey> fun!
[22:30] <lifeless> we're in rangiora http://www.geonet.org.nz/earthquake/quakes/3366241g-maps.html
[22:31] <lifeless> http://www.stuff.co.nz/the-press/news/4094979/Huge-earthquake-rocks-Christchurch
[23:28] <mlaci> hi guys! can i hope that the timeout error goes away from this page anytime soon? - https://launchpad.net/~chromium-daily/+archive/ppa/+packages?field.name_filter=&field.status_filter=&field.series_filter=
[23:50] <lifeless> mlaci: what OOPS ID did you get
[23:50] <lifeless> !oops


[08:00] <veger> Could someone set the importance of bug #469641 to Low (as there is an easy workaround: fill in a suitable log file location) and the status to Triaged?
[08:00] <ubot2> Launchpad bug 469641 in trac "trac broken after changing logging settings" [Undecided,New] https://launchpad.net/bugs/469641
[08:18] <rbasak> veger: done, thanks
[08:27] <veger> rbasak: ty
[15:20] <hggdh> when testing 973747
[15:47] <mfisch> bdmurray: is there a bug meeting today?
[15:48] <bdmurray> mfisch: yes, that sounds good
[16:12] <geoffreyvanwyk> Hi All!
[18:09] <mfisch> bdmurray: Are there requirements for maintaining membership in bug control?  The wiki is pretty light on details
[18:11] <bdmurray> mfisch: no there are not, members can self renew
[18:12] <mfisch> bdmurray: that was one of my questions for a meeting
[18:12] <bdmurray> questions can be asked any time!
[18:12] <mfisch> bdmurray: I was saving them up! ;)
[18:13] <mfisch> bdmurray: the other was wrt Triaged, should we be attempting to repro bugs before marking them as triaged?  I've been doing so when feasible
[18:13] <bdmurray> mfisch: yes, definitely
[18:14] <mfisch> bdmurray: but that's not a requirement IIRC
[18:14] <hggdh> it is
[18:15] <mfisch> it's required that we repro bugs before marking them triaged?  sometimes that's not possible
[18:15] <hggdh> it is a requirement that you cannot go triaged if you cannot reproduce (i.e., confirm) the bug
[18:16] <mfisch> for example a bug about grub timeouts when talking to an HP iLO over a serial console
[18:16] <mfisch> let me go re-read
[18:16] <hggdh> mfisch: look for the definition for 'confirmed'
[18:16] <mfisch> "Triaged" doesn't mention repro here: https://wiki.ubuntu.com/Bugs/Status
[18:17] <mfisch> hggdh: right that's the different between Confirmed and Triaged
[18:17] <mfisch> or do you consider Triaged a superset that includes Confirmed?
[18:17] <hggdh> if it is reproducible, it is confirmed. Triaged means no new action from the triager is necessary
[18:18] <hggdh> triaged is the end of triaging (i.e., the point where I take out the triager's hat, and put on the developer/maintainer's one)
[18:19] <hggdh> of course, sometimes you may not really need the confirmed status -- for example, when you *know* the problem is true
[18:19] <bdmurray> I think the question is must bugs be Confirmed before they can be Triaged and the answer is no
[18:19] <mfisch> exactly
[18:19] <hggdh> agree
[18:19] <bdmurray> so Triaged is not a subset of Confirmed
[18:20] <mfisch> if the bug contains enough info to be actionable etc it's triaged, even if I dont have an HP iLO to test grub with
[18:20] <bdmurray> correct
[18:20] <mfisch> bdmurray: last question, are the meetings weekly/monthly/randomly?
[18:21] <roadmr> randomly ftw :)
[18:21] <bdmurray> they should be weekly but there hasn't been much participation in them
[18:21] <bdmurray> so some have been skippd
[18:21] <mfisch> i've missed my share due to lunch ;)


[01:32] <Saviq> Yeah I think since we're interpeting it, we should be more vocal about it
[01:32] <alan_g[m]> That can be misleading when the client paints a title bar (with yet another "title")
[01:32] -GitHub[m]:#mir-server- **[MirServer/mir]** wmww drafted [pull request #2858](https://github.com/MirServer/mir/pull/2858): Implement XDG poup constraint adjustment support
[01:32] -GitHub[m]:#mir-server-
[01:32] -GitHub[m]:#mir-server- > Passes the test, but still doesn't work perfectly with gedit. Might be an issue in precedence order. Will take out of draft when I sort that out.
[01:32] <Saviq> Oh on that note, did I ask to print the surface titles as they come in? Did you get to it?
[01:32] <Saviq> As good as any, at least no interpretation needed. Only thing is maybe window-title would be more commonly known?
[01:32] <Saviq> Good night o/
[01:32] <alan_g[m]> I forgot that, but it is already optional (the window-management-trace shows it). But can do...
[01:32] <alan_g[m]> ...done
[01:32] -GitHub[m]:#mir-server- **[MirServer/mir]** wmww edited [pull request #2858](https://github.com/MirServer/mir/pull/2858): Implement XDG poup constraint adjustment support
[04:38]  * RAOF uploaded a video: (418KiB) < https://libera.ems.host/_matrix/media/v3/download/cooperteam.net/tYtPNSHfjZtQiNtWVsyYgocu/SlimAmusedCrocodile-mobile.mp4 >
[04:38] <RAOF> Today's status
[06:15] -GitHub[m]:#mir-server- **[MirServer/wlcs]** bors[bot] merged [pull request #276](https://github.com/MirServer/wlcs/pull/276): Test popup constraint_adjustment
[10:35] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** Saviq self-requested a review for [pull request #129](https://github.com/MirServer/ubuntu-frame/pull/129): Allow configuration to assign applications to outputs
[16:52] <Saviq> alan_g FYI: I'll take care of the CVE influx
[16:52] <alan_g[m]> Thank you. Forgot to mention that  earlier
[16:52] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** AlanGriffiths requested a review from Saviq for [pull request #129](https://github.com/MirServer/ubuntu-frame/pull/129): Allow configuration to assign applications to outputs
[16:52] <Saviq> alan_g for the gedit case, you mean? I didn't get the "re-titled" log, FWIW
[16:52] <alan_g[m]> Saviq surface-titles can and do change, that's yet another reason to avoid using them
[19:21] <Saviq> Oh fudge. No hook is called after an interface disconnection. And since we're greedy, a disconnect hook doesn't mean there's no other slot is connected.
[19:21] -GitHub[m]:#mir-server- **[MirServer/mir]** wmww marked [pull request #2858](https://github.com/MirServer/mir/pull/2858): Implement XDG poup constraint adjustment support as ready for review
[19:21] <Saviq> This puts quite a stick in our spokes
[19:21] <Saviq> I've to go o/


[05:13] <rcsheets> is it just me, or is the wiki really slow?
[05:14] <rcsheets> hmm, wound up with a 502 proxy error. i'm guessing it's not just me.
[15:40] <newz2000> cjohnston: I'm sorry I missed you, I was quite sick last week and over the weekend.
[15:41] <newz2000> I've got a few meetings but otherwise you've got my full attention if you need me still
[17:28] <cjohnston> hey newz2000
[17:59] <newz2000> hey cjohnston
[18:19] <cjohnston> feeling better?
[18:53] <cjohnston> newz2000: bug 510303 - is the ubuntu counter run by ubuntu/something that ubuntu/canonical wants to promote?
[18:54] <cjohnston> what happened to the bug bot again?
[18:56] <cjohnston> https://bugs.edge.launchpad.net/ubuntu-website/+bug/509217 - is that to save BW or something? otherwise i would tend to agree
[19:10]  * newz2000 checks
[19:12] <newz2000> Hmm… I'm really not sure who manages that nor what the reasoning for the auth is. Maybe it's to reduce it's use for spamming
[19:12] <newz2000> oh, I know who made that
[19:13] <cjohnston> https://bugs.edge.launchpad.net/ubuntu-website/+bug/510303
[19:14] <cjohnston> was the other one
[19:14] <cjohnston> since mr. bug bot isnt here
[19:14] <newz2000> cjohnston: I'm not sure what project it should be associated with but I've assigned it to the canonical sysadmins
[19:14] <newz2000> they manage that
[19:14] <newz2000> I don't think I'm going to link to that counter from any official Ubuntu webpage
[19:14]  * newz2000 checks before making final judgement though
[19:15] <cjohnston> thats my opinion too
[19:15] <cjohnston> fwiw, best i can tell, all of the bugs that are still new, you are going to have to look at..
[19:15] <newz2000> I'll update it
[19:15] <newz2000> ok
[19:15] <cjohnston> i dont have enough knowledge to determine anything about them
[19:16] <cjohnston> next im gonna start going through confirmed and see what is still valid
[19:17] <cjohnston> did you ever look at https://bugs.edge.launchpad.net/ubuntu-website/+bug/106056 to see if its still valid?
[19:17] <newz2000> that is still valid and should be pretty easily fixed actually
[19:17] <newz2000> the about page is probably the bst place for it
[19:17] <cjohnston> k
[19:18] <cjohnston> starting by looking at high priority.. as.. well.. they are high priority
[19:18] <cjohnston> lol


[17:15] <xubuntu99i> hi folx. I'm  about to rock rock the new Xubuntu 23.04. I went for a minimal install, as I prefer not to have bloatware.  The next version, they introduce a new setting or "feature", etc.
[22:46] <gnrp> I don't know, but I'd guess that the connectivity check to mozilla cannot be easily switched off without re-compiling?


[01:59] <akgraner> jussi, ping
[02:20] <akgraner> I'm starting a new drinking game - every time jono uses the word "keen" in any form you have to take a shot...
[02:20] <akgraner> the whole community will be drunk in no time flat
[07:13]  * AlanBell likes akgraner's plan
[09:31] <nigelb> akgraner: haha
[09:34] <czajkowski> same goes for jcastro and AWESOME
[12:34] <akgraner> czajkowski, yep /me adds jcastro and awesome to the list as well
[13:43] <jussi> akgraner: pong (and how are we supposed to get things done when we are drunk as skunks?)
[15:32] <akgraner> jussi pong
[15:32] <akgraner> :-)
[15:39] <jussi> akgraner: o/
[15:39] <akgraner> hey
[15:40] <akgraner> jussi, you back home?
[15:40] <jussi> akgraner: not yet, about 600k to go and my flight is delayed!!
[15:40] <jussi> *shakes fist*
[15:40] <akgraner> :-(
[15:41] <jussi> akgraner: but almost home
[15:41] <akgraner> oh good
[15:41] <jussi> and much better to happen in helsinki than CDG (that airport is hell)
[15:55] <akgraner> you know I am just glad no one has to drink when I say y'all....we would all be hurting
[15:57] <jussi> hahah
[15:57] <jussi> I should so suggest that... :P
[15:58] <nigelb> actually, we should have a drink when someone pronounced jussi name wrong.
[15:58] <nigelb> *pronounces
[15:58] <akgraner> hahaha
[15:59] <jussi> nigelb: youll get alcohol poisoning...
[16:00] <nigelb> jussi: haha
[16:00] <nigelb> jussi: same for me as well.
[16:01] <nigelb> I listen to about 5 different variations of pronounciation because people get my name wrong *all* the time.
[16:02] <AlanBell> spd-say -l fi jussi
[16:03] <nigelb> hahahhahaha
[16:03] <jussi> AlanBell: hrm, might have to install spd-say just to see how that sounds :P
[16:03] <AlanBell> spd-say -l pl czajkowski
[16:03] <jussi> hahahah
[16:03] <nigelb> its probably installed by default
[16:03] <AlanBell> jussi: it is default
[16:03] <jussi> AlanBell: nigelb: in kubuntu?
[16:03] <nigelb> *maybe*
[16:03] <AlanBell> oh, default on the *real* ubuntu :p
[16:03] <nigelb> hahahaha
[16:03] <jussi> wot?
[16:04] <mhall119> how do people get "nigel" wrong?
[16:04] <AlanBell> might be there in kubuntu
[16:04] <jussi> :P
[16:04] <nigelb> mhall119: maco was suprised about that as well.
[16:04] <nigelb> A lot of people pronounce the g, like "go" instead of like "gel"
[16:04] <mhall119> who gets it wrong, westerners or indians?
[16:04] <AlanBell> spd-say -l in nigel
[16:04] <nigelb> indians
[16:04] <nigelb> westerners *always* get my name right :)
[16:05] <mhall119> ok, well I can see that, it is a very british name
[16:05] <nigelb> except for the last name.
[16:05] <mhall119> that's still not a complicated one
[16:06] <nigelb> true
[16:06] <mhall119> I mean, as far as Indian last names go, that's about as simple as they come
[16:06] <nigelb> heh, truue
[16:07] <AlanBell> spd-say is the command line interface to speech dispatcher, by default it uses the espeak synthesiser, but you can swap in other speech engines
[16:07] <jussi> but the a could have several different sounds, as could the u...
[18:03] <popey> indian dude who sits next to me calls me "poppy", malasian woman who sits behind me calls me "pop-eye" (with a delay), everyone else calls me popey. (poh-pee)
[18:09] <czajkowski> popey: nobody calls you alan at work eh :)
[18:15] <mhall119> who's alan?
[18:23]  * pleia2 points to AlanBell
[18:33] <popey> czajkowski: nope
[18:35] <czajkowski> it;s odd how my name changes depending on what group I'm in, my close uni mates call me Laurs, work Laura oss folks who can say my name say czajkowski or Laura Cz
[18:36] <AlanBell> I call my sister Laura "Lowly Worm"
[18:37] <czajkowski> always amazed when cjwatson comments on my blog that he's taken the time to read a post
[18:37] <czajkowski> ot that I don't hold popey in the same esteme
[18:37] <czajkowski> :)
[18:37] <czajkowski> AlanBell: one of my mates in dublin used to attempt to call me la la he used to get a punch when he did that
[18:39] <AlanBell> lolo?
[18:39] <czajkowski> *smack*
[18:40] <AlanBell> I will save that one for my little sister then
[18:40] <AlanBell> who is older than you :)
[18:40]  * czajkowski is getting older soon
[18:40] <czajkowski> :/
[18:40]  * pleia2 is getting older sooner
[18:41] <czajkowski> pleia2: date?
[18:41] <pleia2> 29th
[18:41] <czajkowski> sept?
[18:41]  * popey is 40 next year ⍨
[18:41]  * Pendulum is getting older after pleia2, but before czajkowski
[18:41] <pleia2> czajkowski: yeah
[18:41] <popey> thinking of having a big party
[18:41] <czajkowski> pleia2: yeah I still find this hard to believe
[18:41] <pleia2> I turn 30!
[18:41] <czajkowski> pleia2: piss off
[18:41] <czajkowski> ;)
[18:41]  * AlanBell will get popey a pipe and slippers
[18:41] <czajkowski> popey: neither looks nor acts his age
[18:41] <popey> :p
[18:41] <pleia2> it meant I couldn't qualify for the "young professonals" rate at my new gym, I was very sad
[18:42]  * czajkowski hugs pleia2
[18:42]  * pleia2 hugs
[18:42] <pleia2> I don't actually mind getting older, that was a bummer though :)
[18:42]  * czajkowski is reading up on disc surgery
[18:42] <czajkowski> pleia2: tbh neither do I, but I hate fuss of it
[18:43] <czajkowski> as in the mothership just phoned asking was I flying home fo rthe weekend
[18:43] <czajkowski> hadn't any plans, she sounds as upset now as when I told her I was fecking off to canada for my 30th
[18:43] <pleia2> heh, the weekend following my birthday I'm going to a memorial service :(
[18:43] <pleia2> thursday birthday, friday I get on a plane
[18:44] <pleia2> no big 30th birthday bash for me
[18:45] <pleia2> but at least I'll get to see some family I haven't seen in a while :)
[19:08]  * Pendulum hugs pleia2
[19:08]  * pleia2 hugs
[19:14] <Pendulum> I just found the Department of Labor guidelines for unpaid internships in the US. I'm starting to think most unpaid internships are actually illegal...
[19:22] <mhall119> I'm pretty sure they're all immoral
[19:31] <czajkowski> hey at home in ireland you should see slave.ie


[00:38] <RAOF> blackboxsw: The curtin update appears to add a new dependency on probert?
[00:38] <RAOF> blackboxsw: ...which is in Universe, so you'll need to get that into Main before we could release the SRU?
[09:27] -queuebot:#ubuntu-release- Unapproved: u-boot (xenial-proposed/main) [2016.01+dfsg1-2ubuntu4 => 2016.01+dfsg1-2ubuntu5] (desktop-core, ubuntu-server)
[09:31] <apw> ^ intended as a fix for the u-boot in xenial-proposed
[09:40] -queuebot:#ubuntu-release- Unapproved: glib-networking (disco-proposed/main) [2.60.1-1 => 2.60.3-1~ubuntu19.04.1] (ubuntu-desktop)
[09:41] -queuebot:#ubuntu-release- Unapproved: glib2.0 (disco-proposed/main) [2.60.0-1ubuntu0.1 => 2.60.4-0ubuntu<IP_ADDRESS>] (core)
[09:41] <rbasak> apw: by fixed in later versions, do you mean that you've confirmed that "return ret" is present in the newer series including the development release?
[09:43] <rbasak> apw: if so, then +1 for your u-boot one line quilt patch upload - do you want me to accept?
[09:43] <apw> rbasak, exactly that, i traced it to making that change, then confirmed that the next series version was fixed in that way already
[09:44] <apw> rbasak, yes please
[09:44] <rbasak> done
[09:45] -queuebot:#ubuntu-release- Unapproved: accepted u-boot [source] (xenial-proposed) [2016.01+dfsg1-2ubuntu5]
[09:46] <apw> rbasak, thanks
[10:00] -queuebot:#ubuntu-release- Unapproved: vaultlocker (bionic-backports/universe) [1.0.3-0ubuntu1~ubuntu18.04.1 => 1.0.3-0ubuntu<IP_ADDRESS>~ubuntu18.04.1] (no packageset)
[10:01] <jibel> cking, Hi, do you plan to fix the failing tests of zfs-linux 0.7.12-1ubuntu6 / spl-linux 0.7.12-1ubuntu4. It seems that they must depend on each other to build.
[10:03] <cking> jibel, yep, i keep on getting distracted by other issues, I will get around to it today
[10:03] <jibel> cking, thanks
[10:09] -queuebot:#ubuntu-release- Unapproved: ceph (bionic-proposed/main) [12.2.11-0ubuntu<IP_ADDRESS> => 12.2.12-0ubuntu<IP_ADDRESS>] (desktop-core, ubuntu-server)
[10:54] <cking> https://appletonwildlifediary.wordpress.com/
[10:55] <cking> oops, that was not meant to be pasted there
[10:58] <jamespage> vorlon: hey - did you have any feedback on the binary packaging changes for https://launchpad.net/ubuntu/+source/ceph/14.2.1-0ubuntu1 ?
[10:58] <jamespage> the one that cast doubt in my mind was the libradospp-dev package - trying to get to the bottom of why upstream ceph thought that was needed
[10:59] <jamespage> cking: nice post all the same - love a bee orchid :-)
[10:59] <cking> ah, serendipity
[13:31] <coreycb> hello, can an archive admin please remove the binary package for python-oslo.log 3.44.0-0ubuntu2 from eoan-proposed? this was partially done yesterday i think but it seems the binary is still there.
[13:32] <coreycb> python3-oslo.log is the binary
[13:34] <cjwatson> It is not still there
[13:34] <cjwatson> Where are you seeing it?
[13:35] <cjwatson> "rmadison -s eoan,eoan-proposed -S python-oslo.log" does not show it, and https://launchpad.net/ubuntu/eoan/amd64/python3-oslo.log shows that binary as deleted
[13:37] <jamespage> coreycb: I guess you hit rebuild again :)
[13:38] <cjwatson> I hit retry on https://launchpad.net/ubuntu/+source/python-oslo.log/3.44.0-0ubuntu3/+build/16934603 to make sure I'm looking at something current
[13:39] <jamespage> ah right-oh
[13:40] <cjwatson> That built
[13:41] <cjwatson> I didn't make a careful note of the time before retrying, but buildd-manager logs say nobody had retried it since the removal
[13:42] <xnox> rbasak:  do you have capacity to process an openssl sru for bionic to fix up the 1.1.1 landing.
[13:42] <rbasak> xnox: I suspect that's non-trivial? If so, sorry, I don't this week (and probably not next week).
[13:43] <rbasak> I'm a bit behind on things I'd like to have finished two weeks ago, and am blocking people :-/
[13:43] <xnox> rbasak:  it actually is a trivial diff.
[13:43] <coreycb> jamespage: nope
[13:43] <rbasak> xnox: but does that make it a trivial review? :)
[13:43] <coreycb> jamespage: ah you got a response
[13:44] <coreycb> jamespage: well that was easy :)
[13:44] <xnox> rbasak:  https://paste.ubuntu.com/p/56WzxXCSnt/ the bit that are slightly more time sensitive is the postinst ;-)
[13:44] <xnox> rbasak:  there is more comments then code changes? =)
[13:45] <xnox> rbasak:  basically we forgot to restart services upon upgrade from 1.1.0 to 1.1.1 and we must do that....
[13:47] <rbasak> xnox: for me that's a non-trivial review, sorry. It'll take me time to understand the context.
[13:50] <coreycb> cjwatson: thanks and sorry for the noise. i assumed the new python-oslo.log was uploaded this morning.
[13:55] <xnox> rbasak:  ack
[14:45] -queuebot:#ubuntu-release- Unapproved: fetchmail (bionic-proposed/main) [6.3.26-3build1 => 6.3.26-3ubuntu0.1~18.04.1] (ubuntu-server)
[14:47] -queuebot:#ubuntu-release- Unapproved: accepted fetchmail [source] (bionic-proposed) [6.3.26-3ubuntu0.1~18.04.1]
[14:58] <vorlon> jamespage: sorry, infinity had asked about the ceph binaries and I said I hadn't gone far enough to be holding a lock on the review, I thought he was going to take a look
[15:08] <xnox> vorlon:  can you please review this openssl bionic SRU hotfix? https://paste.ubuntu.com/p/FxNnWp2d4F/    it has a regression fix, a low CVE, and an upgrade maintainer script to actually trigger restarting services......
[15:08] <xnox> (the last bit makes many things not-worky until restarted, or the machine reboots)
[15:10] -queuebot:#ubuntu-release- Unapproved: openssl (bionic-proposed/main) [1.1.1-1ubuntu2.1~18.04.1 => 1.1.1-1ubuntu2.1~18.04.2] (core) (sync)
[15:11] -queuebot:#ubuntu-release- Unapproved: openssl (disco-proposed/main) [1.1.1b-1ubuntu2.1 => 1.1.1b-1ubuntu2.2] (core) (sync)
[15:11] -queuebot:#ubuntu-release- Unapproved: openssl (cosmic-proposed/main) [1.1.1-1ubuntu2.2 => 1.1.1-1ubuntu2.3] (core) (sync)
[15:11] <xnox> vorlon:  the srus for other releases do not have maintainer script thing, as well, not needed / too late.
[15:12] <xnox> vorlon:  and they are syncs, because built in security pocket, to be copyable into -security as requested by the security team.
[15:29] <vorlon> xnox: I don't love seeing adjustments to the behavior of the service-checking code in an SRU hotfix...
[15:29] <xnox> vorlon:  i can get away with just changing the version numbers in those hunks.
[15:30] <vorlon> xnox: that would reduce friction
[15:30] <xnox> vorlon:  meaning only services that still have matching initd scripts will be restarted by invoke-rc.d => which should be true for most/all the ones listed.
[15:30] <xnox> vorlon:  what about the other two patches cherrypicked from upstream. Are those ok, or not?
[15:31]  * xnox prepares reupload.
[15:31] <vorlon> xnox: ah, because we do a literal check for /etc/init.d/foo there... hmm
[15:31] <vorlon> so rbalint was right ;)
[15:32]  * vorlon checks to see if this is still buggy in libpam
[15:33] <xnox> vorlon:  and invoke-rc.d internally redirects to systemctl. Thus the right thing to check is with systemctl is-active => cause only those will be restartable.....
[15:34] <xnox> i can quickly pull all of the packages mentioned, to double check that they still ship init.d/ scripts or not.
[15:37] <vorlon> xnox: yeah considering we've never agreed to drop init scripts and it's still required by Debian policy, I think we should just go with the version-check-only change for now
[15:37] <xnox> vorlon:  uploading
[15:40] <xnox> vorlon:  please reject the current sync then.
[15:40] <vorlon> ack
[15:40] <xnox> (the bionic one only)
[15:41] <vorlon> done
[15:42] -queuebot:#ubuntu-release- Unapproved: rejected openssl [sync] (bionic-proposed) [1.1.1-1ubuntu2.1~18.04.2]
[16:25] -queuebot:#ubuntu-release- Unapproved: openssl (bionic-proposed/main) [1.1.1-1ubuntu2.1~18.04.1 => 1.1.1-1ubuntu2.1~18.04.2] (core) (sync)
[16:26] <xnox> vorlon:  updated sru ^
[16:53] <vorlon> xnox: test case on LP: #1828215 appears to depend on files not included in the test case, where should they be sourced?  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1828215/comments/6 ?
[16:53] <xnox> vorlon:  in the comments of the bug.
[16:54] <vorlon> xnox: can you please extract that into a recipe in the description that can be followed without reference to the comments
[16:54] <xnox> vorlon:  i.e. it is just /etc/ssl/openssl.cnf with more stanzas added to them.
[16:54] <vorlon> and without "assumes you've already generated a CA key" which most SRU testers aren't going to have just lying around
[16:54] -queuebot:#ubuntu-release- Unapproved: erlang (bionic-proposed/main) [1:20.2.2+dfsg-1ubuntu2 => 1:20.2.2+dfsg-1ubuntu2.1] (ubuntu-desktop, ubuntu-server)
[17:10] <xnox> vorlon:  updated will all step by step instructions from scratch. creates CA, creates CA key, creates cert request, spkac request, and signs it
[17:11] <xnox> could be made more non-interactive, and quicker, but this is all step by step and works. just redid it from scratch in a chroot.
[17:11] <vorlon> xnox: thank you
[17:12] <vorlon> xnox: unrelated, any idea why the apache2 autopkgtests broke again? they were broken for a while by libfoo-ssl-perl, now they're broken differently
[17:13] -queuebot:#ubuntu-release- Unapproved: accepted openssl [sync] (bionic-proposed) [1.1.1-1ubuntu2.1~18.04.2]
[17:14] <xnox> vorlon:  in which releases? they are a bit fragile and i was monitoring it.... it's only arm64 at the moment, no?
[17:14] <xnox> (in eoan, unless you mean some other release)
[17:50] <vorlon> xnox: arm64/eoan yes
[17:59] <vorlon> infinity: I notice that the Debian release team has announced a buster target release date of July 6; and eoan DIF is set to August 22.  Should we consider moving up DIF to match buster release, so we don't import the first month's worth of crazy from unstable?
[18:18] <cjwatson> Better get it in eoan than in F, IMO
[18:19] <cjwatson> I'm sure there'll be some new upstreams and such that we want to have in 20.04 and where it'd be better for them to have a cycle to shake out
[18:19] <cjwatson> ICBW
[18:39] <xnox> vorlon:  both openssl bugs verified; i guess wait for autopkgtests results and release?
[18:39] <xnox> (autopkgtests to confirm it's not a complete toast)
[18:47] <vorlon> cjwatson: fair point, if we're going to get a logjam it may be better to have it sooner
[19:36] -queuebot:#ubuntu-release- Unapproved: accepted openssl [sync] (cosmic-proposed) [1.1.1-1ubuntu2.3]
[19:39] <vorlon> xnox: to be clear, this SRU is slated to be released to -security and that's why there's a CVE ref with no bug #, right?
[19:40] -queuebot:#ubuntu-release- Unapproved: accepted openssl [sync] (disco-proposed) [1.1.1b-1ubuntu2.2]
[20:54] <juliank> vorlon: I think we should probably look at experimental now and start merging from there if possible to reduce a jam
[20:54] <juliank> Also, is anything crazy going on that would interfere with an apt ABI+API break?
[20:55] <juliank> I guess I'll do rebuilds in PPA first
[20:55] <juliank> but still
[20:56] <juliank> I don't think I see anything
[20:56] <vorlon> juliank: I consider merging from experimental something to only be done if the merger is making a committment to field bugs in lieu of the Debian maintainer if that version doesn't make it to unstable before the next Ubuntu release
[20:56] <juliank> Well, I guess if you know that they're planning to upload to unstable
[20:57] -queuebot:#ubuntu-release- Unapproved: scilab (disco-updates/universe) [6.0.2-0ubuntu1 => 6.0.2-0ubuntu2~19.04] (no packageset) (sync)
[20:59] <juliank> Oh I guess I'll just add an apt transition tracker for planned transitions to make sure I get a good overview?
[21:00] <juliank> like bad is libapt-pkg5.0|libapt-inst2.0, good is libapt-pkg5.90
[21:00] <juliank> but with proper quoting
[21:00] <juliank> or rather escaping
[21:05] -queuebot:#ubuntu-release- Unapproved: scilab (cosmic-updates/universe) [6.0.1-7ubuntu1~18.10 => 6.0.1-7ubuntu1~18.10.1] (no packageset) (sync)
[21:06] <juliank> This seems about right: https://paste.ubuntu.com/p/3mqHtv7Nc5/
[21:06] <juliank> Note that we're dropping libapt-inst, as it's folded into libapt-pkg
[21:06] <juliank> (and the combined library is smaller than an older libapt-pkg thanks to removal of deprecated code :D)
[21:07] <vorlon> in which case the last regexp can be shortened to /libapt-pkg5\.0|libapt-inst/
[21:07] <juliank> true
[21:07] <vorlon> and don't forget your \b around words
[21:07] -queuebot:#ubuntu-release- Unapproved: scilab (bionic-updates/universe) [6.0.1-7ubuntu1~18.04 => 6.0.1-7ubuntu1~18.04.1] (no packageset) (sync)
[21:07] <vorlon> (maybe not necessary in this case, but we have a history of overbroad regexps in the tracker)
[21:07] <juliank> it's fine here
[21:08] <vorlon> yes but it sets a bad example for others who cargo-cult you later ;)
[21:08] <juliank> vorlon: Is .depends ~ /\b(libapt-pkg5\.90)\b/ equivalent to .depends ~ "libapt-pkg5.90"?
[21:09] <vorlon> does the tracker support a non-regexp form?  I'm not familiar with that
[21:09] <juliank> there are some examples in there that use it
[21:10] <juliank> but I'm not sure if it's whole words
[21:12] <juliank> with \b and shortened a bit, I have https://paste.ubuntu.com/p/nKGGS4Yyz8/
[21:13] <juliank> hmm, why do I have () in is_good, not necessary there
[21:14] -queuebot:#ubuntu-release- Unapproved: scilab (disco-proposed/universe) [6.0.2-0ubuntu1 => 6.0.2-0ubuntu2~19.04] (no packageset) (sync)
[21:15] -queuebot:#ubuntu-release- Unapproved: scilab (bionic-proposed/universe) [6.0.1-7ubuntu1~18.04 => 6.0.1-7ubuntu1~18.04.1] (no packageset) (sync)
[21:15] -queuebot:#ubuntu-release- Unapproved: scilab (cosmic-proposed/universe) [6.0.1-7ubuntu1~18.10 => 6.0.1-7ubuntu1~18.10.1] (no packageset) (sync)
[21:22] <cjwatson> AFAICS, ben implements ~ "..." by splitting the string on |, regex-quoting each piece, joining with | again, and then matching using /\b(%s)\b/
[21:22] <cjwatson> Also damnit you made me try to read ocaml
[21:23] <juliank> cjwatson: heh
[21:23] <juliank> I quite like ocaml
[21:23] <juliank> Not that I've ever used it
[21:23] <cjwatson> You can work out any remaining fine details then :)
[21:24] <juliank> but I did provide like two patches or so
[21:24] <juliank> for edos something I think
[21:24] <juliank> but really never had the chance to actually invest more like a few mins in it, or compile any ocaml program
[21:25]  * juliank committed the regex version fwiw, with the  \b added in the useful places
[21:25] <juliank> But I'm going to sleep, so I hope I did not break it
[21:26] <cjwatson> I'm pretty sure the answer to your equivalence question is yes BTW, in case that wasn't clear from what I wrote
[21:26] <juliank> it was perfectly clear
[21:26] <cjwatson> Good
[21:31] <bdmurray> tjaalton: Could address https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1740894/comments/42 since you changed the tag from failed to done?
[21:54] <tdaitx> I mistankenly uploaded scilab to bionic/cosmic/disco -updates (should have been -proposed, which I did shortly after), could someone please take care of rejecting the ones for -updates?
[21:56] <tdaitx> s/uploaded/copied/
[23:10] -queuebot:#ubuntu-release- New binary: utf8.h [amd64] (eoan-proposed/none) [0~git20190120.2a7c5bf-1] (no packageset)


[20:27] <diverse_izzue> where can i find them in the filesystem?
[20:27] <mac_v> diverse_izzue: weather and the rest are supposed to be desaturated by a tweak in the notification area , DBO , has an idea , but the design team hasnt made a decision
[20:28] <mac_v> diverse_izzue: find which , the bluetooth icon or all icons?
[20:28] <mac_v> humanity icons*
[20:28] <diverse_izzue> just found them
[20:28] <diverse_izzue> all tray icons
[20:29] <mac_v> hmm.. will get cracking on the bluetooth icon ;)
[20:30] <diverse_izzue> anyway, i have some criticism for the design. i find them relatively hard to see/read. that's true for: indicator-applet, batter, wireless network (maybe others that i don't see now)
[20:30] <diverse_izzue> in detail:
[20:30] <diverse_izzue> generally, i find the grey used too light
[20:30] <diverse_izzue> also, they should be more stylised, simplified. for example, the battery contact plus pole: could be filled. also why is the battery shaded and has a 1px space inbetween?
[20:31] <diverse_izzue> the wireless could do with thicker bars and drop the antenna
[20:31] <diverse_izzue> the envelope in the indicator-applet should be more saturated, it's hard to see now
[20:32] <mac_v> diverse_izzue: thats the best we can achieve for both light and dark panels , since the notification area isnt tweaked out , for now... any darker the icons will be lost in dark panels... any lighter the icons will be lost in light panels... :(
[20:33] <mac_v> diverse_izzue: since its in the default install , it has to be at minimum visible in *all* the default themes
[20:33] <diverse_izzue> mac_v, can't we just say, whoever wants to use the humanity theme needs to have a bright panel background? that is after all the default
[20:34] <mac_v> diverse_izzue: wish we could ;)
[20:34] <tgpraveen1> diverse_izzue: that will lead to many sad users and bugs being filed
[20:35] <diverse_izzue> tgpraveen1, i have a feeling that will happen as they are now as well
[20:35] <Amaranth> I think the biggest issue with the notification area icons is there isn't a gray icon for bluetooth
[20:35] <mac_v> diverse_izzue: yeah , i already expect ...there will definately be more bugs regarding this than the update notifier removal ;)
[20:36] <mac_v> Amaranth: i forgot that one ;p [/me dont use bluetooth]
[20:36] <Amaranth> most laptops have bluetooth so they're going to have this nice gray row of icons then *bam* bright blue
[20:36] <Amaranth> before they even start a program :)
[20:36] <diverse_izzue> there's more: transmission. ibus and scim.
[20:36] <Amaranth> diverse_izzue: But those aren't running by default
[20:37] <diverse_izzue> but at least transmission is installed by default
[20:37] <Amaranth> diverse_izzue: so are the other two
[20:37] <diverse_izzue> and for many users outside the western world, some IME will be installed as well
[20:37] <mac_v> diverse_izzue: we have made it a point not to do icons for any apps , then the list will be endless... as i said ... the notification area needs to be tweaked
[20:38] <Amaranth> mac_v: knotificationitem would let you just apply a filter on all the icons :)
[20:38] <diverse_izzue> you think it's possible to programmatically desaturate icons with the result looking good?
[20:38] <tgpraveen1> mac_v: hmm not doing icons for apps
[20:38] <diverse_izzue> i have my doubts...
[20:38] <Amaranth> diverse_izzue: Not when we have no control over the icons in the notification area
[20:38] <mac_v> diverse_izzue: its already done in UNR , for the window list
[20:38] <diverse_izzue> mac_v, is there a screenie of that somehwere?
[20:38] <tgpraveen1> is going to cause some problems as well. eg most music players eg rhythmbox, banshee minimze to tray as a default setup and it will look out of
[20:38] <tgpraveen1> place
[20:39] <Amaranth> diverse_izzue: There are corner cases that screw up but most work fine
[20:40] <mac_v> diverse_izzue: also another issue is , these icons will be used in the apps too! to do it properly , the theme needs to be tweaked... there is a whole bunch of issues , but the design team said nevermind ;)
[20:41] <diverse_izzue> sorry for being a bit negative about this, but while i agree with the whole thing in principle, i would rather opt to leave it as it was until a clean and professional looking solution is found for *all* icons. as it is (a mix of b/w and colour and somewhat amateurish drawing) i'd rather it was reverted.
[20:41] <mac_v> diverse_izzue: tgpraveen1: also we are not allowed to do app icons in the default theme , the icons we had were removed
[20:43] <mac_v> diverse_izzue: all , already we tried to raise these issues... but were told to just do it ... but think of it this way only the system icons are desaturated , while the apps will have color ;) ...
[20:44] <tgpraveen1> mac_v: hmm maybe having screenshiots wit combinations of some apps icons and humanity tray icons would
[20:45] <tgpraveen1> give better clarity into the issue
[20:45] <tgpraveen1> mac_v: are you on any planet ? if so it would be great if yoy could do a blog ;post with some combination./permutation
[20:45] <mac_v> tgpraveen1: we are thinking of tweaking out the notification area itself to not show color ,
[20:46]  * mac_v hates blog ;p
[20:46] <tgpraveen1> showing onlhy desaturated icon,showing app icon+destrate etc
[20:46] <tgpraveen1> mac_v: hmm wasnt the artwork deadline today?
[20:46]  * diverse_izzue is afraid that what results will be an imitation of OS X at half the quality...
[20:47] <tgpraveen1> also i would actually support removing colour maybe though it does seem somewhat controversial and diverse_izzue raises a good point
[20:47] <tgpraveen1> instead of having half colour half desaturated icons
[20:48] <tgpraveen1> mac_v: can you point me to some screenshots of desktops usng the new humanity theme with the default tray icons etc
[20:48] <diverse_izzue> really, i'm no mac fanboy, but look at this screenshot for example: http://blandname.com/wp-content/uploads/2006/09/mac-os-x-1047-server-screenshot.png
[20:48] <tgpraveen1> maybe a screenshot of ur desktop as am on my win laptop right now
[20:48] <diverse_izzue> this is *much* easier to see
[20:49] <zniavre> !gdm
[20:49] <zniavre> !gdm2
[20:49] <mac_v> tgpraveen1: my system is too tweaked out , not default but any sense ;)
[20:50]  * tgpraveen1 too feels having desturated icons only gives a osx ripoff feel
[20:52] <bullgard4> Firefox 3.5.3 in Ubuntu 9.10 shows blurred fonts. The procedure outlined in http://klo-2k.spaces.live.com/blog/cns!2872308BEB65CA67!716.entry does not help. How to obtain crisp fonts?
[20:53] <shakall691> Failure : AppArmor profiles failed to load. what to do next ?
[20:56] <diverse_izzue> bullgard4, they look quite crisp for me. which fonts are you using? do fonts look ok in other apps?
[20:58]  * mac_v > reboots
[20:59] <SeekerNL> can someone help me why in systemmonitor is only showing up 2,9 gb but I have 4gb and I am using amd64 release
[21:00] <SeekerNL> Linux Seeker 2.6.31-10-generic #34-Ubuntu SMP Wed Sep 16 01:09:15 UTC 2009 x86_64 GNU/Linux
[21:00] <wekt> SeekerNL: Linux can be configured at compile time to only work with up to 3GB.  maybe that is why.
[21:01] <SeekerNL> strange I am really using amd64 I know my gpu takes 512
[21:01] <diverse_izzue> wekt, even the 64 bit release?
[21:01] <guntbert> wekt: do you expect the default ubuntu kernel to be configured this way?
[21:02] <wekt> diverse_izzue: that would be unusual & unlikely.
[21:02] <wekt> certainly i expect the 64 bit release to not be configured that way.  but i don't know.
[21:02] <kklimonda> SeekerNL, may be a bios issue. have it worked fine in jaunty? also check dmesg from bootup for any suspicious messages
[21:02] <SeekerNL> does somone know how much 4gb memory is in software?
[21:02] <wekt> i also do not know how to check at run time.  or maybe i do know.  i hav an idea
[21:03] <Dai> 4GB?
[21:03] <SeekerNL> kklimonda its brandnew pc, info which comes which motherboard says support up to 8 gb, I putted 4 in
[21:04] <SeekerNL> my bios shows clearly 4
[21:05] <wekt> The answer for kernel configuration is in /boot/config*
[21:05] <SeekerNL> going look into it
[21:06] <SeekerNL> quite a hassle a nvidia
[21:07] <SeekerNL> http://paste.ubuntu.com/277376/  the config file
[21:07] <SeekerNL> which line do I need to search?
[21:16] <shang> hi all, how do I apply this patch ( http://bugzilla-attachments.gnome.org/attachment.cgi?id=143915 ) to totem-pl-parser??
[21:17] <mostafa_> any body knows how to auto power on the computer ?
[21:18] <sunshinepants> mostafa_: wake on lan?
[21:18] <sunshinepants> mostafa_: you can get really fancy and use an appliance timer
[21:19] <mostafa_> sunshinepants: what was that
[21:19] <mostafa_> ?
[21:19] <mostafa_> ?
[21:19] <sunshinepants> mostafa_: appliance timer http://www.google.com/search?q=appliance+timer&ie=utf-8&oe=utf-8&aq=t&rls=com.ubuntu:en-US:official&client=firefox-a
[21:20] <sunshinepants> mostafa_: wake on lan: http://ubuntuforums.org/showthread.php?t=234588
[21:23] <mostafa_> sunshinepants: thanks for that another question
[21:24]  * sunshinepants taps foot
[21:24] <mostafa_> sunshinepants: I wanna write a shell script that opens a program as root but I want to do it automaticly
[21:25] <mostafa_> sunshinepants: what should I do?
[21:25] <mrmcq2u_> does anyone else's network manager crash if you left click on it?
[21:25] <sunshinepants> mostafa_: you want to execute the script from console, or X?
[21:26] <mostafa_> prefer console
[21:26] <mostafa_> sunshinepants: prefer console
[21:27] <joumetal> shang: http://blogs.gnome.org/metacity/2008/12/16/how-to-apply-a-patch-under-ubuntu/ is worth trying. use checkinstall instead of make install.
[21:27] <ripps> Okay, I've finally got karmic reinstalled. My only issue is that nm-applet has an ifupdown (eth0) entry that can't be deleted.
[21:27] <sunshinepants> mostafa_: this is not secure, but you can use "echo <rootpw>|sudo touch /root/test" within your shell script.  you can pipe your root password to the sudo operation basically.
[21:27] <ActionParsnip> mrmcq2u_: i dont use it, log a bug
[21:28] <mrmcq2u_> ActionParsnip -you dont use network manager?
[21:28] <mrmcq2u_> the applet?
[21:28] <shang> joumetal: checking for intltool >= 0.35.0... ./configure: line 6293: intltool-update: command not found
[21:29] <shang> joumetal: do we still use have that in karmic?
[21:29] <ActionParsnip> mrmcq2u_: no, its a waste of resources
[21:29]  * shang was running ./config
[21:29] <SeekerNL> does someone know why my 4gb don show up in amd64 kubuntu? systemmonitor just shows 2,9
[21:29] <shang> ./configure
[21:29] <ActionParsnip> mrmcq2u_: waste of resources
[21:29] <SeekerNL> Linux Seeker 2.6.31-10-generic #34-Ubuntu SMP Wed Sep 16 01:09:15 UTC 2009 x86_64 GNU/Linux
[21:30] <ActionParsnip> mrmcq2u_: i use static IP so I define all in /etc/network/interfaces. I can also change addressing using ssh, something not possible with nm-applet
[21:31] <ActionParsnip> mrmcq2u_: also makes boot faster as I dont have to wait for it to come up and for dhcp to complete
[21:31]  * shang sorry, my bad, installing intltool right now
[21:31] <SeekerNL> !bug
[21:33] <ActionParsnip> mrmcq2u_: maks sense doesnt it?
[21:34] <AlanBell> bug 436142
[21:35] <mostafa_> sunshinepants: what should happened when I type "echo <rootpw>|sudo touch /root/test" ?
[21:36] <mrmcq2u_> hmmmm... better debug it
[21:36] <mrmcq2u_> bbl
[21:37] <Winball> Networkmanager does not work in Karmic ?
[21:37] <AlanBell> Winball: not today it doesn't
[21:37] <AlanBell> but I am sure it will shortly
[21:37] <guntbert> mostafa_: are you talking about the actual root password - or about the user password who may sudo?
[21:38] <mostafa_> guntbert: about user passworf
[21:38] <sunshinepants> mostafa_: nm.. I was wrong, you can't do it that way for sudo
[21:38] <mostafa_> sunshinepants: what should I do then?
[21:39] <sunshinepants> mostafa_: you can setuid=root on the file I guess..  what exactly are you trying to do?
[21:39] <ActionParsnip> Winball: could use wicd until its righted
[21:39] <guntbert> mostafa_: you can allow the user to start one special command as root without password - edit /etc/sudoers
[21:39] <Winball> ActionParsnip Ye. The bugreport gave me another way around it too.
[21:39] <SeekerNL> why is mplayer not with VDPAU compiled in Ubuntu?
[21:39] <ActionParsnip> Winball: or wifi-radar
[21:40] <sunshinepants> guntbert: that works
[21:41] <guntbert> sunshinepants: but the syntax of /etc/sudoers is a bit ... difficult :-)
[21:41] <DanaG> Bauldrick-netboo: oops, sorry for the long delay.
[21:41] <DanaG> What was up with your touchpad?  Not functioning at all, or just not applying your settings?
[21:41] <DanaG> !visudo
[21:41] <mostafa_> guntbert: how could I edit that to do my work?
[21:41] <DanaG> use visudo, not just an editor.
[21:42] <nemo> Hm.
[21:43] <nemo> Ok. I decided to try installing fglrx onto my AMD64 machine w/ ATI Radeon HD
[21:43] <nemo> it appears the fglrx driver is... 32 bit?
[21:43] <nemo> that was a bit odd.
[21:43] <guntbert> mostafa_: sorry, as I just said, that file is a bit difficult, I always google for examples before I touch it, but using visudo is a good idea (you'll have to learn vi though)
[21:43] <mostafa_> guntbert: how could I edit that to do my work?
[21:43] <nemo> anyway. after installing, compiz still fails
[21:43] <nemo> I see a 10fglrx under the new Xsession.d
[21:44] <nemo> compiz complains "Checking for texture_from_pixmap"  not present
[21:44] <guntbert> DanaG: thx for the hint :-)
[21:44] <nemo> so. Is there any way to get ATI Radeon HD to work w/ compiz on AMD64?
[21:45] <wekt> SeekerNL, diverse_izzue, guntbert:  Ubuntu Koala x86-32 is configured for Max 4 GB RAM.  so I presume 64bit supports at least as much.  You can check the HIGHMEM setting in /boot/config
[21:46] <ripps> Can someone help me figure out why I have an ifupdown entry in nm-connections thtat I can't delete?
[21:46] <Matt-W> Hello. Karmic alpha 6 upgrade hosed my grub2 configuration, does anybody know anything about it? As far as I can tell the system's intact, it's just the grub2 config is completely wrong.
[21:46] <SeekerNL> wekt so Ubuntu onluy supports 4 gb at amd64 systems?
[21:47] <guntbert> SeekerNL: no, the other way round
[21:47] <DanaG> oh yeah, you can EDITOR=nano visudo
[21:47] <DanaG> that is, set the EDITOR variable.
[21:47] <SeekerNL> wekt I am using amd64
[21:48] <SeekerNL> how do I use that shortcut so I can search that file?
[21:48] <guntbert> DanaG: very instructive evening for me :-) - thx
[21:48] <wekt> less /boot/config-2.6.31-10-generic
[21:49] <guntbert> SeekerNL: less /boot/config<tab><tab>
[21:49] <edgy> hi, I just installed the flgrx driver from jockey and the computer now is very slow, even while I am typing the letters are in slow motion, glxgears rotate in slow motion too, is this known?
[21:49] <SeekerNL> no I mean a shortcut then search bar pops up
[21:50] <Bauldrick-netboo> DanaG: touchpad is just not responding atall - keyboard responds, but touchpad does not
[21:50] <Bauldrick-netboo> DanaG: as i look at it logged now, the toolbar is all scrambled also
[21:51] <Bauldrick-netboo> so i thought xorg.conf, which said hal has taken over
[21:55] <natewiebe13> have they made the new gdm match xsplash yet?
[21:55] <DanaG> Bauldrick-netboo: cat /proc/bus/input/devices
[21:55] <DanaG> check if there's touchpad in there.
[21:56] <ActionParsnip> Bauldrick-netboo: it will supercede hal if its used
[21:56] <DanaG> xorg.conf changes on touchpad get lost on vt-switch and suspend/resume, though.
[21:56] <DanaG> Better to use an fdi file.
[21:57] <DanaG> example: http://users.csc.calpoly.edu/~dgoyette/19-synaptics.fdi
[21:57] <nemo> hm. my glxinfo yields
[21:57] <SeekerNL> what was that package which will install you make install as a deb?
[21:57] <nemo> bad request
[21:57] <nemo> ditto fglrxinfo
[21:58] <nemo> that could explain the fail of compiz
[21:58] <Bauldrick-netboo> DanaG: thats what i read - but the .fdi file should be where? /etc/hal  or /usr/share
[21:58] <DanaG> /etc/hal/fdi/policy
[21:59] <DanaG> I also symlinked it to give it the additional name, 10-synaptics.fdi
[21:59] <DanaG> in the same dir.
[21:59] <SeekerNL> normall you do make and then make install but there is a package which you cal make of that make install a deb file so you can easy remove the software
[21:59] <Bauldrick-netboo> DanaG: i only had preferences.fdi in there - tried to mv a synaptics.fdi from /usr/share to there but mad no difference
[22:09] <DanaG> Bauldrick-netboo: is touchpad in /proc/bus/input/devices ?
[22:09] <DanaG> cat it (that path is a file.)
[22:10]  * nemo sighs and deletes fglrx
[22:10] <nemo> lets see now. is there any way to get compiz + ati + amd64... :-/
[22:11] <_iTroll> hello guys, having problem with latest karmic on a lenovo s10e with an intel 945. X will not start
[22:12] <SeekerNL> is XINE compiled with vpdau in Ubuntu?
[22:17] <alokito> how to chainload grub 2 in grub legacy?
[22:21] <Bauldrick-netboo> DanaG: sorry about delay, /proc/bus/input/devices  N: name synps/2 synaptips touchpad
[22:21] <DanaG> hmm, anything special in xorg log?
[22:22] <_iTroll> Xorg.log at pastebin.com/f642e91b
[22:23] <ripps> wtf, someone just tried to dcc me a keylogger
[22:23] <ikt> that happens
[22:23] <Bauldrick-netboo> loads of shite about RADEON
[22:25] <aboSamoor_> anyone facing problem with the window decorator, I don't have it anymore !
[22:26] <Bauldrick-netboo> DanaG: xorg.conf says everything is done via HAL and i dont have anything in /etc/hal/fdi/profile
[22:26] <krushia> where do I go to find the list of patchsets applied to vanilla to make the ubuntu kernel?
[22:28] <Bauldrick-netboo> *policy
[22:28] <DanaG> !info pastebinit
[22:34] <Bauldrick-netboo> DanaG: pastebin of what file?
[22:34] <DanaG> Xorg log.
[22:35] <Bauldrick-netboo> http://pastebin.com/f6e29a896
[22:37] <DanaG>  Query no Synaptics: 000000 (--) SynPS/2 Synaptics TouchPad: no supported touchpad found (EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware. (EE) PreInit failed for input device "SynPS/2 Synaptics TouchPad"
[22:38] <_iTroll> talking of Xorg log..... here's mine http://pastebin.com/f642e91b  X wont start for me on latest karmic
[22:38] <Bauldrick-netboo> so i guess thats not good then !
[22:38] <DanaG> "SynPS/2 Synaptics TouchPad"
[22:39] <DanaG> http://www.google.com/search?q=SynPS%2F2+Synaptics+TouchPad%3A+no+supported+touchpad+found+&aq=f&oq=&aqi=
[22:41] <DanaG> http://www.google.com/search?q=%22no+synaptics+event+device+found%22&aq=f&oq=&aqi=
[22:45] <nemo> weird
[22:45] <nemo> why is flashplugin-nonfree pulling in 32 bit stuff.
[22:46] <nemo> I thought adobe made the flash plugin for linux 64 bit
[22:46] <nemo> in fact, before they released for other 64 bit
[22:46] <_iTroll> Hello ubuntu+1! X wont start on latest karmic for me.  Xorg log here http://pastebin.com/f642e91b . Graphics are intel mobile 945
[22:47] <Bauldrick-netboo> DanaG: i'm gonna look at those/this tomorrow, as I'm one bottle of red over the limit at the moment - thank-you kindly
[22:48] <tormod> _iTroll, lsmod|grep drm
[22:48] <_iTroll> tormod: just rebooting
[22:49] <_iTroll> tormod: nothing
[22:52] <jpds> nemo: The 64bit version isn't packaged.
[22:53] <jpds> nemo: If you want the 64bit one, download it, place it in your ~/.mozilla/plugins/ directory and remove the 32bit packaged one.
[22:55] <Martyn> meep
[22:55]  * Martyn watches the inexorable browning of karmic ...
[22:55] <Martyn> it's interesting to update every day and see some new item become brown
[22:59] <ikt> I don't like brown :(
[22:59] <ikt> ok maybe I like it a little
[23:00] <DanaG> hmm, it's actually pretty nice.
[23:00] <DanaG> Though, I don't like how much the scroll bars stand out.
[23:00] <AlanBell> I like the new hotness of very brown
[23:00]  * jpds still prefers DarkRoom.
[23:01] <AlanBell> I am looking forward to the default wallpaper and the gdm background
[23:02] <DanaG> Right now, I get xsplash->gdm->xsplash->gdmwall->mywallpaper
[23:02] <DanaG> it looks horrible.
[23:03] <DanaG> Default gdm doesn't match default xsplash.
[23:03] <AlanBell> yes, it is a bit crazy at the moment
[23:03] <nemo> jpds: 'k
[23:03] <nemo> jpds: thanks...
[23:03] <nemo> is there any reason for that?
[23:04] <jpds> nemo: It's still in beta.
[23:04] <nemo> jpds: gee. that sounds familiar ;)
[23:04] <nemo> *cough*shiretoko*cough*
[23:07] <penguin42> has anyone seen a change in gnome-terminal rendering behaviour in the last couple of days?
[23:12] <penguin42> it seems to be having problems with the colours in Mutt
[23:19]  * nemo sobs
[23:19] <nemo> I want graphics accel
[23:19] <nemo> this is so embarassing.
[23:19] <nemo> coworkers know I have a super-fast card in this box
[23:20] <nemo> seeing a simple screensaver creep by a frame at a frame...
[23:20] <penguin42> what card?
[23:20]  * nemo hunts around on ATI website for AMD64 fglrx
[23:20] <nemo> Radeon HD 4000
[23:20] <nemo> oh
[23:20] <nemo> wait
[23:20] <nemo> that's the audio. lol
[23:20] <nemo> Radeon HD 4670 (gfx)
[23:21] <nemo> ok. not super-fast, but lot better than the intel cards they all have
[23:21] <penguin42> I've run fglrx on amd64 (not on ubuntu though) - you shouldn't need to hunt, ubuntu should find you drivers shouldn't it?
[23:21] <nemo> penguin42: I installed fglrx on amd64 karmic.  it seems to have failed horribly in some way
[23:21] <nemo> penguin42: besides, it seemed to be using the 32 bit wrapper
[23:21] <nemo> glxinfo simply exited in an error
[23:21] <nemo> sooo, I removed it again
[23:22] <penguin42> sometimes binary drivers take a while to catch up
[23:22] <nemo> can't seem to find any bugs to watch either :(
[23:33] <penguin42> nemo: If you go to system->Admin->Hardware Drivers does it find anything?
[23:37] <virtuald> i don't like the new browner theme :(
[23:38] <Etu> Hi
[23:38] <Etu> Im using 9.10, And I installed awesome
[23:38] <test34> is it normal that you need to use alsactl store/restore to save and restore your sound settings?
[23:39] <Etu> Whats the name of the file I should put stuff I want to start autmatic when X start?
[23:39] <Etu> Is it the .xsession file?
[23:41] <penguin42> Etu: What do you want to start?
[23:41] <Etu> penguin42: nm-applet, I wat to run some setxkbmap commands
[23:42] <Etu> I done in gentoo several times. just place it in .xinitrc
[23:42] <penguin42> hmm setxkbmap - I think there's somewhere special for that
[23:42] <nemo> penguin42: YAY
[23:42] <nemo> penguin42: thanks dude
[23:42] <nemo> I thought that was done automatically in the "searching for available drivers" that it does when activating compiz
[23:42] <nemo> then I tried the synaptic package
[23:42] <nemo> either the wrong one, or what, I do not know, but I have my gfx accel
[23:42] <nemo> woot
[23:43] <penguin42> Etu: You should be able to create a ~/.Xmodmap that's passed to /usr/bin/xmodmap by /etc/X11/Xsession.d/80ubuntu-xmodmap
[23:44] <Etu> And I want to start the power-managent stuff too :)
[23:45] <penguin42> Etu: I would have though it should have automatically started ?
[23:47] <Etu> Maybe it is started, but not the graphical battery moniter, for example
[23:47] <Etu> The networkmanager krashes when I click on it in awesome systray :)
[23:49] <penguin42> Etu: You should be able to start that, and then go to system->preferences->startup applications and options and tell it to remember them
[23:49] <Etu> bah... I don't even start gnome
[23:49] <Etu> or the gnome application witch auutstarts
[23:50] <penguin42> oh
[23:52] <_iTroll> ubuntu+1! X wont start on latest karmic for me.  Xorg log here http://pastebin.com/f642e91b . Graphics are intel mobile 945
[23:54] <NerveClasp> hi! I have a problem with auto mounting my cd/dvds (((( what can be wrong?
[23:55] <NerveClasp> I cannot reach it through /media/cd also//
[23:55] <penguin42> _iTroll: I'd see if there was anything in your dmesg as well - I've not seen anyone else report those errors (but I haven't been on here today - but I've been on for last few days) - i945 from yesterday is working fine for me
[23:55] <NerveClasp> can anybody help me?
[23:55] <_iTroll> penguin42: yeah i think i am a special case....
[23:56] <_iTroll> dmesg coming up
[23:58] <_iTroll> http://pastebin.com/f33b72b64
[23:58] <_iTroll> penguin42: ^^^^^ dmesg
[23:59] <penguin42> _iTroll: I don't see anything bad in there