[04:02] <sage1364> hello?
[04:03] <tsimonq2> !help | sage1364
[13:07] <ricardogsilva> help a newbie out ;) I'm trying to test a javascript scope on my phone but keep getting 'using a custom scopelauncher is not yet supported'
[13:12] <ricardogsilva> I've started with the example scope, did not customize the scopelauncher
[13:21] <ricardogsilva> I got the SDK to upload my scope to the phone by deleting the ScopeRunner line from my scope's .ini.in file
[13:22] <ricardogsilva> now it loads but does nothing
[13:22] <ricardogsilva> and it also fails on the desktop, where it was working fine before
[13:22] <ricardogsilva> help?
[13:27] <ricardogsilva> appdevs how to test a javascript scope on a real phne when I keep getting 'using a custom scopelauncher is not yet supported' message?
[14:12] <owaishanif786> hi there
[17:00] <dubstar_04> any design guys in?
[21:05] <micael> Hi, i just made a app in python to ubuntu phone but i don't knonw how to run it in my ubuntu phone
[21:06] <micael> Can someone help me?
[21:10] <dubstar_04> did you use the sdk?
[21:14] <dubstar_04> micael: A simple way to run python *apps* on the phone is to used pyotherside: http://pyotherside.readthedocs.org/en/latest/
[21:15] <dubstar_04> if you want to run a *script* then  copy the script to the phone and use terminal to run it. python3 /path/to/script
[21:15] <micael> i made my app in pyside
[21:16] <micael> python, pyside and qml
[21:16] <micael> with ubuntu conponents
[21:16] <micael> components
[21:20] <micael> i think i have to make a click package!?
[22:03] <dobey> yes if you want to ship it, you have to make a package to upload to the store. you will also have to include most of all the python bits in your package as well
[22:15] <micael> python bits?
[22:25] <dobey> micael: yes, pyotherside (or pyside) etc…
[22:26] <dobey> micael: really, you shoudn't even rely on the interpreter being available.
[22:42] <micael> It was what he thought
[22:43] <micael> Thanks :)


[00:08] <robru> infinity: no i guess not. There's a check against publishing the same version twice though. Can you file a bug against cupstream2distro?
[00:14] <infinity> robru: You could!
[01:44] <robru> infinity: k https://bugs.launchpad.net/cupstream2distro/+bug/1478293


[22:45] <mort> so on ubuntu (20.10 but also 21.04), under wayland, maximized windows will occasionally appear below the dock and it's kind of annoying
[22:46] <mort> for example, when waking my laptop from sleep, all maximized windows often get placed behind the dock as if it wasn't there; it's as if gnome's window sizing logic happens before it's aware that there's a dock or something
[23:28] <guiverc> mort, if it's occuring on 21.04/hirsute, a bug should be filed as hirsute is currently in bug finding & fix stage ... have you looked for a reported bug on your issue?
[23:29] <mort> I looked briefly for something, I didn't found anything in launchpad but I don't quite know what to search for
[23:31] <mort> https://p.mort.coffee/6uX.png shows it in action
[23:32] <mort> I got that by literally just closing the lid on my laptop and opening it again, both firefox and gnome-terminal was maximized and firefox was in front of the terminal in the window stack
[23:32] <mort> but I don't think the exact setup is that important
[23:32] <guiverc> I would suggest filing a bug on it using hirsute (https://help.ubuntu.com/community/ReportingBugs) as now is the time to get issues fixed
[23:32] <mort> I've seen both firefox and gnome-terminal end up behind the dock
[23:33] <mort> what component? gnome-shell? ubuntu-desktop? the dock extension?
[23:34] <guiverc> if you can achieve it using *live* media it may be better; it can be reported on iso.qa.ubuntu.com and linked to bug report & other testers will also be asked to look for it (ie. confirm it)
[23:34] <guiverc> mort, looking..
[23:35] <mort> I could probably reproduce it on an installer USB tomorrow or something
[23:36] <guiverc> I'd worry less about filing against the wrong package; it'll be changed if incorrect (esp. currently for hirsute), but http://iso.qa.ubuntu.com/qatracker/milestones/419/builds/228164/buginstructions implies xorg (even if it's mutter or something else; sorry I'm not knowledgeable enough with gnome's stack to be specific)
[23:37] <mort> yea that should probably be updated I bet now that wayland is a thing
[23:38] <mort> I'll just file it against gnome-shell
[23:38] <guiverc> & xorg issues are usually xorg-server.. yeah I've seen discussion on changing it in recent days..   gnome-shell should work
[23:39]  * guiverc thinks vanvugt will see it I bet & correct as necessary
[23:46] <mort> alright, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919394
[23:48] <guiverc> Thank you for taking the time to report & helping make Ubuntu better mort
[23:50] <mort> :)


[16:26] <Excelsian> ok so alot of communication platforms have ended up with me having to prove over & over again that I am not a "robot".  I don't think robots interface many communications a person would, that's just creepy, but somehow this is going on.


[16:08] <nand> hiya!
[16:08] <nand> for anyone interested on bikeshed, please tell me what you think of the items in http://www.ndeschildre.net/2008/01/19/ubuntu-websites-titles-mockups/ :)
[16:44] <thorwil> hi nand. i'd prefer real text next to the logo images. space efficient and accessible
[16:45]  * thorwil goes for a walk
[16:47] <nand> you mean, HTML text outside the img? Not really feasible if we want to keep the ubuntu font for the ubuntu word...
[17:10] <thorwil> nand: yes, that's what i mean. well, i wouldn't make that a hard requirement
[17:15] <nand> we don't also have the same positioning freedom than in an img, and the same font variety.
[17:16] <nand> thorwil: do you think http://img175.imageshack.us/img175/7743/scrot4.png is too stylised?
[17:16] <thorwil> nand: yes. the 2 fonts are from separate parts of the world and don't even talk to each other
[17:17] <nand> this bikeshed color is quite difficult to choose :)
[17:17] <thorwil> nand: seeing the width you could take, i would try putting the text on a single line
[17:18] <thorwil> all lowercase
[17:18] <nand> thorwil: that would require the same font for all, I guess
[17:19] <thorwil> nand: should be tried, anyway. even though the title font is known to not be that great for anything that is not an u, b, n or t :)
[17:19] <nand> :)
[17:19] <nand> I give some more tries
[17:19] <kwwii> re
[17:19] <kwwii> hi all
[17:19] <thorwil> hi kwwii
[17:20] <kwwii> hi thorwil
[17:21] <thorwil> nand: the horizon / bottom line of the logo background asks to be at least tried as baseline for  the text
[17:22] <thorwil> nand: oh, and while i don't want to keep anyone from being creative, if you really really want title text as image, i would prefer if you let me do it
[17:23] <nand> thorwil: ok thanks! We will compete on this one :)


 Tonight I'm going to knock out a good portion of the 5.9.4 transition.
 qtscript building in sbuild right now.
 Like I said before, the goal is to get it ready to test by this weekend.
 @mitya57 Did you ever get the chance to hook up the IRC integration in Salsa?
 qtscript uploaded to the PPA, qtwebkit-opensource-src and qttools-opensource-src need to be built, then once all that's done, I'll do the ABI bump on qtbase and qtdeclarative, then rebuild all the other packages without ~1
 er, I think I'm gonna skip qtwebkit, I remember they had a versioning thing going in
 *on
 qttools uploaded, going to go through the dance from before
 (well, that I said before)
 qtbase uploaded putting the ABI bump back into place
 I'm going to have to do another qtbase upload to the PPA
 Cherry picking some patches from Solus and updating symbols
 Tomorrow I'll work more on it.
 (approaching midnight, bedtime)
 @tsimonq2, Not yet, but I can bump your permissions to Master if this will help you to set up it
 @mitya57, Sure
 Done
 Thanks!


[11:52] <daftykins>  knightwise: psst you've got the trampoline under you again, bouncy bouncy!
[11:52] <daftykins> happy Monday all, with coffee in hand we can knock back those blues
[11:53] <daftykins> oy, first up is a very strange email from a client claiming he can't sleep because i didn't answer a call on my birthday or call back over the weekend - you're damn right i didn't!
[11:53] <daftykins> this is honestly pretty weird
[12:24] <zxmpi_> only technical requests answered on birthdays come written in birthday cards that drop 50 shekels when you open them :-)
[12:24] <daftykins> lol, exactly
[12:39] <daftykins> ah it's so odd, it's not like we're talking about critical issues, they're not even things i can action right now
[12:40] <zxmpi_> could be someone who's had a disaster at some point and is nervous of having an 'issue' unresolved
[12:41] <zxmpi_> could be someone who's heard of all the delays and queues in relation to new hardware and is anxious
[12:41] <zxmpi_> i'd guess #2 with no other info
[12:41] <daftykins> nah been almost 20 years with this one, gone a bit weird since his recent divorce... always tries to rush these property jobs though, so tends to put pressure on about tasks in the wrong order
[12:42] <daftykins> "i want it now, now, now!"
[12:43] <zxmpi_> ah, midlife i'm in control jobbie
[12:46] <daftykins> really has been losing it lately, a bit ago i attended the new property and saw a bit of a shortcut job done by the satellite TV contractors i'd sub'd in, mentioned it to the guy
[12:46] <daftykins> he had no idea
[12:46] <daftykins> called up the contractors "oh yeah client ok'd it, i spoke with him before doing anything"
[12:47] <daftykins> so he'd just completely forgotten about it due to divorce/lack of sleep/other dramas
[12:47] <zxmpi_> any history of heart disease. have seen that feck up memory
[12:47] <daftykins> not that i'm aware of
[23:00] <davef> Reminder, it's Twosday tomorrow.
[23:00] <davef> Tuesday Feb 22nd, 2022
[23:01] <davef> 22/2/22


