[04:06] <mrp123> hi all
[04:07] <TheLordOfTime> o/
[04:09] <mrp123> Just submitted this bug and patch. Is anyone else affected by this?
[04:09] <mrp123> https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1268250
[04:09] <ubot2> Launchpad bug 1268250 in software-center (Ubuntu) "software-center fails to display reviews" [Undecided,New]
[04:13]  * TheLordOfTime doesn't use software center, so he wouldn't know.
[04:13] <TheLordOfTime> I'd suggest leaving that bug be, it'll be seen soon enough, I think
[04:13] <TheLordOfTime> and if anyone else is affected by it it'll have people confirm it
[04:14] <TheLordOfTime> mrp123: but I'd also suggest that you provide steps to reproduce if necessary, so it can be tested by people who look at that package
[04:15] <mrp123> Ok. I wasn't sure what to write about reproducing it. It just happens no matter what.
[04:15] <TheLordOfTime> then there's no need for reproduction steps, so long as you've mentioned what OS and what version you're using
[04:16] <TheLordOfTime> I will ask you to give me the page you're looking at in software-center to see if I can reproduce this
[04:16] <TheLordOfTime> because although I don't use software-center it *is* installed
[04:16]  * TheLordOfTime just uses the command line :P
[04:16] <TheLordOfTime> so I can at least look :0
[04:16] <TheLordOfTime> :) *
[04:18] <TheLordOfTime> mrp123: at a most basic level, confirmed, but i did encounter a software-center crash error so i have to check that before I can say I can confirm your bug
[04:19] <mrp123> It happened for Stellarium, Midnight Commander, GeoGebra and any other I looked at.
[04:19] <TheLordOfTime> mrp123: confirmed looking at 7zip but I see a time-date string crash too so meh
[04:20] <mrp123> Thanks Lord ^^. I don't understand that last post
[04:22] <TheLordOfTime> mrp123: do you have the traceback that you can add into the bug?
[04:23] <mrp123> I can reproduce it and put it there.
[04:24] <TheLordOfTime> make sure it doesn't have any personal information in it, and is just the traceback
[04:24] <TheLordOfTime> i have traceback here and I'd like to see if it matches what you had
[04:24] <TheLordOfTime> to make sure i'm seeing the same bug
[04:25] <TheLordOfTime> mrp123: i commented on the bug asking the traceback to be attached, especially since I want to see if I'm seeing the same stacktrace
[04:25] <TheLordOfTime> same (or similar)
[04:26] <mrp123> won't be a minute, will have to replace reviews.py with the original one to reproduce it.
[04:26] <TheLordOfTime> i ain't going anywhere :P
[04:27] <TheLordOfTime> mrp123: note that "bodgy patches" don't usually end up being accepted.
[04:27]  * TheLordOfTime also swears he's seen another bug on this, but doesn't remember where it is
[04:32] <mrp123> Another bug report? I have seen a post on UbuntuAsk about it
[04:32] <mrp123> http://askubuntu.com/questions/403231/software-center-crashed-twice-works-but-wont-show-reviews-fresh-install-of-12
[04:33] <mrp123> Seems to be the same bug, but I searched for a bug report and It hadn't been submitted.
[04:33] <mrp123> Oh and I updated the bug description with the traceback :)
[04:36] <mrp123> And about using the command line instead of the software-center. I'm still learning my way around Ubuntu and I can never get the richness of detail about the program with apt-cache. (Maybe theres something I don't know about yet)
[04:36] <TheLordOfTime> mrp123: well the software-center adds some nifty other things to Ubuntu
[04:37] <TheLordOfTime> but i'm old school and I don't usually use anything outside the repositories that're standard :p
[04:37] <TheLordOfTime> so i can get by on my own :)
[04:37] <TheLordOfTime> without software-center
[04:37] <TheLordOfTime> but meh
[04:40] <mrp123> What ever works I suppose. I've recently changed my OS from windows. So far there's alot that I have come to enjoy (Especially the package management).
[04:43] <mrp123> About the bodgy fix, it was all I could manage and it fixed my problem at least.
[12:41] <cristian_c> Hi
[12:42] <cristian_c> I've opened this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972604
[12:42] <ubot2> Launchpad bug 972604 in linux (Ubuntu) "168c:001c [HP Compaq Presario C700 Notebook PC] Wireless led button doesn't switch colors" [Low,Triaged]
[12:42] <cristian_c> I was linked to: https://wiki.ubuntu.com/Bugs/Upstream/kernel and I've read it
[12:42] <cristian_c> I need some info
[12:42] <cristian_c> 'Please take care that when you provide the below information, you should be booted into the newest available upstream mainline kernel only. Failure to do this will have negative unintended consequences.'
[12:43] <cristian_c> which of the two kernels?
[12:43] <cristian_c> Any ideas?
[12:57] <penguin42> hmm
[12:58] <penguin42> why do you say 'of the two kernels' ? If it's latest upstream then that's only one
[12:59] <cristian_c> penguin42, before, I've installed the latest upstream kernel for my release
[13:00] <cristian_c> penguin42, then, I've installed the kernel showed by the user
[13:00] <cristian_c> *shown
[13:00] <penguin42>  'showen by the user' ?
[13:01] <penguin42> I don't understand where that comes from?
[13:01] <cristian_c> 'I've also tested the latest upstream kernel (3.8.13-03081314) for my installed ubuntu release'
[13:02] <cristian_c> 'cristian, thank you for your comments. Could you please test the latest mainline kernel available via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc5-trusty/ and advise to the results?'
[13:02] <cristian_c> 3.8.13 vs 3.13-rc5
[13:03] <penguin42> Reporting upstream I'd always report on the latest - i.e. 3.13
[13:04] <penguin42> cristian_c: However you're saying 3.13 doesn't change colour at all
[13:05] <cristian_c> penguin42, 3.13 aggravate the bug
[13:05] <penguin42> cristian_c: Be careful - it might be a completely different bug
[13:06] <penguin42> cristian_c: Still, if it happens on the upstream kernel then you should report it, but I'd report what you're seeing on 3.13 and put a note saying what used to happen, but it's important to report what you're seeing on the latest upstream
[13:06] <cristian_c> penguin42, in https://wiki.ubuntu.com/KernelMainlineBuilds:
[13:07] <cristian_c> 'In order to choose which is the closest mainline kernel to any particular Ubuntu release you can use the Ubuntu to mainline mapping table, which contains mappings from Ubuntu releases and pockets to mainline versions.'
[13:07] <penguin42> cristian_c: But if you've tested on 3.13 that's what I'd report upstream
[13:08] <cristian_c> I was suggested from you to install http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.13.14-raring/
[13:08] <cristian_c> penguin42, ok
[13:08] <penguin42> right, but that was a while ago!
[13:08] <cristian_c> I'll report upstream about 3.13
[13:08] <cristian_c> :)
[13:09] <cristian_c> penguin42, understood :)
[13:09] <penguin42> cristian_c: And for reporting upstream you always want latest
[13:10] <cristian_c> penguin42, but before the led changed color with echo none > "/sys/class/leds/ath5k-phy0::tx/trigger"
[13:10] <cristian_c> echo phy0radio > "/sys/class/leds/ath5k-phy0::rx/trigger"
[13:10] <cristian_c> inverted but changed
[13:10] <cristian_c> and with 3.13 no, the switch from connected to disconneted is much slower
[13:11] <cristian_c> penguin42, I'd like to be solved the original bug, too
[13:11] <cristian_c> :)
[13:12] <cristian_c> penguin42, for that, what should I do?
[13:17] <penguin42> cristian_c: I don't really know how that bit of stuff works so don't know, but if in 3.13 everything works except the LED then the two bugs might be related
[13:18] <cristian_c> penguin42, Is the same bug but aggravated
[13:19] <cristian_c> *it's
[13:19] <penguin42> cristian_c: That's really difficult to say without knowing how the code works
[13:20] <cristian_c> penguin42, but I've opened the report for the original bug
[13:21] <cristian_c> I've not undestood if the fixing the regression, the original bug is interested
[13:21] <cristian_c> or it solves only the regression
[13:22] <cristian_c> in the first case it's needed only the upstream report
[13:22] <penguin42> cristian_c: I don't think you can do anything except report what you're seeing in 3.13 but explain when you do that what used to happen and what's expected
[13:22] <cristian_c> penguin42, it's an old bug, that I reported
[13:23] <cristian_c> from old ubuntu releases, never worked on it
[13:24] <cristian_c> in the old bug: the led light is blinking (red/blue)
[13:24] <cristian_c> if I use the workaround, I can switch colors, but they are inverted
[13:25] <penguin42> yes, I understand what you're saying - but unless you're prepared to debug the code yourself, the only thing you can really do is report the upstream bug
[13:25] <cristian_c> on all the kernel (except 3.13)
[13:25] <cristian_c> *kernels
[13:25] <penguin42> cristian_c: What about 3.12?
[13:26] <cristian_c> penguin42, instead, with the 3.13 it's aggraveted because the the switch between wifi on and off is very slow and the LED does not change color by pressing the button before or after performing the workaround.
[13:26] <cristian_c> penguin42, I've not tried 3.12
[13:26] <cristian_c> version
[13:26] <cristian_c> :)
[13:28] <penguin42> cristian_c: The upstream guys only care about very recent
[13:28] <penguin42> cristian_c: If you can show a regression and point them to exactly which version regressed they might be interested; so like if you can show the LED stopped working between 3.12 and 3.13 say they might be help
[13:29] <cristian_c> led has not never worked well
[13:29] <cristian_c> penguin42, but I can't use the 3.12 kernel
[13:30] <cristian_c> because it's not in the ubuntu release mainline, I think
[13:30] <penguin42> cristian_c: OK, so report against 3.13 and describe what happens
[13:30] <penguin42> cristian_c: The difficulty is that this might only happen on your exact model of the laptop, and the guy who wrote the driver probably doesn't have one, so he might never have seen it and have no way of testing it
[13:30] <cristian_c> I'll try to report against 3.13 and if the regression is fixed
[13:30] <cristian_c> I'll continue to report the old bug in the launchpad report
[13:31] <cristian_c> penguin42, sure, it's related to my laptop, I've always said so
[13:31] <cristian_c> to atheros wifi card
[13:52] <cristian_c> penguin42, a question
[13:52] <cristian_c> penguin42, how can I get the specific commit for the regression?
[13:53] <penguin42> cristian_c: That's very tricky; you have to do what's called a bisect
[13:53] <penguin42> cristian_c: I wouldn't even try doing that unless you're happy with building your own kernels
[13:54] <cristian_c> penguin42, 'While booted into the newest mainline kernel only describe how the bug is reproducible in the latest mainline kernel only. If this is a regression, please note the specific commit. '
[13:54] <cristian_c> penguin42, Here is told to report the note about the commit that makes the regression
[13:55] <penguin42> yeh, if you can't find the commit then just state it's in the 3.13 whatever kernel version
[13:55] <penguin42> cristian_c: If you can try 3.12 for example and say that it's a regression between 3.12 and 3.13 then that's better than it being being 3.8 and 3.13
[13:56] <cristian_c> uhm
[21:45] <YOURBESTFRIEND> hello, I need help fixing some bug
[21:46] <Noskcaj> YOURBESTFRIEND, What bug
[21:47] <YOURBESTFRIEND> Noskcaj: this one: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1237749
[21:47] <ubot2> Launchpad bug 1237749 in indicator-keyboard (Ubuntu) "Icon does not change with theme switch" [High,Triaged]
[21:47] <YOURBESTFRIEND> it looks simple enough to fix
[21:47] <YOURBESTFRIEND> not sure if it is
[21:48] <Noskcaj> branch the code and try
[21:49] <YOURBESTFRIEND> Noskcaj: not sure if the bug is in unity (unity-panel-service) or indicator keyboard
[21:51] <Noskcaj> I can't help you with that bit sorry, i don't have unity installed
[21:54] <YOURBESTFRIEND> Noskcaj: isn't there some kind of menthoring program for newbie bug hunters?
[21:55] <TheLordOfTime> i think the mentors program disappeared...
[21:55] <TheLordOfTime> for bug stuff at least
[22:00] <YOURBESTFRIEND> (  ;____;)
[22:01] <TheLordOfTime> you'd have to branch the code and see if it fixes it
[22:02] <TheLordOfTime> for either indicator-keyboard or Unity
[22:02] <TheLordOfTime> that's relaly the only way to test a fix for a bug, branch the code, patch the code, build it, test it.
[22:03] <YOURBESTFRIEND> not sure what's missing though… the keyboard indicator and ubuntu cloud indicator have a similar bug, but not exactly the same…
[22:04] <YOURBESTFRIEND> so I guess they are bugs respective to the indicator themselves, would make more sense to me
[22:04] <YOURBESTFRIEND> but yeah I will try
[22:05] <YOURBESTFRIEND> TheLordOfTime: is there an easy way to branch the code and use *my* version instead of the system one?
[22:06] <TheLordOfTime> similar but not the same is not the same :P
[22:06] <TheLordOfTime> so the fixes might be different
[22:07] <TheLordOfTime> YOURBESTFRIEND: i don't test Unity or indicator bugs, i almost exclusively test server packages only, so I can't advise you
[22:07] <TheLordOfTime> ultimately I never test things on my production (i.e. "actual install") environment, unless I have to
[22:07] <TheLordOfTime> i always try and reproduce in virtual machines where I can rebuild them if I accidentally obliterate the system with the patches
[22:07] <TheLordOfTime> even with server packages I maintain, I do that
[22:07] <TheLordOfTime> s/maintain/work on and maintain inside of PPAs/
[22:07]  * TheLordOfTime doesn't officially maintain any server packages (yet)
[22:08] <YOURBESTFRIEND> I see, I should do that too, and maybe try to see if the bug is still there on 14.04
[22:09] <TheLordOfTime> yeah i had to confirm a bug in the 14.04 packages, then in Debian, so I had to create two VMs, but at least THAT bug wasn't a UI bug
[22:09] <TheLordOfTime> :P