[03:30] <qwebirc48096> `
[03:31] <qwebirc48096> `i just did a fresh install of mythbuntu 14.x - i ca not get network to work any ideas


[09:51] <knome> flocculant, yes, you can't forward links with the bot...
[10:04] <bluesabre> flocculant: have you seen the issues described here https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1762569 ?
[10:06] <bluesabre> https://imgur.com/a/OoeiP visual differences between the 2
[10:38] <bluesabre> there's also https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1689008
[16:43] <ali1234> https://bugs.launchpad.net/ubuntu/+source/xfpanel-switch/+bug/1762779
[16:55] <flocculant> bluesabre: re 'have you seen issues described' not seen anything like that no - but only use calc and writer, as far as the smb one - as long as that's not going to lead to us having things we don't want then I've no gripe against it
[16:57] <flocculant> ali1234: confirmed that - I thought bluesabre had dealt with that though
[16:57] <ali1234> i zsynced the daily and installed about an hour ago
[16:58] <ali1234> at least i think i did...
[16:58] <flocculant> ali1234: and did you see the timeout issue?
[16:59] <ali1234> no, but this is on a laptop with bluetooth
[17:00] <flocculant> oh right - good job you didn't then :)
[17:23] <vabi> Anyone knows how fstrim is enabled in 18.04? No fstrim flie in cron.weekly
[17:30] <flocculant> vabi: systemd it looks like - locate fstrim
[17:33] <vabi> flocculant: thank You, despite that svideo GM965 issue 18.04 works fine for me.
[17:34] <vabi> ...so far
[17:34] <flocculant> nice :)
[17:51] <flocculant> bluesabre: just updating here - ahaving gnome-session-common and gnome-startup-applications being installed
[21:58] <bluesabre> flocculant: doesn't seem like something new since the 4th https://wiki.bluesabre.org/bionic_changes?do=diff&rev2%5B0%5D=1522889195&rev2%5B1%5D=1523397435&difftype=sidebyside
[21:59] <ali1234> ochosi: i cane up with a gtkrc hack to fix adwaita gtk2 and xfce-panel
[21:59] <ali1234> http://paste.ubuntu.com/p/mcg5xXg3yY/ this makes it look like it did in 16.04
[21:59] <ali1234> i have not checked if it is identical. but this fixes the cut off icons
[22:00] <bluesabre> knome, ochosi: UIFe approved, https://bugs.launchpad.net/ubuntu/+source/xubuntu-artwork/+bug/1761623


[11:31] <echo-area> Is there a bzr-svn version that supports bzr-2.3.0?
[11:33] <maxb> yes, but not a release
[12:58] <echo-area> maxb: Okay thanks
[19:39] <Zblakany> i have a simple question
[19:40] <Zblakany> along time ago i set bunch o bzr repos as bzr user in /home/bzr
[19:40] <Zblakany> then i moved them to new server as bazaar user in /home/bazaar
[19:41] <Zblakany> after that i must add symlink /home/bzr which points /home/bazaar
[19:41] <Zblakany> that solution is not my idea, but person who uses this bzr repos
[19:42] <Zblakany> and my question is: why this symlink is needed?
[19:49] <maxb> Zblakany: You have not provided enough information about your environment for anyone to help you.
[19:50] <maxb> < Zblakany> that solution is not my idea, but person who uses this bzr repos
[19:50] <maxb> You mean your users told you to create it?
[19:50] <Zblakany> maxb: yes, exactly
[19:50] <Zblakany> he wrote: create symlink and this fix problem
[19:50] <maxb> Why don't you ask the users what problem they were having then?
[19:51] <maxb> I imagine the users just didn't want to have to update existing references to the branches
[19:51] <Zblakany> how can I fix all bazaar repositories, because I want to remove that ugly symlink
[19:52] <maxb> You haven't said anything that leads me to believe they are broken
[19:52] <maxb> Merely that your users don't want to have to deal with them moving
[19:52] <Zblakany> maxb: if I remove this stupid symlink, then part of theese repositories can't work
[19:53] <Zblakany> so probably in this repositories is static path in form /home/bzr/ not /home/bazaar
[19:53] <Zblakany> so I should fix this path
[19:53] <Zblakany> how can I find them?
[19:54] <Zblakany> maybe it's in .bzr/branch/branch.conf?
[19:56] <Zblakany> or .bzr/branch/location?
[19:56] <Zblakany> in some files with /home/bazaar in this files are proper path with /home/bzr
[19:57] <Zblakany> can I safely change them?
[20:00] <Zblakany> maxb: part of them has moved location to /home/bazaar, because in his bzr serve command i see different paths
[20:35] <maxb> Zblakany: Just saying that something doesn't work does not give enough information for people to figure out what the problem might be
[20:36] <maxb> You should always try to be as precise as possible, including exact error messages, when asking for help on IRC
[20:36] <Zblakany> maxb: I know, but logs and messages after I moved that repos to new location are gone :-/
[20:37] <maxb> The only reference to other filesystem paths in bzr branches that I can think might cause things not to work is stacked_on locations in .bzr/branch/branch.conf
[20:41] <Zblakany> maxb: I can change this stacked_on locations manually, or should I use some command?
[20:44] <Zblakany> s/I can/can I/
[20:44]  * jelmer waves
[20:51] <maxb> Zblakany: yes, you can edit them manually for this sort of fixup
[20:56] <Zblakany> maxb: thanks :-)


