[02:06] <andresmujica> hi, i'm dealing with a suspend/hibernate bug #15372 and maybe i hit another bug while recopiling info from the debuggers to improve the report.
[02:07] <andresmujica> the thing is that when the /etc/acpi/hibernate.sh force script is executed, a total freeze occurs, while executing gnome-power-cmd.sh hibernate behaves as expected..
[02:08] <andresmujica> are the acpi scripts deprecated? should we use the gnome-power-cmd.sh to debug those issues?
[02:44] <Ryan52> how do you best handle when a bug was reported against hardy and is already fixed in jaunty?
[02:47] <stgraber> usually it's marked fix released as it's fixed in the latest devel release. If it could become a SRU, the bug can also be changed to reflect that
[02:49] <Ryan52> that's what I assumed...wanted to double check. (/me worries that he's doing things wrong a lot..)
[02:50] <Ryan52> thanks
[04:11] <jedex> hi
[04:51] <jedex> while i am gathering information in order to triage a bug, should i assign it to myself?
[04:56] <greg-g> jedex: no. Just subscribe.
[06:57] <thekorn> good morning
[09:25] <dholbach> good morning
[09:25] <BUGabundo_work> hi dholbach
[09:25] <dholbach> hi BUGabundo_work
[09:28] <thekorn> good morning dholbach
[09:29] <thekorn> and BUGabundo_work
[09:30] <dholbach> hiya thekorn
[10:47] <andresmujica> bug 268719
[10:53] <BUGabundo_work> thekorn: hi, back
[12:35] <CrownAmbassador> Hi guys... How do I filter the bug lists so that I only see the bugs that has no package assigned to it?
[12:36] <andresmujica> https://wiki.ubuntu.com/Bugs/EasyTasks
[12:36] <andresmujica> first link
[12:36] <nhandler> andresmujica: You can use http://tinyurl.com/5uxg9a
[12:38] <CrownAmbassador> Fantastic! I had that tinyURL but lost it! Thank you both!
[12:39] <nhandler> You're welcome CrownAmbassador
[12:58] <afflux> kernel people, bug 51779 was about having to manually load the ircomm module and to  create some /dev/ircommX devices. The devices are now created automatically, after loading ircomm manually. Can I consider this fixed?
[13:55] <hggdh> afflux, best to check on #ubuntu-kernel
[13:56] <afflux> good idea, thanks
[15:19] <CrownAmbassador> Hi again guys. Does this pass as a bug or a suggestion? https://bugs.launchpad.net/ubuntu/+bug/316780
[16:05] <joumetal> ponimato
[16:06] <joumetal> sorry for noise
[18:18] <BUGabundo1> howdy! can some QA or KDE dev take a look at https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/316837 ? thanks
[19:37] <jarnos> Would it be possible that Launchpad would show upstream changelog of a software?
[19:41] <pedro_> jarnos: better to ask in #launchpad ;-)
[19:41] <jarnos> pedro_: thanks
[19:41] <pedro_> you're welcome
[19:52] <MrKanister> hey. I have a question regarding the UbuntuBugDay. If I change the status of a bug (let's say from "new" to "incomple") do I then have to edit the page of the active UbuntuBugDay and move the bug to the roght section?
[19:52] <MrKanister> *right
[19:53] <thekorn> MrKanister, just mark the row of the bug in lightgreen and add your name
[19:54] <thekorn> don't move bugs from one list to another
[19:54] <MrKanister> thekorn: hm..that easy? Thanks :)
[23:37] <kostmo> Is there an "ubuntu" way to observe debugging events in GTK without recompiling?
[23:38] <RAOF> kostmo: Installing the various -dbgsym packages.
[23:40] <kostmo> what is the difference between a *-dbg package and *-dbgsym ?
[23:41] <kostmo> I am trying to follow the instructions in this bug report: http://bugzilla.gnome.org/show_bug.cgi?id=567312
[23:41] <hggdh> dbgsym are created by us; dbg are usually created by the build process; apport uses dbgsym
[23:41] <RAOF> kostmo: The difference is naming only.
[23:41] <hggdh> either will do the trick if you are gdb-ing
[23:41] <RAOF> (Mostly)
[23:42] <kostmo> is there a way to set a shell variable to make GTK spit out debug messages?
[23:42] <kostmo> (without using gdb)
[23:44]  * hggdh does not know how
[23:47] <kostmo> Are "debugging symbols" different than "printf messages used to assist in debugging"?  If so, then would it be fair to say I would have to recompile to do what the bug report asks?
[23:48] <hggdh> kostmo, yes, debugging symbols and printf messages have nothing to do with each other (although both help on debugging)
[23:48] <hggdh> you only need to recompile (probably) if you want a compile-time option to kick in
[23:49] <hggdh> for debugging sysmbols you need the .dbg or .dbgsym packages
[23:49] <kostmo> OK, I believe the poster in the report is referring to a compile-time option that probably spits out printf's
[23:49] <hggdh> kostmo, what bug #?
[23:49] <kostmo> http://bugzilla.gnome.org/show_bug.cgi?id=567312
[23:50] <hggdh> ugh
[23:51] <hggdh> did you try to run with 'env GDK_DEBUG=events whatchamacallit' ?
[23:51] <kostmo> yeah, didn't work
[23:51] <hggdh> heh
[23:52] <hggdh> this will probably be painful
[23:52] <kostmo> actually, I typed the line before I executed the program
[23:52] <kostmo> I didn't use "env"
[23:52] <hggdh> how?
[23:52] <kostmo> first I typed "GDK_DEBUG=events"
[23:52] <hggdh> nope
[23:52] <hggdh> will do get it done
[23:53] <hggdh> you can either export the environment variable (which might trigger debugging on all GTK applications running) or do it in one single line as I showed
[23:53] <kostmo> ok, this is what I just tried: "env GDK_DEBUG=events ./leave_notify_testcase"
[23:54] <hggdh> yes
[23:54] <kostmo> where "leave_notify_testcase" is the name of my program
[23:54] <hggdh> did it work out OK?
[23:54] <kostmo> ok, didn't seem to do anything
[23:54] <hggdh> sigh... then I am back to 'this will probably be painful'
[23:55] <hggdh> I never built GTK, so I am unsure on what to do, but
[23:55] <hggdh> you will probably need to build it/them yourself with the debugging support the poster is asking
[23:55] <kostmo> I'm thinking I will do "apt-get source libgtk2.0-0"
[23:56] <kostmo> then do the custom build
[23:56] <hggdh> you should start with a 'apt-get build-dep libgtk2.0-0'
[23:57] <hggdh> to get all dependencies in place
[23:57] <kostmo> ok good idea
[23:57] <hggdh> then 'apt-get source libgtk2.0-0'
[23:57] <hggdh> and find out how to set debugging in the build process
[23:58] <hggdh> (it is probably a #define somewhere
[23:58] <hggdh> )
[23:59] <kostmo> i think the ./configure command sometimes displays a list of options
[23:59] <hggdh> ./configure --help
[23:59] <kostmo> thats it