[00:19] bryceh, RAOF: I have a small patch for oneiric's x server: http://paste.ubuntu.com/712635 [00:19] it's an obvious fix for a code path that I must have missed testing [00:19] but it is hit everytime a touchpad gesture is accepted by our new gesture recognizer [00:20] Causing a memory leak? [00:20] what's the best way to get this into oneiric, since precise won't have these patches [00:20] RAOF, no, dereferencing a NULL ptr [00:20] it's not obvious from the patch [00:20] Fair enough. [00:21] but the if statement is literally "if (first)" [00:21] the if statement that you can't quite see at the top of the patch [00:21] Nothing in oneiric actually hits this, right? At least, *my* touchpad gestures don't seem to crash the server :) [00:22] no, you'll only hit it if you are using touch grabs on trackpads [00:22] which I am doing with my new gesture recognizer [00:22] But it's still SRUable even if it doesn't apply to precise. [00:22] yeah [00:22] so that's my question [00:22] should I just leave precise as is? [00:22] create a new git branch for oneiric [00:23] and then upload following the sru procedure? [00:23] because precise hasn't actually deviated from oneiric yet, has it? [00:23] so I *could* upload it to precise too [00:24] Precise hasn't deviated just yet, no. [00:25] I've got an ubuntu+1 branch already which will become ubuntu once it's ready. Until then, feel free to push to ubuntu and from there to oneiric-proposed. [00:26] RAOF, so I should skip precise? [00:27] We can copy the upload from oneiric-proposed into oneiric-updates & precise (if we haven't already uploded a new server to precise, in which case we don't need to anyway ?) [00:27] In short: yeah, skip precise. [00:27] ok [00:37] RAOF, bryceh: I'm going to upload to oneiric-proposed [00:38] heads up, just in case you were working on an sru too [00:39] alright [01:12] RAOF, are you able to release a package into -updates? [01:12] I am, yes. [01:12] there's an sru that has passed verification (though hasn't been tagged), and it's been a week [01:12] I was wondering if you could take a look [01:12] Why hasn't it been tagged? [01:13] not sure [01:13] Unless it's tagged it doesn't show up as green on the SRU page. [01:13] who is supposed to tag it? [01:13] bug 827958 [01:13] Launchpad bug 827958 in libgrip (Ubuntu Precise) (and 3 other projects) "eog crashed with SIGSEGV in gdk_x11_window_get_xid() (affects: 36) (dups: 6) (heat: 160)" [Undecided,Triaged] https://launchpad.net/bugs/827958 [01:13] Anyone can tag it; the person who's done the verification is fine. [01:14] oh, in the past someone always came by and tagged it for me [01:14] they read the comments, and then tagged it as appropriate [01:14] oh oh there are people [01:14] can someone help me with how to respond to http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2011-October/006721.html ? when you're done with that bug [01:15] RAOF, I may see the issue [01:15] I'm moving bugs to fix committed [01:15] instead of leaving them as in progress [01:16] RAOF, wiki.ubuntu.com/SRU says the SRU team will set the verification tags as appropriate [01:16] Fix committed is the right status for "uploaded to -proposed". [01:16] ok [01:16] nm then [01:17] Yeah. We do set those tags. [01:17] hmmm, who sets the verification-needed tag? [01:17] The person who accepts it into -proposed. [01:17] there seems to be a whole in the process, according to the wiki page [01:18] oh, I'm getting ahead of myself [01:18] the bug has verification-needed [01:18] I think one reason that bug hasn't been tagged as verified is that it's not immediately obvious that it did succeed. [01:18] that's one thing I worried about [01:19] So people browsing through their SRU mail won't necessarily go "ok, time to set verification-succeeded" [01:19] ahh [01:19] RAOF, does this bug look ok to you for being verified? [01:19] And it's perfectly reasonable to raise these to ubuntu-sru members. [01:19] It does, yes. [01:19] ok [01:20] it's only been 8 days, so just one day past the waiting period [01:20] so I didn't want to grab someone too fast [01:20] I just happened to notice that you are an sru member :) [01:23] Marked as verification-done; once I've got through the pending-sru queue I'll run through the srus that are verified. [01:25] RAOF, ta! [01:26] maco, if you need info on the nvidia binary driver, tseliot would be the one to ask [01:26] cnd: as far as i can tell, he's NEVER on irc [01:27] maco, he's in italy [01:27] maybe your timezones aren't overlapping [01:27] you could also email him at alberto.milone@ubuntu.com [01:27] i'm in the eastern us. we should overlap at least for the morning [01:27] yeah, I know he's on in the morning [01:28] i'll look again tomorrow then [01:28] I can try to ping him tomorrow morning as well [01:28] but I'm on the west coast, so I may not catch him either :) [01:29] maco, he'll be in orlando next week too [01:29] so you should be able to catch him on irc during the day then as well [01:29] oops, nm, looked at the wrong alberto [01:30] he'll be at uds in a week and a half [01:30] maco: nvidia-settings is open-source, though. I've not checked the source, but the fallback-to-compile-time-variable sounds like it would work. [01:31] yeah i missed that bit of the code when i was going "see if it makes a call to pkg-config...oh hey look it does, ok i guess that bug reporter is right" [06:14] * RAOF is surprised by "do_butmap_changed" [08:41] hey! [08:41] is there any main bug where you guys are tracking the issue with jockey and hybrid gpu systems? [08:42] (where jockey will show drivers, but will be unable to load them) [08:47] ara: maybe filed against jockey, dunno [08:47] tseliot1, ^ any ideas? [08:51] ara: no, sorry, I've never seen that bug report [08:53] OK, thanks, then I will suppose that the master bug is https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/660443 [08:53] Launchpad bug 660443 in jockey (Ubuntu) "Recommended drivers don't work with Nvidia Optimus (affects: 3) (dups: 1) (heat: 20)" [Undecided,Confirmed] [08:53] although it is strange to not see more activity on it [09:11] ara: yes, that one should work as the master bug [10:44] Hi, my keyboard and mouse are forzen at log in (11.04 64), I edited xorg.conf adding AutoAddDevices false, and only the mouse came back. I reinstalled xserver-xorg and fglxr with no success. Any suggestion? thx [10:50] "frozen" means you have no mouse/kbd [10:50] if you add that option you're on your own [10:52] yes, they are dead at log in. but I can switch to terminal with alt F1, after pressing alt-sysrq-r. I tried to restore a backup'd copy of xorg.conf, too. But it didn't work [10:54] file a bug without the AutoAddDevices-nonsense [10:57] ok, I'll do it. With that line in xorg.conf I'm able to use the mouse, though. With the original conf, or with a new one generated with X -configure, mouse doesn't work, unless I edit the config [10:59] what if you start it without xorg.conf? [11:01] they're still dead [11:02] install pastebinit, and run 'pastebinit /var/log/Xorg.0.log' [11:02] post the link here [11:05] ok, I'll need to reboot to do that, because I'm using an other OS right now. I'll come back as soon as I have done it. [11:35] Hi, here's my log as requested before. http://paste.ubuntu.com/713097 [11:36] tocia: nope, you have the xorg.conf in place [11:42] I suspect it could be a layout issue, since HAL is working, xorg is working and it's not the hardware. But I still can't understand why the mouse is dead until I add the option AutoAddevices "False". Well, I'll need to look for something else, or just do a clean install and see if it works [11:42] HAL isn't used [11:42] udev is [11:42] why can't you just move the xorg.conf aside and redo what I asked [11:44] I did boot without xorg.conf, mouse and keyboard are still dead, but in this case when I switch to a terminal with alt F1 my screen freezes [11:44] for starters, purge fglrx [11:45] done, nothing changed, I purged xserver-xorg, too [11:45] uh [11:45] no need to do that [11:46] it was a suggestion, I tried lot of things this two days [11:46] suggestion by whom? [11:47] anyway, unless you've rebooted and removed the xorg.conf, you still have the fgrlx module loaded etc [11:48] It was a suggestion in the ubuntu chat, I don't remember who said that to me. I did reboot when I rm the xorg.conf [11:49] so did you purge the 'fglrx' package before reboot? [11:51] yes [11:52] what does 'apt-cache policy xserver-xorg-input-evdev' tell [11:55] I need to reboot to do anything on ubuntu, with no keyboard on the GUI, I have to browse the internet on win7. [11:56] you don't need to browse internet.. [11:56] and to chat here, too [11:56] i suspect you don't have -evdev installed [11:57] reinstall xserver-xorg and see if it installs the missing drivers [11:59] I already did a reinstall of that package after I purged it. But I can do it again. along with fglrx [12:01] Anyway, Is that right to purge fglrx? sudo apt-get remove --purge xorg-driver-fglrx fglrx* [12:34] I purged fglrx, reboot, reinstalled xserver-org, reboot, same as before. apt-cache policy xserver-xorg-input-evdev says: Installed 1:2.6.0-1ubuntu12/ Candidate 1:2.6.0-1ubuntu12/ Version Table:/ *** 1:2.6.0-1ubuntu12 0/500 http://ch.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages/ 100 /var/lib/dpkg/status [12:35] ok, so pastebinit Xorg.0.log [12:36] it worked with 11.04 at some point? [12:40] It worked since last weeks, I upgraded to 11.10, I had some problems and I reinstalled 11.04, it worked for a couple of days until I had this problem. When I was installing some package with Synaptic suddenly mouse and keyboard frozen, I rebooted and they were still dead [12:42] ok [12:42] i'd rather fix the issues with 11.10 though [12:47] I had black screen and fglrx problems after the second reboot of the installation, I wasn't able to resolve them, so I reinstalled 11.04. I'll come back with the log in 5 [12:57] http://paste.ubuntu.com/713160 [13:01] tocia: and again, you have the xorg.conf there.. [13:01] tocia: pastebinit /etc/X11/xorg.conf [13:03] mmh, I lookd for the xorg.conf after the reinstall of xserver-xorg and I didn't find it, now I see it's been used, too [13:05] that's the old one I used before the issues http://paste.ubuntu.com/713172/ [13:05] now I reboot and look if there's a new one [13:06] doesn't the default ati driver work, or why do you use fglrx? [13:08] yes, they work, but I'm using the fglrx since very long without any problem [13:09] I'll try to switch back to ati drivers and see if something changes [13:10] but had issues in 11.10. [13:11] i'd say install that and use the default driver.. [13:13] So I have been suffering from an odd corruption for a while [13:13] http://people.canonical.com/~jj/screeshot.png [13:13] Ok, I'll give a shot at that. [13:13] jjohansen: xterm? [13:14] oh [13:14] tjaalton: no not just xterm, all windows [13:14] not just the term [13:14] goes away when the window get refreshed [13:14] which hw/driver? [13:18] tjaalton: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c) (prog-if 00 [VGA controller]) [13:18] Kernel modules: intelfb, i915 [13:18] tseliot1: hello? [13:18] sorry, was doing lspci in a terminal on the wrong machine at firts :) [13:19] maco: hi [13:19] tseliot1: i need help replying to debian nvidia people [13:19] tseliot1: can you look at http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2011-October/006721.html ? [13:20] jjohansen: this with oneiric? [13:20] tjaalton: yes and natty [13:20] tjaalton: actually I can't say most recent natty, I upgraded the machine early in the cycle [13:21] my x61 seems to work fine [13:22] hrmmm, I was afraid of that. Possibly a hardware issue on my end [13:22] is this with dualscreen or some other special case? [13:23] nope, regular laptop, shows up after a day or two uptime, no suspend needed [13:23] even [13:23] ah, ok [13:23] tbh i don't use the machine much anymore [13:24] tseliot1: this was related to bug 721453 [13:24] Launchpad bug 721453 in nvidia-settings (Ubuntu Oneiric) (and 1 other project) "nvidia-settings should depend on pkg-config and python-gtk (affects: 3) (dups: 2) (heat: 26)" [Undecided,Fix committed] https://launchpad.net/bugs/721453 [13:25] maco: yes, sorry, I'm multitasking (poorly). I'll have a look at it [13:25] thanks [13:25] tjaalton: well it is getting a little long in the tooth, but I haven't found a machine to replace it with yet. It has a nice 12.1" 1400x1050 ips display and they don't see to do anything close anymore [13:26] maco: oh, so the fix is already in [13:26] tseliot1: in ubuntu, yes, i was suggesting it to debian as well and then the usefulness of adding pkg-config came up and i dont really know [13:27] i know its on my system and nvidia-settings works for me! [13:27] maco: do they use my code to make use of policykit (through pygtk2) in Debian? [13:28] i dont know. is that whats breaking it here? ubuntu-specific patchiness? [13:31] maco: I'm wondering why the package would need pkg-config at runtime [13:33] maco: screen-resolution-extra is what the nvidia-settings panel uses (thanks to an Ubuntu patch) to allow users to write xorg.conf through policykit (i.e. without having to run the whole app as root) [13:34] tseliot1: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/nvidia-settings/precise/view/head:/src/XF86Config-parser/Generate.c i was looking at line 217 when i went "hey yep that sure looks like it uses pkg-config" [13:35] what i missed was line 248 [13:36] maco: now, that's new to me. Forget what I said about policykit, it their code that's using pkg-config at runtime. === kinoucho` is now known as kinouchou [14:00] maco: do you need anything else from me to help you reply that email? [14:19] tseliot1: is it that netiher is required in debian? [14:21] maco: I believe that pkg-config is needed in debian (since the Nvidia code calls it) but pygtk2 is not (as we use it only in Ubuntu). Good catch BTW [14:22] tseliot1: debian people said that with the fallback they dont think pkg-config is necessary either [14:26] maco: if the problem doesn't affect debian users, then I guess they're right. This would mean that, somehow, the fallback is broken in ubuntu. I don't think our move to multi-arch could have caused this. Did you see what find_libdir() returns when using the fallback? [14:29] no. im leaving a message on the bug asking the original reporter how he determined pkg-config was needed [14:31] hey guys [14:31] i got a problem with my touchpad [14:34] maco: it sounds like a good idea ;) === soreau_ is now known as soreau [21:32] heh, ironically just had the most annoying tech support call ever, with my mother, setting up dual head [21:34] bryceh: hehe :) [21:38] she wanted the displays mirrored but at their own native resolutions [21:38] secondary problem - seems to be no way in gui to set which monitor is primary, so with it !cloned everything was on the wrong monitor [21:40] bryceh: remind me to buy your mother any hardware I need fixed :) [21:40] heh [21:41] it's funny to realize the dorky minuscule things that roadblock non-technical users [21:42] like, dragging the panel toolbars from screen to screen is hard because there's no visual clue that things are "dragging" [21:42] or in the monitor gui that you have to click on the laptop box to set the laptop settings. _quite_ perplexing to mom [21:43] yeah, doing tech support for non-technical users is a real eye opener for details like that [21:44] my mother in law used to click column titles in evolution to sort her mail by date or subject, and if she moved the mouse by a couple of pixels while clicking, evolution thought you were trying to drag away the column to delete it. [21:46] yeah my dad has shaky hands and so certain seemingly simple tasks can be kind of challenging for him [21:46] and touchpads are right out [21:49] bryceh: now fix my bugs, or I'll send you mom a poulsbo [21:49] :) [21:50] heh