[14:34] note: the above is an open bug in linux [15:55] https://launchpad.net/ubuntu/+source/adobe-flashplugin How come Hardy-Karmic have a later version than Lucid?? [15:56] xteejx1: that's handled separately from the regualr archive === xteejx1 is now known as xteejx [15:57] I know its universe, but I can't understand why the older version have later versions [15:58] xteejx: not universe, partner [15:58] micahg: without sounding stupid (too late) what's the difference? [15:58] universe/multiverse is uploaded by MOTU, partner is only uploaded by canonical [15:58] AFAIK [15:59] ahhhh i see [15:59] xteejx: I suggest filing a bug as the partner uploaded deadline is soon [15:59] umm ok :) [16:01] It's hardly a great bug report, but points the problem out bug 508799 [16:01] Launchpad bug 508799 in adobe-flashplugin "[lucid] flash version in older releases is older upstream version" [Undecided,New] https://launchpad.net/bugs/508799 [16:30] there have been many bugs that upstream don't update as fixed but they are actually fixed in development releases so after testing should they be marked fixed? [16:35] Yes [16:35] Maybe put a note on the upstream bug report too [16:36] xteejx, ok, thanx [16:37] om26er: only if it's confirmed as an actual issue in the app [16:38] sure [16:38] and if you see an upstream issue is fixed, comment on the upstream bug [16:40] micahg, thanks, will do that [17:11] om26er: the empathy bug is actually not fixed , the user wants the dropbox to use the *full* width [17:13] *dropdown combobox [17:25] What is the procedure for KDE bugs now, are we politely asking everyone to try the latest now, since the KDE devs are through with working on KDE3 ?? [17:26] xteejx: upstream bugs are opened upstream and closed in LP [17:26] micahg: I don't understand [17:27] one sec [17:27] we're closing the LP bugs ? [17:27] * micahg is pulling up the docs [17:27] xteejx: http://www.kubuntu.org/news/timelord [17:28] I'll be back online in about 45 min [17:28] timelord? is this doctor who? hehe [17:28] thanks though micahg :) [18:49] micahg: ping [18:49] hi xteejx [18:50] micahg: Hey, I had a look at that timelord thing, but it didn't say anything about old versions, just future development [18:50] xteejx: I suggest hoping in #kubuntu-dev and asking [18:51] another room I haven't seen hehe will do cheers micah :) [18:51] no such room i'll /list [18:51] maybe #kubuntu-devel [18:52] That's the one ;) [19:06] micahg: Usual procedure apparently, check latest version, and close KDE3 bugs that aren't security problems. [19:07] xteejx: k [19:07] thanks for pointing me to the right peeps :) [19:07] xteejx: np === oxide is now known as Oxide [20:52] Aren't nvidia drivers in place yet in Lucid? [20:53] xteejx: ask in #ubuntu+1 [20:53] ok [20:54] xteejx: are for me now [20:54] Hmmm, jockey won't install 173 or 'current' [20:55] * hggdh wishes for a working ATI [20:55] * xteejx wishes for an AMD phenom [20:55] :P [20:56] saw a barebone kit with a phenom for under 300 dollars [20:56] hggdh: I saw something about ATI not being ready for the Lucid kernel yet [20:56] im in the uk sadly [20:57] hggdh: forget ati [20:57] its still stucks [20:57] micahg: yes... Still running VESA. But now even the virtual consoles are hosed [21:12] hggdh: if you're in a pinch, make sure /boot is mounted, purge plymouth, allow the initramfs to be regenerated, and reboot [21:19] crimsun: thank ypu will try it now [21:20] brb [21:21] I was bitten by the latest cryptsetup upload (really bug 496765). [21:21] Launchpad bug 496765 in plymouth "plymouth ask-for-password doesn't display --prompt argument" [High,Fix committed] https://launchpad.net/bugs/496765 [21:25] yeeeeehhh I have the virstual consoles again!! [21:25] thank you, crimsun [21:27] np === oxide is now known as Oxide [22:21] micahg: what is your take on bug 508867? Just curious [22:21] Launchpad bug 508867 in firefox-3.5 "following any link from giganticurl.com leads whole system inresponsibility" [Undecided,New] https://launchpad.net/bugs/508867 [22:21] haven't looked yet [22:22] fun, even more with the typo on the title (or is it a typo?) [22:22] hggdh: I think it's an abuse of URLs [22:22] I have to see if it violates a standard or not [22:22] if it does it's not a bug [22:22] if it doesn't then it might be [22:23] I followed one of the link, just out of curiosity, and got a 404 [23:43] Just want to check this is a kdm bug before i file a report, basically if i boot to a kernel without ipv6 support i get the following in kdm.log http://pastebin.com/d5d31271c