 right, anything else infra-wise that's busted and needs my attention
 just checking in of course :)
[01:28]  * tsimonq2 sets up Chaos Monkey to keep teward busy
[16:06] <arraybolt3[m]> OK, back in action. Simon Quigley I don't think I have the necessary access in Phab to do everything documented here: https://github.com/lubuntu-team/new-release
[16:06] <arraybolt3[m]> oh wait maybe I do?
[16:07] <arraybolt3[m]> Heh, nevermind, I do. Add that to the list of things I didn't know I was able to do.
[16:11] <arraybolt3[m]> And the stuff I probably don't have access to there I have access to in Gitea.
[16:18] <arraybolt3[m]> Testing wiki update complete.
[16:19] <arraybolt3[m]> (I may be slow since I'm juggling, but the process is in progress.)
[16:23] <arraybolt3[m]> Do we still want to be using the Phab sidebar, or should I be making that universal Gitea repo and starting to do stuff there instead? Simon Quigley, teward, Dan Simmons
[16:25] <arraybolt3[m]> OK so somehow I lost all of the branches of lubuntu-meta except for ubuntu/jammy...
[16:26]  * arraybolt3[m] digs
[16:26] <arraybolt3[m]> Yep, just plain gone. Sigh. And I used git push --all...
[16:29] <arraybolt3[m]> Wow. So this is what I missed: https://stackoverflow.com/questions/10312521/how-do-i-fetch-all-git-branches And that is... insanely complicated.
[16:29] <arraybolt3[m]> At least it looks like it.
[16:32] <teward> fyi `git pull --all` exists
[16:32] <arraybolt3[m]> That doesn't do it.
[16:32] <arraybolt3[m]> My problem is that "git branch -r" shows me all the branches, and "git branch" shows me just one.
[16:33] <arraybolt3[m]> I need to pull every branch.
[16:33] <arraybolt3[m]> And now I just wiped my master command to do that...
[16:36] <tsimonq2> git fetch --all
[16:37] <tsimonq2> git pull --all likely replaces your local copies, git fetch is just updating what is considered to be the latest remote reference
[16:38]  * arraybolt3[m] sent a code block: https://libera.ems.host/_matrix/media/v3/download/libera.chat/c08e1d7ffb03bcdc51786e4d10e65aa2ffe55318
[16:40] <arraybolt3[m]> Bash makes my brain hurt.  This is what finally did the trick: mangled command here
[16:41] <arraybolt3[m]> Yes, that is two nested subshells within a subshell used in a for loop.
[16:42] <arraybolt3[m]> And yes, it throws some errors since the output of git branch -r isn't quite right but it's close enough for it to work.
[16:43] <tsimonq2> If you're concerned about losing branches, just remember that we should still have at least a get up here and maybe even a launch pad mirror, if not fabricator itself even though all those services have been turned off
[16:44] <arraybolt3[m]> Talk to texans?
[16:44] <tsimonq2> As a general rule I would tell you when you're pushing to a good repository that other people have to use, never use a command like get pulled all because it will have some negative unintended consequences
[16:44] <tsimonq2> This was a fairly good case of that where it isn't that impactful
[16:44] <arraybolt3[m]> tsimonq2: OK.
[16:46] <tsimonq2> To clarify now that I'm stopped... I'm glad this happened while we still have mirrors :P
[16:46] <arraybolt3[m]> I can't believe Git made it this hard. Like, really, is getting a full list of all branches that unusual?
[16:47] <arraybolt3[m]> Anyway this should be fairly easy to fix.
[16:51] <tsimonq2> arraybolt3[m]: git fetch
[16:51] <tsimonq2> fetch the status of the remote without pulling it (which clubbers your existing stuff)
[16:52] <tsimonq2> s/clubbers/clobbers/
[16:53] <arraybolt3[m]> Simon Quigley:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/013148df4a607924c26f42fb9618d099ef0c805a>)
[16:53] <tsimonq2> git remote add mirror URL && git fetch --all && git push origin mirror/ubuntu/kinetic:ubuntu/kinetic (or similar)
[16:54] <tsimonq2> one repo one clone less network needed :)
[16:54]  * tsimonq2 more coffee
[17:04] <arraybolt3[m]> OH I GET IT.
[17:04] <arraybolt3[m]> Only just now did the last "git push" command click.
[17:07] <tsimonq2> I would rather take this slow enough for you to learn than rush and do this for you - now you know how to deal with such a situation, I'm glad :)
[17:08] <tsimonq2> Thanks for having enough patience with Git. I have a feeling you're past the Dunning-Kruger peak :P
[17:09] <arraybolt3[m]> LOL don't get your hopes up quite yet... I want to get there but this is really tricky.
[17:09] <arraybolt3[m]> Simon Quigley: OK so I'm still a bit confused here.
[17:10] <arraybolt3[m]> Simon Quigley: On Gitea, the only branch is ubuntu/jammy.
[17:10]  * tsimonq2 uploaded an image: (47KiB) < https://libera.ems.host/_matrix/media/v3/download/linuxdelta.com/QuzWEQOogLbqSiQzhpHolgYi/1024px-Dunning%E2%80%93Kruger_Effect_01.svg.png >
[17:10] <arraybolt3[m]> On Phab, there's lots of branches.
[17:10] <tsimonq2> arraybolt3[m]: The only branch or the default branch?
[17:10] <arraybolt3[m]> tsimonq2: The only branch. All the older ones are missing.
[17:10] <arraybolt3[m]> Also it looks like we neglected to make an ubuntu/kinetic branch last cycle, somehow.
[17:10] <tsimonq2> arraybolt3[m]: Doesn't surprise me. It's okay, processes get defined this cycle :)
[17:11] <arraybolt3[m]> So I'm trying to get all of the older branches to migrate also.
[17:11] <arraybolt3[m]> I just want to mass-move all the branches from Phab onto Gitea.
 Humm..now measuring 😊 metacognitive abilites...
