[00:58] <Imasami> Anyone know why when I try to use gnome shell, gnome classic is used instead?
[01:03] <RainbowzzIsFrust> Hello hello
[01:04] <RainbowzzIsFrust> I need some assistance trying to get my webcam to work with a certain streaming site
[01:04] <RainbowzzIsFrust> Having all kinds of issues
[01:46] <Rainbowzz> sorry got disconnected
[01:46] <Rainbowzz> was looking for help getting my webcam working
[03:06] <duanedesign> :)/25
[03:23]  * Unit193 passes this note to duanedesign http://niklas.laxstrom.name/page/eng/irssi
[03:24] <duanedesign> thank you
[03:24] <duanedesign> i should wait to read it before thanking you
[03:25] <Unit193> It's alright, I don't use it myself. :P
[08:14] <stevmmm> anyone here?
[08:14] <stevmmm> im trying to boot to a ub live CD
[08:14] <stevmmm> it boots, and then just gives me an empty desktop with nothin on it
[08:15] <stevmmm> right click and left click do nothing
[08:15] <stevmmm> the only thing that does it printscr
[08:15] <stevmmm> and all that does is bring up a "save image" dialog
[08:17] <JoseeAntonioR> stevmmm: Yes. You are supposed to try Ubuntu with the LiveCD, it doesn't include any extra package or anything, it is like a fresh installation.
[08:17] <stevmmm> ok jose, so what can i do with it whe i load the live CD. t seems utterly unresponsive. No "start" button or anything
[08:18] <stevmmm> i mean can i type a text document or browse a webpage?
[08:18] <JoseeAntonioR> stevmmm: Yes, you can. what
[08:18] <JoseeAntonioR> What version of Ubuntu did you download?
[08:18] <benonsoftware> stevmmm: Yes, if Ubuntu can detect your internet connection, and type a word document with Libreffice
[08:19] <stevmmm> I didnt download one. someone gave me a CD.
[08:19] <stevmmm> ubuntu DES detect the connection
[08:19] <stevmmm> DOES*
[08:20] <stevmmm> it says so as it loads
[08:20] <stevmmm> but then arrives at empty desktop city
[08:20] <JoseeAntonioR> stevmmm: Ok. So, please click in applications>Internet>Firefox Web Browser
[08:20] <stevmmm> theres no applications button
[08:20] <JoseeAntonioR> stevmmm: With that you will open Firefox
[08:20] <stevmmm> no buttons at all
[08:20] <stevmmm> blank desktop
[08:21] <stevmmm> nothing on it
[08:21] <JoseeAntonioR> stevmmm: Then, hover your mouse around the left part of the screen, and a launcher will appear. Then, click the Firefox icon
[08:22] <stevmmm> ok
[08:22] <stevmmm> ill try that.
[08:22] <stevmmm> need to load it up again. back in a few.
[08:23] <JoseeAntonioR> Ok
[09:22] <stevmmm> ok it said it detected a volme with a package on it
[09:22] <stevmmm> it said do you want to open it
[09:22] <stevmmm> i said open package
[09:23] <stevmmm> and now i have the blank desktop again. It appears to b doing nothing
[11:53] <mayur> mouse cursor spins for along time when I open a folder
[11:53] <mayur> anyone can help?
[21:24] <pointydrip> hello, I am try to do port forwarding using guidedog from eth0 to eth1 to share an internet connection, how to find out what the local ip address for eth0 and eth1 are?
[21:25] <holstein> pointydrip: ifconfig in a terminal give you waht you are looking for?
[21:28] <pointydrip> holstein: yes! there are a few choices, but I can narrow it down from there...you're a pro!
[21:29] <holstein> pointydrip: well.. i am what i am! not sure if pro covers it, but enjoy!
[21:31] <pointydrip> well, it's people like you that keep me on ubuntu...other wise I would have ran away from linux screaming and yelling long ago
[21:35] <pointydrip> holstein: when I apply the rules in guidedog I get the following output: "The "nat" table is not intended for filtering, the use of DROP is therefore inhibited."
[21:35] <pointydrip> holstein: does that mean its not working?
[21:36] <holstein> pointydrip: thats the way i read it... what are you trying to do? i have not heard of guidedog
[21:38]  * holstein gotta run.. bbl
[21:38] <pointydrip> guidedog is in the software center, it's an interface for manipulating iptables...which I need because I always end up doing serious damage when I mess with iptables...I've had to reformat a few times
[21:39] <pointydrip> when I apply the forwarding rules it says the 'drop inhibited' message twice and then this: "Try `iptables -h' or 'iptables --help' for more information.
[21:39] <pointydrip> Enabling routing.
[21:39] <pointydrip> Loading kernel modules.
[21:39] <pointydrip> Inserting masquerade rules.
[21:39] <pointydrip> Finished."
[21:40] <Unit193> It may not be quite the same, but ufw/gufw are other options.
[21:40] <pointydrip> I'll try that
[21:41] <Unit193> Take a look first and see if it does what you want.
[21:50] <pointydrip> it appears to do the same thing, ufw gives the option to specify inbound or outbound for a forwarding rule, this was not there for guide dog so I would assume it was applying in/out for all rules?
[21:50] <Unit193> Never used that one, so it'd just be a guess of yes.
[21:51] <Unit193> You could list them from iptables directly though.
[23:42] <Arthur_> hello?
[23:47] <Arthur_> I am having issues getting the installer to run anyone have experience with that?


