[00:57] <hihihi100> hi
[00:57] <hihihi100> GEM leak bug
[00:57] <hihihi100> who can help me?
[00:58] <hihihi100> 1.4 GLX version
[01:00] <yofel_> hihihi100: what does glxinfo | grep "GLX\ version"    give you?
[01:01] <hihihi100> 1.4 i believe, but let me do it again
[01:01] <yofel> if you have an up-to-date stable release you shouldn't get 1.4
[01:01] <hihihi100> yup, 1.4
[01:01] <hihihi100> so what do I have to do to downgrade to 1.2?
[01:02] <yofel> hihihi100: actually... what graphics driver?
[01:02] <hihihi100> NVIDIA GeForce G 105M, Card type: PCI-E 8x, 512 MB, 169 MHz
[01:02] <hihihi100> drivers.. 195 I believe
[01:02] <yofel> driver... not card
[01:02] <hihihi100> k, srry
[01:03] <yofel> ok, glx 1.4 then
[01:03] <yofel> and nvidia doesn't use gem, so you're not affected by the bug
[01:03] <hihihi100> 195.36.24
[01:03] <yofel> if you have a memory leak then that's a different bug
[01:03] <hihihi100> crap
[01:03] <hihihi100> nvidia doesnt use gem... ill keep that in mind
[01:03] <yofel> sec
[01:05] <yofel> hihihi100: see here for nvidia issues: http://www.nvnews.net/vbulletin/forumdisplay.php?f=14
[01:07] <hihihi100> one question, since u seem to know about this: the first lines of https://wiki.ubuntu.com/X/Testing/GEMLeak read: Intel will always be affected since DRI2 is used with and without KMS, ATI uses DRI1 without KMS.
[01:07] <hihihi100> my laptop has an Intel centrino inside..
[01:07] <hihihi100> how does that affect me?
[01:07] <yofel> intel as in.. intel graphics card, the cpu is completely unrelated here
[01:08] <hihihi100> k, I didnt know I could be this dumb..
[01:08] <hihihi100> thx
[01:08] <yofel> np
[01:09] <hihihi100> thax for the lin, ill give it a try
[01:09] <hihihi100> link
[01:13] <hihihi100> can u also help me with an IBUS problem I have?
[01:14] <yofel> this channel really is for handling bug reports, support is in #ubuntu (or #kubuntu, etc.)
[01:14] <hihihi100> In the combo box, I can see the installed languages, and change the inupt method, but there is no way I can see the icons that are supossed to be on the left
[01:14] <hihihi100> k, im a noob
[01:15] <yofel> and I don't know anything about ibus anyway, so ask there please
[02:51] <zus> ddecator, hey there
[07:45] <kermiac> bdmurray, ogasawara or jcastro I got an email today saying that my bugcontrol membership will expire in 7 days. Can one of you please renew it?  https://edge.launchpad.net/~kermiac
[08:11] <enrry> hi all
[08:11] <enrry> anybody there?
[08:15] <enrry> I experience a systematic crash in lucid installation, probably related to keyboard. Where can I post information or get help? Thank you
[08:54] <BUGabundo_remote> no Pony just Tuna. morning!
[09:09] <BUGabundo_remote> this must be one of the funniest bugs I've ever reported https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/581608
[09:10] <ubot4> Launchpad bug 581608 in indicator-applet (Ubuntu) "two clock applets with diff minutes (affects: 1)" [Undecided,New]
[09:10] <enrry> hi guys
[09:10] <BUGabundo_remote> hey enrry
[09:12] <enrry> I experience a systematic crash in lucid installation, probably related to keyboard. Where can I post information or get help? Thank you
[09:12] <enrry> I can't workaround that
[09:13] <BUGabundo_remote> enrry: bugs are filled at launchpad
[09:13] <BUGabundo_remote> !bugs > enrry
[09:13] <ubot4> enrry, please see my private message
[09:15] <enrry> I can't track that because in that case it is impossible to run bug reporting tool
[09:20] <BUGabundo_remote> even from a recovery console?
[09:20] <BUGabundo_remote> or alternate installer
[09:20] <enrry> the system crashes during installation
[09:21] <enrry> you have to shut down manually
[09:21] <enrry> :)
[09:21] <BUGabundo_remote>  alternate installer?
[09:23] <enrry> I could try, but with older versions I had no problems
[09:23] <enrry> keyboard freezes as you press a key
[09:23] <enrry> only with lucid
[09:26] <BUGabundo_remote> beats me
[09:26] <BUGabundo_remote> not an expert on that
[09:26] <BUGabundo_remote> what GPU?
[09:27] <seb128> BUGabundo_remote, the bug you opened is not a bug and on the wrong component
[09:27] <seb128> BUGabundo_remote, you might want open the "1 minute off" for the buggy clock
[09:29] <enrry> GPU?
[09:31] <BUGabundo_remote> seb128: there's one already?
[09:31] <BUGabundo_remote> enrry: graphics card
[09:32] <enrry> ATI, it has already given problems with last 2 or 3 versions
[09:32] <seb128> BUGabundo_remote, I don't know, I don't know of anybody crackful enough to run maverick yet ;-)
[09:33] <seb128> BUGabundo_remote, the double clock is probably because you installed unity and the indicator clock
[09:33] <BUGabundo_remote> there are a bunch of us in +1 :D
[09:33] <seb128> BUGabundo_remote, and still kept the GNOME applet in your config
[09:33] <BUGabundo_remote> seb128: ohhh right
[09:33] <BUGabundo_remote> makes sense
[09:33] <seb128> it's an user config error
[09:33] <BUGabundo_remote> but the diff time is what worries me the most
[09:33] <seb128> well look at which one is wrong and open a bug against it
[09:33] <BUGabundo_remote> its a clock....
[09:34] <BUGabundo_remote> I have no idea which one is correct
[09:34]  * BUGabundo_remote goes running ntp
[09:34] <seb128> well the GNOME one has the calendar
[09:34] <seb128> ?
[09:34] <seb128> you don't have a watch?
[09:34] <seb128> or you don't know how to look at the time on your computer our of the applet?
[09:35] <BUGabundo_remote> seb128: the prob is not me looking at a clock
[09:35] <BUGabundo_remote> the bug here is having two applets showing the same thing at diff times
[09:35] <seb128> open a command line, look the time there, compare to clock and bug the one which is wrong
[09:36] <seb128> it's only a display issue in one of those, I would guess the indicator one
[09:36] <seb128> since it's not likely that the one we use by default for several cycle is buggy, we would have notice
[09:36] <BUGabundo_remote> $ date
[09:36] <BUGabundo_remote> Mon May 17 09:36:33 WEST 2010
[09:36] <BUGabundo_remote> according to date, the 'old' clock is correct
[09:37] <BUGabundo_remote> and the unity one is not
[09:37] <seb128> ok, so open a bug against that indicator
[09:37] <seb128> we should stop people to file bugs against indicator-applet too
[09:37] <seb128> that's only a container for actual indicator-*
[09:38] <BUGabundo_remote> !info indicator-datetime
[09:38] <ubot4> BUGabundo_remote: Package indicator-datetime does not exist in lucid
[09:38] <BUGabundo_remote> humm ok found the unity ppa package
[09:38] <BUGabundo_remote> reasingning
[09:39] <seb128> bah
[09:39] <seb128> close the ubuntu task, that's not even an ubuntu component
[09:40] <BUGabundo_remote> ok
[09:40] <BUGabundo_remote> its not 'yet'
[09:40] <BUGabundo_remote> man changing projects is hard
[09:42] <seb128> BUGabundo_remote, it will probably not be in the current version either
[09:43] <BUGabundo_remote> seb128: can you check https://bugs.edge.launchpad.net/ubuntu/+source/indicator-applet/+bug/581608
[09:43] <ubot4> Launchpad bug 581608 in indicator-applet (Ubuntu) (and 2 other projects) "two clock applets with diff minutes (affects: 1) (heat: 6)" [Low,Invalid]
[09:43] <BUGabundo_remote> ohhh didie triaged it
[09:44] <BUGabundo_remote> bad LP for not auto refreshing the page while changign projects :P
[09:46] <bbordwell> I believe this bug is ready to be marked as triaged, could a member of BC please do so? https://bugs.launchpad.net/ubuntu/+source/pidgin-libnotify/+bug/574933
[09:46] <ubot4> Launchpad bug 574933 in pidgin-libnotify (Ubuntu) (and 2 other projects) "Tapping on the libnotify box several times causes a segmentation fault (affects: 2) (heat: 12)" [Undecided,Confirmed]
[10:39] <enrry> hi all!
[10:39] <enrry> goodbye all!
[13:31] <arand> I think I've found the fix for Bug #519541 should it be pushed to Maverick first? Or is that unecessary if Maverick is going to have 2.8.4 anyways?
[13:31] <ubot4> Launchpad bug 519541 in abiword (Ubuntu Lucid) (and 3 other projects) "Abiword 2.8.1 freezes with document lost when help is clicked or F1 is pressed (affects: 8) (dups: 1) (heat: 68)" [Critical,In progress] https://launchpad.net/bugs/519541
[13:36] <micahg> arand: if the fix hasn't landed in maverick yet, it should be pushed there first
[13:37] <micahg> arand: has it already landed upstream?
[13:37] <arand> micahg: Yea, I cherrypicked from svn
[13:38] <micahg> arand: k, so you should make a DEP-3 patch for it  and then a debdiff for maverick and lucid-proposed.  you'll also need to add the test case if it's not there per the SRU process
[13:39] <arand> micahg: DEP-3?
[13:39] <micahg> arand: it described the headers in the patch
[13:39] <micahg> !dep-3
[13:39] <ubot4> Factoid 'dep-3' not found
[13:40] <micahg> arand: http://dep.debian.net/deps/dep3/
[13:41] <micahg> arand: there's a sample for cherry-picked from upstream
[13:41] <arand> micahg: Ok, I'll check it out, cheers.
[14:31] <zaran_> Hi, I have a question
[14:31] <arand> Would this be a good DEP-3 http://pastebin.com/Ackvde3u (For https://launchpad.net/bugs/519541)
[14:31] <ubot4> Launchpad bug 519541 in abiword (Fedora) (and 4 other projects) "Abiword 2.8.1 freezes with document lost when help is clicked or F1 is pressed (affects: 8) (dups: 1) (heat: 68)" [Unknown,Unknown]
[14:33] <zaran_> I'm working on a bug that seems to have come up after an update to Lucid; the user had some packages (Eclipse) installed in a non-standard way and now it is causing openjdk to crash.  I cannot recreate the bug despite getting more information from the reporter.  What's the next step?
[14:40] <ogasawara> kermiac: I've extended your bugcontrol membership for another year.  Thanks for the help!
[14:41] <kermiac> thanks ogasawara :)
[14:56] <micahg> arand: you need to put where the patch came from
[14:58] <arand> micahg: Done: http://launchpadlibrarian.net/48605446/abiword-libxml2-xmlCleanupParser-is-harmful.patch  (Although, according to the page you linked, it is optional is Author is defined)
[14:58] <micahg> arand: author is, but I don't think origin is
[14:59] <arand> "Origin (required except if Author is present)"
[14:59] <micahg> arand: looks good to me, is that the same patch that was applied upstream
[15:01] <micahg> arand: as I understand it, origin can be omitted if one is the original author
[15:02] <arand> micahg: Well, I copied it from the bugzilla source, the only diff is that the SVN specifies deifferent commits.
[15:04] <micahg> arand: what do you mean?
[15:08] <arand> micahg: just that in "--- src/af/util/xp/ut_xml_libxml2.cpp   (revision 28764)" the (revision *) fields are different between the bugzilla original, and the svn extract, I assume that doesn't matter at all though.
[15:09] <micahg> arand: I think that's fine if that's the only difference
[15:09] <micahg> arand: actually, #ubuntu-motu is probably a better place to ask about SRUs and patches
[15:10] <micahg> arand: I'll be back in a few minutes if you need anything els
[15:10] <micahg> e
[15:10] <arand> micahg: Okay, cheers for the help :)
[16:57] <nigelb> ddecator: hey, ping
[16:58] <ddecator> nigelb: pong
[16:58] <nigelb> I'm looking for folks interested in writing apport hooks
[16:58] <nigelb> are you interested?
[16:58]  * BUGabundo_remote seats back and watchs the pingpong game
[16:58] <ddecator> i've never done it. how hard is it to write one?
[16:58] <nigelb> I can give you all the docs + live help when you get stuck
[16:58] <nigelb> its easy, its python
[16:59]  * nigelb didn't know either when he started
[16:59] <ddecator> sure. i'm still just starting out with python, but if there are docs and live help then it'd be a good learning experience :)
[16:59] <nigelb> I'd like to expand the list of folks who know how to write apport hooks :)
[17:00] <ddecator> sounds good to me. it'll be a good skill to have
[17:00] <ddecator> nigelb: btw, i still plan to help with patch review, but it realistically won't happen until after i'm out of school (in about a month)
[17:05] <nigelb> ddecator: no problem, take your time :)
[17:05] <nigelb> ddecator: you can start off with nautilius, open a bug, set importance wishlist and say 'apport hook for nautilius'
[17:05]  * nigelb needs to write a wiki about how to go about it
[17:07] <ddecator> nigelb: do you have a link for the docs?
[17:07] <nigelb> ddecator: hold on, its a bundle ;)
[17:08] <nigelb> https://wiki.ubuntu.com/Apport/DeveloperHowTo#Package%20Hooks
[17:09] <nigelb> https://wiki.ubuntu.com/MeetingLogs/devweek0909/ApportPkgHooks
[17:10] <zus> hello everyone
[17:10] <zus> ddecator, you around?
[17:10] <ddecator> zus: atm yes
[17:10] <ddecator> nigelb: just those 2?
[17:17] <nigelb> ddecator: hold on, my power situation isn't really stable
[17:20] <ddecator> nigelb: np, just want to make sure i bookmark all of them :)
[17:20] <nigelb> oh, grr, can't find it
[17:20] <nigelb> the best doc is already in your ststem
[17:21] <nigelb> ddecator: run 'pydoc apport.hookutils' on terminal, should give you best docs ;)
[17:21] <nigelb> im pretty sure your running on caffeine right now, if you want we can talk a bit earlier tomorrow on how to get started :)
[17:22] <ddecator> nigelb: thanks. it's morning for me, but i'm busy the next two days with stuff for school, so maybe later this week?
[17:23] <nigelb> sure :)
[17:23] <nigelb> you've uploaded a fix to any bug yet?
[17:23] <nigelb> if not, you can get started with this one ;)
[17:24] <ddecator> can't say i have at this point
[17:24] <nigelb> ddecator: well, then this will be you first bug fix.  I'll open a bug for nautilius and assign to you
[17:25] <ddecator> haha, i was going to do that after reading the docs, but sure, go ahead
[17:28] <nigelb> ddecator: you're in luck, there is already a hook, you just need to add stuff
[17:29] <ddecator> i'm guessing that's easier? haha
[17:29] <nigelb> yep, only one line of code to add
[17:30] <nigelb> if there is some sort of sensitive stuff in that, its lots of lines of code though :D
[17:30] <nigelb> you'll have to scrubb data
[17:30] <nigelb> ooh, I like this new warning
[17:30] <nigelb> Draycen DeCator (ddecator: 3255) [bugsquad] [ubuntu-bugcontrol]  did not previously have any assigned bugs in Ubuntu.
[17:30] <nigelb> If this bug was assigned by mistake, you may change the assignment.
[17:30] <nigelb> very shiny new feature of LP I suppose :)
[17:31] <nigelb> ddecator: bug 581812
[17:31] <ddecator> heh, well that makes me look like a noob :p
[17:31] <ddecator> nigelb: thanks
[17:31] <nigelb> ddecator: yeah, we'll change that soon enough
[17:31]  * nigelb look for next target, kermiac 
[17:31] <nigelb> *looks
[17:32] <ddecator> not sure he's around right now, haha
[17:32] <ddecator> we'll drag him into it
[17:32] <nigelb> he's probably asleep, but tomorrow morning :D
[17:32] <nigelb> yes, he needs a bit of dragging ;)
[17:33] <nigelb> ddecator: I'll write up how I write hooks so you can sue the same process, a little bit of play with symbolic links ;)
[17:33] <nigelb> s/sue/use gasp!
[17:33] <ddecator> nigelb: haha, thanks, i'd appreciate it. i'll start reading the docs tonight
[17:34] <nigelb> awesome, thanks for helping out ;)
[17:34] <ddecator> no problem :)
[18:14] <A-R-R> What does 'heat' pertain to for a bug?
[18:15] <arand> http://blog.launchpad.net/bug-tracking/bug-heat
[19:52] <A-R-R> I read about bug triaging and am practicing on some bugs before I apply for membership in the Bug Squad. When do I subscribe the Ubuntu-desktop-bugs team? or am I allowed to?
[20:48] <duncan> New issue: I've lost the 'me menu', anyone know of a bug report I should look at?
[20:50] <qense> duncan: Lost as in gone from the panel?
[20:51] <qense> duncan: Can't you add the applet back to the panel?
[20:51] <duncan> I can't find it in the 'add' menu. what's it called?
[20:52] <qense> duncan: Indicator applet session
[20:52] <Cajun_Lan_Man> Hello all.  I've got a quick question, if someone could guide me in the right direction. I'm getting more and more interested in Ubuntu, and using it for more things all the time. I just noticed the "bug squad" and I'm thinking it would be enjoyable to help out, as well as learn more about Ubuntu in the process.  I'm no programmer, but I am a Network Admin (windows based, of course) so I wouldn't be looking at these bugs from a completely new perspe
[20:52] <duncan> Thanks, how is anyone supposed to know that's what it's called?
[20:53] <jjesse> Cajun_Lan_Man have you looked at the bugsquad wiki page or the bugsquad documentaiton on helping w/ bugs?
[20:53] <jjesse> the links are in the topic of the channel
[20:53] <jjesse> btw i come from a windows admin background as well
[20:53] <duncan> Cajun_Lan_Man, you could just start by finding bugs with the status 'new' and seeing if you can reproduce them.
[20:54] <Cajun_Lan_Man> jjesse: I have.  I was just wanting to get an actual persons perspective first.
[20:54] <Cajun_Lan_Man> duncan: That is exactly where I was thinking about starting off.
[20:54] <jjesse> Cajun_Lan_Man: thanks for helping out :)
[20:54] <Cajun_Lan_Man> I've already got a launch pad login, as I try to submit a hardware test report on each new computer I run Ubuntu on.  (Trying to help where I can)
[20:55] <jjesse> nice
[20:55] <qense> duncan: Because the session applet thing is part of the MeMenu. :)
[20:55] <qense> And you should just know it, of course.
[20:55] <jonathank89> I've found this weird bug and I'd like to report it or found out if it's already been reported...could someone give me a hand?
[20:55] <duncan> Cajun_Lan_Man, great, I've heard a few times that the biggest issue is finding the real bugs and closing the non-bugs.
[20:56] <duncan> jonathank89, what's the issue?
[20:56] <jonathank89> It's better described in a screenshot
[20:56] <jonathank89> can i post a link here?
[20:56] <jbicha> qense: more precisely, the "MeMenu" is one of the indicator applets :-)
[20:57] <duncan> Any idea why I could have lost the 'Indicator Applet Session'?
[20:57] <jonathank89> duncan, can I post a screenshot link here?
[20:57] <duncan> links, yes
[20:57] <jonathank89> http://dl.dropbox.com/u/451161/Screenshot.png
[20:58] <jonathank89> you'll notice in the top right the problem
[20:58] <jbicha> jonathank89: yeah I've had that same problem too but didn't know how to report it
[20:59] <jbicha> I think you can try killall gnome-panel to refresh the panel
[20:59] <Cajun_Lan_Man> I'll sign up and try to help out with confirming bugs.  Thanks guys.
[20:59] <duncan> thanks all, bye
[20:59] <hggdh> jbicha: I apologise if I sounded harsh
[20:59] <charlie-tca> Isn't that a double me-menu?
[21:00] <jonathank89> charlie-tca: sort off, but only one works...
[21:00] <Cajun_Lan_Man> btw, I'm not sure if it's the same issue, but I just recently installed ubuntu on a Thinkpad (the model escapes me at the moment) and I noticed that my user name cut off my me-menu, like it was overlapping.
[21:00] <charlie-tca> But you could report it against the indicator-applet
[21:01] <jonathank89> charlie-tca: what about in the bottom left
[21:01] <jonathank89> charlie-tca: you'll notice the white bar next to the desktop icon.
[21:02] <jbicha> hggdh: my feelings weren't hurt, I'm just going to focus on triaging more bugs this week to get more experience
[21:02] <hggdh> jbicha: did my email clarify what we look for, or did I just made things more confusing?
[21:03] <charlie-tca> jonathank89: don't know that one. It looks like an applet was installed, but only expands when something is done. If you right click on the white bar, does it tell you anything?
[21:04] <jonathank89> charlie-tca: the weird thing is the little white bar thing disappears after a while and in regard to the indicator-applets being messed up, that only happens sometimes it's weird...
[21:04] <charlie-tca> yeah, that is
[21:05] <jbicha> hggdh: your email was helpful, I tend to be too concise so I need to use more words to explain what I'm doing, but I also think that since I have to look hard to find 5-10 good examples
[21:05] <jbicha> of bug triaging, I ought to do more to strengthen my application
[21:06] <hggdh> your case is borderline -- we (meaning some of us) have been seeing your work here. I just used the moment in time to try to explain it more
[21:07] <hggdh> I would personally expect you to be accepted
[21:08] <jbicha> hggdh: so should I triage my own bugs or not?
[21:09] <hggdh> jbicha: no, we should never triage our own bugs. Our prejudices would be too strong
[21:09] <jbicha> yeah, I thought it was good to at least have someone else confirm
[21:09] <jbicha> hggdh: and is acceptance to bug-control decided just on the mailing list or is there an actual meeting too?
[21:11] <hggdh> jbicha: you need two positive votes (and, ideally, no negative ones ;-) then the bugmeister decides
[21:11] <hggdh> there is no requirement for a meeting
[21:11] <hggdh> jbicha: so I was just giving my view, not casting in iron the decision
[21:12] <jbicha> hggdh: right, and I still got a half of a positive vote so it's not too bad :-)
[21:14] <hggdh> :-)
[21:19] <ddecator> nigelb: ping
[21:29] <jonathank89> okay I think I've tracked down what the problem package could be, I think it's the gnome-panel (see bug screenshot: http://i289.photobucket.com/albums/ll235/ChaosTheory5789/bug.png)
[21:29] <jonathank89> for the record i'm just trying to figure out what package to report the bug under...
[21:31] <ddecator> jonathank89: i think i know a report for that, let me find it a sec
[21:32] <jonathank89> ddecator: great!
[21:33] <ddecator> bug 439448
[21:33] <ubot4> Launchpad bug 439448 in gnome-panel (Ubuntu) (and 2 other projects) "visual corruption affecting several panel applets (affects: 85) (dups: 31) (heat: 666)" [Low,Triaged] https://launchpad.net/bugs/439448
[21:33] <ddecator> jonathank89: take a look at that one ^
[21:36] <jonathank89> ddecator: i think that's it, thanks!
[21:36] <ddecator> jonathank89: no problem :)
[21:37] <jonathank89> ddecator: however notice the date on it, 2009-09-30
[21:37] <ddecator> jonathank89: yes, but look at the recent comments. still in lucid (unfortunately)
[21:38] <jonathank89> ddecator: it's a gnome problem so i'm not sure the ubuntu guys are going to fix it...
[21:39] <ddecator> jonathank89: it's reported upstream though, so the gnome devs know about our report and can access it, so hopefully they'll fix it
[21:39] <ddecator> it certainly affects enough people to warrant attention...
[21:40] <jonathank89> ddecator: hopefully, it bugs that hell out of me!
[21:49] <jonathank89> ddecator: thank for the help. bye all
[21:49] <ddecator> cya jonathank89
[21:53] <chilicuil> Hi, sry if the question is somekind noob, can I use quilt/cdbs to generate a patch from /debian/* ?, or should I use a simple debdiff?
[22:23] <hggdh> chilicuil: you can use quilt to *create* a patch in ./debian
[22:24] <hggdh> chilicuil: if you are patching an upstream source, then the patch should live in ./debian/patches, not in the upstream source
[22:33] <cwillu_at_work> BUGabundo, can I borrow you for a minute?
[22:33] <BUGabundo> sure
[22:34] <BUGabundo> for you I have 1min and 5 sec :D
[22:34] <cwillu_at_work> only that long?
[22:35] <cwillu_at_work> I'm tired, and have a really really complicated piece of code to write for work, and I'm in no way competent to do that at this moment due to "I'm tired".  So.  I've decided that in the interests of "Looking Busy", I'm going to report bugs to you, and report patches to you, and you get to take all the credit, as long as they move in the right direction :)
[22:35] <cwillu_at_work> basically, I'm in the mood for mindless following of instructions of how to report patches that I've already written and used :p
[22:37] <BUGabundo> not sure I can handle that right now...i can't even read what I type
[22:37] <cwillu_at_work> hmm :/
[22:37] <BUGabundo> but shoot... ill see what I can do
[22:38] <cwillu_at_work> compiz-fusion-plugins-main
[22:38] <BUGabundo> ehe
[22:38] <cwillu_at_work> the snapping plug-in is broken, in that it causes excess dragging on the other dimension when it's snapping/resisting on the other axis
[22:38] <BUGabundo>   Installed: 0.8.4-0ubuntu3
[22:38] <cwillu_at_work> i.e., if you drag a window across the top of the screen, it moves far slower across the top than it should
[22:39] <BUGabundo> moves fine here
[22:39] <cwillu_at_work> do you have mouse acceleration?
[22:39] <BUGabundo> no idea
[22:39] <cwillu_at_work> it's far more noticable on slower machines and machines with high pointer acceleration
[22:39] <cwillu_at_work> this occurs because it needlessly warps the mouse pointer in addition to warping the window
[22:39] <BUGabundo> its at ~60%
[22:39] <cwillu_at_work> so it 'fights' your motion
[22:40] <cwillu_at_work> if you comment out the mouse warping line (which I have a patch for), the motion becomes silky smooth
[22:41] <cwillu_at_work> oh, top of the screen is a bad example if you're also dragging with the titlebar instead of alt-dragging, because the constrain-y uses different code
[22:42] <cwillu_at_work> try alt-dragging a window across the top (such that you could move that window above the top of the screen)
[22:43] <BUGabundo> ahh
[22:43] <cwillu_at_work> :)
[22:44] <BUGabundo> jhummm still very fast
[22:44] <cwillu_at_work> try a bigger window :p
[22:45] <cwillu_at_work> the place where it really kills me is dragging a fullscreen window from one monitor to another
[22:45] <cwillu_at_work> but it's noticable (as you've noticed :p) in many situations
[22:45] <BUGabundo> well if I use a maximize wind, it tries to snap, instead of moving
[22:45] <cwillu_at_work> er, a maximized by-hand window
[22:45] <cwillu_at_work> think a big xterm
[22:46] <BUGabundo> did it now
[22:46] <BUGabundo> it gets suck with the mouse in the corner
[22:46] <BUGabundo> will not drag across desktops
[22:46] <cwillu_at_work> if you drag faster you should be able to force it past
[22:46] <cwillu_at_work> if you drag slow enough with edge-attraction on, you can't actually make any progress
[22:48] <BUGabundo> no matter how fast I go
[22:48] <cwillu_at_work> your computer is too fast then :p
[22:48] <BUGabundo> if its stuck at the corner, it will not move
[22:48] <BUGabundo> if it's a few px down, it works
[22:50] <micahg> any gcc experts in here?
[23:01] <cwillu_at_work> BUGabundo, aptitude build-dep compiz-fusion-plugins-main; apt-get source compiz-fusion-plugins-main; cd compiz-fusion<tab>/debian/patches; wget http://cwillu.com/files/fix-snapping-plugin.patch; cd ../..; dpkg-buildpackage; dpkg -i compiz-fusion-plugins-main*.deb; restart compiz, and test :)
[23:02] <BUGabundo> not tonight
[23:02] <BUGabundo> busy :/
[23:03] <cwillu_at_work> my minute and 5 seconds is up? :p
[23:03] <cwillu_at_work> didn't realize that was clock time and not user time
[23:04] <BUGabundo> :)
[23:04] <BUGabundo> not that
[23:04] <BUGabundo> I really can't reboot
[23:04] <BUGabundo> and restart compiz is prob the most scaring thing I hate doing
[23:04] <BUGabundo> it tends to never start again
[23:07] <cwillu_at_work> in theory you can just disable and re-enable the plugin
[23:08] <cwillu_at_work> but being c plugins, it has the potential to knock compiz over
[23:08] <cwillu_at_work> granted that all the patch does is comment out a call to warp_pointer
[23:32] <ddecator> anyone know off-hand what package contains notify-send?
[23:33] <yofel> libnotify-bin
[23:34] <yofel> (powered by apt-file :P)
[23:35] <ddecator> yofel: thanks, mind testing something for me real quick?
[23:36] <yofel> sure
[23:37] <ddecator> yofel: great. if you have a video on your system, use totem to play it. while it's playing, try using notify-send from the terminal so create a notification. then pause the video and try again
[23:37] <ddecator> s/so/to
[23:38] <yofel> works fine (I use KDE though)
[23:38] <yofel> libnotify should work the same I think
[23:38] <ddecator> ah, anyone using gnome that can test this for me real quick? (not sure if it's just my system)
[23:39] <ddecator> just in case...if totem is playing any video, then notify-send doesn't work for me at all. works if i pause
[23:40] <ddecator> not sure if it's a bug i should report or if my system is just screwy
[23:41] <MrKanister> ddecator: I can confirm the issue, but no only for videos
[23:42] <ddecator> MrKanister: great, thanks :)
[23:42] <MrKanister> ddecator: np
[23:43] <yofel> notify-osd issue then I guess (or whatever else snatches the notification away)
[23:44] <ddecator> that's what i'm not sure of. i can only reproduce it when playing video (or i guess audio as well) with totem. no issues with vlc
[23:44] <ddecator> not sure if it's something totem does, or a notify-osd issue
[23:45] <yofel> maybe there's some cool(?) don't-disturb-while-playing-video feature in gnome...
[23:45] <ddecator> that could be. it's not fullscreen though. let me check totem's settings to see if anything like that is in there
[23:48] <ddecator> hm, not seeing anything in totem's preferances or gconf