[17:11] <tsimonq2> here go https://stackoverflow.com/questions/37884832/git-push-all-branches-from-one-remote-to-another-remote
[17:12] <arraybolt3[m]> Ah, that looks more right.
[17:12] <arraybolt3[m]> (What I was trying to do is clone from Phab, change the origin URL to Gitea and then push. Now I'm realizing that's the wrong way to do that.)
[17:12] <tsimonq2> @Leokolb: It's always in my head when training new people... "where are you on the curve?" I've seen enough of this to be patient :P
[17:13] <tsimonq2> arraybolt3[m]: It's not the wrong way to do it necessarily, it's just easier and more "best practice" to do it this way instead
[17:13] <tsimonq2> (Add the remote instead of replacing)
[17:13] <arraybolt3[m]> Perfect. Alright, let's try it.
[17:15]  * arraybolt3[m] starts playing MercyMe's "We Win"
[17:16] <arraybolt3[m]> OK so now I guess I do that to the other three migrated repos.
[17:23] <arraybolt3[m]> Turns out lubuntu-meta was the only repo with multiple branches.
[17:23] <arraybolt3[m]> So I guess that's taken care of now.
[17:23] <arraybolt3[m]> (The only repo that was migrated the other day, I mean.)
[17:33] <tsimonq2> Very nice! Thank you :)
[17:34] <tsimonq2> TIL `set -eux && echo $DEBEMAIL` crashes QTerminal :P
[17:37] <arraybolt3[m]> OK I just had yet more personal junk hit, but not as severe as last time. Probably going to be gone for about an hour or so, brb asap.
[19:06] <arraybolt3[m]> Alright that took forever.
[19:14] <arraybolt3[m]> lubuntu-meta update.cfg reconfigured for Lunar.
[19:14] <tsimonq2> arraybolt3[m]: If it builds, let me know, I'll upload
[19:15] <tsimonq2> (I'm willing to bet though, unless you grab my debootstrap from the Lunar queue, download, build, and install it, that it will fail)
[19:15] <arraybolt3[m]> Oh hold on it's not that far done.
[19:15] <arraybolt3[m]> (I checked gitk to see how it was done and missed badly now that I'm looking at the changelog...)
[19:15] <tsimonq2> No worries, take as much time as you need
[19:16] <arraybolt3[m]> OK I'm starting to get it. (debootstrap from the Lunar queue?)
[19:17] <tsimonq2> https://launchpad.net/ubuntu/lunar/+queue
[19:17] <tsimonq2> `Show` -> `Unapproved`
[19:17] <tsimonq2> `Search`
[19:17] <tsimonq2>  * `Update`
[19:17] <arraybolt3[m]> Yikes, wait, I'm supposed to install that on the system that does the building?
[19:18] <arraybolt3[m]> If so, /me needs time to spin up a VM
[19:18] <tsimonq2> well I'm the one that authored the upload, let me tell you how to jerry-rig it for your system ;)
[19:18] <tsimonq2> symlink `/usr/share/debootstrap/scripts/gutsy` -> `/usr/share/debootstrap/scripts/lunar`
[19:18] <tsimonq2> and debootstrap will magically work
[19:19] <arraybolt3[m]> And that's after installing Lunar's debootstrap on my system, or I just do that with the one I have here?
[19:19] <tsimonq2> You can just do that with the one you have installed
[19:19] <tsimonq2> (That's all the upload does; create that symlink)
[19:20] <arraybolt3[m]> Oh! I get it! So eventually that upload will end up in all Ubuntu systems anyway, right?
[19:20] <arraybolt3[m]> (I am going to make the symlink, I'm just making sure I understand how things work here.)
[19:22] <tsimonq2> arraybolt3[m]: Right :)
[19:22] <tsimonq2> (Although, I don't often see debootstrap SRUs)
[19:23] <arraybolt3[m]> 👍, ok, cleaning up loose ends and then here goes!
[19:24] <arraybolt3[m]> Simon Quigley: Just to be clear on something, I see that for each release except the ones that got skipped, there's a "Welcome to Hirsute", "Welcome to Jammy', etc. commit in Git. I assume that commit isn't made until the release is put out, right?
[19:24] <arraybolt3[m]> Like I'm not about to make a "Welcome to Lunar" commit.
[19:27] <tsimonq2> Your assumption is incorrect :)
[19:27] <tsimonq2> Many of the uploads you've just seen from me have the text "Welcome to the Lunar Lobster!"
[19:27] <tsimonq2> "Welcome" messages are usually done at the beginning of the cycle, is what I'm trying to say
[19:28] <arraybolt3[m]> Ah. That's why I asked. :)
[19:28] <arraybolt3[m]> I just noticed lots of changes that lookedl ike they were made late in the cycle (version number changes and the like) in the "Welcome to jammy" commit.
[19:28] <arraybolt3[m]> So... how exactly does that work? Are those changes made early in the cycle?
[19:29] <tsimonq2> I can only speak for my time as Release Manager and my governance of such things - I personally take the approach of "as soon as we release the latest one, jump on as much as you possibly can, get it all updated, and we'll be able to spend more time working out the kinks and less time updating version numbers"
[19:30] <tsimonq2> That's also part of the reason I decided to personally get involved in the Qt 5.15.7 transition; the more time we have to find Qt bugs, the more mature things tend to be when it actually is crunch time :)
[19:31] <tsimonq2> That's my entire point of "hey, yo, everyone take the weekend off" because someone needs to hold the executive position, I'm not comfortable putting some of this work on anyone else
[19:31] <tsimonq2> It's all documented, so you should be able to follow in my steps, but it's a huge burden
[19:31] <arraybolt3[m]> Makes sense. But... I don't know what we want Lunar's seed to look like this cycle.
[19:32] <arraybolt3[m]> I mean, in the "Welcome to Jammy" commit, we removed Trojita (I think) and stuff like that. So I guess the question is, what all should I add and remove right now?
[19:32] <arraybolt3[m]> Either that or else I'm badly confused and still need a bit of extra explanation.
[19:33] <tsimonq2> All of the lists in lubuntu-meta are automatically generated from the contents of the seed (see historical context, I made sure, a few years ago, that this was all Git and the main Ubuntu infrastructure supported it as such): https://lubuntu.me/lubuntu-seeds-are-now-in-git/
[19:34] <tsimonq2> lubuntu-meta should be updated every time the seed is updated, both the common Ubuntu seed and Lubuntu's
[19:34] <tsimonq2> Is that done in practice? lol nah
[19:34] <tsimonq2> That's where your confusion may come from
[19:34] <tsimonq2> "Welcome to Jammy" was just likely the first update they've done in a while
[19:35] <tsimonq2>  * "Welcome to Jammy" was just likely the first update they did that cycle
[19:35] <arraybolt3[m]> click I get it!
[19:35] <arraybolt3[m]> So I'm supposed to run whatever automatically updates those lists and then document the changes it makes in the changelog?
[19:35] <tsimonq2> I'd say yes, but I don't want you to get confused: the script even updates the changelog for you :)
[19:36] <arraybolt3[m]> Oh. :P Alright so it really is just "update that one file and then trigger everything".
[19:36] <tsimonq2> yep :)
[19:36] <arraybolt3[m]> So do I now run `./update`?
[19:37] <arraybolt3[m]> (I'm in the lubuntu-meta Git repo.)
[19:38] <tsimonq2> *Usually*, yes. First, I'd make sure the Git repo is in sync with the archive and `git log` is full of nice tags
[19:38] <arraybolt3[m]> Oh sap. That probably isn't true.
[19:38] <tsimonq2> (Make sure your baseline is established and in-sync with the archive before you make the changes, is what I'm saying.)
[19:38] <arraybolt3[m]> Right. I always forget to do that.
[19:38] <tsimonq2> Well, you can create tags, that's no big deal, we've never required signed tags (that's a Fedora thing)
 Sometimes late people are late :/ (re @lubuntu_bot: (irc) <tsimonq2>  * "Welcome to Jammy" was just likely the first update they did that cycle)
[19:41] <tsimonq2> That's why I'm not taking the time to rail on you guys for it, it happens, you know?  No shame from me :)
[19:42] <arraybolt3[m]> OK so shoot. How do I delete just a branch on Gitea?
[19:42] <arraybolt3[m]> (I made the ubuntu/lunar branch a bit too early.)
[19:43] <tsimonq2> arraybolt3[m]: `git push REMOTE_NAME :MY_BRANCH`
[19:43] <tsimonq2> so in your case, *probably*, `git push origin :ubuntu/lunar`
[19:43] <tsimonq2> (`null` before `:` means delete the remote branch you're about to specify)
[19:43] <arraybolt3[m]> Nice, thanks!
[19:43] <tsimonq2> Of course :)
[19:45]  * tsimonq2 looks like a homeless person right now - about to go get my hair and beard cut :)
[19:45]  * tsimonq2 afk for probably an hour
[19:45] <arraybolt3[m]> o/
[19:50] <arraybolt3[m]> Ah, now not having an SSH key on my Launchpad profile has come back to bite me.
[19:50] <arraybolt3[m]> s/Ah/ArGH!/
[20:14] <arraybolt3[m]> Hey it's finally working! \o/
[20:19] <arraybolt3[m]> Sooo... I don't have a Lunar schroot that I can use to build this.
[20:20] <arraybolt3[m]> Do I just build it with Kinetic and hope for the best?
[20:21] <arraybolt3[m]> FWIW it builds with Kinetic just fine.
[20:29] <arraybolt3[m]> Also Lintian makes it look like I might should update some of the packaging, is that correct?
[21:43] <arraybolt3[m]> It's been two and a half years since we made any packaging changes to lubuntu-meta other than messing with the changelog. I'm going to declare it a good time to upgrade our packaging there if no one has any objections.
[21:43] <arraybolt3[m]> (Last it was updated was before Focal, looks like. It may have been longer than two and a half years.)
 "Do I just build it with Kinetic..." <- Pragmatically speaking: the underlying toolchain and packages have not changed at all during this point of the cycle. FWIW, I was able to create a Lunar schroot using the following syntax, after the local symlink dance: `mk-sbuild lunar --distro="ubuntu"`
[21:49] <tsimonq2> "Yes, you can technically still use a Kinetic schroot at this point in the cycle, but harumph, while it walks like a Kinetic it doesn't quack like a Kinetic, so it's not a Kinetic"
[21:49] <tsimonq2> s/Kinetic/Lunar/, s/Kinetic/Lunar/, s/Kinetic/Lunar/
 "It's been two and a half years..." <- Exactly the best time :)
[21:50] <arraybolt3[m]> Nice. OK, looks like we're all set then.
[21:50] <arraybolt3[m]> (We're still on Debian Policy Manual version 4.1.5...)
 "(We're still on Debian Policy..." <- Best practice: read all the changelogs from Debian Policy and check all of them
[22:21] <arraybolt3[m]> Simon Quigley: I just used this extremely handy tool: https://www.debian.org/doc/debian-policy/upgrading-checklist.html#version-4-1-5
[22:22] <tsimonq2> Precisely, nice ;)
[22:22] <arraybolt3[m]> Didn't end up needing a single change, miraculously.
[22:22] <arraybolt3[m]> (And I even dug deeper into a couple of spots where I wasn't quite sure.)
[22:24] <arraybolt3[m]> Whew! I think I'm done.
[22:25] <arraybolt3[m]> Just rebuilding to make sure everything worked.
[22:29] <arraybolt3[m]> Simon Quigley: One small problem, lubuntu-desktop depends on an X fonts package, which Debian's manual says must not happen. It will let me put it as a Recommends, though. Trouble is it must be sneaking in through ${misc:Depends}. Is there some way for me to specifically exclude a Depends, or is this an indication of something broken elsewhere?
[22:30] <arraybolt3[m]> (The particular package is `xfonts-efont-unicode`)
[23:03] <tsimonq2> Can I please get a link to the policy stanza you're referring to so I can figure out intent?
[23:04] <arraybolt3[m]> Simon Quigley: https://www.debian.org/doc/debian-policy/ch-customized-programs.html, section 11.8.5.
[23:04] <arraybolt3[m]> Point 1.
[23:04] <arraybolt3[m]> The link to Footnote 8 contains the reasoning.
[23:06] <tsimonq2> Yeah... I think you're right on this one
[23:07] <tsimonq2> They are very intentional with must/should wording, I Shall Not Doubt Debian Policy
[23:07] <tsimonq2> Please create an MP on Launchpad for the seed/throw me a Git patch and I'll be happy to get it in... all you have to do is surround that font package in parentheses
[23:08] <tsimonq2> VERY NICE catch
[23:08] <arraybolt3[m]> I don't know what an MP means but sure.
[23:08] <tsimonq2> Merge Proposal :)
[23:08] <tsimonq2> (Same as a PR)
[23:08] <tsimonq2> Also, changes here would be done in the seed, not the control file itself :)
[23:08] <arraybolt3[m]> You read my mind, that's what I was just about to ask.
[23:08] <tsimonq2> Sweet :)
[23:09] <tsimonq2> I need to get going here, but I'll check in later
 "Please create an MP on Launchpad..." <- ``... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/5fd2d20cfbfa756cfaea4458a4d71fed323ec380>)