[14:10] <mathrick_> jelmer: do you have any tracker bug or TODO of what remains to be sorted out for git push?
[16:11] <jelmer> mathrick_: yes, http://pad.lv/544776
[16:12] <jelmer> it doesn't have a summary of what's left though
[16:12] <jelmer> you can run the full bzr testsuite with bzr installed to get some idea of what's missing
[16:12] <jelmer> (you'll get ~1000 broken tests)
[16:13] <mathrick_> I see
[16:14] <mathrick_> I assume it's not only bzr-git that fails in those 1000?
[16:17] <jelmer> it is just bzr-git
[16:17] <jelmer> I'm sure you can get more errors if you install more plugins :)
[16:18] <mathrick_> heh


[05:46] <Scary_Guy> well uptime went when I restarted hoping it would fix my multimon issue.  Turns out it did not and it just didn't like/support that monitor.  Swapped it with the original in the new location
[05:47] <Scary_Guy> ten minutes shy of a day and I'm doing it agian to install a USB3 card
[05:47] <Scary_Guy> l8r
[12:17] <cmaloney> morning
[13:20] <obscurehero> mrgoodcat, look who's on IRC again
[13:20] <obscurehero> o7 cmaloney
[13:42] <cmaloney> ?
[13:43] <cmaloney> How's the morning so far?
[17:46] <Scary_Guy> so far so good.  computer hasn't cought fire yet
[17:46] <Scary_Guy> https://nakedsecurity.sophos.com/2016/08/18/nists-new-password-rules-what-you-need-to-know/ this came up in another channel


[00:00]  * micahg doesn't know offhand
[00:00] <directhex> micahg, yes, it's for a firefor addon
[00:00] <micahg> but thanks to bdrung_we have an installer for addons now
[00:00] <RAOF> directhex: Did you see the xul packgaing team mail on debian-devel@ recently?
[00:01] <directhex> RAOF, no. link?
[00:01] <sebner> Keybuk: haha, I agree but the lines are too long imho, won't you agree? :P
[00:01] <micahg> http://wiki.debian.org/mozilla-devscripts
[00:01] <sebner> hi directhex :)
[00:01] <directhex> evening seb128
[00:01] <directhex> sebner,
[00:01] <RAOF> http://lists.debian.org/debian-devel/2010/02/msg00011.html
[00:02] <mneptok> Keybuk: You're in a desert, walking along in the sand, when all of a sudden you look down. You look down and see a tortoise, Scott. It's crawling toward you. You reach down and you flip the tortoise over on its back. The tortoise lays on its back, its belly baking in the hot sun, beating its legs trying to turn itself over, but it can't. Not without your help. But you're not helping. I mean ... you're not helping, Scott! Why is that?
[00:02]  * directhex retires mneptok
[00:02]  * sebner is scared
[00:03] <Keybuk> mneptok: because I crave tortoise soup
[00:03] <Keybuk> sebner: "the lines" ?
[00:03] <directhex> micahg, blurgh, xpi-ifying what i have is added work
[00:03] <ion> mneptok: Have you stopped beating your wife?
[00:03] <Keybuk> sebner: I really don't know what about the graph you're asking me to comment on
[00:03] <Keybuk> it looks like a bootchart to me
[00:03] <micahg> directhex: an xpi is a zip file
[00:03] <Keybuk> of a hard-drive based machine
[00:04] <Keybuk> where on the first boot you took longer to log in than ureadahead bothered to wait
[00:04] <mneptok> ion: Sushi. That's what my ex-wife called me - cold fish.
[00:05] <micahg> directhex: there's an example of building from source in the wiki page
[00:06] <directhex> actually, maybe it's not so bad...
[00:07] <directhex> bleh, not sure
[00:08] <sebner> Keybuk: 38 seconds are bothering me :P
[00:09] <pitti> sebner: http://people.canonical.com/~pitti/bootcharts/tick-lucid-20100122-2.png ..
[00:09] <micahg> directhex: the ever shrinking rules file
[00:10] <directhex> micahg, for simple cases perhaps
[00:10] <sebner> pitti: on my bootcharts from february 1st too but I thought we are decreasing boot time instead of increasing it :P
[00:10] <bdrung_> when will be the next autosync run?
[00:12] <directhex> micahg, so delete all the ubufox Npp stuff?
[00:13] <micahg> directhex: I'm not sure what that is...which package?
[00:13] <bdrung_> directhex: i read xpi. do you work on xul extensions?
[00:13] <directhex> micahg, moon
[00:14] <bdrung_> ok, moon is not a xul extension - so not my field
[00:15] <directhex> bdrung_, so we're drawing a line between plugins & extensions? these rules are for extensions only?
[00:16] <micahg> yeah, this is for extensions, not plugins
[00:16] <bdrung_> directhex: yes.
[00:16]  * directhex has been wasting his time, then
[00:16] <bdrung_> directhex: did you read debian-devel ML?
[00:16] <directhex> so where should *plugins* be shoving themselves?
[00:16]  * micahg is looking directhex
[00:18] <micahg> directhex: /usr/lib/firefox-addons/plugins seems to be the place
[00:18] <directhex> micahg, firefox on karmic will load a plugin from /usr/lib/xulrunner-addons/plugins. on lucid it won't. hence the question
[00:18] <micahg> see above
[00:19] <Keybuk> sebner: well, part of your problem is that it's not auto-login
[00:19] <Keybuk> sebner: make it auto-login
[00:19] <Keybuk> wipe the ureadahead pack
[00:19] <Keybuk> then do two reboots
[00:19] <Keybuk> giving it about 30s to a minute after the first to settle and make the pack
[00:20] <jdong> is there a secure way (reasonably) to auto-login and lock the screensaver?
[00:20] <micahg> directhex: firefox on lucid doesn't use xulrunner
[00:20] <jdong> I'd love to boot and walk away and come back to a ready desktop
[00:20] <directhex> i see
[00:20] <micahg> in fact, the xulrunner-addons is explicitely denied in the apparmor profile
[00:20] <sebner> Keybuk: I'll give it a try. Btw, what's the goal now. 15-20 seconds right?
[00:21] <Keybuk> sebner: along those lines
[00:21] <micahg> oops
[00:21] <micahg> ignore my last statement
[00:21]  * micahg read it wrong
[00:21] <jdstrand_> micahg: that is actually unrelated-- it is denied to prevent logging-- DAC wouldn
[00:21] <jdstrand_> 't allow it anyway
[00:21] <directhex> and in debian, is /usr/lib/firefox-addons/plugins appropriate?
[00:21] <micahg> jdstrand_: yeah, I misread it
[00:22] <micahg> bdrung_: ^^
[00:22] <lifeless> cjwatson: https://bugs.edge.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/516344 for your depressed edification
[00:24] <lifeless> pitti: where to language pack bugs go? [scott was asking about a klingon desktop but there isn't a klingon (-tlh) langpack]
[00:24] <ion> jdong: I’d like that, too. It would also be nice if the unlocking of the screensaver unlocked the Gnome keyring in the same session as well.
[00:25] <bdrung_> micahg: yes
[00:26] <directhex> /usr/lib/firefox-addons/plugins/ for both distros, then? right, that simplifies matters.
[00:27] <directhex> and what's an appropriate Depends: line to use, without the commonality of xulrunner? firefox|iceweasel|abrowser|somethingelse ?
[00:27] <pitti> lifeless: there needs to be a locale first; once there is, and some translations on LP, they'll be created automagically
[00:28] <bdrung_> directhex: i think we should provide tools for plugins, too.
[00:28] <dpm> lifeless, https://wiki.ubuntu.com/Translations/KnowledgeBase/StartingTeam
[00:29] <micahg> directhex: you still need to build on xulrunner
[00:29] <StevenK> Apparently, the colour of Klingon should be a deep purple
[00:30] <micahg> so technically, it still depends on xulrunner, but enhances firefox in Ubuntu
[00:30] <directhex> bdrung_, that could well be useful. although plugins can be somewhat unwieldy beasts, so don't go overboard in how much hand-holding you do. i'd settle for a variable signifying the system plugin dir plus a substvar for the odd thing here & there
[00:30] <micahg> that reminds me, I should talk to asac about that...
[00:31] <directhex> but ff on lucid doesn't use xulr... frankly, i'm totally lost now
[00:31] <micahg> bdrung_: maybe an install-plugin similar to install-xpi
[00:31] <ccheney> isn't xulrunner being killed off for all releases?
[00:32] <micahg> ccheney: not entirely, just for firefox
[00:32] <directhex> ccheney, did i mention i was lost? ;)
[00:32] <ccheney> micahg: ok
[00:32] <bdrung_> micahg: and dh_xul-ext needs to be adjusted on cloned to dh_xul-plugin (or something like this)
[00:32] <ccheney> directhex: heh
[00:32] <micahg> ccheney: we're migrating what we can away from it
[00:32] <ccheney> micahg: ah ok, i thought it was migrate what we can and kill everything else :)
[00:32] <ccheney> but i am probably wrong
[00:33] <bdrung_> micahg: you are welcome tho write install-plugin
[00:33] <bdrung_> :)
[00:33] <micahg> bdrung_: is that an invitation for me to work on it ;)
[00:33] <micahg> you beat me to it bdrung_...
[00:33] <micahg> bdrung_: where should I file the bug?
[00:34] <bdrung_> micahg: it should go into mozilla-devscripts
[00:34] <directhex> i really really don't care about the specifics. i just want a symlink to usr/lib/moonlight/plugin/libmoonloader.so to be shoved in whatever location is used by mozilla-flavoured browsers, whatever they may be. that's all i want. with or without Xb-Npp-MimeType or other such nonsense, that's all i need. one symlink in the correct place.
[00:34] <directhex> and dependencies of some variety to make it actually work
[00:35] <directhex> meaning moonlight-plugin-core plus whatever else tastes good, like shlibs:depends and misc:depends and a browser of some variety
[00:36] <bdrung_> directhex: for the second part you want a equivalent to dh_xul-ext
[00:36] <directhex> yes, that'd be fine & dandy
[00:37] <ccheney> pitti: do we have code to ask a user to install a particular package when an app runs, similar to how the codec stuff works?
[00:37] <ccheney> pitti: i need to ask users to install java when they run OOo if they don't already have it
[00:38] <lifeless> pitti: oh thats interesting; I'm making the locale for scott now.
[00:38] <directhex> ccheney, i don't know of a generic framework for that
[00:38] <micahg> bdrung_: it's on my list, but I don't know when I'll get to it
[00:38] <micahg> oops
[00:39] <micahg> bdrung_: bug 516350
[00:40] <bdrung_> micahg: you may want to write a equivalent to dh_xul-ext
[00:40] <micahg> bdrung_: should I rename it to that
[00:40] <micahg> bdrung_: is it not 2 pieces of the same thing?
[00:41] <bdrung_> micahg: no. install-xpi installs the xpi file (extract + symlinks). dh_xul-ext evaluates ${xpi:*}
[00:42] <bdrung_> micahg: 2 scripts for the same thing
[00:42] <micahg> bdrung_: I think I'll call the bug provide plugin install assistance and explain the in description
[00:42] <bdrung_> sound good
[00:42] <micahg> done
[00:43] <lifeless> pitti: langpack-locales - does that control what langpacks are made?
[00:43] <pitti> lifeless: indirectly
[00:43] <pitti> /usr/share/i18n/SUPPORTED has the list of available locales
[00:44] <lifeless> right
[00:44] <pitti> langpack-locales ships that file, and the locales
[00:44] <lifeless> ah
[00:44] <pitti> and langpack-o-matic builds packages for locales which are in SUPPORTED
[00:44] <lifeless> pitti: thats not quite right
[00:44] <pitti> why not?
[00:44] <lifeless> pitti: la_AU.UTF-8 is in my SUPPORTED file, and not in the package
[00:45] <pitti> /usr/share/i18n/locales/la_AU
[00:45] <pitti> lifeless: ^ it was you who contributed that :)
[00:45] <lifeless> I know
[00:45] <lifeless> but I've just done apt-get source langpack-locales
[00:46] <lifeless> and it doesn't have la_AU in the source package so I'm checking my facts
[00:46] <pitti> lifeless: it's in debian/patches
[00:46] <pitti> (it's still not accepted upstream)
[00:46] <lifeless> yeah
[00:46] <pitti> or should I rather say "refused"
[00:46] <pitti> so we keep it as a patch
[00:46] <lifeless> ok, well I'll add klingon the same way
[00:47] <lifeless> I wish I had time to do a proper orthogonal language separate from location system
[00:47] <pitti> Qapla'
[00:48] <StevenK> pitti: Won't Klingon hit the "Enough isn't translated, so no langpacks for joo"
[00:48] <pitti> StevenK: no, we have plenty of scarcely translated langpacks
[00:50] <lifeless> also klingon folk are insane
[00:50] <directhex> lifeless, they're just overly exuberant
[00:59] <lifeless> dpm: so why did you link that wiki page to me?
[01:01] <dpm> lifeless, I was complementing pitti's answer to your question on Klingon translations. You need to create an Ubuntu Klingon team following that process to be able to translate Klingon in Launchpad
[01:06] <directhex> dpm, klingon needs more vocab first though, surely? i mean, eskimos have 50 words for snow, klingons have 50 words for "disembowel"
[01:06] <directhex> and whilst "disembowel" might work as a replacement for "cut", i'm not sure where else it fits
[01:08] <sebner> directhex: but they don't have a word for fridge! :P
[01:14] <lifeless> dpm: I have no interest in translating it ;)
[01:15] <lifeless> dpm: I'm doing a favour for Keybuk
[01:15] <dpm> np, just trying to be helpful :)
[01:15] <lifeless> kk:)
[01:16] <Keybuk> directhex: you could translate fridge pretty easily
[01:16] <Keybuk> "be cold box"
[01:17] <Keybuk> tep bImeHwI or something
[01:17] <directhex> o_o
[01:17] <Keybuk> "box for the purposes of being cold" :p
[01:18] <directhex> nerd!
[01:18] <Keybuk> heh
[01:18] <Keybuk> Klingon has a sufficiently large vocab that entire books have been translated into it, and a fairly flexible one that it allows word creation by description
[01:20] <lifeless> hmm, I've forgotten how to turn a locale on
[01:21] <StevenK> Keybuk: And words invented due to cultural references
[01:23] <pitti> lifeless: sudo locale-gen xx_YY.UTF-8
[01:23] <pitti> lifeless: and then export LANG=xx_YY.UTF-8
[01:24] <zul> cjwatson: im in the middle of writing an apport hook for openssh-server do you want to review it after can i just upload it when Im done writing it?
[01:24] <directhex> shame unicode doesn't formally include klingon
[01:25] <lifeless> pitti: actuall  I needed to edit /var/lib/locales/supported.d/local
[01:25] <lifeless> pitti: so that it stays up to date when the locales package is refreshed
[01:25] <lifeless> anyhow
[01:25] <lifeless>   tlh_GB.UTF-8... done
[01:25] <lifeless> Keybuk: ^
[01:25] <StevenK> lifeless: Where GB is effectively, well, Earth?
[01:26] <lifeless> StevenK: its for Keybuk, so I've used GB layout
[01:26] <StevenK> lifeless: Does it work, though? :-)
[01:27] <lifeless> StevenK: 'meh'
[01:28] <directhex> barring the confusing rules regarding plugin packaging in lucid, the lack of adequate support for firefox 3.6, the lack of a debian/copyright file, and a debian/rules which doesn't work twice in a row, i have a preliminary package for moonlight 2.0. i feel i should sleep now
[01:29] <directhex> seb128, ^^
[01:30] <seb128> directhex, waouh, good work ;-)
[01:31] <lifeless> pitti: https://code.edge.launchpad.net/~lifeless/ubuntu/lucid/langpack-locales/bug-516359/+merge/18496
[01:31] <directhex> seb128, upstream have promised me a new release within a couple of weeks which will resolve at least one of those issues. as well as the current need to +dfsg some of the tarballs which i've been ignoring
[01:39] <seb128> lamont, is that normal that amd64 has only 2 buildds?
[01:41] <lamont> seb128: some days
[01:41] <lamont> and yes
[01:41] <lamont> i386 is the workhorse that does all, so it has more
[01:41] <seb128> hum, ok
[01:41] <seb128> I guess those changes will be for tomorrow then
[01:42] <seb128> it's annoying to have things blocked for over 10 hours as soon as gcc or openoffice get uploaded
[01:42] <seb128> lamont, thanks
[01:46] <lamont> seb128: yes, it is.
[01:46] <lamont> I know where we can find our favorite german.....
[01:47] <seb128> lamont, yeah, me too
[01:47] <lamont> seb128: yeah - but I can actually throw  things at him...
[01:48] <seb128> oh, please do ;-)
[01:49] <StevenK> seb128: Yes, I'm blocked for an armel CD build for 28 hours because of OO.o
[01:50] <seb128> StevenK, that's a different issue
[01:50] <seb128> StevenK, you have 7 buildds, which means it at least doesn't block everything else
[01:50] <StevenK> seb128: Sure, but while we're complaining about OO.o and gcc :-P
[01:50] <seb128> ;-)
[01:55] <Riddell> geser: do you have a magic script for these move to universe bugs or are you doing it all manually?
[01:57] <cjwatson> zulI'd like to review it
[02:15] <lifeless> pitti: ping
[02:16] <pitti> lifeless: pong
[02:16] <lifeless> hey, klingon all gtg :) - pushing the second patch in a second
[02:16] <lifeless> been interrupted ;>
[02:17] <lifeless> https://code.edge.launchpad.net/~lifeless/ubuntu/lucid/langpack-locales/bug-516359/+merge/18496 is the langpack one
[02:17] <pitti> lifeless: ++territory "Great Britain"
[02:17] <pitti> shouldn't that be "Kronos"? :=)
[02:17] <lifeless> pitti: no :P
[02:17] <lifeless> pitti: its GB phone # layout etc
[02:21] <pitti> lifeless: no translated weekdays? :)
[02:21] <lifeless> patches accepted :)
[02:21] <lifeless> how many weekdays does klingon have?
[02:22] <pitti> no idea
[02:22] <pitti> anyway, uploading now :)
[02:23] <lifeless> pitti: lp:~lifeless/ubuntu/lucid/libx11/bug-516359 is the second
[02:23] <lifeless> pushed
[02:24] <pitti> lifeless: nice, it's already in langpack-o-matic's maps/languages
[02:25] <StevenK> pitti: It's also already in Rosetta
[02:29] <pitti> lifeless: uploaded
[02:30] <Riddell> DktrKranz: do you have an opinion on bug 508013 ?
[02:41] <lifeless> pitti: weet, thanks
[02:47]  * Dante_J greets the room
[02:49] <Dante_J> Under Lucid Alpha 2 with Firefox 3.6, noscript in the repo is not compatible with Firefox, and noscript supplied via Mozilla locks everything - caps light won't even toggle.
[02:49] <Dante_J> This is on a T30 Laptop with a radeon graphics card.
[02:54] <gnomefreak> IIRC noscript is waiting for xul* naming update
[04:50] <Linux-CLI> hi
[04:55] <Linux-CLI> I'm trying to install a .deb package, however it told me that I already had a package in use (because I pressed Ctrl+C on "sudo apt-get install patch"). So I gave up & just rebooted. Still getting the error when trying to install the .deb package, any ideas?
[04:59] <sbalneav> Linux-CLI: Can you give the exact error message?
[05:09] <Linux-CLI> I'm trying to install a .deb package, however it told me that I already had a package in use (because I pressed Ctrl+C on "sudo apt-get install patch"). So I gave up & just rebooted. Still getting the error when trying to install the .deb package, any ideas?
[05:09] <Linux-CLI> Do we use the Debian maintainers guide to create .deb packages for Ubuntu?
[05:10] <RAOF> Yes.
[05:10] <Linux-CLI> Thanks
[05:10] <RAOF> The answer to your first question is likely to be “get dpkg to configure the partially-installed package by calling 'sudo dpkg --configure -a'”
[05:11] <Linux-CLI> Yeah it was, sorry
[05:11] <Linux-CLI> lol
[05:11] <Linux-CLI> It took me 5 minutes to download fakeroot before
[06:00] <Mad_Gouki> what sort of kernel development happens specifically for Ubuntu?
[06:01] <crimsun> Mad_Gouki: the async population, hardware enablement (OEM), among others
[06:02] <crimsun> async rootfs *
[06:02] <Mad_Gouki> interesting
[06:02] <Mad_Gouki> do most distros have kernel developers, and do the changes get folded back into the main kernel from time to time?
[06:03] <maco> the corporate sponsored ones do tend to have them, yes
[06:03] <maco> and at least of ubuntu, red hat, and suse.... yeah, those get submitted upstream
[06:03] <Mad_Gouki> very cool
[06:03] <crimsun> the merge policies tend to be governed by each team, but the general approach is to work directly in upstream as much as possible
[07:00] <superm1> any archive admins about?  I was wondering if someone could clear ubiquity from binary new so that it can be included on the live cds for tomorrow in time?
[07:17] <sabdfl> hi folks, why are redland-utils and raptor-utils in the default install?
[07:20] <cjwatson> sabdfl: openoffice.org-core Depends: librdf0 Depends: redland-utils; librdf0 Depends: libraptor1 Depends: raptor-utils
[07:21] <cjwatson> sorry, Recommends: for the last step in each of those chains, not Depends:
[07:22] <cjwatson> superm1: done
[07:22] <superm1> thanks
[07:23] <sabdfl> cjwatson: i have oo.o-core 1:3.2.0~rc4-1ubuntu1, which appears not to
[07:24]  * cjwatson peers
[07:26] <cjwatson> sabdfl: ah, in that case the answer is that it is no longer in the default installation :-) I've confirmed this from the current override files
[07:26] <sabdfl> doh
[07:26] <sabdfl> so much changes so quickly round here :-)
[07:26] <cjwatson> (I hadn't updated since this afternoon ...)
[07:27] <cjwatson> it may or may not fall out automatically due to apt-get autoremove; I'm not sure exactly how sensitive that is
[07:27] <cjwatson> it looks like it will stay in main for some time due to KDE bits and pieces
[07:29] <cjwatson> specifically (at least) soprano-daemon)
[07:39] <geser> Riddell: I checked them manually
[08:06] <superm1> dang, appears to have missed the publisher cycle in time, still got the old ubiquity in the livefs :(
[08:23] <slytherin> Hi. I would like to know if anyone is working on updating evolution-data-server in lucid. I want to upload latest version of evolution-mapi which depends on e-d-s 2.29.x.
[09:03] <strycore> slytherin, if I recall correctly, Lucid sticks with Evolution 2.28
[09:53] <slytherin> strycore: Where was this discussed? And what is the reason?
[10:29] <strycore> slytherin, sorry I can't find where it has been discussed but I remember seeing that on IRC
[10:30] <slytherin> hmm, I trust a discussion on mailing list than IRC discussion about such a bug decision.
[10:37] <strycore> http://irclogs.ubuntu.com/2010/01/20/%23ubuntu-desktop.txt
[10:37] <strycore> at 20:07
[10:39] <slytherin> hmm, I wonder when and why was this decided.
[16:16] <hexa-> hey, can anybody take a quick look into bug #514299 please?
[16:34] <jelmer> slangasek: Hi
[16:35] <jelmer> slangasek: Are you aware of any source packages in Debian that have component orig tarballs at the moment, or are bz2 tarballs the main issue when syncing ?
[16:36] <Laney> aiui the sync script is hardcoded to expect orig.tar.gz at the minute
[16:36] <Laney> jelmer: wgrant was looking at it AFAIK
[16:38] <jelmer> Laney: I'm working on the v3 support for the sync script at the moment, but the bug mainly talks about bz2 support.
[16:56] <smoser> james_w, it looks to me like 'bzr branch lp:ubuntu/python-boto' is out of sync with the archive, could you kick it ?
[17:01] <lifeless> pitti: https://code.edge.launchpad.net/~lifeless/ubuntu/lucid/libx11/bug-516359/+merge/18538
[17:02] <lifeless> bryceh: ^ may interest you too
[17:12] <superm1> lifeless, "   * Add klingon language definition." is that a patch pulled from upstream I hope?
[17:12] <jdong> hahaha
[17:13] <StevenK> superm1: You tell funny jokes ...
[17:13] <jdong> sounds SRU-worthy!
[17:13] <slangasek> jelmer: bz2 tarballs are the only issue I can recall running into
[17:14] <superm1> slangasek, could you re-roll daily-live from today?  tried to get the new ubiquity in in time, but the publisher was a little late
[17:22] <slangasek> superm1: "daily-live" - mythbuntu or ubuntu?
[17:22] <superm1> slangasek, ubuntu
[17:22] <slangasek> superm1: ok, running
[17:23] <superm1> slangasek, thanks
[17:43] <lifeless> pitti: https://code.edge.launchpad.net/~lifeless/ubuntu/lucid/libx11/bug-516359/+merge/18538 is the new patch
[17:52] <mdeslaur> slangasek: do you own nvidia hardware? Would you like to see what plymouth looks like on my nvidia laptop (including freeze every second boot)?
[17:53] <TheMuso> mdeslaur: *raises hand, I get that too.
[17:54] <TheMuso> mdeslaur: Although mine is a little worse than that. Atm I can't boot the -12 kernel at all, either with plymouth or without/recovery mode.
[17:56] <charlie-tca> Most of us have to use the Alt+SysRq+k to get a gdm screen in the -12 kernel
[17:57]  * TheMuso can never remember what sysrk is... Please remind me. :) as in what key it is.
[17:57] <charlie-tca> printscreen
[17:57] <TheMuso> ah ok thanks.
[18:19] <doctormo_> I have a question about this bug:
[18:19] <doctormo_> https://bugs.launchpad.net/groundcontrol/+bug/516651
[18:19] <doctormo_> I want to know what the best thing to do about translating debug messages
[18:20] <StevenK> cjwatson: Should we remove the lpia kernel section in the platform.lucid installer seed?
[18:27] <cjwatson> StevenK: feel free
[18:37] <ccheney> is lock screen broken for anyone else today?
[18:38] <persia> ccheney: I've heard a couple reports.  `gnome-screensaver -l` seems to be the workaround.  Go chase dbus.
[18:38] <chrisccoulson> somebody mentioned gnome-screensaver?
[18:38] <StevenK> kees: Just curious, is the fortification stuff in our toolchain upstream?
[18:38] <chrisccoulson> heh, i bet the new autostart delay causes it to race with the indicator-session applet
[18:38] <chrisccoulson> ccheney - can you not lock the screen from there?
[18:38] <persia> chrisccoulson: Seems to be a bug in how the notification applet calls it right now.  g-s itself seems fine.
[18:39] <kees> StevenK: the glibc goo that responds to setting -D_FORTIFY_SOURCE=2 is in upstream glibc, yes.
[18:39] <chrisccoulson> persia - right, i've noticed this before. if the indicator starts before gnome-screensaver, then it doesn't work
[18:39] <kees> StevenK: our compiler sets -D_FORTIFY_SOURCE=2 by default.  that is not in the upstream compiler.
[18:39] <chrisccoulson> and we just changed gnome-screensaver to not start for 5 seconds
[18:39] <chrisccoulson> so, that's an indicator bug
[18:39] <ccheney> ah ok
[18:40] <ccheney> i tried locking by the power button in the top right of the screen in lucid
[18:40] <ccheney> it does nothing though :-\
[18:40] <ccheney> chrisccoulson: so i think that is the applet you are talking about?
[18:40] <chrisccoulson> ccheney - yeah, it's broken because of my change to gnome-screensaver to delay starting it
[18:40] <chrisccoulson> yeah, thats the applet i'm talking about
[18:40]  * ccheney larts chrisccoulson for breaking stuff ;-)
[18:41] <chrisccoulson> heh, yeah, that's my fault :P
[18:43] <dholbach> kenvandine: did you guys see a bug about the indicators that rhythmbox is not shown although it's running (up-to-date lucid)?
[18:45] <kenvandine> dholbach, i haven't seen that
[18:46] <dholbach> kenvandine: which source package should I report a bug on and what kind of info do you need?
[18:46] <kenvandine> rhythmbox
[18:47] <kenvandine> the patch is to a plugin that is included
[18:47] <slangasek> charlie-tca: sorry, who's "most of us"?  The two folks who have laptops I've looked at haven't needed to Alt+SysRq+K anything
[18:47] <Sarvatt> Heyo, anyone around that works with plymouth? Got a patch for it to work with the linux-backports-modules-nouveau kernel module that is being worked on now and is not really upstream material -- http://sarvatt.com/downloads/patches/0001-src-plugins-renderers-drm-plugin.c-Add-check-for-lbm.patch
[18:47] <charlie-tca> Sorry, I had two or three in #ubuntu+1 with this issue
[18:48] <charlie-tca> It seems to be the way around the garbled gdm screen that appears after update to the -12 kernel in lucid
[18:53] <dholbach> kenvandine: awesome, will do
[18:53] <kenvandine> dholbach, thx
[19:01] <dholbach> kenvandine: bug 516685
[19:02] <Keybuk> james_w: around?
[19:04] <StevenK> cjwatson: I'm going to try a sync of a package that is quilt 3.0 and orig.tar.bz2, I'll let you know if it goes bang
[19:05] <StevenK> cjwatson: Looks fine ...
[19:05] <kenvandine> dholbach, thx
[19:05] <dholbach> no worries
[19:18] <lifeless> pitti: ping :P
[19:20] <pitti> lifeless: hi; will get to the merge, still debugging pm-utils
[19:21] <lifeless> kk
[19:21] <lifeless> I can get someone else to do it if you like
[19:22] <pitti> sure, go ahead
[19:25] <seb128> DktrKranz, hi
[19:26] <seb128> DktrKranz, do you think you could get the change from bug #495326 in debian?
[19:26] <seb128> DktrKranz, we need it in lucid and since the package is in sync right now...
[19:26] <StevenK> seb128: That looks like the wrong number ...
[19:27] <seb128> StevenK, why?
[19:28] <StevenK> seb128: There's no Debian task, and I didn't think lazr.restfulclient was in Debian
[19:29] <seb128> StevenK, well the fix is upstream now so there is no real reason to add a debian task there
[19:29] <seb128> and it is in debian and in sync right now
[19:34] <cjwatson> StevenK: oh, did somebody fix soyuz?
[19:35] <StevenK> cjwatson: It seems so, it got synced correctly, and went through source and binary NEW easily
[19:35] <StevenK> But let's see if the publisher goes BANG
[19:36] <DktrKranz> seb128: hi! I think I can easily cherrypick and upload it. I don't have main upload privileges, may I ping you so you can eventually sync it?
[19:37] <seb128> DktrKranz, yes, I was going to upload to lucid but I figured it would be better to get it in debian
[19:37] <seb128> DktrKranz, thanks
[19:37] <seb128> DktrKranz, I will sync when it's uploaded to debian
[19:38] <DktrKranz> seb128: I don't think I beat dinstall, so you have to sync from incoming. Is that still possible?
[19:38] <seb128> DktrKranz, yes
[19:38] <seb128> thanks
[19:38] <DktrKranz> ok then
[19:45] <zul> cjwatson: ping
[19:46] <pitti> kees: http://cgit.freedesktop.org/pm-utils/tree/src/import-fdi-quirkdb.in#n75
[19:47] <cjwatson> zul: yes?  (please include content with pings :-) )
[19:47] <tkamppeter> pitti, can you help Stew Ellis on bug 447961? He has problems installing CUPS from -proposed.
[19:48] <zul> cjwatson: sorry im going to adding an apport hook to openssh do you want to review it first or should I just upload it
[19:48] <cjwatson> zul: I answered yesterday - I'd like to review it, please
[19:48] <zul> cjwatson: ah ok i didnt see it yesterday ;)
[19:49] <StevenK> slangasek: Is yada still trying to enter main? I have this feeling I got 70% through a yada-repackage
[19:49] <cjwatson> zul: feel free to commit it to lp:~ubuntu-core-dev/ubuntu/lucid/openssh/lucid though
[19:49] <cjwatson> zul: is there some urgent need for it? :-)  openssh doesn't get many crash reports
[19:49] <zul> cjwatson: no urgency its just apart of the server-lucid-apport-hooks spec
[19:50] <cjwatson> zul: ah, ok
[19:50] <cjwatson> the spec is missing /etc/ssh/ssh_config, which is useful for client bugs
[19:51] <cjwatson> I imagine the hook should be binary-package-specific if possible
[19:51] <zul> cjwatson: will do
[19:53] <slangasek> StevenK: see components-mismatches?  I don't know if it's still trying to get back
[19:57] <geser> zul: Hi, in case you didn't notice: your php5 upload depwaits on libmcrypt-dev, looks like it slipped though in the merge
[19:58] <zul> geser: thanks ill take a look
[20:09] <StevenK> slangasek: No yada, so I guess we are safe :-)
[20:09] <slangasek> Riddell: what's happening with koffice-l10n?  It's removed in Debian, and ISTR hearing that was specific to old koffice and should also eventually be removed for us - or should it be sync-blacklisted instead?
[20:11] <Riddell> slangasek: we probably want to sync it from debian experimental
[20:11] <Riddell> our koffice update is blocked on MIRs currently
[20:12] <slangasek> hmm, when is koffice-l10n going to re-enter unstable then?
[20:12] <Riddell> I don't know I'm afraid
[20:12] <slangasek> doh
[20:12] <StevenK> Riddell: How many MIRs?
[20:12] <ScottK> Piles
[20:13] <Riddell> StevenK: 6
[20:13] <StevenK> 6 is not piles
[20:13]  * ScottK thought he'd take longer to answer so the phear would build.
[20:14]  * StevenK has submitted and argued for a large number of MIRs
[20:14] <Riddell> it's enough to stop it progressing anyway
[20:15] <Riddell> we could really do with more main inclusion reviewers
[20:19] <ScottK> StevenK: I know the feeling.  IIRC I had to do 22 or some similar number to get spamassassin in Main.
[20:24] <Riddell> asac, lool: got any MIR time schedule in the near future for those koffices ones you have assigned?
[20:28] <lifeless> pitti: james_w is uploading it
[20:34] <dpm> ccheney, doko, would you have a few minutes after lunch to discuss OO.o translations?
[20:35] <ion> keybuk: Please see my last comment in LP #506727.
[20:36] <Keybuk> ion: I'm not reading bugs at the moment
[20:37] <doko> dpm: is there anything to add after the uds discussion?
[20:37] <didrocks> currently Quickly use python-mkdebian from python-distutilsextra which needs debchange and so, devscripts. devscripts recommends bsd-mailx | mailx | mailutils and by and large, postfix is installed with the awful debconf question. What do you think about putting the recommends as only a suggests and patch the scripts using mail to tell something like "you need blablabla package"?
[20:39] <dpm> doko, I'd simply like to know what the current status is. Translations in LP are scheduled to be open tomorrow, and if the infrastructure for importing and exporting translations is not working, I think we should disable them from Launchpad.
[20:40] <dpm> (disable does not mean deleting, just hiding the templates in the UI in order not to create false expectations on translators that their translations will be included in Ubuntu)
[20:40] <doko> dpm: afaik ccheney did commit to updating the import/export for lucid and have the translations from lp included in the -l10n package
[20:42] <dpm> doko, yes, that was in UDS, I just want to have a quick chat to know about the current status, if this is still doable, and whether there is something else to do on the LP side (e.g. enabling or disabling translations)
[20:43] <lamont> didrocks: what "awful debconf question"
[20:43] <lamont> didrocks: what "awful debconf question"
[20:43] <lamont> ?
[20:44] <LaserJock> lamont: the questions about how to set up postfix
[20:45] <LaserJock> like satelite, host only, no config, smart server, or something along those lines
[20:46] <didrocks> LaserJock: the relayhost one, yes
[20:46] <didrocks> lamont: ^
[20:47] <LaserJock> didrocks: I would love to see such a patch to debscripts
[20:48] <LaserJock> that issue has annoyed me for the last few years but I not enough to write one myself
[20:48] <didrocks> LaserJock: should be pretty easy to fix, but I prefer to have some feedback on it first :)
[20:49] <lamont> well, that's what you get for recommending an MTA
[20:52] <didrocks> lamont: that's why I think we can just suggests it and tweak the scripts to help the user/dev
[20:53] <ccheney> dpm: have not had time to even look at it since i have been focused on firefox related issues
[20:54] <slangasek> doko: you uploaded sagemath for python 2.6, but left a build-dependency on libboost-python1.38-dev...
[20:54] <ccheney> dpm: i got OOo 3.2 uploaded but only to make sure it got in under the FF deadline in a working state
[20:54] <dpm> ccheney, no worries, I just wanted to know the status. I think for now the best would be to disable them in LP until you've had the time to have a look at them
[20:54] <ccheney> dpm: yea
[20:55] <dpm> ccheney, ok, but still, I think it'd be good to have a quick chat about it, would you have a few mins later on?
[20:55] <ccheney> dpm: ok
[20:55] <doko> slangasek: ok, will have a look, was just a no change upload
[20:56] <persia> kees: armel schroots are now buildable: after fixing another little bobble.  It's still in bzr though.
[20:56] <ccheney> anyone able to upload to ubuntu?
[20:56] <ccheney> its hanging for me atm
[20:56] <dpm> thanks ccheney :)
[20:57] <persia> ccheney: The last-1Kbyte hang, or a different one?
[20:58] <ccheney> well with dput it just hangs directly after checking signatures
[20:58] <ccheney> last 1k byte hang usually is a local router issue
[20:59]  * ccheney will try copying to chinstrap then uploading from there
[20:59] <ccheney> worked fine from there, very strange
[20:59] <ccheney> and the scp to chinstrap worked fine also
[21:01]  * ccheney bbl lunch time
[21:01] <kees> persia: \o/
[21:02] <persia> kees: http://paste.ubuntu.com/368455/
[21:42] <Keybuk> kees: when you get a moment, could you come down to the Foundations room
[21:52] <DktrKranz> seb128: lazr.restfulclient uploaded and available on incoming, all yours :)
[22:22]  * ccheney still can't upload directly from home, this is annoying :(
[22:23] <ccheney> actually i'm not uploading from home, i'm uploading from my laptop, hnmm
[22:23] <ogra> slangasek, did you upload the plymouth fix that should make it work on imx51 already ?
[22:23] <slangasek> ogra: yes
[22:23] <ogra> hmm
[22:23] <slangasek> did it build on arm yet?
[22:23] <ogra> we dont have a splash on the current live image
[22:24] <ogra> oh, didnt check yet
[22:24]  * ogra goes to look
[22:24] <ccheney> ah passive mode :)
[22:24] <slangasek> yah, it's built on arm
[22:24] <ogra> right
[22:24] <slangasek> does the current live image have 0.8.0~-8 on it?
[22:24] <ogra> i'll check soon, cant access it atm
[22:25] <seb128> DktrKranz, thanks
[22:30] <ogra> slangasek, manifest says it has 0.8.0~-8
[22:30] <ogra> http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-live/20100203/lucid-netbook-armel+imx51.manifest
[22:31] <slangasek> hmm
[22:32] <lifeless> james_w: so we're happy that the debhelper bug is fixed?
[22:34] <slangasek> ogra: please give me the value of readlink /lib/plymouth/themes/default.plymouth; it's possible this is a separate bug
[22:34] <slangasek> (I don't see any mistakes in my code)
[22:34] <ogra> will do
[22:34] <ogra> i'm just downloading it, i cant access the one booted instance atm
[22:34]  * slangasek nods
[22:43] <ogra> slangasek,
[22:43] <ogra> ubuntu@ubuntu:~$ readlink /lib/plymouth/themes/default.plymouth
[22:43] <ogra> ubuntu-logo/ubuntu-logo.plymouth
[22:43] <ogra> looks ok to me
[22:44] <slangasek> ogra: yep - so it's a different bug :)
[22:44] <ogra> ubuntu@ubuntu:~$ plymouth-set-default-theme
[22:44] <ogra> ubuntu-logo
[22:44] <slangasek> what's your framebuffer?  (cat /proc/fb)
[22:44] <ogra> seems ok
[22:44] <ogra> 0 DISP3 BG
[22:44] <ogra> 1 DISP3 BG - DI1
[22:44] <ogra> 2 DISP3 FG
[22:44] <slangasek> ooookay... what are those? :)
[22:45] <ogra> heh, mxcfb devices
[22:45] <ogra> plymouth worked on my former install so i know the framebuffer does actually work
[22:45] <ogra> i havent seen it since the theme was updated though
[22:46] <slangasek> is other fb output working?
[22:46] <ogra> sure, X is on the framebuffer
[22:47] <ogra> (we have no free driver for the GPU so it defaults to xfbdev)
[22:47] <slangasek> right
[22:47] <slangasek> ogra: can I come get a console on this?
[22:48] <ogra> console is no prob, we're a bit out od monitors atm
[22:48] <ogra> *of
[22:48] <ogra> but you can have a serail console
[22:48] <ogra> *serial
[23:12] <pitti> slangasek, Keybuk, tseliot: if you get complaints about plymouth breaking X.org and boot, hold on with debugging
[23:13] <pitti> I just found out that gdm's "force first server to vt7" patch does not work any more for some reason
[23:13] <pitti> I'm debugging that now
[23:14] <pitti> aah
[23:15] <pitti> the patch is just fine, but debian/patches/28_plymouth_transition.patch breaks it
[23:15] <pitti> it implements its own startup logic
[23:15] <Keybuk> pitti: yes, there is different startup logic if plymouth is running
[23:16] <Keybuk> since you want to re-use plymouth's vt, and not cause a vt switch
[23:16] <Keybuk> there's possibly an issue there if you're not on vt7 ;)
[23:16] <Keybuk> ie. if plymouth wasn't showing the splash
[23:16] <pitti> right, jdstrand booted without "splash"
[23:17] <Keybuk> yeah, that should still have switched vt
[23:17] <Keybuk> but it doesn't
[23:17] <pitti> for jdstrand, X.org always starts on vt1
[23:17] <pitti> which wreaks a lot of havoc
[23:18] <pitti> (you get the password and other input to vt1, control-C kills the server, etc.
[23:19] <pitti> Keybuk: would you recommend that 28_plymouth_transition.patch gets fixed to run X on vt7 again, or should we just stop having a getty on vt1?
[23:19] <Keybuk> pitti: no
[23:19] <Keybuk> neither
[23:19] <Keybuk> I would recommend that plymouth is fixed to switch to vt7 in the text/details case
[23:19] <Keybuk> it's a plymouth bug
[23:19] <Keybuk> it's actually outputting to vt7
[23:19] <Keybuk> it just forgot to switch
[23:19] <pitti> ok
[23:19] <Keybuk> if it had, then X would have inherited it
[23:20] <pitti> Keybuk: so I guess we still need to fix the patch to start X on vt7 the first time if we boot with "nosplash"?
[23:20] <Keybuk> no
[23:20] <Keybuk> no
[23:20] <Keybuk> no
[23:20] <Keybuk> we need to fix *plymouth*
[23:20] <pitti> "nosplash" -> no plymouth?
[23:20] <Keybuk> no
[23:20]  * pitti confused now
[23:20] <Keybuk> nosplash -> plymouth using a text output plugin, rather than a graphical one
[23:21] <pitti> ah
[23:21] <Keybuk> you still need plymouth to arbitrate who's asking for input, etc.
[23:21] <pitti> ok, got it
[23:21] <Keybuk> when you have no splash, it means plymouth uses text.so or details.so instead of drm.so or fb.so
[23:21] <Keybuk> the code to do the vt switch is missing in the text/details case
[23:21] <pitti> Keybuk: that actually means that we can drop this hideous 05_initial_server_on_vt7.patch patch
[23:21] <Keybuk> (it assumes drm/fb did it already)
[23:21] <Keybuk> pitti: in theory
[23:21] <Keybuk> pitti: I left that there so when people do "start gdm", it does flip to vt7
[23:22] <pitti> *nod*
[23:22] <pitti> ok, thanks for the heads up!
[23:23] <Keybuk> (from single user mode, etc.)
[23:23] <pitti> Keybuk: interestingly enough, when adding a sleep to the gdm upstart job it works just fine
[23:23] <Keybuk> sure
[23:23] <pitti> presumably because the getty is faster, or so
[23:23] <Keybuk> yeah
[23:23] <Keybuk> red car wins the race, despite stuffing its face, etc.
[23:25] <cjwatson> sigh, I broke grub.  again.
[23:25] <cjwatson> (not in the archive)
[23:26] <lamont> cjwatson: that's because you rock
[23:26] <cjwatson> "grub-probe: error: unknown filesystem."  not what you want to see w.r.t. /
[23:26] <lifeless> Keybuk: https://translations.edge.launchpad.net/ubuntu/karmic/+source/launchpad-integration/+pots/launchpad-integration/tlh/+translate - fully translated. a rgh.
[23:30] <Keybuk> I like the translation of Launchpad - taghwI'
[23:30] <Keybuk> "Thing the begins a process/initiates proceedings" - ie. launches
[23:33] <crimsun> hmm, bzr merge-package is (perhaps correctly) picky with the trailing / ("bzr: ERROR: Invalid source branch URL?")
[23:34] <ion> keybuk: The message i wanted you to see was about it seeming like mountall blocks while waiting for the user to either skip a mount or have mountall exit to shell when boredom_timer is triggered on a mount. IMO the prompt should be done asynchronously. If the device appears and the user hasn’t done anything by then, just hide the prompt and continue with the mount. The guy who reported the bug has the boot hang consistently to that prompt just because the ...
[23:35] <ion> ... device doesn’t happen to appear quickly enough.
[23:35] <Keybuk> ion: if you can work that out, do it ;)
[23:36] <ion> keybuk: I’ll try to get that done.
[23:44]  * Keybuk decides that Debian clearly needs to be translated to ghobchuq loDnI'pu'
[23:44] <Keybuk> lit. "The Brothers Fight One Another"
[23:46] <ion> Hah
[23:49] <cjwatson> ah, I didn't break grub, upstream did
[23:50]  * ogra files another plymouth bug so Keybuk doesnt get bored ...
[23:50] <StevenK> ogra: He's not bored, he's translating
[23:51] <ogra> StevenK, splash screens to klingon ?
[23:54] <StevenK> Keybuk: Idea from plars about Ubuntu in Klingon: "I have what I have because I killed you for it"
[23:55] <plars> StevenK: might require some small modifications to the CoC
[23:55] <StevenK> plars: I welcome a translation of the CoC into Klingon
[23:55] <Keybuk> StevenK: I was going with something like "My honour is mine because of the enemies of I have killed"
[23:59] <Keybuk> StevenK: Heghlu'meH QaQ jajvam
[23:59] <crimsun> StevenK: do you have plans to merge ekiga from squeeze soon?


