Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 35890

Summary: IRC clients should specify a Gentoo-specific username
Product: Gentoo Linux Reporter: Sean Egan <sean.egan>
Component: Current packagesAssignee: Packages in net-irc <net-irc>
Status: VERIFIED WONTFIX    
Severity: enhancement CC: abhishek, avenj, brad, dberkholz, klasikahl, kutsuya, mkennedy, piman, scox, sean.egan, solar, spider, thekingant
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: Removes support from the component causing the error.

Description Sean Egan 2003-12-15 12:11:44 UTC
As Gentoo users are generally an annoying nusiance in my IRC channel, I would like to be able to set a +b on *!gentoouser@*, in order to keep them out.  In order to accomplish this, I would like Gentoo to set the default username to something Gentoo specific.

Reproducible: Always
Steps to Reproduce:
1. Join an IRC channel
2. Wait for a Gentoo user to come in, talk about how he "emerged" this and that and all the "optimizations" he used, but something still isn't working
3. Mention that he should have read the FAQ before /joining and /kick him.
Comment 1 SpanKY gentoo-dev 2003-12-15 12:27:57 UTC
you gotta be kidding me
Comment 2 SpanKY gentoo-dev 2003-12-15 12:36:42 UTC
on a side not, if you have real beef with something Gentoo is doing with respect to Gaim, please contact gaim-bugs@gentoo.org
Comment 3 Seemant Kulleen (RETIRED) gentoo-dev 2003-12-16 04:10:02 UTC
this is too funny, you've taken the crown of being the biggest jack ass I've seen this year.  well done, I think.
Comment 4 Donnie Berkholz (RETIRED) gentoo-dev 2003-12-16 04:12:29 UTC
There's a pretty funny "stereotypical gentoo user" guide around, I think you nearly quoted it.
Comment 5 solar (RETIRED) gentoo-dev 2003-12-16 15:44:43 UTC
Sure lets rush out an edit every single IRC client ebuild in portage so 
the gaim lead dev does not have to deal with gentoo users reporting 
bugs.

This has to be worst initial contact I think anybody could have made. 
Not sure I expect much more out of somebody that codes for AOL software.

I hope to see this bug make the GWN for an example of what an INVALID    
bug looks like or for seemants jackass award.
Comment 6 Andrea Luzzardi 2003-12-16 16:35:16 UTC
"Lindows.com, a proud gaim supporter!" <- this could explain
Comment 7 Donnie Berkholz (RETIRED) gentoo-dev 2003-12-16 18:04:51 UTC
Could you guys please have a little more respect? You don't need to respond in kind.
Comment 8 Spider (RETIRED) gentoo-dev 2003-12-17 09:44:04 UTC
please,  I'm chuckling here.  So far its the funniest troll this month.
Comment 9 Luke Schierer 2003-12-17 10:33:27 UTC
i do not know which is funnier, that sean actually submitted this bug, or that you all are so stereotypically gentoo users as to take it seriously. 
Comment 10 Luca Barbato gentoo-dev 2003-12-17 15:06:15 UTC
yawn
just to let you know I just built gaim with debug and got this nice backtrace if I try to reconnect to icq...

#0  gaim_connection_get_account (gc=0x23) at connection.c:416
#1  0x10060ec4 in signed_on_off_cb (gc=0x0, dialog=0x1034d948)
    at gtkaccount.c:1351
#2  0x10043d74 in gaim_marshal_VOID__POINTER (cb=0x42004824, args=0x8,
    data=0x100a1ff4, return_val=0x100a3c3c) at signals.c:569
#3  0x100437b8 in gaim_signal_emit_vargs (instance=0x0,
    signal=0x10352ea0 "\0205K`", args=0x7fff8f40) at signals.c:446
#4  0x100436c0 in gaim_signal_emit (instance=0x10060ec4,
    signal=0x10060ec4 "|~\exH\006P\021|\177\ex\200|") at signals.c:405
#5  0x100251d0 in gaim_connection_set_state (gc=0x100e3788, state=8)
    at connection.c:333
#6  0x0e9512fc in gaim_bosrights (sess=0x10352ea0, fr=0x1035be08)
    at oscar.c:3849
#7  0x0e92e044 in rights (sess=0x7fff8f40, mod=0x8, rx=0x100e3788,
    snac=0x10352ea0, bs=0x19e) at bos.c:44
#8  0x0e92e2dc in snachandler (sess=0x0, mod=0x8, rx=0x100a1ff4,
    snac=0x100a3ca0, bs=0x19e) at bos.c:150
#9  0x0e93e040 in consumesnac (sess=0x1035c1b8, rx=0x1035be08)
    at rxhandlers.c:138
#10 0x0e93e8c4 in aim_rxdispatch (sess=0x1035c1b8) at rxhandlers.c:525
#11 0x0e947adc in oscar_callback (data=0x10060ec4, source=8, condition=0)
    at oscar.c:525
#12 0x10037558 in gaim_io_invoke (source=0x0, condition=G_IO_ERR,
    data=0x100a1ff4) at proxy.c:205
#13 0x0f888478 in g_io_unix_dispatch () from /usr/lib/libglib-2.0.so.0
#14 0x0f863408 in g_main_dispatch () from /usr/lib/libglib-2.0.so.0
#15 0x0f86471c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#16 0x0f864aa4 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#17 0x0f8652dc in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#18 0x0fcd14b8 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#19 0x100a01c8 in main (argc=0, argv=0x0) at main.c:914

please fix that while I'm trying to educate my users to not be a pain/stereotype gentoo lusers.
Comment 11 J. Paul Reed 2004-01-13 13:05:54 UTC
To the reporter: Maybe if gaim wasn't such a unstable piece of shit, you wouldn't have people constantly asking you questions about why your software is ass.
Comment 12 Mark Doliner 2004-02-24 13:04:45 UTC
Luca Barbato: You don't happen to be using an architecture other than x86, do you?
Comment 13 Rob Flynn 2004-04-04 19:48:50 UTC
This has gotten a bit out of hand.  I do not condone the original report, nor do I condone any of the inflammatory responses that were made by either side.

Comment 14 Joe Kappus 2004-08-05 21:44:39 UTC
This is blasphemy, and just proves there are people with way to much time on their hands.  If you got a problem, don't bitch on bugzilla, we have better things to do then listen to your incessant whining.
Comment 15 Jim C. Nasby 2004-09-25 17:13:27 UTC
Simply adding this link to the GAIM docs should suffice: http://www.funroll-loops.org/
Comment 16 Spider (RETIRED) gentoo-dev 2004-09-25 19:24:18 UTC
Ha. Ha. Ha.
Comment 17 mike <loft306> 2005-09-14 20:12:52 UTC
ROFL.....
Comment 18 Gloin Oin 2005-09-14 21:18:35 UTC
Created attachment 68484 [details, diff]
Removes support from the component causing the error.

This should be adequate to solve the problem listed above, although a
sanity-check on my syntax is probably in order.
Comment 19 Jakub Moc (RETIRED) gentoo-dev 2006-03-01 23:59:29 UTC
*** Bug 124595 has been marked as a duplicate of this bug. ***