[23:16] <arraybolt3[m]> > <@tsimonq2:linuxdelta.com> Please create an MP on Launchpad for the seed/throw me a Git patch and I'll be happy to get it in... all you have to do is surround that font package in parentheses... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/df8aa974dee338d8578aeb4e3dcecfdb0892283a>)
[23:17] <arraybolt3[m]>  * ```... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/ef55c9d566b5860756a3f97cf1f362ec65071c40>)
[23:17] <arraybolt3[m]>  * ```... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/b3c530f2d15cff55f64eef3b8922de8b2899ad35>)
[23:32] <tsimonq2> That's not verbose :/ I'll look in a bit heh
[23:32] <arraybolt3[m]> OK. I'll send you what I have so far shortly.
[23:33]  * arraybolt3[m] posted a file: (9KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/fOwfmUkUQYaxYDZQGFlQXvro/diff.txt >
[23:34] <arraybolt3[m]> Simon Quigley: ^ diff containing all my changes to lubuntu-meta, THIS DOES NOT BUILD


  I really wish I could go to sleep, but I leave for the airport in 3 hours.
[08:18] <hrw> GrueMaster: trip to Prague?
[08:31] <lool> Prague is the hot place to be!
[08:35] <hrw> 33°C there today
[08:52] <Taalas> I have a iMX25 with Ubuntu installed. How can I get the touchscreen working? ts_calibrate throws following message: "ts_open: No such file or directory"
[09:01] <ukleinek> Taalas: which file does ts_open try to open?
[09:05] <hrw> Taalas: and /proc/bus/input/devices lists ts device at all?
[09:08] <lag> sebjan: Sorry if I've asked this before (if I did, I've forgotten the answer)
[09:08] <lag> sebjan: Do _any_ of the OMAP chips have Parallel Ports?
[09:08] <lag> Either ISA or PCI?
[09:10] <sebjan> lag: hi! I would not speak about all omap chips, as there are many variants. I am not aware of such ports.
[09:11] <sebjan> lag: you could maybe ask this question on #linux-omap?
[09:11] <lag> I can :)
[09:12] <lag> And have
[09:22] <cooloney_> #linux-omap
[09:29] <Taalas> ukleinek: I don't know. Where can I see it?
[09:30] <ukleinek> Taalas: ask strace
[09:30] <Taalas> hrw: /proc/bus/input/devices lists 2 devices. One is named N: Name="mxckpd" the other N: Name="imx_adc_ts"
[09:30] <hrw> Taalas: did you ever used tslib tools before?
[09:30] <GrueMaster> hrw: yea, Prague.
[09:31] <hrw> so imx_adc_ts is your touchscreen. check which /dev/input/event it got
[09:31] <cooloney> ogra: i tried to turn off swap in the kernel. then one of the oops is gone
[09:31] <hrw> tslib is easy
[09:31] <ogra> cooloney, so it apparently cant handle swapfiles properly
[09:31] <Taalas> hrw: I never used tslib before. The Handler is event1
[09:31] <cooloney> ogra: i think swap is required for you Ubuntu system, right?
[09:32] <hrw> Taalas: TSDEVICE=/dev/input/event1 ts_calibrate
[09:32] <ogra> cooloney, well, at least with so low memory
[09:32] <cooloney> ogra: https://bugs.edge.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/605739
[09:32] <ubot2> Launchpad bug 605739 in linux-ti-omap4 (Ubuntu Maverick) (and 1 other project) "BUG: Bad page state in process swapper pfn:94d23 (affects: 1) (heat: 6)" [High,In progress]
[09:33] <cooloney> ogra: so currently, we are using a swapfile in SD card, how about a swap partition?
[09:34] <ogra> cooloney, tricky but doable
[09:34] <Taalas> ukleinek: strace tells /dev/touchscreen/ucb1x00 is not found
[09:34] <ogra> cooloney, though its still a bug
[09:34] <Taalas> hrw: same error
[09:34] <ogra> cooloney, swapfiles work fine on other ubuntu arches
[09:35] <cooloney> ogra: but without swap, i saw several memory allocation fails when i was trying apt-get dist-upgrade on the board
[09:35] <ogra> sounds more like a general memory prob with the kernel
[09:35] <Taalas> The folder /dev/touchscreen is not existing
[09:36] <cooloney> ogra: maybe, i need more investigation.
[09:36] <cooloney> but i think 512M memory is OK for Ubuntu on omap4,
[09:37] <cooloney> although i found the system sometime is quite slow
[09:37] <ogra> cooloney, yes, something is wrong, it got a lot slower between two image tests i did
[09:37] <ogra> cooloney, but that also happened on omap3 so i suspect thats rather userapce
[09:38] <ogra> i'll resarch and fix that at the sprint
[09:38] <cooloney> ogra: got it. i assume is my SD card's problem.
[09:38] <ogra> no, we all see it on different SD cards
[09:38] <cooloney> sometimes my SD card cannot be recognized by my PC
[09:39] <ogra> there is definately something not acting as it should
[09:39] <hrw> Taalas: /dev/touchscreen never existed - maybe ltib (or whatever you used before) created it
[09:39] <cooloney> ogra: ok, cool.
[09:39] <ogra> the MMC driver on the panda *has* some speed issues though
[09:39] <ogra> but thats not alone the reason for the slowness
[09:40] <Taalas> I created my rootfs with rootstock
[09:47] <hrw> Taalas: so use strace to check why it does not work
[09:47] <hrw> Taalas: check permissions etc
[10:45] <lag> amitk: Hi
[11:30] <amitk> lag: hola!
[11:31] <lag> Hey amitk
[11:31] <lag> Do you have the ability to search though the kernel mailing list?
[11:32] <amitk> lag: LKML?
[11:32] <lag><EMAIL_ADDRESS>[11:33] <amitk> yes, why?
[11:33] <amitk> Did Google go bankrupt? ;)
[11:33] <cooloney> lol
[11:33] <amitk> http://lkml.indiana.edu/hypermail/linux/kernel/
[11:34] <amitk> http://marc.info/?l=linux-kernel
[11:34]  * amitk subscribes to lkml through gmail to use search
[11:35] <hrw> lag: gmane ;)
[11:35] <lag> amitk: Search for - Stop ARM boards crashing when CUPS is loaded
[11:37] <amitk> http://marc.info/?l=linux-kernel&w=2&r=1&s=Stop+ARM+boards+crashing+when+CUPS+is+lo&q=b
[11:37] <amitk> lag: ^^ I see your comment there
[11:40] <lag> apw: Mentioned that Lenaro may have the funding to make the LK better in this way
[11:40] <amitk> lag, are you pitching a project for Linaro? :)
[11:40]  * apw referred to the 'platformisation' of things like the paralellel port driver ...
[11:42] <lag> Maybe :)
[11:43] <lag> apw: Yep
[11:44] <lag> Similar to the work that was undertaken on the serial driver a little while ago
[11:44] <lag> Mentioned by Russle
[11:44] <lag> Mentioned by Russell
[11:44] <lag> :)
[11:45] <amitk> lag: This is unlikely to be a priority for Linaro (parallel port is not an interface that many people care about anymore). You might try pitching it to to GregKH for his Linux drivers project.
[11:45] <amitk> some student wanting to get their feet wet might want to dive into it
[11:47] <lag> Okay, I'll ping him an email explaining
[11:47] <amitk> lag: I'll ask around in Linaro, but don't expect too much.
[11:47] <lag> No problem, thanks
[11:48] <lag> Can I mention Linaro in an email to Greg and Russell?
[11:48] <lag> I'm assuming I can if I can mention them here
[11:49] <amitk> lag: mention Linaro in what context?
[11:50] <lag> "I've put in a pitch for Linaro to complete the work, however, this is unlikely .... <blar>
[11:51] <lag> "I was wondering if you'd be interested ... <blar>
[11:53] <lag> amitk: --^
[11:53] <lag> Hi mythripk
[11:55] <amitk> lag: sure, but TBH this isn't the kind of work Linaro is geared for. I can almost certainly say that no machine ships with parallel ports anymore (on any platform). So just ask Greg if he knows anybody who might be interested in taking on this challenge
[11:55] <lag> amitk: np
[11:57] <hrw> amitk: parport_pc is not only LPT1:
[11:57] <hrw> parport_serial which handles multi port PCI serial cards depends on parport_pc
[11:57] <hrw> there are ARM boards with PCI slots...
[12:00] <amitk> hrw: interesting. But are these modern boards?
[12:01] <hrw> I know that pcie multi i/o cards also exists. and pcie is present in modern arms too
[12:01] <hrw> amitk: intel ixp4xx had pci but it is xscale
[12:03] <amitk> hrw: that is not really an architecture linaro cares about, is it? The discussion here is whether this is something that is a blocker for Linaro. There are ARM boards doing all sorts of things, but Linaro only cares about a small percentage of those
[12:03] <lag> amitk: Is it worth mentioning that you suggested to email Greg? I.e. does he know who you are by name?
[12:04] <hrw> I would just disable parport_pc from default configs
[12:04] <lag> hrw: Check the kernel-team mailing list
[12:05] <amitk> lag: you're being too formal about this (intros and references) :) And no, I'm not that famous ;)
[12:05] <lag> One must be professional :)
[12:08] <ogra> which one ?
[12:08] <hrw> lag: did not found 'parport' in last 3 months
[12:12] <lag> hrw: Are you searching in subject lines or main body?
[12:13] <lag> hrw: Search for "Stop ARM boards crashing when CUPS is loaded"
[12:15] <hrw> found
[12:15] <lag> :)
[12:15] <hrw> !ARCH_OMAP one
[12:15] <ubot2> Factoid 'ARCH_OMAP one' not found
[12:15] <lag> Yup
[12:15] <ogra> lag, cooloney-afk, "omap_device: mmci-omap-hs0: new worst case deactivate latency 0: 30517" any idea what that cound mean ?
[12:15] <ogra> i wonder if thats the reason for the SD slowness
[12:15] <lag> Slow read?
[12:16] <ogra> i get that on the console if fsck runs before resizing the filesystem
[12:16] <ogra> (on panda)
[12:16] <lag> It's not a kernel message
[12:17] <lag> Wait
[12:17] <lag> Sorry
[12:17] <lag> 1 min
[12:18] <ogra> it must be kernel or a driver
[12:22] <lag> ogra: That's just wake-up latency
[12:22] <lag> ogra: It's putting the card to sleep - saving power
[12:23] <ogra> while writing to it ?
[12:23] <ogra> wow
[12:23] <lag> Yeah, that doesn't sound good
[12:23] <ogra> it appears immediately after fsck starts
[12:23] <lag> Are you sure it't not _after_ it finishes?
[12:23] <ogra> yes
[12:24] <ogra> printf "Checking filesystem before resizing..."
[12:24] <ogra> /sbin/e2fsck -fy /dev/${DISK}${SEP}2 >>${LOG} 2>&1
[12:24] <ogra> echo "[done]"
[12:24] <ogra> thats the code
[12:24] <ogra> it appears between the ... and done
[12:25] <ogra> immediately after the printf was run
[12:26] <lag> And in the ${LOG}?
[12:26] <ogra> so either while e2fsck runs or right before it starts
[12:26] <ogra> still waiting for the resizing to finish
[12:26] <ogra> i'll grab the log but usually there is just plain e2fsck babbling
[12:30] <ogra> lag, http://paste.ubuntu.com/464486/ nothing special from e2fsck
[12:30] <lag> do cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
[12:31] <ogra> hrm
[12:31] <ogra> i have no user on that system yet
[12:31] <ogra> that will take a while
[12:33] <lag> I don't think that messages is an issue
[12:33] <lag> It's just showing you the worst case latency of the MMC card
[12:33] <lag> Once it's awake, it's awake
[12:33] <lag> How slow is e2fsck?
[12:35] <ogra> takes around a minute
[12:35] <ogra> probably two
[12:36] <ogra> (1.5G filesystem)
[12:36] <ogra> overall the SD I/O seems to be way to slow though
[12:40] <ogra> lag, no cpufreq at all
[12:41] <lag> Hold on
[12:42] <ogra> (in another note i tried to run iotop yesterday and it seems we're missing config options for it to work)
[12:43] <lag> Which board is this?
[12:43] <ogra> panda
[12:46] <lag> From initramfs?
[12:47] <ogra> yep
[12:47] <lag> How can I replicate?
[12:48] <lag> mythripk: ping
[12:48] <ogra> grab a recent preinstalled image
[12:48] <ogra> and i can give you a uInitrd to replace on the SD card with the jasper changes
[12:49] <lag> I'm still having monitor issues
[12:50] <ogra> just change the shipped boot.scr and use a serial console for that
[12:52] <mythripk> lag: That is in the PSM mode and when it is on ,it is working fine with the patch right ?
[12:54] <lag> Mythripk: Yes
[12:54] <lag> Is the delay in the correct place?
[12:54] <lag> Is it long enough?
[12:55] <lag> ogra: Okay
[12:55] <mythripk> i have sent a single clean patch with this i was not able to reproduce the on/off issue
[12:59] <ogra> lag, http://people.canonical.com/~ogra/uInitrd
[13:30] <lag> ogra: debconf: DbDriver "config": could not write /var/cache/debconf/config.dat-new: No space left on device
[13:30] <lag> On a 16GB SD - WTF?
[13:30] <ogra> that was with a fresh image and you only added the console entry to the existing boot.scr ?
[13:31] <ogra> (it didnt resize, thus the no space message)
[13:31] <lag> I had to mkimage it again
[13:31] <lag> But yes
[13:31] <lag> Fresh image, only the boot.scr changed to add console
[13:31] <ogra> looks to me like the image is already configured
[13:31] <lag> It was brand-spanking
[13:31] <ogra> hmm
[13:31] <lag> I dd'ed myself
[13:32] <ogra> can you check if 7var/loga7jasper.log exsists in the foorfs ?
[13:32] <ogra> *rootfs
[13:32] <ogra> gah
[13:32] <ogra>  /var/log/jasper.log
[13:32] <lag> Nope
[13:32] <lag> No consle
[13:32] <lag> console*
[13:32] <ogra> on your PC
[13:32] <ogra> just mount the Sd
[13:33] <ogra> the resizer only doesnt run if root=UUID= is set on the cmdline
[13:33] <mythripk> lag: can you try and let me know
[13:33] <ogra> and thats set by the second part of jasper
[13:33] <lag> mythripk: Doing it right now
[13:35] <lag> mythripk: Monitor entered PSM/on/PSM/on ...
[13:35] <lag> mythripk: You want the log?
[13:36] <lag> mythripk: http://paste.ubuntu.com/464515/
[13:41] <mythripk> lag:looking at the log give me a min
[13:43] <lag> ogra: /var/log/jasper.log is missing
[13:43] <ogra> lag, very weird
[13:43] <lag> ogra: I haven't used your initrd yet
[13:43] <lag> The only thing I changed was the boot.scr
[13:43] <ogra> my initrd just adds more output to jasper
[13:44] <ogra> apart from that it shoudl be identical to whats on the image
[13:44] <lag> So why isn't it resizing then?
[13:44] <ogra> no idea
[13:44] <ogra> and hard to say without log
[13:44] <lag> Are there any other logs which may help?
[13:44] <ogra> nope, its all in initramfs, nothing logs there by default
[13:45] <ogra> it works fine here with the latest image and my hacked initramfs
[13:45] <ogra> as well as with the shipped one
[13:45] <mythripk> lag: did you try with debug today and with debug prints it works is it
[13:46] <lag> Not yet
[13:46] <lag> Wait one
[13:47] <lag> Yes, it works fine with debug on
[13:47] <lag> ogra: http://paste.ubuntu.com/464520/
[13:49] <ogra> lag, how long did it sit between line 243 and 244 ?
[13:49] <ogra> should be like 30min for a 16G card
[13:50] <lag> Nowhere near that
[13:50] <ogra> so resizing failed for an unknown reason
[13:52] <lag> How do I debug?
[13:53] <ogra> you cant
[13:54] <ogra> well, you could use break=premount and try to run jasper_growroot manually
[13:55] <ogra> or use break=bottom and inspect /dev/.initramfs/jasper.log
[13:55] <ogra> but i doubt you will get much info from that
[13:56] <lag> Well I need to fix it
[13:56] <lag> So I need somewhere to start
[13:57] <ogra> right, on a fresh image break=bottom and checking /dev/.initramfs/jasper.log is probably the best
[13:57] <lag> Does growroot have a -vvv setting?
[13:57] <ogra> heh, its a script
[13:57] <lag> Okay
[13:57] <lag> I'll hack the script
[13:57] <ogra> depends how good you are with ed :)
[13:57] <ogra> there is no editor in the initramfs
[13:58] <lag> I'll mount it on my PC
[13:58] <ogra> you mount the initramfs ?
[13:58] <ogra> :)
[14:02] <lag> Is that where the script is/
[14:02] <lag> ?
[14:02] <ogra> yes
[14:03] <ogra> thats why making or testing changes is so hard
[14:03] <ogra> or debugging
[14:04] <ogra> all commands called by jasper redirect their output to jasper.log though, if you boot with a break= statement you can at least cat that file from the busybox prompt
[14:08] <lool> Folks, do you know why we don't have ddebs for armel ATM?
[14:08] <hrw> what are ddebs?
[14:09] <ogra> lool, no idea
[14:09] <ogra> lool, ask pitti ?
[14:10] <ogra> i think he fiddled with pkgbinarymangler
[14:10] <lag> ogra:
[14:10] <lag> (initramfs) ls /dev/.initramfs
[14:10] <lag> bootchart.pid
[14:10] <lag> ..
[14:10] <ogra> where did you break ?
[14:10] <lag> break=bottom
[14:10] <ogra> try premount
[14:11] <lag> Do I have to reflash?
[14:11] <ogra> bottom might be to late ... the script in local-bottom has a mv command for the log
[14:11] <ogra> yes
[14:11] <lag> Oh no, I tried premount
[14:11] <lag> Should I try bottom?
[14:11] <ogra> whats the last you see on the screen ?
[14:12] <ogra> did it run local-premount already ?
[14:12] <lag> device-mapper: ioctl: 4.17.0-ioctl (2010-03-05) initialised<EMAIL_ADDRESS>[14:12] <ogra> or only init-premount
[14:12] <lag> udev: starting version 151
[14:12] <lag> omap_device: mmci-omap-hs.0: new worst case deactivate latency 0: 30517
[14:12] <lag> Begin: Loading essential drivers ... Btrfs loaded
[14:12] <lag> device-mapper: uevent: version 1.0.3
[14:12] <lag> device-mapper: ioctl: 4.17.0-ioctl (2010-03-05) initialised<EMAIL_ADDRESS>[14:12] <lag> done.
[14:12] <lag> Spawning shell within the initramfs
[14:12] <ogra> k
[14:12] <lag> So?
[14:12] <lag> Now what?
[14:13] <ogra> sh /scripts/local-premount/jasper_growroot
[14:13] <ogra> sh shouldnt be necessary though
[14:13] <ogra> then check for the log again
[14:14] <lag> (initramfs) sh /scripts/local-premount/jasper_growroot
[14:14] <lag> scripts/local-premount/jasper_growroot: line 104: syntax error: /255/63/512
[14:14] <lag> Oooooooooooooooooooooooo
[14:14] <ogra> hmm, seems the mmc isnt there
[14:14] <ogra> check /dev if mmcblk0 exists
[14:14] <ogra> you probably need to break later
[14:14] <lag> Doh!
[14:15] <lag> My bad
[14:15] <lag> Wait one
[14:18] <lag> Resizing root fiomap_device: mmci-omap-hs.0: new worst case deactivate latency 0: 30517
[14:18] <lag> lesystem please wait, this will take about ten minutes ...
[14:18] <lag> (initramfs)
[14:19] <ogra> heh, thats it ?
[14:19] <ogra> it should have taken 10mins :)
[14:20] <ogra> well, check for jasper.log
[14:21] <lag> http://paste.ubuntu.com/464529/
[14:23] <ogra> weird
[14:23] <ogra> given that e2fsck just ran before
[14:24]  * ogra has no idea how that could happen
[14:25] <lag> Well learn ;)
[14:25] <lag> This is userspace :)
[14:25] <ogra> well, that would mean that something in your FS is dirty
[14:25] <ogra> which cant be
[14:26] <lag> It's a new dd
[14:26] <ogra> resize2fs is the next line after e2fsck ... the disk isnt mounted so there is no way it could get dirty again after it was just checked
[14:28] <lag> Anything else I can try?
[14:28] <ogra> not really
[14:29] <ogra> i have no clue why your SD appears dirty right after e2fsck -fy
[14:29] <ogra> thats technically impossible
[14:30] <ogra> you could try the same with the other uInitrd
[14:30] <lag> With your one?
[14:30] <ogra> but i doubt it will change much about the fact that either e2fsck or resize2fs cant handle your Sd properly
[14:30] <ogra> yes, with mine
[14:39] <ogra> you dont happen to have it mounted manually or some such ?
[14:52] <lag> ogra: I flash the card and put it in the Panda
[14:52] <lag> ogra: I do nothing else
[14:53] <ogra> right, but there is no technical explanation for that error
[14:53] <lag> ogra: It must do something, cause it trashes the boot partition
[14:53] <ogra> trashes in what way ?
[14:55] <lag> Won't mount on my PC any more
[14:57] <ogra> like you issue mount /dev/mmcblk0p1 /mnt and get an error ?
[14:57] <ogra> or how does that manifest ?
[14:58]  * ogra quickly makes some coffee before the call
[14:58] <lag> It does mount
[14:59] <lag> It just doesn't auto mount
[15:01] <ogra> thats how its supposed to be :)
[15:01] <ogra> it shouldnt show on your desktop or in places or automount
[15:02] <ogra> mount it manually if you need to manipulate it
[15:18] <ogra> lag, when the repartitioning happens the vfat partition gets recreated and gets a label added that udev explicitly ignores
[15:18] <lag> k
[15:18] <lag> So it gets that far
[15:18] <ogra> it runs the whole stuff apart from resizing
[15:19] <lag> Seemingly so
[15:19] <ogra> i'm pretty sure even the jasper_setup script from local-bottom runs fine
[15:19] <ogra> i could add a force to resize2fs but that scares me a bit
[15:20] <ogra> it might ignore if the FS is dirty
[15:20] <ogra> not sure what checks -f disables i know it doesnt drop all of them
[15:20] <lag> Well it can't be any worse than it already is
[15:20] <ogra> indeed
[15:22] <ogra> let me roll you another uInitrd with -f
[15:22] <lag> k
[15:24] <ogra> http://people.canonical.com/~ogra/uInitrd
[15:24] <ogra> try that one on a fresh dd'ed card
[15:25]  * ogra takes a break
[15:51] <ogra> lag, any change ?
[16:24] <ogra> lag, did you have any luck with the other uInitrd ?
[16:28] <XorA|gone> hmm, is there any 4430 SDP compatible images?
[16:28] <XorA|gone> maverick ones
[16:29] <ogra> only for panda
[16:30]  * XorA|gone suspects has destroyed image trying to upgrade :-)
[16:31] <ogra> http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/current/
[16:31] <XorA|gone> oh no, just too a long time for ext3 recovery
[16:50] <lag> ogra: How do I know if the resize has completed correctly?
[16:50] <lag> (initramfs) sh /scripts/local-premount/jasper_growroot
[16:50] <lag>  mmcblk0: p1 p2
[16:50] <lag> Resizing root filesystem please wait, this will take about ten minutes ...
[16:50] <lag> (initramfs)
[16:51] <ogra> check jasper.log
[16:51] <ogra> but for my hand rolled initramfs thats not enough output
[16:51] <ogra> so i guess it died again
[16:54] <lag> http://paste.ubuntu.com/464598/
[16:54] <ogra> sigh
[16:56] <lag> Fix it
[16:56] <ogra> buy a better SD :P
[16:57] <lag> bug 373409
[16:57] <ubot2> Launchpad bug 373409 in gparted (Ubuntu) (and 1 other project) "resize2fs doesn't notice the partition was fsck'ed (affects: 1) (heat: 13)" [Undecided,Confirmed] https://launchpad.net/bugs/373409
[16:57] <lag> It's a Kingston
[16:57] <ogra> gparted ?
[16:57] <ogra> lol
[16:58]  * lag shrugs
[17:03] <ogra> lag, hmm
[17:04] <ogra> we actually set the clock to last mount time in omap
[17:04] <ogra> so that such a broken clock setting cant interfere with mounting
[17:07] <ogra> hmm
[17:07]  * ogra has an ugly idea but one that will surely fix it
[17:09]  * ogra rolls a new test initrd
[17:13] <lag> (initramfs) /sbin/resize2fs /dev/mmcblk0p2
[17:13] <lag> resize2fs 1.41.12 (17-May-2010)
[17:13] <lag> ext2fs_check_mount_point: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/mmcblk0p2 is mounted.
[17:13] <ogra> lag, http://people.canonical.com/~ogra/uInitrd updated, i bet it works now
[17:13] <lag> What did you do?
[17:14] <ogra> i mount/unmount it once before e2fsck runs :)
[17:14] <lag> Okay
[17:14] <ogra> just to confirm its the same
[17:14] <ogra> if its the same bug it should have a new last mounted timestamp and stop complaining
[17:15] <lag> k
[17:15] <ogra> indeed thats not the right solution
[17:15] <lag> Did you see the output of my /sbin/resize2fs /dev/mmcblk0p2
[17:16] <ogra> your jasper.log you mean ?
[17:16] <ogra> oh, i missed the lines above
[17:17] <ogra> dont worry, the script creates an mtab
[17:17] <ogra> and removes it at the end again
[17:17] <ogra> you would have to do the same if you want to run it manually ... just link /proc/mounts to it
[17:23] <lag> k


