[02:26] Is anyone going to hate me if I got an iPad? [04:38] anyone else having rendering issues in FF using LP edge? Using edge server I get http://imgbin.org/images/1847.png. If I temporarily disable edge it renders properly - http://imgbin.org/images/1848.png [04:49] FYI - if anyone cares, I asked in #launchpad. edge has broken css. fix has landed and will be re-rolled with the next edge rollout [07:38] hi there [07:38] hi baptistemm [10:25] nigelb: Hi Jasneet here [11:39] since Karmic when I disconnect the charger of my netbook the battery status goes to full :( how do I where the bug lies? [11:39] there are so many things here, gnome-power-manager, upower, kernel, and maybe acpi-support so I cant think what it can be [11:42] upower could be ruled out as it was not in Karmic but the problem was there... [13:31] ddecator: are you around? [13:34] empathy in lucid seem to be acting up, it freezes but dont show anything is wrong. Others see you as offline but empathy shows it is online. need to kill telepathy before restarting empathy as a temperary fix. was planning on filing a bug on this, but there was already 500 bugs for empathy and 200 for telepathy...to many for checking if it already exist [13:36] good morn all [13:37] morn bcurtiswx [14:18] Hi all, I'm currently looking at bug 593578 and am wondering how to take it forward. Presumably, the user would need to be able to find what process causes the performance problem but I'm not sure what to ask in order to get that information. [14:18] Launchpad bug 593578 in nautilus (Ubuntu) "impossibile due sessioni attive... (affects: 1) (heat: 6)" [Low,Invalid] https://launchpad.net/bugs/593578 [14:21] brunogirin, you could ask if the screensaver is running [14:21] could be a 3d screensaver on the other session [14:25] seb128: yes it could be but how would the user know whether this is running in the other session? ps would tell you but to do that, he'd need to open a terminal and from what he says, once the system is unresponsive, he can't do very much; maybe ask him to run s short script that gather ps output every 5 seconds in the background to find what causes it? [14:25] well try asking him to turn off the screensaver setting [14:26] or to delay it to 15 minutes or so [14:26] so he can see if that works better [14:34] seb128: thanks, I'll see what I can do; but shouldn't the screensaver be disabled on the session that is not active on the grounds that it doesn't have control of the screen? [14:35] it should [14:35] I'm not sure it is though [14:37] seb128: the only way to find out is to find the process that causes the problem; I think something like this could help: ps -eo uid,pid,ppid,%cpu,%mem,args --sort -%cpu | head -5 [14:37] or ask to open the system monitor and see what eats cpu [14:38] Hi, I am new to this and was wondering if bug tracking is a good starting point to help out the development of Ubuntu [14:38] seb128: same problem as with running a command: if the whole desktop is unresponsive, he won't be able to open the system monitor [14:39] Vork: dealing with bugs is certainly a very good way to help out, thanks :-) [14:39] ok thanks :) [14:41] Vork, you could always ask here if you need any help. [14:41] ok, i am joining right now, i am reading over the code of conduct [14:41] brunogirin, get it running before getting the issue and wait for it to start [14:44] seb128: thanks, will do something along those lines, hopefully I'll manage to explain that clearly enough in Italian ;-) [14:44] vish: Thank you for your awesome work on the mentors project! You've really done a lot of work. [14:45] vish: Bruno Girin has sent a mail addressed to the both of us in which he said that although he is now confident to triage bugs on his own he doesn't have the time to be active in the Bug Squad. [14:47] qense: well, I can be active occasionally but not as much as I was planning to :-) [14:47] hello brunogirin! [14:47] brunogirin: That's fine, just contribute at the level you want. [14:47] qense: hello! thanks for your reply to my email [14:47] You're a volunteer after all and we are happy with anything you do for Ubuntu. [15:02] qense: well, there's always this pesky thing called work getting in the way :-) Anyway, I found a way to contribute that should suit me better: I'm going to adopt the shotwell package [15:02] brunogirin: Happy to hear someone's adopting the default photo manager-to-be. Thank you! [15:04] hey, qense , brunogirin [15:04] brunogirin: you can also get into BC , via upstream dev [15:04] qense: I might need help once it actually becomes the default ;-) [15:05] brunogirin: If you are going to adopt Shotwell I think you really should apply for Bug Control membership, though. [15:05] Especially considering you are doing upstream work I think you will make a good chance. [15:05] vish, qense: ok, will do [15:05] great! [15:06] brunogirin: "If you are an upstream developer or bug triager for an upstream project contact Jorge Castro" from > https://wiki.ubuntu.com/UbuntuBugControl [15:06] jcastro! ^^ [15:07] jcastro: Rejoice (and wake up if you still have to)! We've got an adopter for Shotwell! [15:07] qense: yeah , that was a lot of backlog in the team :) [15:07] vish: You really are awesome! :D Was it a lot of work to do? [15:08] qense: took nearly 6 hrs ;) [15:08] So yes it as. [15:08] qense: i doubt a few of the students will reply, some of them had applied a long while ago [15:08] 6 hours of volunteer time: priceless [15:09] i'm gonna suck it all out of micahg ;p [15:09] vish: It is good we give them a chance to still reply anyway. If not, that's mostly a pity for us since we might have lost potential bug triagers. [15:09] * micahg wonders what vish has in mind [15:09] oh! [15:09] * vish vampire ;) [15:10] qense: micahg pinged me yesterday for a student , and saw the pending list , thought it was time it got cleared :) [15:11] It waws time it got cleared indeed, but man, what a lot of workt hat must have been. [15:11] the tough part was figuring out the TZ , some had given the time in their own TZ converting it to UTC was irritating :/ [15:12] yeah [15:16] qense: woo hoo! [15:16] brunogirin: awesome, we should see a bunch of bugs for shotwell coming in when we start daily builds! [15:19] jcastro: yes I bet! if we can ask people to test the hell out of it in the beta phase, that would be good too [15:19] whats the diff on CD between fspot and shotwell? [15:43] Another question, on bug 590182: I can't reproduce as my locale is English so should I ask the reporter for a screenshot in order to demonstrate the bug? [15:43] Launchpad bug 590182 in shotwell (Ubuntu) "Publish button text cut off in Russian locale (affects: 1) (heat: 2906)" [Undecided,New] https://launchpad.net/bugs/590182 [15:45] brunogirin: it is a good idea [16:17] Ok I am trying to follow the steps to getting a bugsquad mentor. How do I setup an Ubuntu Wiki-page? [16:18] hggdh: thanks, done [16:19] Vork: When you go to and make sure you are logged in your (nick) name should be in the top right corner. Clicking on that should bring you to your wiki page. [16:20] If it doesn't exist yet you can create it then. [16:21] qense: doesn't that direct you to your preferences? [16:21] aw [16:21] let me check [16:21] yes it does [16:21] My bad! [16:22] Vork: alternatively, go to https://wiki.ubuntu.com/[your name], at which point it will tell you that the page doesn't exist and ask you if you want to create it. Select the HomepageTemplate and it will open an editor where you can create your page [16:23] Vork: After you've done what brunogirin said, make sure to add your wiki page to your Launchpad profile. [16:24] Vork: and if you want an example of what to put in, you can plagiarise this one: https://wiki.ubuntu.com/Qense ;-) [16:25] Feel free to plagiarise, as long as your story is original! :) [16:42] brunogirin, thank you [16:42] qense : will do [16:43] Vork: good! === ogra__ is now known as ogra === bac` is now known as bac [18:06] qense, hi [18:06] qense, i'm your student for mentorship [18:07] qense, i have read your email [18:07] qense, well that was a good introduction of ours ... [18:08] qense, are you online qense [18:22] hello simar [18:22] I wasn't paying attention to IRC, that's the reason for my late response. [18:22] simar: How are you doing? [18:23] Have you already started looking at some bugs, or do you want to do that together? [18:27] qense: indicator-applet fail? ;) [18:27] rather messaging menu .. [18:28] vish: I was marked as Busy, which suppresses the notifications, I suppose. [18:28] ah [18:29] chrisccoulson: hi are you fully busy till FF update is done? or able to take on a student for bugsquad mentoring? [19:12] I'm seeing emacs (GTK GNU emacs) going unresponsive. However, I'm not able to figure out exactly when this happens, but is seems to become unresponsive after some compiz operations. It looks like simply clicking on the gtk menu buttons get emacs responsive again. Is there a way to file a useful bug about this? === JayFo is now known as JFo === mach_ is now known as mach1723 [19:51] Vork: oops! pressed the wrong button! could you re-apply :s [19:51] * vish probably needs sleep [19:54] ahah vish [20:03] folecr: I suppose file it as you describe it, maybe be careful about detailing the steps to reproduce the bug === simar is now known as simar_ === simar_ is now known as simarmohar === simarmohar is now known as simar === simar_mohaar is now known as simar === simar is now known as simar_busy === simar_mohaar is now known as simar [21:35] Can anybody name a website that Is a Great place for hosting my terminal log? [21:35] That I can give a link to I Have a bug? [21:37] anyone? [21:37] anothernewbie: attach it as a text file to the bug [21:57] anyone here know anything about acpi? [21:59] dgtombs: the troubleshooting wiki has some stufff [22:00] micahg: thanks, already looked at that. trying to work on backlight bugs [22:00] that page has zero information on that [22:00] perhaps i'll make a DebuggingBacklight page with whatever info i find? [22:01] dgtombs: sure [22:01] now i just need to find an expert on acpi since i know nothing:) [23:51] all: EEEBotu will be restarted for a kernel upgrade in 3 minutes. I shouldbe back in another 2 minutes