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