[11:10] <ochosi> micahg: quick firefox-question: the green arrow in the locationbar (i.e. the "go"-icon), is that themeable? the refresh-icons seems to be taken from the icon-theme but this icon seems to come from firefox directly
[13:36] <micahg> ochosi: offhand, idk, I would think so, but I'd have to look
[14:30] <ochosi> micahg: ok, well if you can or if you know someone who might know, that'd be nice. if not, no worries, it's just one tiny icon


[19:17] <leftyfb> krytarik: their very first post for instance
[19:17] <leftyfb> 2022 Feb 08 19:57:11 <adderall>	I think I'm afraid of the Penguin. I installed the socialist wallpaper that I'v been using for years and Tux is VERY scary
[19:18] <krytarik> I'm very well aware that adderall is a regular issue there, just felt you were a bit quick to react on that particular message.
[19:19] <Maik> they continue to troll in #ubuntu-discuss now
[19:19] <leftyfb> oh, that I can deal with
[19:23] <leftyfb> now they're nick spamming both #u-d and offtopic. Good thing we went easy on them
[19:26] <Maik> oh well, at least there is a op who deals with this kind of things fast. Ban kick done and move on.
[19:26] <Maik> easy as that
[20:06] <leftyfb> krytarik: seriously? encouraging the trolls now?
[20:07] <krytarik> Yes!
[20:11] <leftyfb> krytarik: go ahead, help the fine lad with his completely valid issue
[21:05] <JackFrost> Maik: Yes, that's the easy path (then they maybe ban evade a little), or we can *nudge* them into the right direction and perhaps end up helping others too, it's happened *many* *many* times, but just banning people doesn't ever end up with that outcome.  When people are frustrated and upset, it's better to try and calm them rather than...riling them up more.  This benefits everyone, while poking
[21:05] <JackFrost> them with a stick repeatedly just helps..uh.. well.. I can't think of anyone!
[21:06] <JackFrost> I guess if we're just going to ban everyone, might as well start out with *!*@*, that seems to cover quite a few! :>
[21:07] <Eickmeyer> JackFrost: Heh, that would definitely shut them down. XD
[21:09] <JackFrost> Sometimes ops calls on spammers (dropping webcam links, etc) doesn't get op action because it's seen by network staff and removed from the network instead (or, seen by an op/staffer, at that.  Better to remove from the network than just the channel.)
[21:13] <sarnold> oh I *like* those
[21:14] <sarnold> nothing quite like seeing a kline a moment later in lastlog :)