[06:16] <jibel> Good morning
[06:38] <duflu> Morning jibel
[06:41] <oSoMoN> good morning desktoppers
[06:57] <duflu> Hi oSoMoN
[06:57] <oSoMoN> hey duflu
[07:07] <didrocks> good morning
[07:13] <duflu> Hi didrocks
[07:15] <didrocks> hey duflu
[07:16] <oSoMoN> salut didrocks
[07:16] <didrocks> salut oSoMoN
[07:20] <seb128> goood morning desktopers!
[07:20] <didrocks> salut seb128
[07:20] <duflu> Hi seb128
[07:26] <oSoMoN> salut seb128
[07:35] <seb128> hey didrocks, duflu, oSoMoN, how are you? had a nice weekend?
[07:37] <didrocks> seb128: yeah, was nice, nothing really special, and you?
[07:38] <seb128> it was alright, nothing special either
[07:38] <duflu> seb128, not bad... until I snapped the keyboard cable on my favourite laptop. One that I had never opened before. Otherwise good.
[07:39] <seb128> :-( for the laptop
[07:39] <duflu> I have parts and new tools arrived today so wish me luck
[07:43] <ricotz> hello desktopers!
[07:47] <seb128> hey ricotz, how is it going? feeling better?
[07:48] <oSoMoN> seb128, very good long week-end, yes.
[07:48] <oSoMoN> hey ricotz
[07:49] <duflu> Hi ricotz
[07:50] <ricotz> seb128, hey, yeah, much better, symptoms are nearly gone :)
[07:50] <ricotz> oSoMoN, duflu, hi
[09:45] <lissyx> oSoMoN, seb128, so we can't access earlier versions of snaps from the store, what about the API ?
[09:46] <lissyx> I'm trying to use https://api.snapcraft.io/docs/info.html but it returns 404
[09:46] <oSoMoN> lissyx, afaik, one can access old revisions, but only if they are listed as a contributor to the snap
[09:46] <lissyx> which means I dont have access :)
[09:47] <oSoMoN> and I'm guessing the API would behave the same
[09:47] <lissyx> meh the endpoint is different between v1 and v2
[09:50] <seb128> I'm unsure why they block access to old revision by default but that's a store question
[09:51] <lissyx> not being able to access older versions even from the API will make me basically unable to pull debug symbols
[09:51] <lissyx> I have not been able to find who is supposed to add me to the list of contributors ...
[09:56] <seb128> lissyx, oSoMoN and me have access to do that, but I think mkaply has been handling the mozilla side
[09:56] <seb128> we need at least to ask him before adding someone I think
[09:56] <lissyx> I also need to find how I can auth myself on the api
[10:00] <seb128> lissyx, you can use snap download --revision , unless you prefer to not depend on the snap cmd?
[10:01] <lissyx> well I was hoping to be able to use only the API
[10:01] <lissyx> since auth flow with snap CLI will be interactive
[10:02] <lissyx> seb128, also I would still need something to know those revisions number :/
[10:05] <oSoMoN> lissyx, once you're a collaborator to the snap, you have access to a web dashboard that lists all revisions, with details about the build
[10:06] <lissyx> right, but that's not really practical
[10:06] <seb128> what are you trying to do there?
[10:07] <lissyx> OH
[10:07] <lissyx> seb128, pulling symbols from snapstore once we have then in the snap?
[10:07] <lissyx> > The client must send the Snap-Device-Series and User-Agent mandatory headers. For the Snap-Device-Series header, the only supported value so far is '16'.
[10:07] <lissyx> looks like with this header set to 16 ... I get a full list?
[10:07] <lissyx> at least of the current ones
[10:07] <lissyx> not previous ones
[10:08] <seb128> lissyx, I've set up a meeting for tomorrow with launchpad people to try if we could do something to be able to export or upload the symbols as part of the build, I will let you know if there is anything coming out of it
[10:09] <lissyx> seb128, I'm afraid that until we can have proper handling of secrets, that's going to be complicated
[10:09] <seb128> lissyx, but if you get a snap revision, what do you need to match it with?
[10:10] <lissyx> seb128, sorry, I dont get your "match it with" ?
[10:10] <seb128> > <lissyx> seb128, also I would still need something to know those revisions number :/
[10:11] <seb128> I think I didn't understand what you meant there
[10:11] <lissyx> seb128, well you said "you could try snap download firefox --revision <ID>"
[10:11] <lissyx> I'd still need those IDs
[10:11] <seb128> ah, sorry
[10:11] <seb128>   latest/stable:    101.0.1-1    2022-06-09 (1443) 170MB -
[10:11] <seb128>   latest/candidate: 102.0-2      2022-06-25 (1492) 169MB -
[10:11] <seb128>   latest/beta:      102.0b9-1    2022-06-17 (1467) 169MB -
[10:11] <seb128> those are the number in parenthesis in the snap info output
[10:13] <seb128> lissyx, https://git.launchpad.net/ubuntu-desktop-versions/tree/snaps.py#n85 might be of use to you
[10:14] <lissyx> seb128, nice, thanks
[10:14] <lissyx> right now, it'd be awesome if I could get confirmation from someone knowledgeable of Snap Store that this API you linked (and I was already trying to use) will output me
[10:14] <lissyx> **all** revisions
[10:14] <lissyx> and not just the current ones
[10:15] <seb128> https://api.snapcraft.io/docs/info.html
[10:16] <seb128> 'Get info from the snap and its released revisions.'
[10:16] <lissyx> yes
[10:16] <seb128> I'm unsure but I think 'released' means currently published
[10:16] <seb128> #snappy might be a better place for snap questions though
[10:16] <lissyx> already tried there
[10:17] <lissyx> ah no on #snapcraft
[10:29] <lissyx> ok if I can get all currently published revisions that's already a first sstep in the good direction
[11:29] <seb128> lissyx, in theory you don't need past revisions though if the system keep up with builds?
[11:30] <lissyx> seb128, what happens if we loose the history of the past builds and we need to rebuild it?
[11:31] <lissyx> e.g., something breaks pulling debug symbols, nobody notices for a few weeks, once it's fixed we loose debug info for revisions published in the meantime?
[11:31] <seb128> that can be a manual work from someone having contributor access to the snap
[11:32] <seb128> btw I emailed about give you contributor access, I will let you know if/when I get a reply
[11:32] <lissyx> having to rely on a manual process will only be cumbersome
[11:49] <lissyx> seb128, another case is if you publish several revisions between our runs, we wont have them
[11:53] <seb128> lissyx, k, taking one step back. Is the 'server might loose debug symbols already uploaded' a real usecase?
[11:54] <seb128> lissyx, if so it means we should discard a solution that upload the symbols to the service during the build without storing them somehow as well?
[11:54] <seb128> because if we do that we will not be able to re-upload things lost later on if needed
[11:55] <seb128> I was going to approach that issue asking the launchpad team about a way to get a secret, but that isn't enough then
[11:55] <lissyx> seb128, i'm not referring to the debug symbol here
[11:55] <lissyx> the debug symbol server
[11:56] <lissyx> I'm worrying what happens if for some reason the taskcluster scheduled task is not running / failing to pull data for some time
[11:56] <lissyx> which can happen if we run on a 24h schedule and you publish more than one revision in that interval for example
[11:56] <seb128> right
[11:57] <seb128> well, that's only an issue if we can't get the upload done from the snap build itself
[11:57] <lissyx> indeed
[11:57] <seb128> so I'm focussing on trying to resolve properly first
[11:57] <lissyx> that's why my PR adds support for uploading from GitHub Actions
[11:57] <seb128> right
[11:57] <seb128> well I wouldn't spend more time on plan B solution at this point
[11:57] <lissyx> if we can be sure we will have a proper solution in a timely manner for launchpad as well, I can live with that
[11:58] <seb128> as said earlier we have a meeting with launchpad people tomorrow so see what are our options
[11:58] <seb128> so I would suggest to wait for the outcome of that meeting
[11:58] <seb128> also there are several plan B options
[11:59] <seb128> including setting up a job on our side to store the firefox snap past revisions $somewhere
[11:59] <seb128> I'm unclear why the store makes that private by default, I will ask them
[11:59] <seb128> but there is probably no risk storing those .snap if we need them
[12:00] <lissyx> well if it was private but accessible through the API it would not be a big deal as long as I find doc on how to auth :)
[12:00] <lissyx> (we need a solution on taskcluster to pull symbols from distros anyway, doing it for snap is the good canditate to push me to help my colleague and get that landed, it's not time lost)
[12:03] <jbicha> good morning
[12:08] <seb128> jbicha, hey, how are you?
[12:11] <jbicha> good :)
[12:17] <seb128> lissyx, I don't know about the auth but worth asking on #snappy or forum.snapcraft.io
[13:28] <ricotz> nteodosio, hey, great to see the poppler patch for libreoffice accepted, the 7.3.5~rc1 upload later this week will take care of the transition :)
[13:31] <nteodosio> hey ricotz, that's great news! Thank you for your help last week, much appreciated.
[14:23] <lissyx> seb128, yep I did on #snappy, but I was told it's not exposed at all it seems
[14:23] <lissyx> seb128, that being said, if you manage to get timeout  + secrets fixed on launchpad, it will likely not be such a big deal
[14:24] <lissyx> seb128, local snap I can extract and upload symbols, and online I can pull all from snap store: https://treeherder.mozilla.org/jobs?repo=try&revision=e5fcf7e9dec17134da939a82806719230b2cdd84
[14:24] <lissyx> seb128, now I just need to make sure I keep note of processed snaps, and we should be all good to have something that is ready
[14:25] <lissyx> seb128, and the counterpart https://github.com/canonical/firefox-snap/pull/3 should allow to publish directly from github actions, and package altogether the zip into the snap for the store
[14:48] <seb128> lissyx, great!
[18:35] <lissyx> seb128, https://treeherder.mozilla.org/jobs?repo=try&revision=8505ba516801c04126d3f26f577a536bca7a7735&selectedTaskRun=A6l2O451TBeuOpjtVjZeUQ.0 :)
[18:53] <KGB-2> gnome-control-center ubuntu/jammy e0e1f71 Jeremy Bicha * pushed 29 commits (first 5 follow) * https://deb.li/9yY1
[18:53] <KGB-2> gnome-control-center ubuntu/jammy 3c47db2 sicklylife po/ja.po * Update Japanese translation * https://deb.li/CWfc
[18:53] <KGB-0> gnome-control-center signed tags 1f7042c Jeremy Bicha ubuntu/1%41.7-0ubuntu<IP_ADDRESS> * gnome-control-center Debian release 1:41.7-0ubuntu<IP_ADDRESS> * https://deb.li/3sWON
[18:53] <KGB-2> gnome-control-center ubuntu/jammy 65c1c73 Yuri Chornoivan po/uk.po * Update Ukrainian translation * https://deb.li/3c13y
[18:54] <KGB-2> gnome-control-center ubuntu/jammy f338510 Bruce Cowan po/en_GB.po * Update British English translation * https://deb.li/6PBG
[18:54] <KGB-2> gnome-control-center ubuntu/jammy 7b0c55b Ian Douglas Scott panels/keyboard/cc-keyboard-shortcut-dialog.c * keyboard: Avoid segfault due to no "data" for `custom_shortcut_add_row` * https://deb.li/iwyKM
[18:54] <KGB-2> gnome-control-center ubuntu/jammy 34b5db1 Jeremy Bicha panels/wwan/gnome-wwan-panel.desktop.in.in * wwan: Remove duplicate line from .desktop * https://deb.li/KPMI
[18:54] <KGB-2> gnome-control-center signed tags 96382d7 Jeremy Bicha ubuntu/1%41.7-0ubuntu1 * gnome-control-center Debian release 1:41.7-0ubuntu1 * https://deb.li/3PyRA
[18:54] <KGB-2> gnome-control-center signed tags 5540495 Jeremy Bicha upstream/41.7 * Upstream version 41.7 * https://deb.li/s1je
[18:54] <KGB-0> gnome-control-center upstream/41.x fa37b59 Jeremy Bicha * pushed 23 commits (first 5 follow) * https://deb.li/36gv0
[18:54] <KGB-0> gnome-control-center upstream/41.x 15b8ebf Hugo Carvalho po/pt.po * Update Portuguese translation * https://deb.li/b34z
[18:54] <KGB-0> gnome-control-center upstream/41.x ff6ffbb Quentin PAGÈS po/oc.po * Update Occitan translation * https://deb.li/39Pzs
[18:54] <KGB-0> gnome-control-center upstream/41.x a66e785 Felipe Borges panels/info-overview/ cc-info-overview-panel.c cc-info-overview-panel.ui * info-overview: Allow changing "Device Name" by pressing "Enter" * https://deb.li/3xWDv
[18:54] <KGB-2> gnome-control-center pristine-tar 53c511d Jeremy Bicha gnome-control-center_41.7.orig.tar.xz.delta gnome-control-center_41.7.orig.tar.xz.id * pristine-tar data for gnome-control-center_41.7.orig.tar.xz * https://deb.li/3x10l
[18:54] <KGB-0> gnome-control-center upstream/41.x 82366a0 Kjartan Maraas po/nb.po * Update Norwegian Bokmål translation * https://deb.li/ilqsn
[18:55] <KGB-0> gnome-control-center upstream/41.x 00362a9 Kjartan Maraas po/nb.po * Update Norwegian Bokmål translation * https://deb.li/7Eg