[08:18] <achutha> hi
[08:20] <achutha> is this a chat?
[10:38] <kamstrup> ronoc: senpai! so any gotchas I should know about when porting vala code from dbus-glib to gdbus?
[10:38] <ronoc> kamstrup, i found it very easy, nothing dodgy, let me think
[10:40] <ronoc> kamstrup, i did notice a race condition with regards receiving property update signal against checking the new value of the property on my instance
[10:40] <ronoc> sometimes they value on the instance was stale
[10:40] <ronoc> i got around it with a timeout
[10:42] <kamstrup> ronoc: ok, cool. I don't really use properties, so let's cross fingers for a downhill ride :-)
[10:43] <ronoc> kamstrup, my code is much cleaner using gdbus -> lp:indicator-sound mpris-controller.vala and mpris-interfaces.vala have plenty of example code
[13:05] <ronoc> Cimi_, you never added yourself to the list of contributors on the transport-widget .c and .h
[13:05] <ronoc> fixing now
[14:26] <coz_> good day all
[14:47] <raffaele_> Hi
[14:48] <raffaele_> I have a bug with Unity. It's a segmentation fault
[14:48] <raffaele_> can you help me?
[14:48] <raffaele_> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/686094
[14:51] <coz_> raffaele_,   is this an nvidia card?
[14:51] <raffaele_> yes
[14:51] <raffaele_> a fx 5200
[14:52] <raffaele_> i use the nvidia 173 drivers
[14:53] <coz_> mm  not sure how effective the  fx5200 is going to be with this
[14:53] <coz_> raffaele_,  do you know if it is an agp or  pci  card
[14:53] <raffaele_> agp
[14:53] <raffaele_> 4x
[14:54] <coz_> ok
[14:54] <coz_> raffaele_,  I assume you rebooted after installing the driver ....yes?
[14:54] <raffaele_> yes
[14:56] <raffaele_> I upgraded from maverick
[14:56] <coz_> raffaele_,  ok  one thing you can try  is to reboot  and hold down the "e"  key  or   "shift + e"  to get to the grub menu and the kernel boot stanza
[14:57] <coz_> raffaele_, just before  "quiet splash"   you can type in       nomodeset  and then hit  F10 to reboot with that option
[14:58] <raffaele_> Will I disable the nvidia drivers?
[14:58] <Amaranth> raffaele_: for your backtrace, can you install libnux-0.9-0-dbgsym and get the backtrace again?
[14:59] <raffaele_> ok, wait a moment. I'm installing it
[14:59] <Amaranth> raffaele_: and (though I doubt it will matter) unity-dbgsym if you can
[15:01] <cando_> hi guys ! i'm working on bug #688407  and i need a quick mentoring... :)
[15:02] <cando_> i've already added the quick list...with one entry:EMpty trash..
[15:02] <cando_> the problem is: how to empty trash...^^
[15:02] <cando_> i've already looked to the old unity-private code..
[15:03] <raffaele_> I don't found unity-dbgsym, it isn't in the repo
[15:03] <cando_> but it's in vala...i've also looked to nautilus code...but it's a bit difficult..:)
[15:05] <raffaele_> Amaranth: Ok, I've installed libnux-dbgsym. Now what should I do?
[15:07] <Amaranth> raffaele_: use the directions in the bug report to get a new backtrace
[15:08] <Amaranth> raffaele_: just like you did last time but now it should hopefully give more info there are the top of the stack were it just shows ?? now
[15:09] <raffaele_> ok, I have the backtrace
[15:09] <raffaele_> Do I put it on Launchpad?
[15:14] <raffaele_> Do I put it on Launchpad?
[15:19] <raffaele_> http://launchpadlibrarian.net/61078543/Output2
[15:19] <raffaele_> this is the backtrace, but it looks the same of the file "Output1"
[15:24] <raffaele_> @Amaranth: the new backtrace looks the same in the file "Output1". What should I do?
[15:24] <Amaranth> raffaele_: still getting the ?? at frame 0?
[15:24] <raffaele_> yes
[15:25] <raffaele_> I don't now what does it means
[15:25] <Amaranth> weird, that either means gdb can't find symbol information for a library there or gdb is unable to read the stack correctly
[15:25] <Amaranth> I suppose it could be nvidia's libGL
[15:27] <raffaele_> Ok, so this can be a problem with the Nvidia drivers? Or do I need to install other debug symbols?
[15:28] <Amaranth> well, there is no dbgsym for nvidia and I think they strip debug symbols for "performance reasons"
[15:29] <Sam__> Can ne1 help me
[15:30] <Sam__> how can i help u people
[15:31] <Amaranth> raffaele_: I guess the unity/nux folks will have to see what they call in SubmitStateChanges and see if any of it could cause a crash
[15:31] <Amaranth> raffaele_: Probably a driver thing though :/
[15:31] <Amaranth> Sam__: I don't think anyone from the DX team is actually here
[15:33] <raffaele_> If I install the Nouveau drivers, and unity works, can we say that this is a problem with Nvidia drivers?
[15:34] <Amaranth> raffaele_: Almost certainly
[15:34] <raffaele_> ok
[15:34] <raffaele_> now i try to install nouveau driver
[15:34] <Amaranth> raffaele_: You have to install the experimental package to get nouveau gl
[15:34] <raffaele_> bot the problem will remain
[15:35] <raffaele_> there isn't basic 3d support for fx 5200 in the Nuoveau drivers in the repo?
[15:36] <Amaranth> raffaele_: yeah, you just have to install libgl1-mesa-dri-experimental
[15:36] <raffaele_> ah ok
[15:38] <raffaele_> also libgl1-mesa-dri-experimental-dbg ?
[15:38] <Amaranth> raffaele_: can't hurt, hopefully won't be needed though
[15:39] <Amaranth> raffaele_: If it still crashes with nouveau it would be useful
[15:39] <raffaele_> I hate to remove the Nvidia drivers. xD
[15:40] <Amaranth> eh, you can put them back on easily enough
[15:40] <Amaranth> you can even use jockey-text to do it automatically from command line if you can't get X working
[15:42] <raffaele_> ok
[15:43] <raffaele_> sudo apt-get remove nvidia-173 nvidia-96-modaliases nvidia-current-modaliases nvidia-settings
[15:43] <raffaele_> and
[15:44] <raffaele_> sudo apt-get install libgl1-mesa-dri-experimental libgl1-mesa-dri-experimental-dbg xserver-xorg-video-nouveau xserver-xorg-video-nouveau-dbg
[15:44] <raffaele_> are correct?
[15:45] <raffaele_> I always have trouble removing the proprietary driver! XD
[15:49] <raffaele_> Ok I'm installing nouveau drivers. Now I reboot and next I'll try to start unity
[16:01] <Amaranth> raffaele_: You have to edit or remove xorg.conf too
[16:02] <raffaele_> I'm doing it from safety mode
[16:03] <raffaele_> What is the command to open the Xorg configuration file using gedit?
[16:04] <Amaranth> raffaele_: just do mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup
[16:04] <raffaele_> File not found
[16:04] <raffaele_> °_°
[16:05] <Amaranth> ok, perhaps we've got xorg patched to use the nvidia driver automatically if it is installed
[16:05] <Amaranth> In that case just start X
[16:06] <raffaele_> I'm already using X
[16:06] <raffaele_> I've runned the safe graphic mode
[16:06] <Amaranth> oh, it put you in safe mode?
[16:10] <raffaele_> I was the one to boot into recovery mode, then I used the option failsafeX and then I run in safe graphics mode
[16:12] <raffaele_> Now I'm in the X11 folder
[16:12] <raffaele_> there isn't xorg.conf
[16:12] <raffaele_> °_°
[16:13] <raffaele_> Ok i have a backup, I rename it running nautilus as root
[16:15] <raffaele_> In the driver section should I insert "nouveau" ?
[16:21] <avishekrc> hi
[16:46] <ubuntu_> Hi
[16:46] <ubuntu_> ops
[16:46] <Devil505> hi
[16:47] <raffaele_> ok
[16:47] <raffaele_> Amaranth, i have installed the nouveau drivers.
[16:48] <raffaele_> The result: kernel panick with all my kernels
[16:48] <raffaele_> I am using the ubuntu 10.10 live cd
[16:48] <Amaranth> hrm
[16:49] <Amaranth> kernel panic even when you boot in recovery mode?
[16:49] <raffaele_> yes
[16:49] <raffaele_> my lucky is that i have all my few files on Ubuntu one
[16:49] <raffaele_> xD
[16:49] <Amaranth> weird, how did you even boot the first time?
[16:50] <raffaele_> normally
[16:50] <Amaranth> We run you on nouveau KMS at first boot (and afaik the 10.10 live cd does too) and installing that extra package would only affect things once you get in to X
[16:51] <raffaele_> now i install maverick, I-ll update
[16:51] <coz_> raffaele_,  and all you get is desktop image and cursor ...yes?
[16:51] <Amaranth> you can chroot in to your installed system and remove the package or just edit your xorg.conf to use the vesa driver and edit /etc/modprobe.d/blacklist.conf to blacklist nouveaufb
[16:52] <Amaranth> raffaele_: no need to reinstall for such a thing
[16:52] <raffaele_> ok
[16:52] <raffaele_> ok
[16:53] <raffaele_> say me the commands to do on the live cd
[16:53] <raffaele_> I have the root file system on sda5
[16:53] <Amaranth> raffaele_: just edit /etc/modprobe.d/blacklist.conf and add a 'blacklist nouveaufb' line
[16:54] <Amaranth> raffaele_: then boot in recovery mode and install the nvidia driver again
[16:56] <raffaele_> again? xD
[16:56] <raffaele_> so how we do to fix this bug?
[16:59] <Amaranth> raffaele_: I dunno, the nouveau guys are still pretty much against getting bug reports
[16:59] <Amaranth> If you can get a decent amount of info on the nouveau kernel panic that may be fixable
[16:59] <Amaranth> raffaele_: For unity crashing with nvidia we fall back on "have the unity/nux developers see if something in that last nux function could crash"
[17:00] <Amaranth> If not perhaps running under valgrind will give more info, otherwise it's likely a driver bug and the best solution is to blacklist your card from even trying to run compiz/unity
[17:00] <raffaele_> I now how to run it under valgrind
[17:00] <raffaele_> I had already doed this
[17:01] <raffaele_> but I don't now how save the backtrace
[17:01] <raffaele_> because
[17:01] <raffaele_> the backtrace have A LOT of log lines
[17:01] <Amaranth> raffaele_: yeah, you have to pipe the output to a file
[17:02] <Amaranth> raffaele_: valgrind compiz --replace ccp 2> valgrindlog
[17:02] <coz_> ok be back in about an hour or so
[17:02] <Amaranth> that should do it, iirc
[17:02] <raffaele_> ok
[17:02] <raffaele_> now I reboot and i install the nvidia drivers
[17:02] <raffaele_> bye
[17:03] <raffaele_> quit
[19:30] <raffaele_> @Amaranth: I'm again here. How do I use valgrind to have a backtrace of compiz?
[19:31] <Amaranth> raffaele_: valgrind compiz --replace ccp 2> valgrindlog
[19:31] <Amaranth> raffaele_: I think that should do it
[19:31] <raffaele_> ok
[19:32] <raffaele_> Should I install the debug symbols for compiz, nux, ....?
[19:40] <Amaranth> raffaele_: both, and unity
[19:40] <raffaele_> ok
[19:41] <Amaranth> it's going to be full of junk from the nvidia driver but hopefully something useful will be in there too, just attach it to the bug
[19:44] <raffaele_> ok now i execute valgrind
[19:45] <Amaranth> it's going to be slow and appear to freeze for a long time
[20:05] <raffaele__> ok
[20:05] <raffaele__> I've the output
[20:05] <raffaele__> I've got the output
[20:06] <Amaranth> raffaele__: attach it to the bug and the unity guys should look at it eventually
[20:06] <nmarques> anyone can gimme some pointers... running against some undefined references while building nux, ex: gluErrorString
[20:06] <Amaranth> raffaele__: I'll take a look as well to see if anything obvious jumps out otherwise I think they're on holiday for the rest of the year
[20:07] <raffaele__> http://launchpadlibrarian.net/61089423/valgrindlog
[20:08] <raffaele__> this is the log
[20:08] <raffaele__> 298 errors?
[20:09] <Amaranth> raffaele__: Yeah... wow
[20:09] <raffaele__> The bug squad will have a lot of work
[20:09] <raffaele__> xD
[20:09] <Amaranth> raffaele__: Some of those are likely false positives but that does seem to be a nux bug
[20:11] <raffaele__> Now ?
[20:18] <raffaele__> Now what should be done?
[20:37] <raffaele__> @Amaranth: Now what should be done?
[20:41] <Amaranth> raffaele__: Now we wait
[20:41] <raffaele__> ???
[20:41] <Amaranth> raffaele__: The DX team is not available right now
[20:41] <Amaranth> And even if I could figure out a solution I couldn't get it accepted into unity or nux
[20:42] <raffaele__> DX team is the bug squad?
[20:42] <Amaranth> No, they're the team that works on unity
[20:42] <raffaele__> ah
[20:43] <Amaranth> raffaele__: I've marked it as triaged though
[20:44] <raffaele__> We can also say that it is related to nux
[20:45] <Amaranth> raffaele__: I imagine they'll see that
[20:45] <raffaele__> ok
[20:45] <Amaranth> I dunno if they like having everything under the unity package or split out in to the components
[20:45] <Amaranth> I know for compiz I like having all the bugs filed against the main compiz package
[20:52] <raffaele__> is a segmentation fault system, can we give a greater importance?
[20:52] <raffaele__> It is a segmentation fault system, can we give a greater importance?
[20:53] <raffaele__> It is a segmentation fault, can we give a greater importance?
[20:58] <raffaele__> @Amaranth: Ok, thank you for helping me with this bug. Now I wait for the DX team.
[20:58] <Amaranth> raffaele__: Sorry, I don't want to touch the importance
[20:59] <Amaranth> Well, actually, I could bump it to medium, that's the default for crashes
[20:59] <raffaele__> ok
[20:59] <raffaele__> thank you again. ;)
[21:04] <lamalex> Amaranth, we usually link againt unity and the component
[21:37] <RAOF> nmarques: I didn't see anyone else answer your question; if you're still waiting - that looks like a failure to link against libGLU, which would be a build system bug.
[21:47] <nmarques> RAOF, another question, Iv'e noticed nux on natty requires a git version of mesa... would this trigger such behavior ?
[21:48] <RAOF> nmarques: No.  Does nux actually require a git version of mesa?
[21:48] <lamalex> nux requires whatever mesa is in natty
[21:49] <RAOF> Which is (now) 7.9, but was 7.9 minus a couple of commits.
[21:56] <nmarques> RAOF, I'll take a look deeper into this. Btw it's being built on openSUSE since I'm trying to package Unity for it
[21:58] <RAOF> Ok.  Unity shouldn't require any particular version of mesa (but newer is likely to be better ☺).  For nux I suspect you're being hit by transitive linking problems; nux doesn't itself link to libGLU, but it links to libglew which links to libGLU.
[21:59] <nmarques> RAOF, Mesa is 7.9 upstream as well from my side
[21:59] <RAOF> It's the obvious version to have at this point, yeah.
[22:01] <nmarques> RAOF, ;)
[22:02] <nmarques> RAOF, that's a direction... I'm going to check deeper the glew and glewmx packages
[22:38] <htorque> lamalex: hi, you marked bug 693550 as dupe, but the other bug's status is "fix released" - should this be reopened then?
[22:40] <nmarques> RAOF: Makefile hack for -lGLU kinda fixed it... there's no need to submit this kind of irrelevant patch, right ?
[22:41] <RAOF> nmarques: Depends on whether it's correct or not :).  I'm reasonably sure nux doesn't use glu symbols itself, but if it does then that's a real buildsystem bug.
[22:42] <lamalex> htorque, I'm not sure yet, It still looks fixed to me- I think something is possibly out of date on the reporters machine
[22:42] <nmarques> RAOF, it's for examples and gputests... I choosed not to disable them :)
[22:42] <nmarques> RAOF, the rest works fine mate :)
[22:43] <RAOF> nmarques: Could you check if they use glu symbols directly, and file a bug if they do?
[22:43] <htorque> lamalex, what could be out of date - i'm the reporter :)
[22:43] <lamalex> ha oh
[22:43] <nmarques> RAOF, I'll take a look, there's a couple of things I need to polish here first... so far everything is a bit ugly on my side
[22:43] <lamalex> htorque, unity, nux, gnome-screensaver?