[02:10] <adamkex> I installed fluxbox and then firefox but there is no autogenerated menu entry for firefox. A menu entry is created if I install other applications. Is this a bug or am I doing something wrong?
[02:19] <tsimpson> adamkex: see if logging out and back in solves it, if not then it's likely a bug (somewhere in fluxbox)
[02:26] <adamkex> tsimpson: I've had this problem since yesterday. I also noticed that firefox is missing from /usr/share/menu/ while it is present in /usr/share/applications/
[02:29] <tsimpson> it shouldn't be required to have an entry in /usr/share/menu/, though it could be the cause
[02:29] <micahg> that's an archive wide issue which will probably be dealt with in future releases
[02:32] <adamkex> tsimpson: May I ask you why it shouldn't? All other programs in /usr/share/menu/ are in my fluxbox menu. I can install openbox and so we can see if it is a fluxbox bug or that firefox package is missing a file
[02:32] <adamkex> micahg: Archive wide?
[02:46] <adamkex> tsimpson: In openbox one can only start the default web browser, which in this case is firefox. Firefox has no entry.
[02:46] <tsimpson> I'm in lxde atm, I see firefox in my launcher
[02:48] <adamkex> tsimpson: Does LXDE use the menu or the .desktop system to generate it's menus?
[02:52] <tsimpson> not sure, I'll have a look
[02:53] <tsimpson> adamkex: seems like it ignores /usr/share/menu/ completely actually
[02:57] <adamkex> tsimpson: I see. Then it seems that LXDE uses the .desktop system instead of pulling menu entrys from /usr/share/menu/. I guess this is a bug since firefox properly support some window managers. Should I file this as a bug?
[02:57] <adamkex> does not properly support*
[02:57] <tsimpson> I'd agree and say it should probably include the menu entry, yes
[02:58] <adamkex> tsimpson: Ok, I will file this as a bug
[03:41] <adamkex> tsimpson: I've reported the bug now, if you're interested this is the URL: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1057882 Thank you for helping me.
[03:41] <ubot2> Launchpad bug 1057882 in firefox "No menu entry for firefox in /usr/share/menu/" [Undecided,New]
[03:52] <adamkex> tsimpson: I am leaving now, good bye
[04:26] <em> ouch -- what a devastating and effective lampoon -- https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1055766
[04:26] <ubot2> Launchpad bug 1055766 in gnome-terminal "grep -R doesn't automatically search amazon" [Undecided,Invalid]
[05:10] <dglass> jtaylor:  I uploaded  a few days ago a new debdiff for wakeup on https://bugs.launchpad.net/ubuntu/+source/wakeup/+bug/1040213
[05:10] <ubot2> Launchpad bug 1040213 in wakeup "Request for new upstream version 1.3 upgrade" [Undecided,New]
[05:10] <dglass> if you have the time to look at it that would be great
[18:06] <mitya57> hey, can anybody look at bug 1055710 and check if it really needs to be private?
[18:07] <mitya57> (and probably other private bugs in unity-mail package, if there are any).
[18:09] <jtaylor> looking
[18:10] <jtaylor> swapping bugs is simpler :)
[18:16] <mitya57> jtaylor: I need the stacktrace, and the retracer removes it...
[18:17] <jtaylor> ._.
[18:17] <jtaylor> its a python stacktrace
[18:18] <jtaylor> in C those are seldom useful
[18:18] <jtaylor> k public too, nothing in there
[18:19] <mitya57> without the stacktrace I can't even understand what happened...
[18:20] <jtaylor> I doubt the stacktrce will help
[18:20] <jtaylor> but its visible now
[18:22] <mitya57> jtaylor: thanks
[18:22] <mitya57> in bug 1023158 the stacktrace *is* meaningful :)
[18:22] <ubot2> Launchpad bug 1023158 in unity-mail "Unity-mail crashed with signal 5 in g_object_newv()" [Medium,New] https://launchpad.net/bugs/1023158
[18:23] <jtaylor> yes its hasn't crashed in python
[18:24] <mitya57> by "crashed in python" I mean it's C stacktrace, not python traceback :)
[18:33] <mitya57> jtaylor: thanks a lot, maybe you can look at retext bugs as well?
[18:34] <mitya57> jtaylor: I've got one of them made public today, so I guess there may be other private there
[18:46] <jtaylor> mitya57: done
[18:48] <mitya57> jtaylor: thank you
[18:49]  * mitya57 hates appmenu-qt as it is the cause of both retext bugs...