[00:08] <elleuca> https://bugs.edge.launchpad.net/ubuntu/+source/indicator-messages/+bug/577226
[00:09] <ubot4> Launchpad bug 577226 in indicator-messages (Ubuntu) "<Super>+M shortcut unusable when running Compiz (affects: 1)" [Undecided,New]
[00:17] <NMR_1122> If I have a touchscreen that doesn't work out of the box, is that a bug? Or something else?
=== jmgartner is now known as rackIT
[01:14] <Salvad1> If I report a Gnome bug to Ubuntu; Does Ubuntu report that to the Gnome bug system?
[01:33] <micahg> jcastro: ping
[01:35] <Merlin> bug #432631. fixed released? still does not work here on fully updated 10.04.
[01:35] <ubot4> Launchpad bug 432631 in sudo (Ubuntu Lucid) (and 6 other projects) "clean up system/per-user proxy handling (affects: 2) (heat: 20)" [Medium,Fix released] https://launchpad.net/bugs/432631
[01:38] <micahg> jcastro: I'll just email you'
[02:06] <trinikrono> hey all who has something for a newbie to triage
[02:11] <trinikrono> ddecator: /me waves
[02:11] <trinikrono> lol
[02:11]  * ddecator waves
[02:13] <trinikrono> are you busy
[02:13] <trinikrono> i want to triage something
[02:14] <ddecator> not atm, i'm waiting for a pizza to cook
[02:15] <ddecator> trinikrono: what bug are you looking at?
[02:16] <trinikrono> nice bug 382267,i found a upstream bug for it already
[02:16] <ubot4> Launchpad bug 382267 in checkgmail (Debian) (and 1 other project) "memory leak (affects: 4) (heat: 18)" [Undecided,New] https://launchpad.net/bugs/382267
[02:17] <trinikrono> so i should just wait for them to say they have the latest release , put the link to the upstream bug
[02:17] <trinikrono> and then it can triage right?
[02:18] <ddecator> hm, memory leaks are tricky since it can be hard to tell where the leak is. what's the upstream report?
[02:19] <trinikrono> can i put sourceforge bugs here
[02:19] <trinikrono> whats the handle?
[02:20] <ddecator> sf 12938
[02:20] <ddecator> ...
[02:20] <ddecator> i guess not?
[02:21] <trinikrono> yea
[02:21] <ddecator> what's the link?
[02:21] <ddecator> (brb)
[02:24] <trinikrono> http://sourceforge.net/tracker/?func=detail&aid=2686715&group_id=137480&atid=738663
[02:24] <ubot4> trinikrono: Error: <Bugtracker.plugin.Sourceforge instance at 0x351fd40> bug 2686715 not found
[02:24] <trinikrono> poor ubot
[02:31] <ddecator> hm, looks like it's maintained by a team, so i'm not sure who the best contact would be. i think it would be best if you could find someone familiar with the package and ask if there is anything that can be done so information can be added to the report that may point to what is causing the memory leak. then it can be triaged imo
[02:31] <ddecator> but i need to go eat dinner. gl and i'll be back later!
[02:32] <trinikrono> later
[08:56] <rulus> Morning! I'm having trouble printing a certain PDF in Lucid. I get a popup giving me a 'Print error' and it prints out a page with this text on it: http://paste.ubuntu.com/429913/ Is this a ghostscript issue?
[11:58] <MrKanister> jcastro: Hi. Could you please renew my ubuntu-bugcontrol membership? That would be great. My name is "Martin Mai". Thanks in advance.
[13:04] <SwedeMike> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/215497 <- that problem, I'd really like to make that into a bug and not "wishlist"? I'd really like to see some effort into making Ubuntu have basic functionality for IPv6...
[13:04] <ubot4> Launchpad bug 215497 in network-manager (Ubuntu) (and 1 other project) "IPv6 configuration is not flushed when interface goes down (affects: 4) (dups: 1) (heat: 42)" [Wishlist,Triaged]
[16:21] <eldon> I have another bug i just noticed, I don't know how to prove its happening though. say i have a screensaver, and some of the default ones consume a lot of processor time. and i have laptop screen set to turn off, a short time after the screen saver activates (and locks the computer). and hour later, *sometimes* if you move the mouse, you will see the screen saver for a short time (1/3rd second) and then the login screen. afaik, the scre
[16:27] <astraljava> eldon: You got cut off. "afaik, the scre" ended your line.
[16:28] <eldon> IMO, the screen saver should terminate upon screen shutdown via power management to save power
[16:57] <bcw142> Anyone have a clue how to put a bug against lunchpad itself?
[16:57] <charlie-tca> yup
[16:58] <andre__> bcw142, https://bugs.launchpad.net/launchpad ?
[16:58] <charlie-tca> file it using 'launchpad' as the source package
[16:59] <bcw142> Ok, that looks right, thanks.
[17:00] <TonyP> Hi all! I posted a bug (#573776) about a week ago because I cannot boot following upgrade to Lucid.  Is there any way I can help to get it looked at.  I'm just reduced to booting off a USB stick now.
[17:06] <bcw142> So, TonyP have you tried the safe mode boots for Lucid?
[17:07] <TonyP> Do you mean recovery mode?
[17:07] <bcw142> Ya, the recovery modes.
[17:09] <TonyP> Ok, that only works with an old kernel and will get me into a console session.
[17:09] <bcw142> No it should work with the current kernel as well, that's how I got in this morning to my copy of 10.04
[17:10] <bcw142> I did a fresh install last week and it crashed. We had a power outage and after that I couldn't get in till I used the recovery mode.
[17:10] <TonyP> Recovery mode does not boot with current kernel - it just stops on the at the same point
[17:11] <bcw142> It put me in a a normal shell and I checked the network connection and then started X.
[17:11] <bcw142> Yours sounds like the install never finished.
[17:12] <TonyP> Wasn't an install. It was an upgrade from Karmic
[17:13] <bcw142> Update can be a problem that way. I downloaded the install and formatted the ext3 partition again - it still hung but I can get it working via recovery.
[17:13] <bcw142> If update hangs your left with an incomplete system.
[17:14] <TonyP> Update did finish - nothing looked wrong with it
[17:16] <bcw142> But you can't boot except via USB Stick so something is wrong, you should have at least two things in the menu Ubuntu and recovery generally (I have much more as I have DOS and Windows on the machine too).
[17:17] <TonyP> It's dual boot, so I can get into XP
[17:19] <bcw142> You have the Lucid USB stick and that works fine, it's just normal grub boot your having problems with right?
[17:21] <TonyP> Yes, I its the boot from grub into ubuntu that fails
[17:26] <bcw142> I just checked mine and the grub menu shows Ubuntu and then recovery, I crashed so I picked recovery and after the next prompt to two got a normal shell logon so logged in and started X and all was working. After that next boot it worked normally.
[17:27] <bcw142> That should be prompt or two I got a normal shell ;)
[17:31] <TonyP> As I said, only an old kernel boots further.  In normal mode, it boots to a login prompt, but mouse and keyboard don't work so I get no further.  If I take recovery and choose normal boot, then go to the shell in tty1, and run startx, it goes to Gnome, but no mouse or keyboard.
[17:33] <penguin42> TonyP: When it's booted like that do you have network connectivity or can you get the dmesg out of it?
[17:34] <bcw142> You can do both. dmesg | more will work, but I did ifconfig to check my connection first, then did startx.
[17:35] <TonyP> I have full CLI functionality - network and all.
[17:35]  * penguin42 just wondered if it was possible to see where ht ekeyboard/mouse went
[17:36] <bcw142> TonyP 'startx' does what?
[17:37] <TonyP> Runs a gnome shell but is asking for a keyring password that I cannot enter
[17:37] <penguin42> so you can type - but just not in X?
[17:38] <TonyP> Yes, I can type in the console
[17:38] <penguin42> has the whole of X locked or is it just input - does the clock still change etc?
[17:38] <TonyP> Didn't notice that
[17:38] <bcw142> Your in a shell, you can do most things, maybe even bring up other shells but your X has a problem for unknown reasons.
[17:38] <penguin42> does ctrl-alt-f1 get you back?
[17:39] <TonyP> Yes
[17:39] <penguin42> and then does ctrl-alt-f7 (or is it 8) switch back?
[17:41] <TonyP> Dont forget, I running an old kernel.  ctrl-alt-7 switches me back.
[17:42] <bcw142> So you can get to X now?
[17:43] <TonyP> But if I don't run startx there is not an X session there.  (I'm on the USB key now)
[17:43] <penguin42> TonyP: Ah, so am I correct to say: Lucid kernel fails to boot, old kernel you can boot but you don't get input in X?
[17:43] <TonyP> Yes
[17:43] <penguin42> TonyP: I'm wondering if the new input in X is expected, that stuff has changed a lot
[17:44] <bcw142> Input would be PS/2 or USB and both should work in X.
[17:44] <penguin42> bcw142: I was thinking udev/hal change
[17:45] <penguin42> TonyP: On the new kernel does it boot if you boot with nomodeset ?
[17:45] <TonyP> I'm wondering if there is an X problem with the type of on board graphics with shared memory I have
[17:46] <bcw142> X should work either way, shared memory shouldn't have an effect on it.
[17:46] <TonyP> I could try nomodeset and come back (I assume that is a kernel parameter I can add in grub)
[17:47] <penguin42> TonyP: Yeh, and Radeon mode setting is something the newer kernels definitely do
[17:48] <penguin42> TonyP: You could also try radeon.modeset=0 but I think nomodeset should do it
[17:48] <TonyP> OK, see you later then
[17:48] <bcw142> Ok, bye
=== yofel_ is now known as yofel
[18:03] <opengeekv2> hello i have a bug on kubuntu and I don't know what package is the coause fo the bug tu report it
[18:03] <yofel> opengeekv2: welcome, what's your problem?
[18:05] <opengeekv2> I installed kubuntu LTS from the las ISO image
[18:05] <opengeekv2> I installed the nvidi privative drivers and I rebooted my machine
[18:06] <opengeekv2> after that I made the last updates
[18:06] <opengeekv2> and after installing the last updates and rebooting (because a new kernel was installed) X server don't start
[18:07] <opengeekv2> then who is the vausant of the bug?
[18:07] <SwedeMike> wasnt that listed in the errata that you can't do that anymore?
[18:07] <SwedeMike> I think I read that somewhere.
[18:08] <yofel> opengeekv2: where did you get the driver from? Hardware Drivers ?
[18:08] <opengeekv2> I don't know i searched and the good thing is that I've been working with the beta utill yesterday and in the beta everything worked fine
[18:08] <yofel> SwedeMike: that were the drivers from the nvidia site
[18:09] <opengeekv2> no, I installed the drivers from the jokey-kde
[18:09] <opengeekv2> the current verison
[18:09] <SwedeMike> yofel: oki, I misunderstood that he did that.
[18:09] <yofel> ok
[18:10] <opengeekv2> then i have not to report the bug?
[18:11] <yofel> opengeekv2: wait, do you have X running now? or still broken?
[18:12] <opengeekv2> I am reinstalling kubuntu because I need my computer to work for a programming practice in the univerity
[18:12] <opengeekv2> i think if I not install privative dribers it will work
[18:13] <opengeekv2> (i am talking with you with another computer)
[18:14] <opengeekv2> with a Samsung R50 with an Ati mobility radeon X300 using the radeon opensource dirver, and it not suffers the bug
[18:14] <yofel> well, then reporting it won't work, unless you get the bug again, if that happens: try to get to a tty 'press ctrl+alt+f1' when X won't start, and run 'apport-cli nvidia-current' in there, save the bug and report it later once you have X back
[18:15] <yofel> more like, reporting the bug without the X logs would be useless
[18:16] <opengeekv2> I undertand then I'll try to reproduce the bug when I have time ok? now I have my computer working without the privative drivers
[18:17] <opengeekv2> I hope some the nvidia will free his drivers and everybody will be happy
[18:17] <yofel> no problem, sorry for the inconvenience
[18:17] <opengeekv2> *someday
[18:17] <opengeekv2> bye
[18:26] <TonyP> penguin42: neither of the modeset parameters worked.  My monitor complained "Input signal out of range - change settings to 1280 x1024 - 60Hz" on then goes to sleep.  So if it did boot, I can't see it!
[18:27] <penguin42> TonyP: Hmm annoying! Remind me, is this right at the very start or after grub ?
[18:27] <TonyP> After grub
[18:27]  * penguin42 doesn't really know what to say if modeset doesn't do it
[18:28] <TonyP> I downloaded the latest kernel update with no effect
[18:28] <penguin42> and you've tried taking all the quiet splash   off to see if it has anything else to say?
[18:31] <TonyP> Yes, but I just see what I get anyway.  Alt-Ctrl-F1 gives me some information and up arrow on the splash screen shows other stuff
[18:31] <penguin42> remind me precisely when it fails on a new kernel?
[18:33] <TonyP> Have you seen the bug (#573766) I have a picture of tty1 there
[18:34] <penguin42> 573766 seems to be automatic logon?
[18:35] <TonyP> Sorry 573776
[18:36] <penguin42> oh
[18:37] <penguin42> TonyP: That looks the same as 562843
[18:40] <penguin42> TonyP: Well, looking in the kernel source there is a comment 'FIXME: RS400 & RS480 seems to have issue with GART size if 4G of system memory (needs more testing)'
[18:41] <penguin42> just above that error
[18:41] <TonyP> Yes you are right - I will mark my bug as a duplicate - thanks for the help.  I hope its is fixed soon!
[18:42] <penguin42> TonyP: Well you have the benefit of having a bug affected by a few people!
[19:14] <edlik> please help... I upraded from 9.10 to 10.04 and now  have no gui :( After splash screen my monitor shuts off, I can restart it with Ctrl+Alt+F5 but I only have command line.
[19:18] <astraljava> edlik: #ubuntu is the channel for support issues.
[19:36] <jean-pierresainf> what is startx telling you ?
=== radoe_ is now known as radoe
=== BUGabundo is now known as BUGabundo_DrWho
=== BUGabundo_DrWho is now known as BUGabundo_MythB
=== BUGabundo_MythB is now known as BUGabundo_NCIS
[22:46] <ekilfoil> hello all... a user of my software submitted bug 575465 against xinput... but the problem is actually in xserver-xorg-core (pretty sure)... what's the best way to handle getting it moved to the appropriate package?
[22:46] <ubot4> Launchpad bug 575465 in xinput (Ubuntu) "unable to use mouse buttons to trigger events in mangler (affects: 3)" [Undecided,New] https://launchpad.net/bugs/575465
[22:53] <arand> ekilfoil: open up a new task for that package for that report, and invalidate the other task; if there's already a bunch of useful info on there. Otherwise, just mark it all as invalid and open a new one... (Not by any means an official answer, just my guess of policy)
[22:55] <arand> ekilfoil: Seems like you have some useful info there, so just use "also affects distribution">>ubuntu>>new-package and if you are _sure_, mark the other package as invalid.
[22:56] <ekilfoil> well it's definitely not a problem in xinput
[22:57] <yofel> wait, why invalidate it? just change the affected package
[22:58] <yofel> klick on the arrow beside xinput (Ubuntu) and change xinput into xserver-xorg-core and save the changes (and put a small comment indicating why you're doing so)
[22:59] <arand> yofel: ekilfoil: Ah, you're right, it's easy to change the xinput task to another package directly, which is likely the best.
[22:59] <yofel> ekilfoil: ^
[23:00] <yofel> You only need to use the invalidate approach if you need to handle Projects <-> Distributions
[23:00] <yofel> I hope they fix that issue with launchpad sometime...
[23:05] <ekilfoil> well... I think I may be able to fix this, so I guess I should just assign it to myself?
[23:05] <ekilfoil> I'm not incredibly experienced using launchpad, as you can see :)
[23:06] <yofel> np, we're here to help with launchpad too :P
[23:06] <yofel> ekilfoil: if you plan on fixing the issue assign the bug to yourself, and ONLY in that case
[23:07] <ekilfoil> well... i'm planning to try
[23:07] <ekilfoil> i may get lost in a maze of code and realize i'm in over my head
[23:07] <yofel> np, when you get to that point simply unassign the bug from you
[23:08] <ekilfoil> ok.. thanks for the info
[23:34] <dominicdinada> Is there a known bug for lucid gnome crashing while file transfer ?? Or basically doing anything it has happened 8-10 times since I have installed and when it crashes I lose the Minamize,Maximize,Close the whole window controls
[23:34] <dominicdinada> plus Any window that is not in focus is not listed on the taskbar only all the windows from when the desktop crashed... even when a system monitor kill the process
=== maco2 is now known as maco