[08:52] <ara> xnox, hello! we are starting to use the 12.04.3 to certify systems, and kaxing has been seeing some errors when doing network installation with those
[08:52] <ara> do you know if pxe installation was tested?
[08:52] <ara> kaxing will be able to give you more details
[09:47] <infinity> ara: I'm heading to bed, but I'd be interested in these PXE issues.  Which image (precise, precise-lts-quantal, precise-lts-raring), what the problem is, full syslog, etc.
[09:47] <ara> kaxing, can you file a bug against casper with all the needed info infinity is asking for, please?
[09:48] <infinity> ara: Oh, PXE of the live ISOs, not d-i netboot images?  I might be less interested in that than xnox. :)
[09:48] <kaxing> ara, infinity sure. we are having nfs mounting issue with 12.04.3 desktop iso
[09:48] <infinity> (Do people actually do that outside our labs?)
[09:49] <infinity> Still, same thing applies, full syslog, etc, and point out the bug on IRC, and one of us will poke it with a stick.
[10:48] <kaxing> infinity, please check this bug# for pxe issue on desktop image https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1216853
[10:48] <ubot2`> Launchpad bug 1216853 in casper (Ubuntu) "During PXE booting failed to mount nfs directory" [Undecided,New]
[10:50] <kaxing> infinity, hopefully you are already in the bed :) cc xnox please check this bug for pxe/nfs mounting issue on 12.04.3 desktop image
[14:30]  * xnox is on public holiday here.
[15:48] <srwarren> infinity, I think you'd said you'd look at https://code.launchpad.net/~srwarren/debian-installer/tegra/+merge/175967. Do you have any estimate when that might happen? Is it something that's likely to be accepted?
[18:22] <infinity> srwarren: Oh, odds are good that I'll be including it as-is, or with minor tweaks, yes.  I just need to get it to bubble up my TODO.
[20:23] <srwarren> infinity, oh great - thanks


[01:01] <robru> ogra_, rsalveti: anybody around to kick an image build? just got latest uitk in archive
[01:29] <robru> if only there was a cron job...
[02:11] <Eliyahu`> hey what is a tablet that i can get the ubuntu OS to be installed on that i can use openshot video editing program in to use to edit video on the field
[02:13] <Eliyahu`> i was looking at couple of the hand held tablets today and i saw galaxy and couple other tablets and i would like to be able to get one that i can install and overwrite the system with ubuntu linux
[02:24] <robru> Eliyahu`, none. None of them wll run openshot
[02:25] <robru> Eliyahu`, sorry I gotta run. but that depends on X, which isn't on the ubuntu tablet. so it won't work. it's not ready yet
[16:03] <lops> good morning. You guys doing http://24pullrequests.com ?
[16:07] <randomcpp> lops, what's it? :)
[16:08] <lops> you do one pull request per day until christmas evve
[16:08] <lops> and you get a badge in the end x)
[16:08] <lops> pull requests to open source projects, of course
[16:10] <randomcpp> interesting :)
[16:11] <lops> I hope I can make the time to make a pull request a day xD
[16:12] <user82> is angry birds on ubuntu touch yet?
[16:12] <randomcpp> I don't even have time to work on my own projects :'(
[16:12] <randomcpp> user82, you should try with the web app
[16:13] <user82> randomcpp, so the web app is available?
[16:13] <user82> the icon confused me: http://www.ubuntu.com/phone/app-ecosystem
[16:14] <randomcpp> I mean this web app http://chrome.angrybirds.com/
[16:14] <user82> yeah. that should work
[16:14] <user82> not that i need it. ever
[16:14] <randomcpp> but at the moment performances on ubuntu touch aren't so good
[16:14] <user82> ;)
[16:14] <randomcpp> it could lag a lot
[16:14] <user82> i was just asking. all i would need is whatsapp :p
[16:14] <user82> or actual hardware...one of those ;)
[16:17] <randomcpp> I'd need whatsapp to
[16:17] <randomcpp> there were some efforts, but I don't know what's the status at the moment
[16:19] <user82> randomcpp, you don't want to know i guess
[16:20] <user82> randomcpp, in may there was a "Long term interest". But whatsapp telling them to stop development seems to have dampened it a little...my last status was that it is dead
[16:20] <randomcpp> here's what I was referring to https://launchpad.net/whosthere
[16:21] <user82> yep. whatsapp did not like it.
[16:21] <user82> for whatever reason
[16:21] <user82> randomcpp, but if you have some time, you could write an email to the whatsapp support<EMAIL_ADDRESS>[16:21] <user82> so they know people want to have it on ubuntu touch
[16:22] <randomcpp> http://getfirefoxos.com/apps/whatsapp-firefox-os-released/
[16:22] <randomcpp> go to comments
[16:24] <user82> yeah it is a web app..it could theoretically work
[16:24] <user82> did not know it was taken down
[16:40] <lops> i don't get that image in http://www.ubuntu.com/phone/app-ecosystem. so misleading
[17:36] <randomcpp> daker, I saw your post about UserMetrics, can all apps use that feature?
[17:36] <randomcpp> I'd be interested to add it in saucybacon :p
[17:39] <daker> randomcpp: yes
[17:41] <daker> randomcpp: it's listed under usage, so it's open http://developer.ubuntu.com/publish/apps/security-policy-for-click-packages/
[17:41] <daker> common usage*
[18:57] <frecel> good saturday people
[19:09] <Janet_> I'm installing touch on my nexus 7, and it's saying "ROM may flash stock recovery on boot. Fix? THIS CANNOT BE UNDONE
[19:10] <Janet_> phablet hasn't sent a message, but it's been sitting like this for a few minutes. do I need to select 'Yes' on the tablet to continue? I don't want to mess up the install if not.
[21:12] <Doremus> hi all
[21:22] <lops> Good morning Doremus
[21:48] <RamblingMadMan> Can anybody on here tell me why the hell I have absolutely no wifi and no options pertaining to it in the system settings?
[21:49] <RamblingMadMan> Can anybody on here tell me why the hell I have absolutely no wifi and no options pertaining to it in the system settings?
[21:49] <RamblingMadMan> Anybody at all?
[22:42] <RamblingMadMan> is anybody on currently?
[22:44] <RobbyF> yeah
[22:44] <RobbyF> to answer your question from before: which device
[22:44] <RobbyF> if its nexus you need to be on 4.3.x before flashing
[22:45] <RamblingMadMan> God, if only the wiki said so :P
[22:45] <RobbyF> yeah
[22:46] <RobbyF> I have to downgrade as well
[22:46] <RobbyF> guess i'll do that now
[22:46] <RamblingMadMan> You can just download the radio drivers from the 4.3 firmware
[22:48] <RobbyF> flash it over UT?
[22:56] <lops> RamblingMadMan, wifi support seems to be limited for the time being
[22:56] <lops> the UI is almost useless
[23:03] <RobbyF> how is it useless? wifi works fine
[23:14] <lops> The UI. If you have wifi at home with a password, it's fine
[23:14] <lops> for everything else... eh...
[23:14] <lops> still pretty green
[23:15] <lops> i spent an afternoon trying to copy my wlan profiles from my laptop to no avail
[23:16] <lops> i ended up borrowing a router to tether the wifi from my laptop
[23:46] <RamblingMadMan> If you're running android 4.4 and try to flash the latest Ubuntu touch image wifi isn't functioning


[00:55] <mup> Bug #1874355 opened: Controller details page not updated to match machine details page designs <ui> <MAAS:New> <https://launchpad.net/bugs/1874355>
[00:55] <mup> Bug #1874356 opened: Unable to view storage tab on controllers detail page <ui> <MAAS:New> <https://launchpad.net/bugs/1874356>
[01:04] <mup> Bug #1874355 changed: Controller details page not updated to match machine details page designs <ui> <MAAS:New> <https://launchpad.net/bugs/1874355>
[01:04] <mup> Bug #1874356 changed: Unable to view storage tab on controllers detail page <ui> <MAAS:New> <https://launchpad.net/bugs/1874356>
[01:07] <mup> Bug #1874355 opened: Controller details page not updated to match machine details page designs <ui> <MAAS:New> <https://launchpad.net/bugs/1874355>
[01:07] <mup> Bug #1874356 opened: Unable to view storage tab on controllers detail page <ui> <MAAS:New> <https://launchpad.net/bugs/1874356>
[13:11] <mup> Bug #1874439 opened: Use standard notifications for deprecation notices <MAAS:Triaged by ack> <https://launchpad.net/bugs/1874439>
[20:26] <mup> Bug #1874538 opened: Adding LXD Pod with pre-composed resources errors out <MAAS:In Progress by newell-jensen> <https://launchpad.net/bugs/1874538>
[20:32] <mup> Bug #1874538 changed: Adding LXD Pod with pre-composed resources errors out <MAAS:In Progress by newell-jensen> <https://launchpad.net/bugs/1874538>
[20:35] <mup> Bug #1874538 opened: Adding LXD Pod with pre-composed resources errors out <MAAS:In Progress by newell-jensen> <https://launchpad.net/bugs/1874538>


[08:45] <mpt> Is there any way to see the current translation for a particular string in every available language?
[08:46] <wgrant> mpt: There is not.
[08:56] <mpt> ah, pity
[10:04] <Laney> cjwatson: Do you know about situations like https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-008/+build/7714108? Seems to be waiting for libmedia-dev despite the arch restriction.
[10:05] <cjwatson> Laney: known bug which I spent most of yesterday yak-shaving on
[10:06] <cjwatson> and which will probably continue to consume my time today :-(
[10:06] <Laney> OK :(
[10:06] <Laney> No problem if I just mash the button then?
[10:07] <cjwatson> Laney: will it make any difference?  the other dependencies would have been removed from the list if they were satisfied now
[10:07] <cjwatson> (modulo cronjob)
[10:08] <cjwatson> Laney: oh, of course, they won't because the same bug crashes retry-depwait
[10:08] <cjwatson> Laney: sure, go ahead and mash button
[10:09] <Laney> Ha. Yeah, they should be satisfied.
[10:09] <Laney> mushed
[13:38] <teward> is there a way i can break the bugcheck logic for a linked upstream bug on one case to force it to "Won't Fix" status due to the broken bugtracker logic (https://bugs.launchpad.net/launchpad/+bug/1413304)
[13:40] <teward> or, where in the LP code should I look at for that so I can propose a patch?
[13:46] <cjwatson> lib/lp/bugs/externalbugtracker/debbugs.py + lib/lp/bugs/externalbugtracker/tests/test_debbugs.py (assuming you mean to fix the statuses rather than bodging around them)
[13:48] <cjwatson> follow https://dev.launchpad.net/Running/LXC to set up a dev instance, make a branch, 'utilities/link-external-sourcecode && make', and then you can do 'bin/test -vvct lp.bugs.externalbugtracker.tests.test_debbugs'
[13:49] <cjwatson> after that, given that these tests seem quite easy to extend, I'd recommend writing tests that enforce your improved behaviour specification first, checking that the new tests fail, and then fixing code until they pass
[13:54] <mapreri> aka TDD
[14:01] <cjwatson> Indeed.  Sometimes in LP it's unreasonably difficult to do things that way, but it would work well here and I think would actually be easier for a newcomer to the codebase.
[14:15] <teward> cjwatson: yes, i meant 'fix the statuses'


[07:38] <agateau> afiestas__: a few remarks regarding your mockup,
[07:38] <agateau> afiestas__: the Encrypt checkbox should have a label on the right so that it's easier to click
[07:38] <agateau> afiestas__: you probably want two Password fields, for confirmation
[07:39] <agateau> afiestas__: the Password fields should be indented as I assume they are only enabled if Encrypt is checked
[07:40] <agateau> afiestas__: I like the fact that the FS is selected in a "Compatibility" combobox that sounds less techy
[07:40] <agateau> afiestas__: Is it possible to use encryption for all FS? (ie encryption on FAT sounds dubious)
[07:42] <agateau> afiestas__: you may want to put Capacity and Used Space in a separate group, and place it above "Format options"
[07:42] <agateau> afiestas__: maybe with a nice filled bar, like the one Dolphin uses in its statusbars
[07:43] <agateau> that's it for now :)
[07:43] <agateau> oh and "Advance Mode" => "Advanced Mode"
[08:19] <jussi> Riddell: ping
[08:20] <jussi> Riddell: Ive changed the way my blog feeds work, could you update the planet kde config to use http://jussi01.com/category/kde/feed/ for me?
[08:22] <agateau> Riddell: I see you renamed libindicate-qt0 to libindicate-qt1, was this necessary? iirc version <IP_ADDRESS> is BC with 0.2.5
[08:23] <agateau> Riddell: and it breaks kmail and plasma-widget-message-indicator (they probably need a rebuild)
[08:31] <Riddell> agateau: it's a belated change, the SONAME has been 1 for some time and the packaged should have changed then
[08:32] <agateau> Riddell: oh right
[08:32] <agateau> Riddell: are kmail and plasma-widget-message-indicator being rebuilt?
[08:33] <agateau> Riddell: or did their build fail?
[08:33] <Riddell> agateau: I just clicked rebuild on plasma-widget-message-indicator
[08:33] <Riddell> I'll upload kdepim now
[08:35] <tazz> Riddell, what goes in the documentation ? https://wiki.kubuntu.org/Kubuntu/Todo
[08:35] <agateau> Riddell: great, thanks
[08:35] <tazz> do we copy the documentations right from kde upstream ?
[08:35] <agateau> Riddell: new kdepim? (4.4.10?)
[08:35]  * tazz was looking into doing the remaining documentation....
[08:35]  * tazz goes to rtfm
[08:36] <Riddell> tazz: application documentation comes from upstream, we also have kubuntu-docs which is written by kubuntu people
[08:37] <tazz> ah i see...
[08:38] <Riddell> tazz: for kubuntu-docs I though it's in bzr co lp:kubuntu-docs  and you want to talk to DarkwingDuck
[08:38] <Riddell> and see the todo for the status https://wiki.kubuntu.org/Kubuntu/Todo
[08:38]  * tazz waves at DarkwingDuck
[08:38] <tazz> Riddell, yes i am on that page...
[08:38] <Riddell> he's in the US so he's probably fast asleep for a while
[08:40] <tazz> heh, sunny California.
[08:55] <bambee> hey
[08:56] <Riddell> bonjour bambee
[08:56] <nigelb> Quintasan: Hey for your session, can you talk to jml on #launchpad.  I talked to the lp team and a few people are willing to help.
[08:56] <bambee> Riddell: hehe ;)
[08:57] <Riddell> jussi: planet updated
[09:02] <jussi> Riddell: thanks
[09:02] <bambee> plasma-widget-message-indicator should be rebuild to change its runtime dependency to libindicate-qt1, nop ?
[09:05] <Riddell> bambee: already has been https://launchpad.net/ubuntu/+source/plasma-widget-message-indicator/0.5.7-0ubuntu1  should appear in the archive in half an hour
[09:05] <bambee> nice :)
[09:05] <bambee> ok
[09:05] <nigelb> jussi: hey, ping?
[09:06] <jussi> nigelb: pong
[09:06] <nigelb> jussi: hey, bot devel want to talk about stuff at UDW?
[09:06] <nigelb> jussi: I've been failing at helping with the trivia bot
[09:07] <nigelb> Probably a nice way to talk about tcl and recruit people for it.
[09:07] <jussi> nigelb: best to talk to tsimpson. I own the bot and help where i can, but tsimpson is the real main man.
[09:07] <nigelb> yessir, will do :)
[09:11] <Riddell> it's written in tcl?  people use tcl?
[09:12] <nigelb> eggdrop is tcl I think
[09:12] <Riddell> I should probably know that, I run eggdrop
[09:12] <nigelb> heh
[09:47] <Riddell> yay, owncloud working! http://ec2-50-17-22-55.compute-1.amazonaws.com/owncloud/
[09:49] <Riddell> go test, jr/foo
[09:49] <jussi> Riddell: ubottu is not tcl, thank god
[09:50] <jussi> !info supybot
[09:50] <Riddell> clever ubottu
[09:50] <jussi> Riddell: we even have cloning instructions :D
[09:50] <jussi> !botclone
[09:51] <nigelb> jussi: but triviabot is tcl right?
[09:51] <jussi> nigelb: no idea - ryanakca does it.
[09:51] <nigelb> It is, I remember ryan telling me its eggdrop
[09:53] <Riddell> what's wrong with this dialogue?  http://ec2-50-17-22-55.compute-1.amazonaws.com/owncloud/files/open_file.php?dir=&file=webdav-dialogue.png
[09:53] <Riddell> note the instructions and the button text
[09:55] <jussi> Riddell: whoops
[09:55] <jussi> Riddell: instructions differ from the button text. nice catch
[09:58] <jussi> Riddell: have you got itto work with dolphin?
[09:59] <Riddell> jussi: yes but that dialogue isn't very clear
[09:59] <jussi>  RiddellI have my own owncloud, but I still fail at getting dolphin to work with it+webdav
[10:00] <Riddell> jussi: well does this work in dolphin?  webdav://jr@ec2-50-17-22-55.compute-1.amazonaws.com:80/owncloud/webdav/owncloud.php
[10:01] <jussi> never mind, fixed it<EMAIL_ADDRESS>- this was how I needed to do it.
[10:22] <Riddell> revu needed http://revu.ubuntuwire.com/p/owncloud
[10:30]  * Riddell nudges maco into revu-ing
[10:46] <bambee> while giving some help to shadeslayer, I'll also work on language-selector (I mean both in parallel)
[10:46] <Riddell> bambee: do you know what needs to be done?
[10:47] <bambee> kcm integration into systemsettings->localisation ?
[10:48] <bambee> localization *
[10:49] <Riddell> yep
[10:49] <Riddell> which will take porting to policykit/kauth first
[10:49] <Riddell> although much of its functionality could be done through kpackagekit (most privilaged operations are just package installs)
[10:49] <Riddell> also review features compared to the gtk frontend
[10:50] <valorie> Riddell: just read your email about project neon
[10:50] <valorie> I'll help with the dot article, etc. once techbase is updated
[10:50] <valorie> or work with shadeslayer etc.
[10:50] <bambee> Riddell: ok
[10:51] <valorie> I'll check with shadeslayer tomorrow
[10:55] <Riddell> thanks valorie
[11:09] <bambee> Riddell: Added in my todo, I'll try to do my best :)
[11:10] <Riddell> neversfelde: what's the status of bug 683439 ?
[12:32] <shadeslayer> valorie: sure i'm free tomorrow .... :)
[12:32] <Riddell> shadeslayer: and you think neon will be ready to annonce?
[12:32] <shadeslayer> well ... it works, you can login etc ... PIM does not work, so apart from that it's good to go imo
[12:33] <shadeslayer> yofel: Quintasan_ ^^ opinions
[12:33] <Riddell> shadeslayer: is the techbase page up to date?
[12:33] <shadeslayer> A bit of it is outdated
[12:34] <yofel> Riddell: I'll have that done till tomorrow, it's mostly done
[12:35] <shadeslayer> Riddell: did you read about the nokia internal memo on engadget?
[12:35] <yofel> other than that, kdepim doesn't work right until we work out akonadi, and I have no idea if anything related to python actually works or not (rather not)
[12:35] <yofel> besides that, it works
[12:36] <shadeslayer> oh and i still have to start kwin manually ...
[12:36] <shadeslayer> dunno about you guys
[12:37] <yofel> WFM last time I tried it
[12:38] <Riddell> yofel: yeah so we just warn people not to install kdepim
[12:38] <Riddell> shadeslayer: all rumours until tomorrow
[12:38] <shadeslayer> yep
[12:39] <shadeslayer> http://www.reuters.com/article/2011/02/09/nokia-meego-idUSLDE7180X420110209 << :S
[12:40] <Riddell> that doesn't tell us much except that meego is going slower than hoped, which is well known
[12:40] <KRF> shadeslayer: fyi, there's already a follow-up on that article on reuters
[12:40] <shadeslayer> yeah .... it's wait and watch
[12:41] <shadeslayer> KRF: oh ... lemme look
[12:41] <KRF> but still, rumours...
[12:41] <shadeslayer> yeah
[12:41] <shadeslayer> i do hope they don't drop it
[12:42] <shadeslayer> i'd say go for Android till Meego is fully usable
[12:43] <Riddell> I'd say go with Kubuntu
[12:43] <Riddell> I expect that's what their secret plan is
[12:44] <shadeslayer> hehehe ....
[12:44] <shadeslayer> one can only hope :)
[12:46]  * shadeslayer needs to get his LCD Panel replaced
[14:09] <Quintasan> Riddell, shadeslayer, yofel: Yes, we can release tomorrow. SIP needs to get installed in /opt/project-neon, right?
[14:11]  * Quintasan has winter holidays like in two days so he can work on appearing bugs
[14:11] <yofel> well yes, that's probably the most annoying issue for maverick currently
[14:11] <Quintasan> It's maverick only issue?
[14:12] <yofel> well, we don't need to backport it for natty...
[14:12] <Quintasan> What happens if we backport new SIP?
[14:12] <yofel> we need to rebuild pykde
[14:12] <Quintasan> Can't we rebuild both SIP and PyKDE in our PPA?
[14:12] <Quintasan> I can imagine something will break
[14:13] <yofel> maybe just drop SIP in neon completely as we don't have pykde currently anyway
[14:13] <yofel> Quintasan: sure, how do you put rebuilds for all available kdebindings versions for maverick into one ppa?
[14:13] <Quintasan> Wurgh
[14:13] <Quintasan> no thanks
[14:13] <yofel> see
[14:13] <Quintasan> Well, still noone wants to touch qtscriptgenerator
[14:14] <yofel> easiest workaround currently is to use kubuntu-ppa/backports with neon, but not everyone will probably want to do that
[14:14] <Quintasan> I will do this tomorrow or the day after
[14:14] <yofel> Quintasan: I can build amarok fine in natty without neon, with neon I get a link error in the taglib cmake test
[14:16] <yofel> so we would need to fix our tagblib first I guess..
[14:27] <nigelb> Quintasan: hey
[14:57] <Riddell> shadeslayer: did you get your patch to KDM in?
[15:04] <shadeslayer> Riddell: not yet, i cloned the repo today, still reading up on KAuth and finding the Gnome bits
[15:04] <shadeslayer> apachelogger says the patch is not complete :>
[15:05] <shadeslayer> sadly project-neon-kdebase-apps depends on too many things :(
[15:06] <shadeslayer> well ... i could just dirty my /opt/project-neon and it will be fixed by dpkg later on
[15:08] <Riddell> anyone know how kdm choses its default theme?
[15:08] <shadeslayer> yofel: don't think we ship pykde
[15:12] <shadeslayer> afiestas: have a look at gnome-disk-utility
[15:13] <shadeslayer> they got it right imo
[15:13] <afiestas> shadeslayer: okiz
[15:13] <afiestas> today Uninstall will show me KFormat which seems that it already is kinda working
[15:13] <afiestas> using udisk and so on, so with a little bit of luck I will have only to write a new interface, or modify the curret one
[15:14] <shadeslayer> :)
[15:15] <shadeslayer> great ... now i'm getting SMS Spam -.-
[15:16]  * Riddell works it out
[16:34] <Riddell> ah, maco, good morning
[16:41] <Riddell> debfx: best update the /topic too
[16:46] <shadeslayer> Riddell: can you haz a look at dcmtk ?
[16:46] <Riddell> shadeslayer: yes in a bit
[16:46] <shadeslayer> ok :)
[16:46] <Riddell> debfx: incase I forget (shouldn't do but you never know) call me, jriddell.org/contact.html
[16:48] <debfx> Riddell: okay
[16:48] <shadeslayer> hahah
[16:48] <shadeslayer> http://fluffy.jussi01.com/
[16:49] <shadeslayer> apachelogger: ^^ Ubottu now owns fluffy?
[17:22] <Riddell> maco: so, fancy reviewing my owncloud package?
[17:22]  * maco wonders how big a package it is
[17:23] <maco> i dont mind doing it, just wonder whether i can do it from home or need to find decent wifi
[17:23] <Riddell> it's weeny
[17:25] <maco> ok
[17:25] <maco> there's a new official chinese version of ubuntu apparently
[17:25] <maco> this was not mentioned on ubuntu-devel ml!
[17:28] <Riddell> yes, that did surprise me too
[17:29] <Riddell> that'll be freeflying at work
[17:49] <afiestas> Riddell: did you test Kamoso last 2.0 code?
[17:50] <Riddell> afiestas: I tested alpha 2
[17:51] <Riddell> if that's what you're asking?
[17:52] <afiestas> Riddell: nope, pre-alpha3 would be
[17:52] <afiestas> (or it may be beta1)
[17:52] <afiestas> it should fit in your laptop
[17:52] <Riddell> afiestas: where can I find it?
[17:53] <afiestas> git.kde.org/kamoso
[17:54] <afiestas> shadeslayer: I'm taking a look at gnome-disk-utility isn't it too advanced?
[17:54] <afiestas> I'm mean,  sure we need in kde something like that, for what I wanted to do is something way simpler
[17:59] <debfx> afiestas: why is the bluedevil menu entry in the Internet category? shouldn't it be in System?
[18:04] <afiestas> debfx: in fact, I'm thinking on remove the entry for 1.1
[18:04] <afiestas> bluedevil is something "system wide" so there is no point on executing it
[18:09] <Riddell> afiestas: I just submitted a fix to kamoso, now I feel elite
[18:11] <afiestas> Riddell: thanks, I forgot to that that patch
[18:11] <afiestas> commit the fixed in 2.0 though, and then forward to master
[18:12] <Riddell> afiestas: kamoso works nicely on my netbook now thanks
[18:12] <Riddell> doesn't work on my new laptop though, no camera image
[18:12] <afiestas> Riddell: even the last 2.0 code?
[18:13] <afiestas> with 2.0 I mean 2.0 branch on git
[18:13] <debfx> afiestas: the bluedevil tray icon is autostarted anyway, right?
[18:14] <Riddell> afiestas: git checkout remotes/origin/2.0  ?
[18:14] <debfx> Riddell: is the akonadi tray useful to the average user? I think we should move it into an own package
[18:14] <afiestas> debfx: yes, by BlueDevil kded (only starts it if there is a bleutooth adapter)
[18:14] <afiestas> Riddell: yes
[18:14] <afiestas> if it is not working, can you provide me the terminal output?
[18:15] <Riddell> debfx: I agree
[18:15] <debfx> afiestas: are you sure? bluedevil is running in my natty VM
[18:16] <afiestas> debfx: I'm sure
[18:17] <Riddell> afiestas: http://paste.kde.org/4478/  nothing useful
[18:17]  * Riddell goes out canoeing
[18:17] <debfx> afiestas: the kcm says no bluetooth adaper found but the service and tray icon are running
[18:17] <afiestas> Riddell: enable Kamoso debug area
[18:17] <afiestas> in kdebugdialog
[18:18] <afiestas> debfx:  close it, restart the VM and tell me if it is autoexecuted again
[18:19] <afiestas> maybe (I don't know how these things work) the default KDE session included in Natty has it
[18:20] <debfx> Riddell: have fun :)
[18:22] <debfx> afiestas: I always start with an empty session, it's still autostarted
[18:23] <debfx> when I disable bluedevil in the kcm it's not autostarted anymore
[18:23] <afiestas> debfx: kdebugdialog --fullmode
[18:23] <afiestas> select kded, output to a file
[18:24] <afiestas> (enable bd again in the kcm), and reboot (logout/login)
[18:24] <afiestas> well, you can restart kded4 :p
[18:24] <afiestas> and if you prefer, copy/paste the output to paste.kde.org
[18:30] <debfx> how am I supposed to find kded4 in that huge dropdown list? ^^
[18:31] <afiestas> debfx: ok, forget about that
[18:31] <afiestas> execute
[18:31] <afiestas> kdebugdialog (withotu arguments)
[18:31] <afiestas> search for kded, activate it
[18:31] <afiestas> go to a terminal, and execute
[18:32] <afiestas> "killall -9 kded4; kded4 --nofork"
[18:32] <afiestas> and paste the output in paste.kde.org for example
[18:33] <DarkwingDuck> Riddell: was tazz someone new?
[18:33] <debfx> afiestas: that's much easier, thanks :)
[18:33] <debfx> afiestas: http://paste.kde.org/4480/
[18:34] <afiestas> debfx: sorry my mistake (I was preparing a coffee :p)
[18:34] <afiestas> debfx: not enough information mmm activate everything "bluedevil" :p
[18:36] <debfx> afiestas: no such thing in the list
[18:37] <afiestas> in kded, you have both, the one with the number
[18:38] <afiestas> and the one without it?
[18:39] <DarkwingDuck> tazz, I was just talking about you. :P
[18:39] <afiestas> debfx: ok, there is no need for that
[18:39] <afiestas> I'm just checking the code, and don't tell me why but bluedevil-monolithic is always executed :(
[18:39] <tazz> DarkwingDuck, consider me, the devil :p
[18:40] <DarkwingDuck> tazz: Not if you are asking about documentation I wont. :P:P
[18:40] <tazz> DarkwingDuck, i was...
[18:40] <tazz> DarkwingDuck, i write documentation for kde, i was wondering how i could help out...
[18:41] <afiestas> debfx: I will fix that for 1.1 (the one that Natty will include)
[18:42] <tazz> damn... xchat crashed...
[18:42] <DarkwingDuck> Welcome back... xchat?
[18:42] <tazz> DarkwingDuck, yea.. stupid reason dont ask :)
[18:42] <DarkwingDuck> tazz: :) You use BZR?
[18:43] <tazz> DarkwingDuck, nope...
[18:44] <DarkwingDuck> BZR is the version control system that we use.
[18:44] <DarkwingDuck> taz apt-get install bzr
[18:44] <DarkwingDuck> tazz: ^^
[18:45] <DarkwingDuck> tazz: it intergrates with Launchpad very very well. :)
[18:45] <tazz> what do ya know, i already have it installed... must be using it a year a go or somthing...
[18:45] <DarkwingDuck> :)
[18:45] <tazz> :p
[18:45] <DarkwingDuck> tazz: bzr branch lp:kubuntu-docs
[18:45] <tazz> cool, so i should pull the documentations ?
[18:46] <DarkwingDuck> tazz: the Todo list is found at https://wiki.kubuntu.org/Kubuntu/Todo/Natty
[18:46] <tazz> got it...
[18:47] <DarkwingDuck> tazz: we use docbook for the docs.
[18:47] <tazz> nice, so does kde...
[18:47] <DarkwingDuck> Awesome.
[18:47] <DarkwingDuck> actually... I've been wanted to help with KDE docs :)
[18:47] <DarkwingDuck> So will will be mutual bentificial
[18:48] <jjesse> kde docs use docbook as well
[18:48] <tazz> DarkwingDuck, thats cool...
[18:48] <DarkwingDuck> Hey jjesse
[18:48] <DarkwingDuck> tazz: jjesse is another one of our senior doc gurus
[18:48] <tazz> hello jjesse!
[18:49] <DarkwingDuck> Speaking of... that is what I am working on today jjesse more docs
[18:49] <tazz> DarkwingDuck, you should join the kde-doc-english ml
[18:49] <DarkwingDuck> Joined.
[18:49] <jjesse> hiya tazz
[18:49] <jjesse> yay for doc work
[18:49] <DarkwingDuck> We are actually running out of time.
[18:50] <tazz> so yea, that was one of my questions... do we use upstream docs for kde apps ?
[18:50] <jjesse> yes we do
[18:50] <jjesse> as much as we can
[18:50] <jjesse> DarkwingDuck when is doc freeze?
[18:50] <DarkwingDuck> Apr 7
[18:51] <DarkwingDuck> tazz: our docs are more of an overview of what is installed with Kubuntu and how to manipulate/configure things.
[18:52] <DarkwingDuck> jjesse: the feature freeze is on the 24th
[18:52] <tazz> i see...
[18:53] <jjesse> when is string freeze?
[18:53] <DarkwingDuck> jj Documentation String freeze is the Apr 7
[18:53] <DarkwingDuck> jjesse: ^^
[18:54] <DarkwingDuck> tab fail
[18:54] <DarkwingDuck> jjesse: https://wiki.ubuntu.com/NattyReleaseSchedule
[18:54] <DarkwingDuck> Translations only have 14 days?
[18:55] <jjesse> apparently
[18:55] <DarkwingDuck> fail
[18:55] <DarkwingDuck> Anywho
[18:56] <DarkwingDuck> tazz: any major questions?
[18:57] <tazz> DarkwingDuck, none at the moment, I am just checking out the kubuntu-docs folder
[18:57] <DarkwingDuck> tazz: +1 what do you guys use for KDE docs?
[18:58] <DarkwingDuck> tazz: http://doc.bazaar.canonical.com/en/
[18:59] <DarkwingDuck> tazz: that will help understand bzr better. When you create a patch email myself<EMAIL_ADDRESS>or jjesse<EMAIL_ADDRESS>the diff and we will upload it.
[18:59] <tazz> DarkwingDuck, we use meinproc4
[18:59] <tazz> http://manpages.ubuntu.com/manpages/lucid/man8/meinproc4.8.html
[19:00] <tazz> but we use meinproc4 from the kde trunk itself.
[19:00] <DarkwingDuck> Ahhhh
[19:00] <DarkwingDuck> what do you use for svn?
[19:00] <tazz> DarkwingDuck, we are shifting from svn to git.
[19:00] <tazz> but i just use commandline
[19:00] <tazz> svn up, svn co, svn update
[19:01] <DarkwingDuck> Yeah, I use commandline for bzr too
[19:01] <tazz> it used to be svn+ssh
[19:01] <tazz> and svn+http
[19:01] <tazz> but now everything is going under git.
[19:01] <DarkwingDuck> I think there is a GUI for bzr but, i've never used it.
[19:01] <tazz> ah i see...
[19:25] <DarkwingDuck> Who does the Kubuntu website?
[19:27] <DarkwingDuck> Riddell: ping
[19:43] <ari-tczew> Riddell: look forward for sponsorship bug 716639
[21:40] <blackmoon-105> hi, my /usr/bin/X use a 80% of cpu  and slow all.. i'm under kubuntu 10.10 geeforce 6600GT  (driver nvidia-185   ver.  260.19.06)
[21:52] <ScottK> agateau: It looks to me like currently app menu doesn't work with gtk apps out of the box for us.  I assume we'd need to seed some additional packages.  Do you know what we'd need?
[22:02] <JontheEchidna> works w/ appmenu-gtk for me
[22:41] <ari-tczew> Riddell: could you sponsor this one for me as well? bug 716748
[22:43] <ryanakca> DarkwingDuck: It depends on what you want, if you want a story added, several people around here have the password to the site, if you want a change to the appearance, I think ofirk or shadeslayer are working on it.
[22:43] <Riddell> blackmoon-105: we're not really X people, best to ask in the x channel or mailing list
[22:44] <Riddell> ari-tczew: e-mail me, I'll get them in the morning
[22:44] <ari-tczew> Riddell: yeah!
[22:45] <ari-tczew> Riddell: done
[23:10] <blackmoon-105> Riddell: ok, i ask yo x channel. i've asked here because i tought it was related with kde4
[23:51] <valorie> shadeslayer: ping


[01:38] <callmepk> good morning
[05:46] <jibel> Good morning everyone!
[05:48] <oSoMoN> good morning desktoppers
[05:55] <jibel> Salut oSoMoN
[05:56] <oSoMoN> salut jibel
[06:09] <callmepk> hi jibel oSoMoN
[06:15] <oSoMoN> hey callmepk
[06:23] <jibel> Hi callmepk
[06:30] <ricotz> good morning :)
[06:36] <jibel> callmepk, regarding wsl-integration.sh issue I'd go with a simpler syntax than the proposed fix. ig UBUNTU_WSL_GUI_THEME=${UBUNTU_WSL_GUI_THEME-}
[06:36] <jibel> instead of adding a function to check the sanity of the variables
[06:36] <jibel> what do you think?
[06:37] <oSoMoN> good morning ricotz
[06:38] <jibel> good morning ricotz
[06:39] <callmepk> hi ricotz
[06:39] <callmepk> jibel let me check it now
[06:40] <jibel> callmepk, I can propose a patch if you prefer
[06:43] <callmepk> jibel I am a bit confused, can you help me propose a patch? Thanks!
[06:43] <jibel> callmepk, that should do it https://paste.ubuntu.com/p/GyMYjSVtk8/
[06:44] <jibel> i'll test it and propose something
[06:45] <callmepk> I will test it now
[06:49] <jibel> callmepk, is there a reason to declare the variables readonly ?
[06:51] <jibel> https://paste.ubuntu.com/p/zmWJqy9Cc8/ without RO variables
[06:52] <callmepk> jibel it is mostly used to prevent accidental change of the vaiable
[06:53] <jibel> right, but since we maintain the script. Also the way it's done, if you make a typo in the conf file, then you'll declare a variable that doesn't exist in the script.
[06:54] <jibel> I mean since we maintain the script there is little risk to accidentally change the variable
[06:55] <callmepk> Okay
[06:58] <jibel> but it's just a proposal, do as you prefer
[07:06] <didrocks> good morning
[07:07] <callmepk> hi didrocks
[07:07] <didrocks> hey callmepk
[07:08] <jibel> Salut didrocks
[07:09] <didrocks> salut jibel
[07:09] <seb128> goood morning desktopers
[07:09] <jibel> salut seb128
[07:09] <seb128> hey didrocks, didrocks, callmepk, how are you?
[07:09] <callmepk> hi seb128
[07:12] <callmepk> I am okay seb128 , how about you?
[07:12] <seb128> I'm alright, had a busy but nice weekend and it's nice and sunny today
[07:13] <didrocks> salut seb128, ça va :)
[08:04] <laney> \o
[08:10] <marcustomlinson> morning all
[08:14] <jibel> morning marcustomlinson laney
[08:15] <marcustomlinson> hey jibel
[08:27] <oSoMoN> good morning didrocks, seb128, laney, marcustomlinson
[08:28] <didrocks> salut oSoMoN, hey marcustomlinson, laney
[08:29] <laney> hey marcustomlinson jibel oSoMoN didrocks
[08:34] <marcustomlinson> hey oSoMoN didrocks laney
[08:39] <callmepk> morning laney marcustomlinson
[08:44] <laney> ahoy callmepk!
[08:45] <marcustomlinson> hi callmepk
[08:45] <jibel> callmepk, I merged the fix from microhobby then when you have a minute to review https://github.com/canonical/ubuntu-wsl-integration/pull/4
[08:45] <gitlab-bot> canonical issue (Pull request) 4 in ubuntu-wsl-integration "Simplify variable declaration check" [Open]
[08:45] <jibel> we can then do a release
[08:49] <callmepk> jibel I have tried with some other ways like trap but with no luck, so I merged it
[08:52] <jibel> yeah, same. Since it's sourced when the session is initialized it's a bit tricky. However failing to start if this scripts fails seems okay, since we wouldn't be able to properly initialize the wsl session
[09:01] <laney> jibel: callmepk: not sure if intentional, but if you use the "${FOO-}" form rather than "${FOO:-}" then it doesn't fire for set-but-empty (like if someone uses "FOO=" in a script to clear it instead of using "unset"), usually you want the latter
[09:06] <jibel> laney, it is intentional
[09:07] <laney> alright, I saw bool-like values and thought that it would be odd if they ended up empty
[09:07] <laney> but as long as you did it on purpose
[10:30] <ricotz> seb128, hi :)
[12:30] <cpaelzer> hi, I'm unsure about https://launchpad.net/ubuntu/+source/xrdp/0.9.15-1 while on +1 duty
[12:31] <cpaelzer> is this something the desktop team would look after anyway or is this +1-worthy as it would otherwise be languishing in -proposed?
[12:31] <callmepk> jibel Sorry for being late, but I got the new version ready on github: https://github.com/canonical/ubuntu-wsl-integration/releases/tag/v0.31.3. Could you help me on uploading?
[12:42] <jibel> callmepk, sure
[12:42] <callmepk> thanks jibel
[13:24] <didrocks999> callmepk: sponsored!
[13:24] <callmepk> Thanks didrocks999 !
[13:26] <didrocks999> yw :)
[14:37] <seb128> ricotz, hey, sorry forgot to reply earlier, how are you?
[14:39] <ricotz> seb128, hey, I am good, finally some sunny days, how are you?
[14:39] <ricotz> seb128, I noticed you retried libreoffice, this might be a real issue
[14:40] <ricotz> I have triggered autopkgtests for the hirsute ppa builds of the identical source
[14:41] <ricotz> the newer openjdk-lts package might be the cause
[14:41] <ricotz> hey hellsworth
[14:46] <seb128> ricotz, ok, thanks for the headsup, I usully retry once in case it's flaky
[14:46] <ricotz> seb128, I already retried it earlier ;) https://autopkgtest.ubuntu.com/packages/libr/libreoffice/impish/armhf
[14:47] <seb128> right, it was not there at the time I retried, the website doesn't make it easy to see if there is already a pending retry
[14:48] <ricotz> so java is crashing there, if the hirsute/armhf autopkgtest, I would suggest to force libreoffice to transition to avoid blocking things
[14:48] <hellsworth> good day desktopers, nice to be back after a week off
[14:48] <seb128> hey heather, wb!
[14:48] <hellsworth> thanks!!
[14:49] <seb128> ricotz, we should perhaps retry 1:7.1.3-0ubuntu1 see if that regressed
[14:50] <ricotz> seb128, that sounds good
[14:51] <ricotz> please do so
[15:10] <oSoMoN> welcome back hellsworth
[15:11] <hellsworth> thanks oSoMoN :)
[15:31] <jibel> Good morning hellsworth
[15:31] <hellsworth> hi there jibel :)
[16:57] <KGB-1> tracker pristine-tar 3904927 Iain Lane tracker_3.1.1.orig.tar.xz.delta tracker_3.1.1.orig.tar.xz.id * pristine-tar data for tracker_3.1.1.orig.tar.xz * https://deb.li/3ESth
[16:57] <KGB-1> tracker upstream/latest d13ffe4 Iain Lane * pushed 1405 commits (first 5 follow) * https://deb.li/5762
[16:57] <KGB-1> tracker upstream/latest c78a0f7 Carlos Garnacho src/libtracker-data/tracker-data-manager.c * libtracker-data: Plug leak * https://deb.li/3XYfC
[16:57] <KGB-1> tracker upstream/latest 4b20a14 Carlos Garnacho src/libtracker-sparql/tracker-endpoint-dbus.c * libtracker-sparql: Plug leak * https://deb.li/JYoU
[16:57] <KGB-1> tracker upstream/latest 19ce818 Carlos Garnacho src/libtracker-data/tracker-data-manager.c * libtracker-data: Plug leak * https://deb.li/3GirF
[16:57] <KGB-1> tracker upstream/latest 45b44b9 Carlos Garnacho src/libtracker-sparql/tracker-namespace-manager.c * libtracker-sparql: Plug leak on API misuse * https://deb.li/3Usw7
[16:57] <KGB-1> tracker upstream/latest 143f1bb Carlos Garnacho src/libtracker-data/tracker-db-interface-sqlite.c * libtracker-data: Plug leak * https://deb.li/it7Yd
[16:59] <laney> TBC
[18:46] <KGB-1> gnome-control-center signed tags 0d7e35e Marco Trevisan ubuntu/1%3.38.6-0ubuntu2 * gnome-control-center Debian release 1:3.38.6-0ubuntu2 * https://deb.li/ZJ9G
[18:46] <KGB-1> gnome-control-center ubuntu/master af5ed95 Marco Trevisan (Treviño) debian/patches/ series 0033-display-Ensure-we-list-available-scaling-values-keeping-t.patch * debian/patches: Ensure we list all the usable scaling values * https://deb.li/3LMWM
[18:47] <KGB-1> gnome-control-center ubuntu/master 84c9686 Marco Trevisan (Treviño) debian/patches/0008-Allow-tweaking-some-settings-for-Ubuntu-Dock.patch * debian/patches: Do not leak a variant builder on single monitor setup * https://deb.li/08Xy
[18:47] <KGB-1> gnome-control-center ubuntu/master 6a8d9b9 Marco Trevisan (Treviño) debian/changelog * Update changelog * https://deb.li/ipxd4
[18:47] <KGB-1> gnome-control-center ubuntu/master 37a8d30 Marco Trevisan (Treviño) debian/changelog * Upload to impish * https://deb.li/jVxe


[15:34] <Craig> ello.  I am running the 18.10 version.  I didn't realize I needed to manually update my system all of these years.  How do I update to 22.04?
 Fresh install, saving your /home directory, is probably the easiest way at this point
 Otherwise you'll be going 18.10 -> 19.04 -> 19.10 -> 20.04 -> 22.04 heh
[15:38] <Craig> Thank you.  To do a fresh install, how do I launch that?  I'm a senior citizen.  My son-in-law installed Lubuntu for me.  So, I'm not familiar with the process.
[15:41] <Craig> I found this...https://linuxconfig.org/how-to-upgrade-ubuntu-to-22-04-lts-jammy-jellyfish  Would this work?
 https://manual.lubuntu.me/stable/1/1.1/retrieving_the_image.html
 Follow the steps
[19:20] <lubuntero> Hi everyone , I have 2 questions related, There is no oficial backports PPA to lubuntu 22.10, right? , I asked because I was trying to find the safest way to update lxqt to 1.2 version.
[19:30] <tomreyn> lubuntero: if you look at the "published in" drop down at https://launchpad.net/~lubuntu-dev/+archive/ubuntu/backports you'll see it only lists "jammy" (22.04), so i guess there's no backports for 22.10 (yet?).
[19:32] <tomreyn> the backports-staging ppa also has packages published for "jammy" only. https://launchpad.net/~lubuntu-dev/+archive/ubuntu/backports-staging
[19:32] <lubuntero> Yeah I found 2 versions of backports PPA and both had the 1.1.0 version.
[19:34] <tomreyn> so i assume upgrading to lxqt 1.2 won't be an option anytime soon
[19:35] <tomreyn> it's probably a major effort to make that possible / compatible, so i'd guess the next lxqt upgrade won't become available before a new release.
[19:37] <tomreyn> but that's just a guess, you might want to ask this in #lubuntu-devel, too
[19:48] <lubuntero> If anyone is interested too, from lubuntu-devel:
[19:48] <lubuntero> There are no plans for 22.10, as it's only an interim release, but there definitely are plans for 22.04
[19:49] <lubuntero> For LXQt 1.2, I'd estimate before the end of the year
[19:49] <lubuntero> See you over the net people, bye.


[05:32] <superm1> ah too bad, the mythbox plugin for xbmc eden still doesn't support 0.25
[05:33] <superm1> also doesn't do any upnp stuff to auto fill settings either
[05:35] <tgm4883> superm1, yea the pvr stuff is aimed at eden+1 right nwo
[05:35] <tgm4883> now
[05:36] <superm1> well i hope the mythbox guys plan to add services api support
[14:24] <adam_112> I've been on this channel the last couple of days with a livetv problem. Basically the stream would start run for 5-10 secs when end. I've think I've found my issue. My Cable company has the cgms copy-once flag set on almost all the channels. Shouldn't myth fail more gracefully and let me know of this issue?
[14:25] <rhpot1991> adam_112: you shouldn't be able to view those with hdhr-gui then either
[14:25] <rhpot1991> and you said you could
[14:25] <rhpot1991> adam_112: TWC?
[14:26] <rhpot1991> your recordings should also fail and you said they worked
[14:26] <rhpot1991> guessing you were testing vlc and recordings with a local channel and livetv with something else?
[14:50] <adam_112> That could be.  I was testing different channels so maybe I got lucky.  I can't remember my exact testing sequence. I actuallay discovered this while using the quicktv app in windows.  So I'm no 100% sure this is the only problem I'm having with MythTV.  The Cable Company is coming out later today.   Once we get the cgms fixed  I'll continue testing Myth and take more detail notes if I have...
[14:50] <adam_112> ...problems.
[15:12] <rhpot1991> adam_112: good luck with getting those flags fixed, most people at the cable company have no idea what you are talking about
[15:12] <rhpot1991> adam_112: what cable provider?
[15:16] <adam_112> knology  I had to push for a self install.  So, it should be interesting. :)
[15:17] <adam_112> Wagnerrp says that the cgms flag is not used much anymore.
[15:23] <rhpot1991> some cable cos like TWC turn it on for everything except locals and will not modify otherwise
[15:44] <adam_112> If that is the case I'm screwed?
[15:49] <rhpot1991> adam_112: pretty much
[15:49] <rhpot1991> the fact that its a smaller cable co, you may be able to get somewhere


[14:46] <ema> hi! What is the procedure to follow to request a kernel patch backport? Specifically in this case https://github.com/torvalds/linux/commit/ae2df912d1a557a3548be83da20851ac55f42ab3 to 22.04
[14:46] -ubottu:#ubuntu-kernel- Commit ae2df91 in torvalds/linux "ACPI: CPPC: Disable FIE if registers in PCC regions"


[04:02] <freshblueO3> I'm having trouble with my apt-get installer. I believe I messed it up while trying to fixed a corrupted? update. I would like to manually try to fix it, and I can go into detail, but am I in the right place?
[09:47] <cjwatson_> freshblueO3: no, we're more about initial install of the whole system here. I suggest #ubuntu
[09:48] <cjwatson> (or answers.launchpad.net/ubuntu or #ubuntu+1 or ...)
[10:52] <siretart> in what cases does d-i create loop entries in /target/etc/fstab?
[11:30] <siretart> cjwatson: I've been thinking a bit more about the uuid issue in partman-crypto. I think we should add somehting like http://paste.debian.net/38416 to partman-target
[11:30] <siretart> I'm not committing it yet, because I want to test it tomorrow on the testmachine in my office first
[11:35] <siretart> hm perhaps rather http://paste.debian.net/38418
[11:45] <cjwatson> loop entries> wubi
[11:45] <cjwatson> siretart: could I have a diff instead, please?
[11:46] <cjwatson> and writing $crypttab to /etc/fstab is just odd
[11:52] <CIA-18> ubiquity: cjwatson * r2284 ubiquity/ (4 files in 3 dirs): * Forbid consecutive, initial, or final dots in hostnames (LP: #105890).
[11:54] <CIA-18> ubiquity: cjwatson * r2285 ubiquity/debian/ (changelog control):
[11:54] <CIA-18> ubiquity: * Make ubiquity-frontend-gtk depend on gconf2, since it calls gconftool-2
[11:54] <CIA-18> ubiquity:  (thanks, Kev Rees).
[11:56] <siretart> cjwatson: it is not a diff, but a new file
[11:56] <siretart> cjwatson: I can add it to the branch if you want, but as said, it is totally untested
[11:57] <CIA-18> ubiquity: cjwatson * r2286 ubiquity/debian/ (changelog control): * Add missing Provides to ubiquity-frontend-mythbuntu.
[11:57] <cjwatson> siretart: I don't want there to be two scripts that write /etc/fstab; that's clearly wrong
[11:58] <cjwatson> did you mean it to write to /etc/crypttab instead?
[11:58] <siretart> argh
[11:58] <cjwatson> and presumably read from /etc/fstab
[11:58] <siretart> of course. I had it locally set to /tmp/crypttab
[11:58] <siretart> no, read from /target/etc/crypttab as well
[11:58] <cjwatson> it doesn't belong in partman-target
[11:59] <cjwatson> it should be in partman-crypto
[11:59] <siretart> that is written by partman-crypto and read by the cryptroot-hook
[11:59] <cjwatson> (which isn't in bzr)
[11:59] <siretart> yes. partman-crypto isn't diverged yet.
[11:59] <siretart> that's why I thought it might be easier to have it in partman-crypto
[12:00] <cjwatson> you mean "easier to have it in partman-target"?
[12:00] <cjwatson> no, please don't
[12:00] <siretart> ok. then I'll merge it into partman-crypto
[12:00] <siretart> is it okay to take the latest debian version? debian has a newer one (22, vs 21 in ubuntu)
[12:01] <cjwatson> it should probably also check whether /target/etc/crypttab exists
[12:01] <cjwatson> is there a good reason to?
[12:01] <cjwatson> it doesn't look useful
[12:01] <siretart> ok
[12:01] <cjwatson> we don't use loop-aes and I know that my mkdir -p change is not really relevant, it's just code tidying
[12:01] <siretart> I'll do it this afternoon then.
[12:02] <siretart> cu later!
[12:02] <cjwatson> thanks
[12:02] <CIA-18> ubiquity: cjwatson * r2287 ubiquity/debian/ (changelog control):
[12:02] <CIA-18> ubiquity: * Switch XS-Vcs-Bzr to the ~ubuntu-installer branch we're using at the
[12:02] <CIA-18> ubiquity:  moment.
[12:02] <cjwatson> aside from the above it looks fine to me
[12:03] <cjwatson> god knows how it'd interact with loop-mounted installs :)
[12:03] <cjwatson> but that's hardly urgent
[12:11] <CIA-18> ubiquity: cjwatson * r2288 ubiquity/build/ (intltool-extract.in intltool-merge.in intltool-update.in): update intltool files to 0.36.2
[12:23] <CIA-18> ubiquity: cjwatson * r2289 ubiquity/build/ (config.guess config.sub ltmain.sh): update libtool files to 1.5.24-1ubuntu1
[12:24] <CIA-18> ubiquity: cjwatson * r2290 ubiquity/configure: autogen.sh
[02:47] <CIA-18> ubiquity: cjwatson * r2291 ubiquity/debian/ (changelog rules):
[02:47] <CIA-18> ubiquity: * Stop installing doc/Changelog.Guadalinex as the upstream changelog, as
[02:47] <CIA-18> ubiquity:  it's no longer current.
[08:27] <CIA-18> ubiquity: cjwatson * r2292 ubiquity/ (35 files in 10 dirs): * Upgrade to gettext 0.16.1.
[08:27] <CIA-18> ubiquity: cjwatson * r2293 ubiquity/ (debian/changelog debian/control ubiquity/frontend/gtk_ui.py):
[08:27] <CIA-18> ubiquity: Revert gconf2 dependency, as it would be bad for Xubuntu. Instead:
[08:27] <CIA-18> ubiquity: * Check whether gconftool-2 exists before calling it.


[01:42] <nigel_nb> pleia2: just saw your mail
[01:43] <pleia2> nigel_nb: thoughts?
[01:43] <nigel_nb> mine is an intro to bzr
[01:43] <pleia2> I was hoping we could hash some of this out before our meeting on sunday so we don't bog the meeting down with it
[01:43] <nigel_nb> essentially what doctormo wrote on his blog in a asciidoc class form
[01:44] <pleia2> ok, so you talk about "log into bzr, here is how you commit changes.." etc?
[01:44] <nigel_nb> yes
[01:44] <nigel_nb> wrt to uclp
[01:45] <pleia2> great
[01:45] <nigel_nb> I've finished first draft of 5 sections (half)
[01:45] <pleia2> close to finishing that?
[01:45] <pleia2> ok :)
[01:45] <nigel_nb> since u want it escalated, I'll drop everything and get the first draft complete today and put it up for review
[01:46] <pleia2> thanks, you rock!
[01:46] <pleia2> now I need to track down BiosElement for asciidoc ;)
[01:46] <nigel_nb> :)
[01:47] <nigel_nb> you'll be available online?
[01:47] <nigel_nb> today i mean
[01:47] <pleia2> for another hour at least, I have a terrible cold that is making me sleep like 14 hours/day
[01:48] <nigel_nb> ah :P, join the club
[01:48] <nigel_nb> but I'm still kickin though
[01:48] <pleia2> :)
[01:48] <nigel_nb> I'll start off then, so I can check with you on language
[01:48] <pleia2> great, thanks
[01:54] <nigel_nb> pleia2: tircd shows you replies from people that you're not following?
[01:54] <pleia2> nigel_nb: the client doesn't control that, it's the twitter api
[01:55] <nigel_nb> oh ok :)
[01:56] <pleia2> but yeah, it does
[01:56] <nigel_nb> have to try it out later then
[01:56] <nigel_nb> oh, lp is down
[01:56] <pleia2> doh
[02:06] <BiosElement> pleia2: I'm around >.>
[02:06] <pleia2> hey BiosElement :)
[02:06] <pleia2> see my email?
[02:06] <BiosElement> Aye.
[02:07] <pleia2> where are we with asciidoc structure?
[02:07]  * pleia2 itches to write stuff
[02:07] <BiosElement> Ahh, that's a good question. >.>
[02:11]  * pleia2 watches her energy meter drop significantly faster than she had anticipated
[02:12] <pleia2> stupid cold!
[02:12] <nigel_nb_> pleia2: wanna hit the bed?
[02:12] <pleia2> yeah, I think that's where I'm headed :(
[02:12] <pleia2> I'll be around all weekend though
[02:12] <nigel_nb_> anyway, lp is down
[02:12] <nigel_nb_> anything I do stays in my system
[02:13] <nigel_nb_> asked in #launchpad, it was supposed to be up at 2345 UTC, but some delay.  So, there is no guarantee when it will be up
[02:13]  * pleia2 nods
[02:14]  * nigel_nb_ just noticed something great :)
[02:14] <nigel_nb_> I've finished 5/9 sections so far
[02:14] <pleia2> you rock :)
[02:16]  * nigel_nb_ blushes
[02:30] <nigel_nb> pleia2: if u're still here, I could use some help
[03:49] <BiosElement> heh, I love how "William Chambers doesn't use Launchpad" and yet my branches are still listed :P Gotta love half working systems. >.>
[03:49] <cprofitt> hey BiosElement long time no see dude...
[03:49] <BiosElement> Heya cprofitt
[03:49] <BiosElement> Aye, it's been ages. ^_^
[03:50] <cprofitt> you going to have some free time in Mid-December to do some asciidoc with me?
[03:50] <BiosElement> Speaking of AsciiDoc, I've got to figureout what's up with that. >.>
[13:00] <pleia2> doctormo!
[13:01] <pleia2> we need to talk about asciidoc soon :)
[13:12] <doctormo> Hey pleia2, we do indeed
[13:12] <doctormo> nigel is the obviouslly best persont o ask about writing, after myself.
[13:13] <doctormo> And I wanted BiosElement to get busy with the scripts for building the resulting documents
[13:13] <doctormo> But so far, no work has been done.
[13:13] <pleia2> I spoke with bioselement last night, he said it was in your court
[13:13] <doctormo> It is not
[13:13] <pleia2> I am not interested in scripts at this point, I want raw "how to do stuff"
[13:14] <pleia2> waiting for scripts is killing us
[13:14] <doctormo> Sure
[13:14] <pleia2> *I* don't even know how this all works :)
[13:14] <doctormo> Not these, these aren't important for writing
[13:14] <pleia2> bios was concerned that we don't have asciidoc structure yet
[13:14] <pleia2> so for writing we still just use odt?
[13:14] <doctormo> They're just build scripts, and it's with BiosElement, i'm waiting on him to get those into some order. But enough of that.
[13:15] <pleia2> ok, maybe you should touch base with him?
[13:15] <doctormo> I think Bios isn't accepting the structure that's there already. He wants to keep reinventing it.
[13:15] <doctormo> So it seems I need to.
[13:15] <pleia2> I thought the structure was too complicated?
[13:15] <pleia2> he wanted a simpler one
[13:15] <doctormo> It's not possible.
[13:16] <pleia2> ok - so we did decide upon a structure?
[13:16] <doctormo> Aye, that would be good.
[13:16] <pleia2> if we could get that documented it'd be great, a "this stuff goes here, this file is for this...."
[13:16] <pleia2> maybe with pretty pictures :)
[13:17] <doctormo> Yes, sorry for being absent, it's been busy with me visiting the UK, lots of family and such that need attention.
[13:19] <pleia2> no problem :)
[13:19] <pleia2> I just wanted to get some of this sorted before our meeting
[13:45] <doctormo_> huh my computer cut out
[13:45] <doctormo_> pleia2: if you responded I didn't get it
[13:45] <pleia2> all I said was that I wanted to try and get the asciidoc stuff on track before our meeting
[13:45] <pleia2> so we don't waste time and stall more saying "we need to do this stuff"
[13:46] <doctormo_> pleia2: The problem is that we have say 100 units of work to do, and a capacity to only do about 10 units per week, unless people can be convinced to do more work, there isn't much choice.
[13:48] <pleia2> so should we be telling people to write things in odt until we can sort out the asciidoc situation?
[13:49] <pleia2> I'd help if I could, but I don't even understand the asciidoc format
[13:50] <doctormo_> pleia2: We should be already (I thought that's what we were doing)
[13:50] <doctormo_> pleia2: But don't forget, there is as much structure in odt as there is in anything
[13:50] <pleia2> asciidoc has book directories and things that are confusing
[13:50] <doctormo_> The problems I can see is how much we'll have to rewrite because we don't have odt templates.
[13:51] <pleia2> I don't really understand how it works, or how to create things out of it
[13:51] <doctormo_> pleia2: asciidoc it's self is fairly direct, you create a text file, you run a command on it, it creates a pdf.
[13:52] <pleia2> ok, I'll have to look at it again, I thought there were more directories and files than that
[13:53] <doctormo_> pleia2: There are, but that's not ascii doc's fault, that's mine.
[13:55] <pleia2> hmm
[13:57] <pleia2> alright, I'll take a look later http://bazaar.launchpad.net/~ubuntu-learning-board/ubuntu-learning-materials/trunk2/files/head:/maintain/commandline-basics/ is a good example?
[13:57] <pleia2> this does seem reasonable
[13:57] <pleia2> I think I was confused by earlier versions
[14:00] <pleia2> do we have a document explaining the structure yet? If this is a good example I can write one for my own benefit, show it to you and you can confirm it's correct?
[14:03] <pleia2> sorry for being such a pain :)
[14:40] <nigel_nb> doctormo: ping
[14:41] <nigel_nb> pleia2: up yet?
[14:41] <pleia2> nigel_nb: yeah, but busy morning at work
[14:41] <nigel_nb> oh
[14:41] <pleia2> if you want me to review something just give me a link and I'll get to it when I have some time :)
[14:41] <nigel_nb> just wanted to let you know, I've pushed up to revision 12
[14:41] <nigel_nb> here's the branch https://code.launchpad.net/~nigelbabu/ubuntu-learning-materials/bazaar-introduction
[14:42] <nigel_nb> can u just do a review when you get time and ping/mail me?
[14:43] <pleia2> sure
[14:43] <pleia2> do you want technical testing too?
[14:43] <nigel_nb> thanks :)
[14:43] <nigel_nb> not really, I doubt if u can test it, since its not complete
[14:43] <nigel_nb> but, do let me know if the format gives you trouble
[14:43] <pleia2> ok :)
[14:44] <pleia2> thanks nigel_nb
[14:44] <nigel_nb> thanks to you too pleia2 :)
[14:44] <nigel_nb> hope you're doing better today
[14:44] <pleia2> thanks, I think I am a bit
[14:44] <nigel_nb> great :)
[15:07] <doctormo> nigel_nb: pong
[15:07] <nigel_nb> doctormo: oh great :)
[15:07] <nigel_nb> just wanted to tell I you I pushed to rev 12
[15:07] <nigel_nb> just 3 more sections to go
[15:08] <pleia2> \o/
[15:08] <doctormo> pleia2: Reviewing nigel_nb's branch will also give you a good example
[15:08] <pleia2> doctormo: ok, great
[15:08] <pleia2> thanks :)
[15:08] <ZachK_> hey pleia2
[15:08] <pleia2> I'll try to have this done by our meeting time on sunday
[15:08] <pleia2> hey ZachK_ :)
[15:08] <nigel_nb> doctormo: doing okay?
[15:09] <ZachK_> pleia2: any assistance give I can?
[15:09] <pleia2> ZachK_: same as before, you can link up to good existing documentation in the wiki
[15:09] <ZachK_> cool
[15:12] <doctormo> nigel_nb: One second
[15:12] <nigel_nb> okay
[15:14] <doctormo> nigel_nb: It looks great, I like the ssh key description
[15:15] <nigel_nb> doctormo: talsemgeest helped me with that one
[15:15] <nigel_nb> took a lot of trouble formatting it properly
[15:22] <doctormo> nigel_nb: I see, double cudos for getting help when required.
[15:23] <nigel_nb> well, lyz (I dont wanna ping her) went to bed coz she was sick, so had to find someone :P
[15:34] <nigel_nb> doctormo: I'm off to work then, catch you on meeting day
[15:34] <nigel_nb> or 2morrow
[15:57] <FFEMTcJ> mornin
[16:10] <doctormo> hey FFEMTcJ
[16:11] <FFEMTcJ> whats up doc?
[16:11] <FFEMTcJ> not that you have EVER heard that before
[16:11] <doctormo> FFEMTcJ: No never ;-)
[16:12] <nigel_nb> FFEMTcJ: he probably hasn't seen bugs bunny :P
[16:12] <nigel_nb> doctormo: have you?
[16:12] <FFEMTcJ> hehe
[16:13] <doctormo> nigel_nb: http://www.youtube.com/watch?v=CUYZYJ7XueI
[16:14] <nigel_nb> reminds me of the good old days
[16:14] <nigel_nb> when i was 6 and all I did was cartoon network
[16:14] <nigel_nb> aw, the music itself its nostalgic
[16:15] <doctormo> Oh Mur-dur!
[16:26] <FFEMTcJ> 29
[16:26] <FFEMTcJ> uggh
[16:26] <FFEMTcJ> 29
[16:26] <FFEMTcJ> wtf
[16:26]  * pleia2 offers FFEMTcJ a handful of /s, and the swear jar
[16:27] <FFEMTcJ> ty
[16:27] <FFEMTcJ> after 3 years, still not used to the lappy keyboard
[16:27] <FFEMTcJ> lol
[17:07] <ZachK_> wb ubuntulog
[21:20] <doctormo> hey BiosElement, we should talk
[21:20] <BiosElement> Hey doctormo, what's up?
[21:22] <mhall119|work> sounds serious
[21:24] <doctormo> hey mhall119|worknot really, just clarifying what structures are being promoted and taught.'
[21:25] <mhall119|work> okay
[21:25] <mhall119|work> cause that's how you start the "grandma died" conversation
[21:27] <doctormo> mhall119|work: we should talk
[21:27] <doctormo> mhall119|work: didyou know that peanuts are really beans?
[21:29] <mhall119|work> they're legumes
[21:30] <doctormo> Same thing
[21:30] <mhall119|work> legumes are the parent class of both beans and peanuts, according to wikipedia
[21:31] <mhall119|work> and wikipedia is never wrong
[21:31] <mhall119|work> at least, that's what I read on wikipedia
[21:31]  * mhall119|work just had the best idea for spam chain email
[21:32] <mhall119|work> I'm going to start an email rumor that going to snopes.com will infect your computer with a virus.
[21:32] <mhall119|work> who are you going to use to check if that's true or rumor?
[21:32] <_marx_> beautiful


 Looks like a regression in the v1 stream having 1.21-alpha1 in it again (https://bugs.launchpad.net/juju-core/+bug/1367987) and my installed 1.18 borking on it
[13:19] <mup> Bug #1367987: juju 1.18 and 1.20 cannot parse simplestreams containing version "1.21-alpha1" <hs-arm64> <landscape> <ubuntu-engineering> <juju-core:Fix Released by wallyworld> <juju-core 1.20:Won't Fix by axwalk> <juju-release-tools:Fix Released by sinzui> <https://launchpad.net/bugs/1367987>
[16:16] <themonk> lazyPower, hi
[16:17] <lazyPower> hey themonk
[16:18] <themonk> lazyPower, one of may charm has chrooted env so it conflict with lxc container in local but its ok in cloud service
[16:20] <themonk> i want my charm to be pushed in juju charm store, will charm store accept this limitation?
[16:20] <themonk> lazyPower, ^
[16:21] <lazyPower> themonk: you can get 'in the store' in your personal namespace without any fuss - if your charm has a limitation on the local provider it will need to be *clearly* documented in the readme so the reviewer understands this is expected behavior.
[16:21] <lazyPower> themonk: https://juju.ubuntu.com/docs/authors-charm-store.html#name-space-charms
[16:22] <themonk> lazyPower, ok
[16:22] <lazyPower> i did a write up on this as well if the documentation makes you go cross eyed: http://blog.dasroot.net/the-power-of-community-charming/
[17:58] <tvansteenburgh> noodles775: just ran charmguardian on your fire_wall optional branch, all tests pass on AWS
[17:59] <tvansteenburgh> noodles775: i'm about to update jenkins, then i'll kick off a build to run them on the other substrates
[18:37] <lazyPower> wait, noodles775 made ufw optional?
[18:37] <lazyPower> awesome, i implemented that locally lastnight. i should have looked.
[19:33] <noodles775> tvansteenburgh: Excellent, thanks.
[19:35] <noodles775> lazyPower: Yeah, I did. I'm still interested to know why you'd want to switch it off though? (unless it's just for testig locally, but even then, you can `juju run --unit myservice/0 "curl ..."`
[19:35] <lazyPower> local deployments, testing scenarios
[19:36]  * noodles775 nods
[20:07] <themonk> lazyPower, are you there?
[20:08] <lazyPower> themonk: in a meeting
[20:08] <lazyPower> whats up?
[20:09] <themonk> how long it takes a charm review process, in genarel
[20:14] <lazyPower> themonk: depends on a few factors - 1) how ready is your charm for the review so it gets expedited after first touch, 2) how many charms are in the queue before you
[20:15] <lazyPower> themonk: i'll re-iterate, if you puiblish to your namespace, it wont be subject to a ~charmer review, and will be available at the next ingest (which happens ~ every 30 minutes)
[20:16] <lazyPower> themonk: but if you want to due your due dilligence in preparation for ~charmer review - this is the criteria in which we evaluate charms:  https://juju.ubuntu.com/docs/authors-charm-policy.html
[20:19] <themonk> lazyPower, i was reading this doc i have made a check list :)
[20:19] <themonk> lazyPower, thanks :)
[20:21] <lazyPower> no problem
[20:54] <tvansteenburgh> noodles775: http://reports.vapour.ws/charm-tests/charm-bundle-test-5034-results
[20:54] <tvansteenburgh> noodles775: dunno why the timeouts happen, trying to figure that out now
[20:59] <jrwren> what is the correct url for agent-metadata-url for 1.21-alpha2? i had been using https://streams.canonical.com/juju/devel/tools but that is not working
[21:01] <jrwren> http://streams.canonical.com/juju/tools/streams/v2/ ?
[21:01] <tvansteenburgh> jrwren, tools-metadata-url:  https://streams.canonical.com/juju/devel/tools is what i have
[21:01] <jrwren> tvansteenburgh: have you bootstrapped with that today?
[21:02] <tvansteenburgh> yes
[21:02] <jrwren> tvansteenburgh: thanks. now I know its me.
[21:02] <tvansteenburgh> jrwren, note tools vs agent
[21:03] <jrwren> tvansteenburgh: 1.21-alpha2 tells me to use agent- not tools-
[21:03] <tvansteenburgh> hrm, ok
[21:03] <jrwren> i just tried it with tools same fail for me.
[21:04] <tvansteenburgh> oh you're right, tools- was replaced with agent-
[21:20] <tvansteenburgh> jrwren: see sinzui's email from 4 minutes ago (if you haven't yet)
[21:24] <sinzui> tvansteenburgh, jrwren tools-metadata-url was renamed to agents-metadata-url in alpha2...the later will continue to work for as long as we support trusty
[21:25] <sinzui> jrwren, are you using  a public cloud or a private cloud
[21:26] <jose> lazyPower: hey, I had that one locked!
[21:26] <lazyPower> jose: i'm sorry i'm not sorry ;)
[21:26] <jose> :P
[21:36] <noodles775> Thanks tvansteenburgh
[21:38] <jrwren> sinzui: public
[21:41] <sinzui> jrwren, I see the issue, the mirror file is pointing to the official location in the CPC, which lists only stable agents
[21:42] <sinzui> jrwren, the fix is to directly set the agent-metadata-url for the cloud or to switch to alpha2 and set agent-stream
[21:42] <sinzui> jrwren, which approach do you prefer?
[21:42] <jrwren> i'll try alpha3 if it is in dev ppa
[21:43] <sinzui> jrwren, okay, I cam provide the metadata-url for eahc cloud. in the meantime, I will report a bug about the deprecated mirror files. I think we can get those fixes quickly
[21:44] <marcoceppi> jose: lazyPower has a habit of ignoring the lock
[21:44]  * marcoceppi plans on ways to mess with him as a result
[21:44] <jose> I guess I just noticed :P
[21:48] <lazyPower> jose: gonna do it to you again
[21:48] <jose> hey!
[21:48] <lazyPower> just wrapped up looking @ terracotta
[21:48] <jrwren> I think https://launchpad.net/~juju/+archive/ubuntu/devel the description here should be updated for alpha3
[21:55] <jrwren> yay! i can bootstrap


[08:48] <Lilith_Ardat> Hello. Is there a way in 20.04 to select particular updates to install as it was in 18.04 or am I just stuck with selecting a group of updates (verses)?
[08:48] <Lilith_Ardat> I only see "Apply full upgrade" option here and Software Sources dialog window.
[08:49] <Lilith_Ardat> But Apply Full Upgrade does not allow me to select particular packages to upgrade
[08:52] <Lilith_Ardat> In OTHER WORDS. I would like to see AT LEAST which packages are going to be upgraded before I click on Apply Full Upgrade.
[08:53] <Lilith_Ardat> I dont like when I am asked to update and I do not know what I am getting.
[08:54] <Lilith_Ardat> like it was when in LXDE
[08:58] <Lilith_Ardat> looks like im going to do this in terminal, sigh
[09:00] <Lilith_Ardat> heh, why all the fancy gui apps, when easier solution is just use apt command lol
[09:01] <Lilith_Ardat> bye
 Hi
[17:44] <shane> hello
[17:45] <shane> experimenting with Lubuntu on VM (also recently discovered)
 Hey that's my status
 Well how do I install RDP Server on Lubuntu?
 Any guides/leads?
 Every guide on internet is about ubuntu and Xfce as UI
 I don't want to use xfce
[18:08] <apt-ghetto> A RDP server?
 Xrdp basically
 You want to remote into your Lubuntu machine? Or you want to use Lubuntu to remote into another machine?
 Hi Dan , the first one..
 Remote in to Lubuntu machine
[18:11] <apt-ghetto> From Windows or another Linux?
 Windows :)
 I'm trying to setup a Lubuntu machine on Vultr
 A cloud VM
 Ok, nomachine is one option. It is cross platform.
 The use case is multiple users should be able to login and work via that Lubuntu machine
 4-5 users would be using that machine
 https://www.nomachine.com/
 The machine is bounded by an IP address
 So it checks all the boxes for the use case?
 But it's paid I see
 Yeah, it isn't open source unfortunately. Free for personal use though.
 okies great
 Let me try that then
 Thank you!
 You are welcome, happy to help.
 I see 3 options at the Login Screen
 Lubuntu, LxQt and OpenBox
 What's the difference b/w Lubuntu and LxQt ?
[18:42] <apt-ghetto> The configuration, LXQt is from upstream
 upstream? means the Ubuntu packages?
[18:42] <apt-ghetto> No, the LXQt project
 ..not aware of the terminology
 Oh Okay!
 I'm trying to configure XRDP
 what is the value for Lubuntu ?
 Lubuntu is configured by the Lubuntu team, it also the one we test.
 like I can write openbox if I need to get that loaded..
 am I in the right group? This is support group - correct?
[18:44] <wxl> @IndianOSR911 just use Lubuntu. the other two are basically unconfigured.
[18:44] <wxl> they will give an incomplete experience
[18:44] <wxl> it certainly won't look anything like one expects lubuntu to look
[18:45] <wxl> and, yes, this is the support group
 Xrdp uses startwm.sh file to launch the X session. If you want to use another X Window desktop, edit this file.
 I see the following in the file...
 (Photo, 528x54) https://i.imgur.com/pJUYSnk.jpg
[18:48] <wxl> first, i'll suggest that if you're doing remote desktop, nomachine is the best thing i've ever used. it's proprietary, but it's pretty amazing. i use it every single day.
[18:48] <wxl> you won't have to worry about *any* of this crap with nomachine
 Terminal Server is the product, right?
[18:51] <wxl> huh?
[18:53] <apt-ghetto> Take a look at /usr/share/xsessions/Lubuntu.desktop
[18:54] <wxl> yeah that, if you want to mess with xrdp
[18:54] <wxl> (i wouldn't)
 Thanks
[22:44] <santimir[m]> days ago went through 'manual partitioning' for installing lubuntu 20.04
[22:47] <santimir[m]> in the manual it can be read that for booting in UEFI mode you need /boot/efi with ESP flag
[22:48] <santimir[m]> that flag isn't there, i've used 'boot' I believe and it works fine...


[20:01] <lamont> slangasek: when the need arises, you have maverick-live chroots
[20:02] <slangasek> yay
[20:07] <ScottK> slangasek: Is it possible to remove images from the Kubuntu ports releases page?
[20:11] <slangasek> ScottK: I'm a little uncomfortable removing them after the fact - are they completely unusable?
[20:11] <ScottK> slangasek: I think it's reasonable to say the sparc one is.
[20:12] <ScottK> Our status is: powerpc - somewhat tested and believed to work, ia64 - untested, but may work, sparc - the entire port is broken, so no point in testing.
[20:12] <slangasek> howso?  I heard that the conclusion last week was that sparc is busted and not going to get better, but I don't have details
[20:12] <ScottK> I didn't hear details beyond the kernel doesn't work.
[20:12] <ScottK> That was enough for me.
[20:12] <ScottK> Maybe lamont knows.
[20:12] <slangasek> lamont: do you know?
[20:13] <ScottK> perhaps more relevant, perhaps lamont will admit to knowing....
[20:26] <lamont> heh
[20:28] <lamont> so... the conclusion of the "what about ia64/sparc (and ppc)?" session:  keybuk to go to tech board for ratification and mailing under their from address that sparc is clearly (1) broken and (2) not being loved, therefore all y'all have until feature freeze to make it work, or it'll be removed and lucid will be the last sparc release until such time as revived.
[20:28] <slangasek> lamont: clearly broken how?
[20:28] <lamont> re: ia64:  clearly neglected, but basically working.  Needs a new toolchain champion (as does sparc), doko won't be spending time on it other than vetting patches and uploading for the champion(s).
[20:29] <lamont> slangasek: upgrading from jaunty to karmic causes a reboot in a state where the machine is unbootable.  lucid lacks a kernel, I'm not sure of the state of installability from media in even karmic.
[20:30] <slangasek> "lacks a kernel"?
[20:30] <slangasek> there is one in the archive
[20:30] <lamont> ppc: has a strong community, seems to be doing ok, we'll address that one sometime between now and whatever will expire after the next LTS
[20:30] <lamont> slangasek: if only it booted
[20:30] <slangasek> why doesn't it boot, what range of hardware has this been verified on, is there a bug #?
[20:31] <lamont> slangasek: nfc here.  pure hearsay
[20:32] <slangasek> well, hmm.  Hearsay from whom?
[20:32] <slangasek> I'm not willing to nuke images from the release that we won't be able to get back afterwards, based on hearsay alone
[20:32] <lamont> my sparc box is not very happy (at least according to the guy I loaned it to last), and I haven't played with it in forever
[20:32] <slangasek> (well, ok, we can get those back afterwards by rebuilding from the release pocket, but)
[20:33] <lamont> slangasek: I don't see any reason to nuke them, given that they're clearly not supported in any case
[20:34] <slangasek> the reason to nuke them is that they're kubuntu images and the kubuntu folks (in person of ScottK) are asking for the nukage
[20:35] <ScottK> It's not essential to have it removed, but if we're going to point people at the ports directory, it would seem CoC friendly not to point them at known broken stuff.
[20:36] <ScottK> OTOH, the odds of anyone caring about sparc and a desktop are low enough, meh.
[20:40] <lamont> at least add a header to the html in the directory saying "known broken, fixes welcome"???  dunno


 doesn't seem to time out
[19:24] <CarlFK> finely it did.  seems like 5 min
[19:39] <CarlFK> installer failed to dl public key... lp.../...ppa
[19:39] <CarlFK> because it is behind squid-deb-proxy
[19:44] <CarlFK> Bug #728710 ... looks like the issue got buried ... I'll open a new one and ref that old one
[19:46] <CarlFK> oh whack. by design? # launchpad personal package archives (disabled by default)