[00:01] <nailora> apport-gtk could display something like "hey there... unfortunately i was told that program you wanted to used has just crashed. you can file a bug report on launchpad (without proper retrace) by clicking *HERE*. there is a core file containing further info - click *HERE* to save it or *HERE* to retrace it (requires gdb and debug packages installed, but helps the ubuntu developers a lot)"
[00:09] <BUGabundo> nailora: to much info for most of the users
[00:09] <BUGabundo> LP retracers are able to do 50% of the job
[00:09] <bdmurray> BUGabundo: keep in mind only devel users would see that
[00:10] <BUGabundo> if it fails, then devs request powerfull users to debug it
[00:10] <BUGabundo> yes bdmurray, but still, after beta, *we* get common users, not advanced ones
[00:10] <BUGabundo> and apport still fires a but
[00:10] <BUGabundo> *bit
[00:14] <imachine> I actually think apport could be even easier, well, launchpad could.
[00:14] <imachine> since it asks you about things at times like how would you describe a bug, etc., sometimes requiring a bit more professional a description, than the user can provide.
[00:15] <imachine> overall it;s not bad, but it's confusing; but that seems more of a launchpad issue.
[00:15] <BUGabundo> imachine: that's why we have triage team
[00:15] <BUGabundo> users that go around those bugs, and ask (new) users what they need to do to improve the bug
[00:16] <imachine> k
[00:16] <imachine> yes, that's useful!
[00:16] <imachine> if it works and works good, it's np.
[00:16] <nailora> you would have to think about it a bit. you could hide it in "advanced" section. however personally i would much more likely provide a properly retraced report if it was a one-click thing. ... right now i click "report bug" but if i had the chance i would let apport save the core, download&install the debug-packages and upload the generated backtrace. but until a few minutes ago i did not even know how to get a core to file to give to gdb 
[00:17] <nailora> thinking about the core files, i probably threw away quite a lot of good quality material
[00:18] <nailora> i think apport made it a lot easier to provide quite useful bug reports, but if it was just as easy to report even better reports that automatically include a proper retrace why would you want to NOT have this?
[00:22] <imachine> more options confuse people. imho.
[00:28] <andresmujica> hi all, is there a way to automatically undupe some bugs and let them as they were at a certain date?  someone marked a bunch of BT bugs that i don't really see related between them..
[00:32] <BUGabundo> andresmujica: not that I know of. maybe ask in #launchpad or ML ?
[00:32] <bdmurray> andresmujica: I could probably help with that.
[00:33] <hggdh> andresmujica, not automagically reverting the bugs to the previous state they were, no
[00:33] <andresmujica> bug #318465
[00:33] <hggdh> but the master has spoken...
[00:33] <bdmurray> But you could script unduping and invaliditing them.
[00:33] <andresmujica> maybe i wrong or missing something but all the those bugs marked as dup aren't really dupes from that bug...
[00:34] <andresmujica> i'm unmarking manually.. at least the ones that seemed to be worked on..
[00:34] <andresmujica> all were marked the 04/04/09
[00:35] <bdmurray> andresmujica: were you going to wait for a response first?
[00:36] <andresmujica> well , there are some that were worked at a different metabug, so i'm checking now those..
[00:36] <andresmujica> and for the rest i'll wait.
[00:37] <andresmujica> hmppff..
[00:38] <andresmujica> maybe i won't... let me finish the check..
[00:42] <BUGabundo> one more user expereincing exaclty the same crashs as me.... very very strange... and just a week to RC :(
[00:52] <BUGabundo> ogasawara: ping
[00:52] <BUGabundo> are you still around?
[00:57] <BUGabundo> bdmurray: ping
[00:57] <BUGabundo> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/359051/+activity
[00:57] <BUGabundo> why did you mark it against xorg?
[00:59] <bdmurray> drm:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 ?
[01:00] <BUGabundo> ok
[01:00] <BUGabundo> since the users descrived similar system freeze as I did on bug 359231
[01:12] <andresmujica> the vblank_counter message is similar what's described in bug 341363
[01:12] <andresmujica> the disabled pipe 0 is part of the message, florian described a method to repeat it.
[01:13] <andresmujica> i'm having those messages and the desktop freeze too... :( got to ssh and sudo reboot the laptop
[01:15] <andresmujica> but i don't get the kernel panic as bugabundo
[01:15] <BUGabundo> :(
[01:15] <BUGabundo> I rather not have it either
[01:37] <andresmujica> bluetooth is an area that needs a lot of love...
[01:37] <BUGabundo> yep
[03:05] <cowbellemoo> Would bug 358947 be a dupe of 336158?  Or does the rt version of the kernel make it a separate issue?
[03:06] <BUGabundo> bug 336158
[06:29] <charles_m> Hello...
[06:32] <Hew> charles_m: Hi
[06:36] <Hew> charles_m: you can file bugs at https://bugs.launchpad.net/ubuntu/+filebug
[06:36] <charles_m> ok, thanks!
[06:36] <Hew> charles_m: Any other questions, feel free to ask :-)
[10:18] <paddy2706> hy everyone, i just upgraded my jaunty machine and i get a udev error, for udev 141-1: http://paste.ubuntu.com/148791/
[10:19] <imachine> no probs here
[10:19] <imachine> try reinstalling udev?
[10:20] <imachine> dunno :)
[10:27] <paddy2706> i tried reinstalling udev 140-2 and 141-1 but same result
[10:29] <paddy2706> from what i found online, my computer wont boot any more, because udev wouldnt populate the devices
[10:38] <savvas> paddy2706: try dpkg-reconfigure udev
[10:39] <paddy2706> /usr/sbin/dpkg-reconfigure: udev is broken or not completely installed
[10:39] <savvas> er..
[10:39] <savvas> wanna try something *really* risky? :)
[10:40] <paddy2706> maybe ? ;)
[10:40] <savvas> you have the udev packages handy?
[10:40] <paddy2706> i have udev 140-2 and 141-1
[10:41] <savvas> paddy2706: ls -l /var/cache/apt/archives/udev_141-1_*.deb
[10:41] <savvas> what does that show?
[10:41] <paddy2706> -rw-r--r-- 1 root root 337690 2009-04-09 03:05 /var/cache/apt/archives/udev_141-1_amd64.deb
[10:42] <savvas> ok great
[10:42] <savvas> you're in recovery/root mode now?
[10:42] <paddy2706> no im in normal user mode i havent rebooted yet
[10:42] <savvas> ok
[10:43] <savvas> I have never tried this, but here goes: sudo dpkg -P --force-all udev; sudo dpkg -i /var/cache/apt/archives/udev_141-1_amd64.deb
[10:43] <savvas> it's a one liner
[10:44] <paddy2706> ok now i have a different message
[10:44] <paddy2706> Behalte »local diversion of /sbin/udevadm to /sbin/udevadm.upgrade« bei
[10:44] <paddy2706> Richte udev ein (141-1) ...
[10:44] <paddy2706> invoke-rc.d: unknown initscript, /etc/init.d/udev not found.
[10:44] <savvas> do: ls -l /etc/init.d/udev
[10:45] <paddy2706> lrwxrwxrwx 1 root root 12 2008-12-17 10:50 /etc/init.d/udev -> udev_nocache
[10:45] <savvas> that's weird
[10:45] <savvas> paddy2706: sudo rm -f /etc/init.d/udev; sudo aptitude reinstall udev
[10:47] <savvas> paddy2706: still there? :)
[10:47] <paddy2706> yeah - libindicate0 was removed but i still get the same result
[10:47] <paddy2706> invoke-rc.d: unknown initscript, /etc/init.d/udev not found.
[10:48] <savvas> wheow you scared me :p
[10:48] <savvas> ok try: sudo dpkg-reconfigure udev
[10:48] <paddy2706> /usr/sbin/dpkg-reconfigure: udev is broken or not completely installed
[10:49] <savvas> I can give you my init
[10:49] <savvas> hold a sec
[10:49] <paddy2706> wait a sec
[10:49] <savvas> ok
[10:49] <paddy2706> i just checked the contents of /etc/init.d
[10:49] <paddy2706> and the the symlink udev points to udev_nocache. that does not exist
[10:50] <paddy2706> but i have a udev.dpkg-new
[10:50] <paddy2706> that should probably be the right file
[10:50] <savvas> md5sum /etc/init.d/udev.dpkg-new
[10:50] <paddy2706> 71b8a340eacc3df5f99561c3cf4b2853  udev.dpkg-new
[10:50] <savvas> that's the one :)
[10:51] <savvas> sudo mv /etc/init.d/udev.dpkg-new /etc/init.d/udev
[10:51] <savvas> then sudo aptitude reinstall udev
[10:52] <paddy2706> that was it
[10:52] <paddy2706> thanks a lot :)
[10:52] <savvas> cool :)
[10:52] <savvas> you can continue "sudo aptitude dist-upgrade" I think
[10:53] <paddy2706> you just saved my day. thanks a lot
[10:54] <savvas> np :)
[17:25] <dtchen> for people still experiencing audio glitches (not mute issues!), i'll have test kernels up shortly on kernel.ubuntu.com/~dtchen
[17:25] <dtchen> (bug 345627)
[17:25] <BUGabundo> dtchen: how about video slowdown?
[17:25] <BUGabundo> is it audio?
[17:26] <BUGabundo> mplayer complains about it
[17:26] <dtchen> what's the complaint from mplayer?
[17:27] <dtchen> "your system is too slow"... ?
[17:27] <BUGabundo> system is too slow
[17:27] <BUGabundo> might be drivers or audio related
[17:27] <BUGabundo> this is a fast machine
[17:27] <BUGabundo> and was working fine 3 weeks ago
[17:27] <dtchen> well, these changes are sync-related, so you should try them
[17:27] <BUGabundo> now ALL video players are slow
[17:27] <BUGabundo> ok
[17:27] <BUGabundo> will do
[17:28] <BUGabundo> feed back on bug or irc?
[17:31] <dtchen> on the bug, please
[17:31] <dtchen> irc is fine in addition, but please at least on the bug
[17:34] <BUGabundo> ok
[17:34] <BUGabundo> sure dtchen
[18:45] <BUGabundo> dtchen: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/345627/comments/25
[18:45] <BUGabundo> mplayer presented me with this:
[18:45] <BUGabundo> [pulse] working around probably broken pause functionality, see http://www.pulseaudio.org/ticket/440
[19:00] <dtchen> BUGabundo: bug 440 is already fixed
[19:00] <BUGabundo> some one forgot to tell mplayer devs about it
[22:13] <bcurtiswx> bdmurray: i am handling a bug that seems to be as a wishlist item, but the reporter just told me that the brainstorm people told them it was a bug.  bug #359740 .  How should I handle this?
[22:16] <bdmurray> bcurtiswx: I think wish list is correct and suggesting it be forwarded upstream would be best.  I'm not certain hal is the correct place for it though.
[22:17] <bcurtiswx> bdmurray: ok, will do about the forward.  What controls the volume now?
[22:28] <bcurtiswx> bdmurray: http://packages.ubuntu.com/jaunty/gnome-volume-control-pulse is the only thing i could find that seems remotely related
[22:58] <cowbellemoo> I was told that putting the ubuntu version (ex Jaunty) in a bug report summary would be confusing later on in the next cycle.  Can anyone help me understand why?
[23:01] <savvas> cowbellemoo: I use: apt-cache policy packagename
[23:01] <savvas> it shows the release you're using and the package version and where you got it from :)
[23:03] <cowbellemoo> Hmm okay, so named releases aren't as exact/helpful?
[23:04] <hggdh> cowbellemoo, apt-cache policy gives us more than just the version
[23:05] <hggdh> and, sometimes, the versions change but the bug stays
[23:06] <cowbellemoo> hggdh, savvas Thanks
[23:06] <hggdh> welcome
[23:26] <mehall> hey all
[23:27] <mehall> I'd like to ask that bug #292155 be made medium importance?
[23:27] <dtchen> are you sure it's not a dupe?
[23:27] <mehall> I'm going to get jaunty daily, test a newer kernel, but there's a few that have the issue
[23:28] <mehall> dtchen: the bug has been around since november
[23:28] <mehall> no reported dupes
[23:28] <dtchen> it's likely a dupe of some other bug, then. need to check upstream and other distros' bug trackers.
[23:29] <mehall> okay...
[23:29] <dtchen> sorry, i can't do the legwork now, as i'm fixing audio bugs.
[23:29] <mehall> audio > me needing acpi, that I can handle