[00:49]  * BUGabundo Memory depleted. Please terminate Brain. \n bed
[01:28] <bcurtiswx> ampelbein, 1 hour!! <gets excited> :P
[02:44] <bcurtiswx> Ampelbein: do you have a minute I can bug you?
=== Hellow is now known as Hellow__
=== Hellow__ is now known as Hellow|Alt
=== Hellow|Alt is now known as Hellow
[03:43] <therussianjig>  if I try to boot my laptop while not connected to a power source, I must hold the spacebar down, or the boot will hang, any ideas how to fix this?
[03:48] <micahg> therussianjig: try #ubuntu for support
[03:48] <micahg> please
[03:48] <micahg> this is the bug triage channel
[03:48] <micahg> or #ubuntu+1 if you're running karmic
[03:49] <therussianjig> alright sory
[04:59] <micahg> ping kees
[05:11] <micahg> ping hggdh
[06:32] <dholbach> good morning
[07:32] <thekorn> good morning bugsquad
=== set1 is now known as tommy
=== tommy is now known as zomby
=== zomby is now known as tommy_0_o
[08:59] <tommy_0_o> hi all
[08:59] <tommy_0_o> i have some questions
[09:03] <leoquant> 0_o ok
=== mvo__ is now known as mvo
[13:04] <Syka> Hey guys, I'm having an issue with gnome-panel. It will stop responding every so often, and then after a few minutes it works again and all the clicks are registered at once. If anyone knows a fix that'd be great. I'm running nVidia 180.44, 9800GT, dual monitors, Jaunty Desktop, and standard everything else. Installed it via Add/Remove.
[13:04] <Syka> Any ideas?
[13:07] <bullgard4> What is meant by "official tags" in https://bugs.launchpad.net/ubuntu/jaunty/+source/ekiga?
=== WelshDragon is now known as YDdraigGoch
[13:23] <xteejx> Hey guys, I'm triaging bug 124387, cant think of what else I need to ask for, theres only debugging procedures for dist upgrades on the wiki, any ideas?
[13:23] <ubot4> Launchpad bug 124387 in update-manager "[jaunty] update manager lock file not always removed" [Undecided,New] https://launchpad.net/bugs/124387
[13:23] <tom2> hi
[13:24] <tom2> i have to fix some bugs for university
[13:24] <tom2> i would like to know how i can find some to fix
[13:25] <mvo> xteejx: the file itself in the report is probably not a problem, its more likely that the background apt cron job is triggered
[13:25] <xteejx> tom2: https://wiki.ubuntu.com/BugSquad/GettingInvolved
[13:25] <mvo> xteejx: the file itself is not used, there is a fcntl() call used for the actual locking
[13:27] <xteejx> mvo, thats kinda beyond my knowledge - fro a triaging view is there anything else that i can put to help?
[13:28] <tom2> mvo: thx do you maybe have a list I can choose bugs from?
[13:28] <xteejx> i gave you the link
[13:29] <xteejx> just go to bugs.launchpad.net/ubuntu and look, theres plenty to choose from :)
[13:29] <mvo> xteejx: from the triage POV its good I think
[13:29] <xteejx> mvo, great, ill confirm it and set it medium :)
[13:29] <xteejx> vo, ps thank you
[13:30] <tom2> xteejx thx found what im looking for
[13:30] <xteejx> tom2, no probs
[13:31] <tom2> ok another question
[13:32] <tom2> the importance does that say the difficulty or just the need to be fixed?
[13:33] <xteejx> tom2 The importance of the bug signifies the priority that it should be given by people fixing bugs.
[13:33] <xteejx> hence the importance
[13:34] <tom2> ok thx
[13:34] <tom2> im looking for some java related bug
[13:35] <tom2> do you have any suggestions
[13:35] <tom2> ?
[13:35] <xteejx> any preference, openjdk or sun?
[13:36] <xteejx> tom2 ^^
[13:36] <tom2> sun
[13:37] <xteejx> you can do a package search on launchpad, hang on ill try and link you
[13:38] <tom2> thx
[13:38] <xteejx> https://bugs.launchpad.net/ubuntu/+source/sun-java6
[13:39] <xteejx> 229 open bugs
[13:39] <tom2> nice
[13:39] <tom2> thx again
[13:40] <xteejx> np
[14:30] <xteejx> guys quick question, is ntp available in jaunty? cant see any option anywhere
[14:30] <hggdh> xteejx, yes, ntp and ntpdate are available on Jaunty
[14:31] <BUGabundo> xteejx: yes
[14:31] <xteejx> hey hggdh :) - how do i set it up...it used to be a standard option in gnoe around hardy
[14:31] <xteejx> *gnome
[14:31] <BUGabundo> hggdh: [[]]
[14:31] <BUGabundo> xteejx: humm good question. it used to be on the Clock
[14:31] <xteejx> trying to confirm bug 157215
[14:31] <ubot4> Launchpad bug 157215 in gnome-system-tools "Synchronizing with a time server does not work when time difference is greater than several hours" [Undecided,New] https://launchpad.net/bugs/157215
[14:31] <xteejx> thats what i thought under Time Settings
[14:33] <xteejx> dont think its a bug though, the same happens in *cough* windows
[14:34] <hggdh> well, there is an easy way to check :-)
[14:34] <xteejx> hggdh ?
[14:35] <hggdh> (1) stop ntp; (2) reset the time to something a few hours behind; reboot; check time
[14:35] <hggdh> ntp should be restarted when you acquire a connection
[14:35] <hggdh> also, check the NTP time servers in your configuration
[14:36] <hggdh> /etc/ntp.conf
[14:37] <BUGabundo> xteejx: that's a Feature! not a bug
[14:37] <BUGabundo> you need to force ntp to update date if diff is bigger then X hours
=== dholbach_ is now known as dholbach
[14:38] <xteejx> so hggdh, ntp is installed and activated by default then??
[14:39] <hggdh> yes, it is
[14:39] <hggdh> also keep in mind that there is ntp, and ntpdate
[14:39] <BUGabundo> tenhu q ir! ate logo people
[14:39] <xteejx> ahh ok
[14:40] <hggdh> ntp is a daemon, and ntpdate is a one-run thing
[14:40] <hggdh> better saying: ntp runs continuously
[14:40] <xteejx> so as you said, stop ntp, set time back couple of hours, restart it
[14:41] <hggdh> yes
[14:41] <xteejx> cool thanks hggdh for again more wisdom :D
[14:42] <hggdh> I do not remember the details, long time I do not touch ntp, but -- as long as the time difference is, er, small, NTP will progressively adjust it
[14:43] <hggdh> if the time difference is, er, big, then NTP will adjust in one single setting
[14:43] <hggdh> what I do not remember is the threshold
[14:45] <xteejx> so the guy is right then, and this is still a "problem" - should be wishlist?
[14:45] <hggdh> xteejx, there is a parameter to ntpd that might bring some light: " -g     Normally, ntpd exits with a message to the system log if the offset exceeds the panic threshold, which is 1000 s by default.  This option allows the time to be set to any value without restriction; however,  this  can
[14:45] <hggdh>               happen only once.  If the threshold is exceeded after that, ntpd will exit with a message to the system log.  This option can be used with the -q and -x options.
[14:45] <hggdh> "
[14:46] <xteejx> ahhhhhhhhhh
[14:46] <hggdh> if this limit is exceeded, no, it is not a problem. It is The Way It Is (TM)
[14:48] <xteejx> just set my system time back 5 hours, and then run ntpdate and it updated fine
[14:48] <hggdh> there are two reasons (1) if, while running, the system clock is losing so many tick to get seriously offset, then this is a hardware issue; (2) if, while powered down, the system clock gets lost, then this is a battery issue
[14:49] <hggdh> xteejx, you are not running tnpd?
[14:49] <xteejx> i dunno lol
[14:49] <hggdh> if ntpd is running, ntpdate will not work
[14:49] <xteejx> ntpdate did work....its a fresh jaunty install
[14:49] <xteejx> ^pretty much anyway
[14:49] <hggdh> :-)
[14:50] <hggdh> run a dpkg -l ntp\* | grep ^ii
[14:50] <hggdh> you should see ntp, ntp-doc, and ntpdate
[14:51] <hggdh> (I hope)
[14:51] <Ampelbein> hggdh: hi there. https://edge.launchpad.net/~amoog/+archive/empathy-daily now has -idle in it.
[14:51] <xteejx> nope hggdh, just ntpdate
[14:51] <hggdh> Ampelbein, thank you, very much
[14:51] <hggdh> ah
[14:52] <hggdh> interesting. I *did* expect ntp to be installed
[14:52] <xteejx> obv not in jaunty as default hmm....
[14:52] <xteejx> !info ntp jaunty
[14:52] <ubot4> xteejx: ntp (source: ntp): Network Time Protocol daemon and utility programs. In component main, is optional. Version 1:4.2.4p4+dfsg-7ubuntu5.1 (jaunty), package size 476 kB, installed size 1192 kB
[14:53] <xteejx> oops
[14:53] <hggdh> there you go. I have it installed in all my machines, but I used to run my own time server
[14:53] <hggdh> !info ntpdate jaunty
[14:53] <ubot4> hggdh: ntpdate (source: ntp): client for setting system time from NTP servers. In component main, is optional. Version 1:4.2.4p4+dfsg-7ubuntu5.1 (jaunty), package size 64 kB, installed size 228 kB
[14:54] <hggdh> dat iz weird
[14:54] <xteejx> lol
=== bac` is now known as bac
=== asac__ is now known as asac
=== yofel_ is now known as yofel
[16:15] <lesshaste> hi.. I get lots of errors like [  196.328549] hda: status error: error=0x00 { }
[16:15] <lesshaste> [  196.328552] ide: failed opcode was: unknown
[16:15] <lesshaste> [  196.328556] hda: drive not ready for command
[16:15] <lesshaste> in dmesg
[16:15] <lesshaste> I can stop them by doing sudo hdparm -w /dev/hda
[16:15] <lesshaste> but now I can't access an audio cs in the dvd drive
=== WelshDragon is now known as YDraigGoch
=== YDraigGoch is now known as YDdraigGoch
=== jgoguen_ is now known as jgoguen
=== Hellow_ is now known as Hellow
=== dyfet_ is now known as dyfet
=== WelshDragon is now known as YDdraigGoch