[00:19] <ochosi> pleia2: is there a second page or is it really just the app-selection?
[01:36] <pleia2> ochosi: there are 4 pages to the article
[01:45] <GridCube> :D
[01:45] <GridCube> yes is pretty nice
[01:45] <GridCube> i like that last app recomendation
[01:45] <GridCube> nightdale
[06:01] <laite> ochosi: I created branch 'BBird-laite' and pushed my modification for simpler close-icons
[06:02] <laite> I think it looks pretty nice, but of course there's the question of tradition/continuity with Bluebird-theme
[07:29] <ochosi> laite: right. well we'll see. i don't think tradition should matter all that much, the most important thing to me is if it's maintained properly :)
[07:30] <ochosi> laite: (and since it's git, people can always download the "original" window borders)
[07:30] <ochosi> one more note: for theme-development stuff you might also head over to #shimmer, that's where our commit-bot is running and where we usually discuss fine-tuning of themes
[07:45] <laite> k, cool
[07:47] <laite> If somebody wants to say an opinion, here's pic with old buttons: i.imgur.com/CMTU0.png and here's the same picture with simpler close-button: i.imgur.com/skcrF.jpg
[07:48] <ochosi> what are those funny faces in the right-top corner? :)
[07:48] <Unit193> (Little bit of NSFW warning on the second)
[07:49] <laite> ochosi: I have no idea =D
[07:49] <ochosi> heh
[07:49] <chelz> i kinda like the old buttons
[07:49] <ochosi> laite: you also seem to have quite a funny screen-resolution (or is it cropped?)
[07:49] <chelz> but i always change themes anyway
[07:50] <chelz> kapy terry everywhere
[07:50] <laite> ochosi: it's cropped, my workspace is 2x(1920x1080)
[07:50] <ochosi> laite: oh right, that makes more sense
[09:05] <laite> One (obvious) idea: since xubuntu is considered 'newbie-friendly' distro, could it have something similar on first boot that mint currently has - dialog with a lot of options for newcomers who don't know what to do with linux and how
[09:06] <laite> http://tinyurl.com/d25w7xr
[09:06] <laite> ^pic of linux mint's welcome-dialog
[09:30] <baizon> not needed imo
[09:33] <ochosi> not a totally bad idea
[09:34] <ochosi> but kinda windowsy, those welcome-screens
[09:34] <baizon> yes
[09:34] <baizon> windows xp got it
[09:34] <baizon> but was droped with vista and 7
[09:34] <baizon> 90% wont look at it
[09:34] <baizon> the first thing i did installing mint was disabling that window :D
[09:35] <baizon> it would be kinda nice "help" window
[09:35] <baizon> or "about"
[09:36] <laite> I agree that (at least) 90% close and disable it immediately without even looking, just remembered my own first installation of linux and the 'ok, I've got os running - what do I do now?'-feeling I got
[09:36] <laite> when everything is new and scary :P
[09:37] <baizon> even when i first got the xp installation i didnt watch at the welcome window
[09:37] <baizon> nobody likes to read, people like to test / learn :)
[09:37] <laite> yeah, but that was truly horrible with animated windows and everything =D
[09:37] <laite> and it seemed to load forever
[09:38] <baizon> yes thats why i think this window would do great as help or about, but not as a "welcome screen"
[09:38] <laite> right
[09:46] <ochosi> well yeah, we have to do something about our help and doc anyway...
[09:52] <laite> in roadmap there is 'Refresh the offline documentation ', but what exactly and where is this documentation?
[09:52] <laite> I've deleted 'help'-item from my main menu *blush*
[09:55] <laite> I looked into mintwelcome (https://github.com/linuxmint/mintwelcome) and it's a quite simple python program, shouldn't be too hard to do something similar
[10:11] <ochosi> mhm
[10:11] <ochosi> well the thing is that atm the xfce doc is in a wiki
[10:12] <ochosi> (before it was in mallard)
[10:12] <ochosi> so they keep their doc online-only
[10:12] <ochosi> the question is whether we want to ship a static version
[10:13] <ochosi> and if we do, whether it should be in wiki-form
[11:19] <bluesabre_laptop> ochosi: Wanna have a look at the GTK3 catfish with zeitgeist suggestions?  https://launchpad.net/catfish-gtk3
[11:35] <ochosi> bluesabre_laptop: woot, you mean you actually already started??
[11:38] <ochosi> bluesabre_laptop: ok, the gtk3 part looks great
[11:39] <ochosi> i don't get any suggestions yet
[11:39] <ochosi> do i need extra stuff for that?
[11:39] <ochosi> (already have zeitgeist and activity journal installed)
[11:40] <ochosi> btw, one really easy thing to fix would be to search when hitting enter (when the gtkentry has focus)
[11:40] <ochosi> another would be to have the home-folder selected as default search location instead of catfish's own folder (which is kinda useless imo)
[11:41] <ochosi> oooh, now i do get suggestions
[11:41] <ochosi> great stuff!
[11:42] <ochosi> still getting quite a few warnings:
[11:42] <ochosi> (catfish.pyc:6524): Gtk-WARNING **: /build/buildd/gtk+3.0-3.4.1/./gtk/gtkliststore.c:851: Unable to convert from gint to glong
[11:43] <ochosi> (and the mimetype icons aren't found, but that's not so important)
[11:48] <bluesabre_laptop> yeah, I was going to fix each of those things that you just mentioned.  That's just what I threw together overnight. A lot of what is displayed to terminal would probably be displayed by the gtk2 version too.  I added some extra output for temp debugging
[11:49] <ochosi> yeah, but really, this is so cool! :)
[11:49] <bluesabre_laptop> awesome
[11:49] <ochosi> i'm a huge fan already
[11:50] <ochosi> i think with a few UI tweaks this will be a great step forward
[11:50] <ochosi> i'll draw up a quick mockup
[11:50] <bluesabre_laptop> Good to hear.  Let me know any suggestions you have for the UI.  For this, I just tried to get a working clone
[11:50] <bluesabre_laptop> cool
[11:50] <bluesabre_laptop> doesn't have to be too quick.  I won't be back online for at least an hour
[11:50] <bluesabre_laptop> :D
[11:51] <ochosi> heh
[11:51] <ochosi> well i'll go out to play boccia in an hour or so
[11:52] <ochosi> i'm thinking something like appfinder
[11:52] <ochosi> very minimal
[11:52] <ochosi> and then the results-window pops up underneath the searchbar
[11:52] <ochosi> (not entirely sure yet, just an idea)
[12:05] <ochosi> bluesabre_laptop: something very simple maybe: http://imagebin.org/212684
[12:05] <ochosi> basically the menu-button on the top-right would reveal the settings that the sidebar currently shows
[12:05] <ochosi> oops, i forgot to add the "folder-to-search-in"-widget...
[12:08] <ochosi> better now: http://imagebin.org/212685
[12:09] <ochosi> the sidebar could also be shown/hidden with an arrow-button (instead of the properties/menu-button)
[12:09] <ochosi> but really, a lot of buttons/widgets have to go from the sidebar
[12:09] <ochosi> the close-button, the find-button, and the catfish-title at least
[12:15] <ochosi> (at a later point, we could throw this in a panel-plugin, that'd be really kewl)
[12:38] <ochosi> bbl
[12:52] <bluesabre> I'm back
[12:56] <bluesabre> ochosi: I like that mockup (and I'm sure the elementary team would love it).  That would be easy to implement, I'm sure.
[13:13] <bluesabre> ochosi: Another option would be to have an "advanced" button next to the search box that would unhide a second toolbar with the settings.  But the AppMenu is probably a better option.
[14:02] <knome> bluesabre, re: python3, we're following ubuntu on what they do, but that's not one of our specific goals
[14:03] <bluesabre> Cool.  Thanks for getting back to me knome
[14:03] <knome> no problem, just got home from summer cottage
[14:33] <knome> i think generally the stance about 4.10 should be exaclty "unless you really need it, don't install it"
[15:19] <knome> ok, bbl
[15:24] <bluesabre> ochosi: I think the new InfoBar widget might be useful to display while the search is running.  Just show that the search is in progress, and have the cancel button there.  Thoughts?
[15:44] <ochosi> bluesabre: hmm, infobar is always a good idea yes, but i'm not sure it's ideal for progress
[15:44] <ochosi> bluesabre: but i'll try to include that in a mockup, then it's easier to imagine/think about it
[15:47] <bluesabre> ochosi, not so much for displaying progress as saying * Search in progress...      [Cancel]
[15:47] <ochosi> ok right
[15:47] <ochosi> well the "classical" thing to do would be add a gtk-spinner somewhere
[15:47] <ochosi> but that's usually not in an infobar
[15:49] <bluesabre> true
[15:50] <ochosi> maybe the most elegant place to position the spinner would be the results window
[15:50] <ochosi> ah wait, no i have to draw a mockup of that first :)
[16:12] <ochosi> bluesabre: theoretically you could throw the spinner and the cancel button inside the search-gtk-entry
[16:12] <bluesabre> hmmm
[16:13] <ochosi> too much?
[16:13] <bluesabre> hadn't thought of that
[16:13] <ochosi> i mean the cancel-button could just replace the searchglass
[16:13] <bluesabre> right
[16:13] <bluesabre> I could do that
[16:13] <ochosi> that would kinda make sense to me
[16:13] <ochosi> i guess progressbars don't make sense in this context, hm?
[16:14] <bluesabre> nope
[16:14] <bluesabre> unless you use one of the silly bouncing ones
[16:14] <ochosi> cause then you could do it like web-browsers do to indicate the page-load process
[16:14] <bluesabre> but those rarely make sense
[16:14] <ochosi> hehe, no, those are really silly :)
[16:22] <ochosi> bluesabre: a quick mockup of how i's imagine a panel-plugin: http://imagebin.org/212727
[16:23] <ochosi> in this case it would have to be a kind of "global" search (or maybe a search of /home)
[16:23] <ochosi> cause i think a folder-combo would be a bit too much there
[16:23] <bluesabre> I agree
[16:23] <bluesabre> but that does look cool
[16:23] <ochosi> the borders aren't really perfect yet
[16:24] <ochosi> in fact it should be possible to abuse the UI code of the linelight-plugin for that
[16:24] <ochosi> it's pretty similar iirc
[16:26] <bluesabre> sounds promising
[16:29] <ochosi> it's this one: http://goodies.xfce.org/projects/panel-plugins/xfce4-linelight-plugin
[16:30] <ochosi> meh, of course i can't install it here because it's still built against the old panel :(
[17:21] <mr_pouit> ochosi: it's in the ppa afaik
[17:21] <ochosi> mr_pouit: aha. strange then
[17:22] <mr_pouit> (the only one that uses some api removed from libxfce4util 4.10 :p)
[17:22] <ochosi> meh
[17:22] <ochosi> yeah, i mean it's not soo useful, it never worked so well
[17:23] <ochosi> i just wanted to look at it again to see whether there's anything we can use for a potential catfish-panel-plugin
[17:24] <ochosi> mr_pouit: so i assume you've already commenced to work hard on the display dialog refresh? :D
[17:25] <ochosi> there's in fact one thing i forgot in the mockups: a "reload display-list"-button
[17:29] <ochosi> also: we could pop up huge numbers ("1", "2") on the displays with the respective numbers, so users could more easily identify them
[17:41] <mr_pouit> no, I didn't start :p
[17:51] <knome> heh, today we beat ScottL's country ;)
[18:18] <knome> have i missed something from the blueprints already registered in launchpad?
[18:18] <knome> https://blueprints.launchpad.net/ubuntu/+spec/topic-quantal-flavor-xubuntu shows a quick tree to access them all
[18:18] <knome> (i'm mostly referring to the work items, is there something obvious missing)
[21:31] <bramwelt> d/win 3
[21:38] <pleia2> astraljava: we should chat soon about qa/testing stuff (I learned lots at UDS!)
[21:38] <knome> mm-hmm
[21:39] <knome> don't do that on saturday, i'm going to be offline for most for the day
[21:39] <knome> well, until 7pm-10pm UTC most probably
[21:39] <knome> but i'm going to be dead tired when i get back ;)
[21:41] <pleia2> the weekend following is a holiday weekend in the states and I'll be out of town
[21:41] <pleia2> but I'll be around this sunday
[21:42] <knome> sunday should work relatively fine
[21:42] <Unit193> Wait, it is?
[21:42] <pleia2> Unit193: memorial day weekend
[21:43] <Unit193> Sweetness! We may be going out of town!
[21:45] <pleia2> no no, I am going out of town, you are staying here with Xubuntu :)
[21:45] <knome> haha
[21:45] <knome> WITH ME
[21:45] <Unit193> ...I'm getting message pop up sounds, so weird.


[08:44] <vish> yofel_: could you ping me when you are available for triaging a few kubuntu bugs ? :)
[10:35] <andersk> Bug 586711 had importance High before being marked as a duplicate of bug 546794.  In that case, can someone set the latter to importance High as well?
[10:35] <ubot2> Launchpad bug 586711 in bash-completion (Ubuntu) "[Maverick] Errors whenever opening a terminal (dup-of: 546794)" [High,Triaged] https://launchpad.net/bugs/586711
[10:35] <ubot2> Launchpad bug 546794 in bash-completion (Ubuntu) (and 1 other project) "[revert, causes errors] Smarter lib* aware autocompletion? (affects: 15) (dups: 3) (heat: 110)" [Undecided,Confirmed] https://launchpad.net/bugs/546794
[12:52] <SalmonSam> could anyone help me with running nautilus through valgrind?
[15:18] <pascalFR> any clue on this Bug #587226
[15:18] <ubot2> Launchpad bug 587226 in virt-manager (Ubuntu) "virt-manager cannot start module libvirt not found (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/587226
[15:24]  * wise_crypt is away: need a rest, tired looking a fast channel :)
[15:25] <nigelb> wise_crypt: if thats an auto-away, can you please disable it.
[17:51] <MichaW> Hi?
[17:51] <crimsun> yes?
[17:52] <MichaW> I raised a bug in Ubuntu a few days ago and was wondering if there's any way to get it looked at.
[17:52] <MichaW> Upstream already fixed it (after we notified them).
[17:53] <nigelb> bug #?
[17:53] <MichaW> https://bugs.launchpad.net/ubuntu/+source/gnustep-base/+bug/585179
[17:53] <ubot2> Launchpad bug 585179 in gnustep-base (Ubuntu) "gnustep - parsing of XML property lists broken (affects: 1) (heat: 6)" [Undecided,New]
[17:53] <MichaW> Reason being we're getting ready to release a new version of Oolite and this bug affects it on Lucid.
[17:54] <nigelb> do you have an upstream bug number or commit ?
[17:54] <MichaW> https://savannah.gnu.org/bugs/index.php?29955
[17:54] <MichaW> Upstream already mentioned they won't backport the fix to gnustep-base1.19
[17:54] <MichaW> So Debian/Ubuntu would have to do so. Unless they are prepared to upgrade gnustep-base to 1.20 in Lucid.
[17:54] <nigelb> ok, then its get murkier
[17:55] <nigelb> unless its an isolated patch that fixes this particular bug, its difficult
[17:55] <MichaW> Looking at their commit diff, it's very isolated.
[17:55] <crimsun> gnustep-base has a ton of reverse deps, so upgrading to 1.20 seems rather a long shot
[17:56] <MichaW> That's what I thought :)
[17:56] <crimsun> it'd be much more feasible to cherry-pick fix(es) if possible
[17:57] <nigelb> ugh, I hate cvs
[17:57] <MichaW> I can make (&test) a suitable patch if this would assist.  Just wondering what the normal turnaround-time is for bugs in Ubuntu.
[17:58] <MichaW> Incidentally, the patch I submitted upstream was NOT used by upstream.
[17:58] <vish> heh
[18:00] <siefca> Hi, is the problem with mountall and encrypted partitions a common problem in Lucid? (Initialization hangs just after LUKS partition had been mounted and I need to press 'S')..
[18:00] <nigelb> MichaW: if you're willing to do the work, the turn around time is lower
[18:01] <aburch> But it could still take forever :/
[18:01] <MichaW> nigelb: Ok.  We'd be pretty interested in getting this fixed as Oolite runs fine on all versions of Ubuntu prior to Lucid. In fact, the version of Oolite included in the normal Ubuntu repositories is broken by this bug too.  And most likely other gnustep based software.
[18:02] <nigelb> aburch: +1 to that ;)
[18:02] <nigelb> MichaW: ok, first thing would be fix it for maverick.  Then you can propose an SRU for this bug for lucid.
[18:03] <nigelb> Unless its fixed in maverick, its tough to get a fix for lucid.
[18:03] <MichaW> Yikes. Even though Lucid is a LTS?
[18:04] <MichaW> Ok, anyway I'll see about getting a patch for maverick together this weekend then.
[18:04] <nigelb> You have to understand that if things go wrong, it might introduce a very bad regression
[18:05]  * MichaW nods.
[18:05] <MichaW> Looks like regression testing failed to pick it up in the first place though :) (By upstream as well as distros).
[18:06] <nigelb> So, SRU team needs a lot of documentation.  How it works.  If it introduces regressions, etc
[18:06] <penguin42> there is a 10.04.1 due sometime, there's an OOo bug I have that's been marked for that
[18:06] <nigelb> I would suggest pushing it to a PPA for lucid, so you can test and others can test and check if there are regressions.
[18:07] <nigelb> !sru
[18:07] <nigelb> err.. what was the one for sru?
[18:07] <hggdh> MichaW: why wass the patch rejected by upstream?
[18:08] <hggdh> httpsdon't remember the fatoid, but here's the source: https://wiki.ubuntu.com/StableReleaseUpdates
[18:08] <MichaW> hggdh: I just reverted their changes which introduced the bug.  They decided to fix it in their changes rather than revert to their original code.
[18:09] <nigelb> thanks hggdh :)
[18:09] <nigelb> MichaW: the custom library thing?
[18:09] <hggdh> MichaW: oh, so it was just a revert. Be sure to state what your patch is doing, and what are the consequences
[18:10] <MichaW> nigelb: Yes. They were using it anyway in case the xml2 parser failed. Apparently there's some bad XML files from Apple which don't parse properly using a 'real' XML parser.  Their custom parser works for that.
[18:10] <nigelb> MichaW: ah, ok
[18:10] <MichaW> hggdh: The patch I'd prepare for Ubuntu would be their changes, not the changes I supplied to them.
[18:11] <nigelb> Just so that you know SRU needs a *lot* of ground work, so be prepared with everything thrown at you :)
[18:11] <hggdh> MichaW: OK, even better
[18:11] <MichaW> Well, it needs fixing :) So I'll see if I can work my way through the bureaucracy.
[18:12] <penguin42> what's the right thing to do with a bug that looks valid but is obviously against the wrong package?
[18:12] <nigelb> Its not bureaucracy per se.  Just making sure that things are going to be fine after this patch.  The last time I did an SRU, I introduced a bad regression and had to run around a bit
[18:12] <hggdh> set it to the correct package, penguin42
[18:13] <nigelb> penguin42: ask which is the right package :)
[18:13] <penguin42> hggdh: It's a suspend/resume display issue so I guess either linux or the xserver, but since he's reported it against firefox it has no useful information on the hardware
[18:13] <MichaW> nigelb: Yes, I understand. Just the 'be prepared to handle everything thrown at you' comment sounded like there might be a lot of 'paperwork' involved.
[18:14] <penguin42> is there a tag for suspend/resume issues?
[18:17] <hggdh> penguin42: IIRC it will be against linux. Please ask the OP to 'ubuntu bug linux <bug#>'
[18:17] <penguin42> OP?
[18:18] <hggdh> penguin42: or just reset the package to linux, and the OP runs 'ubuntu-bug <bug#>´
[18:18] <hggdh> OP == Oroginal Poster
[18:18] <hggdh> Original, even
[18:18] <hggdh> the reporter, I mean
[18:18] <penguin42> ah, I didn't know you could run ubuntu-bug with the number
[18:18] <hggdh> darn! I should have respected Saturday
[18:19] <hggdh> cannot write anytihng
[18:19] <hggdh> hell
[18:19] <hggdh> hey nigelb, how did the python go?
[18:23] <MichaW> nigelb: One more question.  Do I raise a separate bug for maverick, and attach my proposed patch to that?
[18:24] <penguin42> does anyone know what size size_t is on 32bit?
[18:24] <hggdh> MichaW: raise the bug to Maverick, and nominate it for Lucid. When Maverick gets the fix, lucid will be in for SRU
[18:24] <hggdh> penguin42: 32?
[18:25] <penguin42> that's what I'd assume
[18:25] <nigelb> hggdh: apparently, running from subprocess always makes problems.  going for a new approach now
[18:26] <MichaW> nigelb, hggdh: Many thanks for your assistance with this.
[18:26] <nigelb> MichaW: no problem  :)
[18:27] <nigelb> hggdh: I'm going to get python to send the mail to debian btw directly
[18:27] <nigelb> bts even
[18:27] <nigelb> arrg, can't type today I guess
[20:35] <stenten> Question: Let's say I tell someone to enable Apport and recreate their resume X crash. Will Apport allow the report to be appended to the bug report, or will it create a new one?
[20:45] <penguin42> stenten: apport-collect can add, not sure if that's the best way
[20:58] <dgtombs> stenten: no, it'll create a new report
[20:58] <dgtombs> but in that case it might be better to file the new one and made an old one a dupe
[20:58] <dgtombs> anyone here into kernel triaging?
[21:04] <dgtombs> well, whenever anyone shows up: bug #376793 has been tested in upstream kernel and doesn't exist. according to KernelTeamBugPolicies, i think it should now go into the Triaged status
[21:04] <ubot2> Launchpad bug 376793 in linux (Fedora) (and 2 other projects) "HP 2140 Lid Close Not Detected (affects: 16) (heat: 110)" [Unknown,Unknown] https://launchpad.net/bugs/376793
[21:05] <dgtombs> i also suggest that the importance is Low and not Medium
[21:07] <BUGabundo> evening slackers & weekenders
[21:10] <SalmonSam> I'm trying to get some information about a memory leak in nautilus with valgrind however the log doesn't appear to contain much information ( http://paste.ubuntu.com/441466/ ) , do I need to install more debug symbols?
[21:41]  * wise_crypt is away: sleeping
[21:46]  * wise_crypt is back (gone 00:05:37)
[21:47]  * wise_crypt is away:
[22:24] <stenten> What package should I assign bugs to where the keyboard is unresponsive on boot?
[22:25] <stenten> I figured it was either 'linux' or 'xorg-server'
[22:35] <penguin42> stenten: If it isn't just X then I'd say linux
[22:35] <penguin42> stenten: Can you ssh in?
[22:39] <stenten> penguin42: Not sure. I'm just assigning bugs that don't have any packages.
[22:39] <penguin42> can you show me the bug?
[22:40] <stenten> #583613
[22:41] <stenten> bug #583613
[22:41] <ubot2> Launchpad bug 583613 in ubuntu "Upgrading super os 9.10 to 10.04 will not reboot from harddrive after install (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/583613
[22:42] <penguin42> stenten: It says command line so I think it is linux
[22:42] <penguin42> it sounds like X didn't start
[22:42] <stenten> Ah. Because X isn't running if it spits you into a command line?
[22:43] <penguin42> however, it's possible X started and crashed
[22:43] <penguin42> yeh
[22:44] <stenten> My thought was that even if it's an X issue, it'd be a KMS issue so it'd be linux anyway.
[23:20] <penguin42> not necessarily, it could just be a duff X driver - KMS only switches modes, it doesn't actually do most drawing
[23:22]  * penguin42 gently wonders about the origin of the phrase 'mode' for a screen resolution - I know the old Acorn machines had it back in '82 but was that the 1st? (OT)
[23:43] <RunePhilosof> Would it be acceptable to sru a package even though the fix is rolling back the fix for another (less important) bug?
[23:47] <lifeless> case by case