[03:30] <odinsbane> I've got an issue thats related to /very similar to #305979
[03:30] <odinsbane> The main difference being, my video card is a different video card.
[03:31] <odinsbane> Still intel though just not the g45
[03:32]  * Ryan52 wonders what odinsbane is telling us for..
[03:33] <odinsbane>     *
[03:33] <odinsbane> Getting advice
[03:34] <odinsbane> My computer crashes and I would like to fix some how.
[03:34] <Ryan52> you still haven't asked a question..
[03:35] <Ryan52> user support should happen in #ubuntu
[03:35] <Ryan52> that's where the people who will help will be.
[03:35] <Ryan52> (will and can)
[03:35] <odinsbane> I've tried ubuntu+1
[03:36] <odinsbane> This bug has been reported fixed and I don't know if I just try to resubmit it.
[03:36] <Ryan52> are you up to date?
[03:36] <odinsbane> yes
[03:37] <odinsbane> as far as the update manager goes, it actually seemed to start happening after update some mesa drivers
[03:39] <Ryan52> I would make a new bug report, and include the information about what exactly you changed to cause the problem.
[03:41] <odinsbane> sounds good, Ill let it go for awhile to see if turning off compiz fixes it .
[03:45] <jtholmes> odinsbane, when and if you report the bug use  ubuntu-bug <packagename>   helps the developers and speeds up the process
[06:18] <lacqui> am i the only person here who finds that bug #362716 sounds more like a feature?
[06:18] <ubottu> Launchpad bug 362716 in app-install-data-ubuntu "Cannot open windows vista" [Undecided,New] https://launchpad.net/bugs/362716
[06:33] <Hobbsee> lacqui: that's *certainly* in the wrong place, for a start.
[06:33] <Hobbsee> at best, that's probably for wubi (in terms of it should restore the bootloader while uninstalling?)
[06:51] <YoBoY> good morning
[07:11] <dholbach> good morning
[08:56] <BUGabundo> guud morning
[10:34] <Rafik> good morning
[10:35] <BUGabundo> Rafik: hey
[10:37] <Rafik> mozilla locale packages are not supposed to depend on myspell right ?
[10:38] <Rafik> it's at bug 362381, similar to bug 138751
[10:38] <ubottu> Launchpad bug 362381 in ubuntu "Thunderbid, with the es localizaiton, is not capable of checking the spelling in spanish." [Undecided,New] https://launchpad.net/bugs/362381
[10:39] <ubottu> Launchpad bug 138751 in thunderbird "[Gutsy] Thunderbird does not depend on myspell" [High,Fix released] https://launchpad.net/bugs/138751
[10:42] <Rafik> need to reboot, brb
=== c0p3rn1c_ is now known as c0p3rn1c
[10:48] <BUGabundo> can someone please triage bug 362804? thanks
[10:48] <ubottu> Launchpad bug 362804 in ekiga "ekiga crashed with SIGSEGV in GMVideoInputManager_ptlib::OPEN " [Undecided,New] https://launchpad.net/bugs/362804
[10:53] <seb128> BUGabundo: nobody is working on ekiga what difference would that make?
[10:54] <BUGabundo> seb128: didn't know that! is it dead?
[10:54] <seb128> BUGabundo: no, it just has nobody in ubuntu actively working on it
[10:54] <BUGabundo> ah ok
[10:54] <BUGabundo> so I better send it upstream?
[10:54] <seb128> BUGabundo: you should really start sending bugs upstream if you want to get those solved
[10:55] <seb128> yes
[10:55] <BUGabundo> seb128: I do send them upstream, when I have reports of similar probs on other distros
[10:55] <BUGabundo> until then I let them be on ubuntu project
[10:56] <BUGabundo> not every upstream likes to be nagged about "our" bugs
[11:07] <BUGabundo> seb128: upstreamed
[11:07] <seb128> cool
[11:08] <BUGabundo> its easy eheh
[11:08] <BUGabundo> bugzilla at gnome is just a bit slow
=== a|wen- is now known as a|wen
[13:25] <lfaraone> Hi, can someone confirm bug 362892.
[13:25] <ubottu> Launchpad bug 362892 in prism "Prism does not mark .desktop items as "trusted"." [Undecided,New] https://launchpad.net/bugs/362892
=== fenris- is now known as e-jat
[15:51] <stickystyle> I just added bug 362951, but I know it affects the bash-completion package also, how do I add the bash-completion package to the bug?  Is it the "Also affects project" button?
[15:51] <ubottu> Launchpad bug 362951 in mtx "Bash completion does not work" [Undecided,New] https://launchpad.net/bugs/362951
[16:14] <BUGabundo> seb128: just tripped on a mem leak from gnome search tool
[16:14] <BUGabundo> can I start it from valgrind?
[16:23] <sbeattie> stickystyle: "also affects distribution" select Ubuntu and bash-completion.
[16:25] <stickystyle> sbeattie: Ah, perfect thanks.  I was reading that option as "distribution=red hat, suse, gentoo", but I guess that doesn't make much sense ;)  Thanks.
[16:27] <sbeattie> stickystyle: that bit is not one of launchpad's most intuitive of interfaces; lots of people get tripped up by it.
[16:31] <BUGabundo> humm
[16:31] <BUGabundo> no one to help me ?
[16:31] <BUGabundo> let try devel
[16:32] <james_w> stickystyle: your bug report is missing at least which version of the the distribution you are running
[16:32] <james_w> and the versions of the packages involved
[16:32] <james_w> stickystyle: consider using "ubuntu-bug" to file your bugs so that information is automatically included
[16:33] <james_w> also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522545 may be relevant
[16:33] <ubottu> Debian bug 522545 in bash-completion "bash-completion: configuration file conflict with mtx" [Serious,Closed]
[16:35] <hggdh> BUGabundo, you can use valgrind, yes. Just make sure the debug packages are installed
[16:35] <BUGabundo> but how to start it hggdh?
[16:36] <BUGabundo> I just searched for *.mp3 and selected all files
[16:36] <BUGabundo> and it used all my ram
[16:37] <hggdh> one way: G_SLICE=always-malloc G_DEBUG=gc-friendly  valgrind -v --tool=memcheck --track-origins=yes --show-reachable=yes --leak-check=full --num-callers=40 --log-file=valgrind.log my-programme and my parms
[16:37] <hggdh> I just put it in a shell script, and call it
[16:38] <BUGabundo> oh I know how to start valgrind
[16:38] <BUGabundo> even have a alias for it
[16:38] <BUGabundo> I mean, gnome search tool
[16:38] <stickystyle> james_w: Thanks for the tips, can't beleive I forgot to list the version.
[16:38] <hggdh> ah, you have to find what programme is called when you select it
[16:39] <BUGabundo> and what dbg files I need
[16:40] <BUGabundo> reboot
[16:40] <hggdh> you can look at the depends
=== rockstar` is now known as rockstar
=== fader_ is now known as fader|lunch
=== selket is now known as asr
=== asr is now known as alre
=== Brownout_ is now known as Brownout
=== fader|lunch is now known as fader_
[19:05] <paolob> Hi guys! Let me ask you before opening a bug. In my Jaunty beta gnome, it's happening that when I'm writing a doc with Oo.o, after some 100/200 characters the keyboard begins entering very strange characters, and I haven't found any way to modify this behaviour rather than closing Oo.o and reopening it. I have italian localization, italian keyboard, but I have a spanish layout too in my gnome settings. Any idea about anything similar?
=== mdz_ is now known as mdz
=== mdz is now known as mdz-crashy
[23:22] <jbotalan> So I found a bug with the notification system in 9.04, but I don't know how to check if it's been reported or not, or how to report it if it isn't.
[23:22] <jbotalan> Any help would be greatly appreciated.
=== asac_ is now known as asac
[23:54] <hggdh> jbotalan, check on http://launchpad.net