[00:00] <twl> If I don't find anything, I'm gonna FAX it to canonical tomorrow. *eg*
[00:01] <secretlondon> i'm still looking
[00:03] <secretlondon> twl https://translations.edge.launchpad.net/ubuntu/hardy/+lang/de is where german translation happens
[00:04] <secretlondon> twl https://translations.edge.launchpad.net/~ubuntu-l10n-de are the translators
[00:06] <secretlondon> twl https://edge.launchpad.net/~ubuntu-l10n-de
[00:06] <twl> Thank you. I bookmarked it and try to contact people tomorrow. Hopefully I that can be resolved before the release.
[00:06] <secretlondon> cool :)
[00:06] <secretlondon> the last link seems to be the best
[00:08] <twl_> re. sorry, that was my 24h-disconnect.
[00:09] <twl_> very well. Maybe I can even add something to the community thus- My English could be better, but it's definitely good enough to translate things into my mother tongue.
[00:10] <twl_> thank you again and good night...
[04:43] <JohnPhys> kees:  are you around?  Did you get a chance to look at Bug #195052?
[06:18] <danage> saivann: you here?
[06:21] <saivann> danage : hi
[06:21] <danage> hi... i followed up on our bug reports
[06:23] <danage> i wonder what is happening, sebastien complained it as a duplicate but noone changed the inaccurate bug description of the "original" bug
[06:25] <saivann> danage : I know, I sent a mail to Sebastian himself after I got his comment to ask him to update the bug description and he answered me to post my request in the bug rather than asking him, but no one changed the description yet
[06:26] <danage> i guess considering the amount of bugs, strictly following procedure is a must, so i understand his reaction
[06:26] <saivann> danage : Actually, I don't really know what I can do, I have no "super powers" on the gnome bugzilla bug tracker
[06:26] <danage> yeah, i saw your comment
[06:26] <danage> there seem to be some pretty serious issues with gvfs left, i hope they get fixed before the release.
[06:26] <saivann> danage : Of course, he did not set this bug as a duplicate without reasons, that's good job, however updating the title would probably help
[06:28] <danage> yeah i guess these kinds of things happen. we didn't really become aware the bugs might be related until late and some serious poking around
[06:28] <saivann> danage : Me too :) But since I have almost no programming skills, I don't know how hard are bugs to fix so I respect developers who work very hard, taking time and doing a good job is already what they do :)
[06:29] <saivann> danage : You asked people to look at a bluetooth bugs yesterday, but I answered you 2 minutes after you left the channel, what was that bug?
[06:29] <danage> yep... and the time before a release... they must be extremely busy
[06:29] <danage> ah :)
[06:29] <saivann> Hehe, extremely :)
[06:30] <danage> my bluetooth mouse, it disconnects after a couple of minutes
[06:30] <danage> but i know nothing of the bluez architecture in order to provide some information. a couple of other people reported similar issues, and i marked some duplicates on launchpad already
[06:30] <saivann> danage : Really? I have a bluetooth mouse here too, but I've never seen a mouse work like that! Your mouse disconnects regularly at a fixed time interval?
[06:31] <danage> saivann: if it is fixed, i do not know. i know that it doesn't correlate with the screensaver being activated
[06:32] <saivann> danage : I mean, does your mouse disconnect every "" minutes?
[06:33] <danage> yeah, i don't know if its always the same amount of minutes, though
[06:33] <saivann> danage : How did you configure the bluetooth mouse? Did you edit some conf. files or you just used the bluez-gnome applet in the right-top border of your screen to connect your mouse?
[06:34] <danage> good question. i activated hidd, because it is disactivated by default. other than that, i only used the applett
[06:34] <saivann> danage : Great that you started to triage bugs :) Be always careful when you set bugs as duplicates, we must always be sure that these are really duplicates
[06:34] <danage> i am pretty sure on this one
[06:35] <danage> https://bugs.launchpad.net/ubuntu/+source/bluez-utils/+bug/197549
[06:35] <saivann> danage : That might be the problem.. Actually, the only thing I did in my case was to connect my mouse using bluez-gnome, and it works flawlessly, even when the mouse die because of low batteries, it automatically reconnect when the mouse ressurect
[06:36] <danage> what might be the problem? hidd has to be activated, right?
[06:36] <saivann> danage : I'm not a expert with bluetooth, so I don't have the answer to this. So far what I know is that using bluez-gnome without anything else always worked
[06:38] <danage> i think that is what i am using, too
[06:41] <saivann> danage : According to http://doc.ubuntu-fr.org/telecommande_bluetooth, it looks like hidd doesn't need to be enabled since Gutsy. I looked at my /etc/default/bluetooth and I have HIDD_ENABLED=0
[06:42] <saivann> danage : And I use a bluetooth mouse currently
[06:42] <saivann> danage : It might be a bug or a misconfiguration problem
[06:46] <danage> saivann: thank you! i will take a shot restoring the original config
[06:47] <saivann> danage : I'm also looking at this too because I don't even know how to connect my mouse with the new bluez-gnome P
[06:47] <saivann> :P*
[06:48] <saivann> Oh I got it, wonderful
[06:49] <danage> is there any other config file besides /etc/default/bluetooth
[06:49] <danage> hidd/hci config?
[06:50] <saivann> danage : I don't think so, but I might be wrong
[06:51] <saivann> danage : /etc/bluetooth/hcid.conf ?
[06:51] <danage> yes
[06:52] <danage> saivann: we should maybe continue this privately so as not to spam
[06:59] <saivann> well..
[09:48] <DOOM_NX> good morning :)
[09:50] <jarlath> Good morning!
[09:51] <jarlath> Can someone tell me what package I should tag this as
[09:51] <jarlath> https://bugs.launchpad.net/ubuntu/+bug/219382
[09:51] <ubotu> Launchpad bug 219382 in ubuntu "fsck not run on boot if on battery power" [Undecided,New]
[09:51] <jarlath> I'm guessing 'linux' as it occurs before the X system gets loaded.
[09:52] <jarlath> But I just want to double check.
[10:57] <hggdh> jarlath: this is initscripts
[10:58] <jarlath> thanks hggdh
[10:58] <hggdh> jarlath: install the apt-file package
[10:58] <hggdh> then you can run 'apt-file search /etc/init.d/checkroot.sh'
[10:58] <hggdh> and it will tell you what package has the file
[10:59] <hggdh> and, of course -- welcome, glad I was able to help
[10:59] <jarlath> hggdh: wow, that's great. I'll certainly do that!
[11:02] <jarlath> hggdh: I'm searching for the package 'initscripts' but launchpad can't find it.
[11:03] <hggdh> ii  initscripts               2.86.ds1-14.1ubuntu45     Scripts for initializing and shutting down the system
[11:03] <hggdh> I know it is there, let me have a quick look
[11:04] <hggdh> huh
[11:04] <jarlath> Thanks. I just found it in packages.ubuntu.com but it's not on launchpad for some reason.
[11:04] <hggdh> sorry, I ended up making the change for you. Here's how
[11:04] <hggdh> open the bug, and click on the down-arrow for the 'affects' package
[11:05] <jarlath> Ah, sysvinit.
[11:05] <hggdh> you will get a new pane, where you can enter the full package name (if you know it), or part of it
[11:05] <jarlath> Yes, that's where I chose to search.
[11:06] <hggdh> so when I entered 'initscripts', LP automagically stated this was a binary package, the source package being sysvinit (and updated the bug)
[11:06] <jarlath> Ah, okay.
[11:06] <hggdh> sorry for jumping the gun
[11:06] <jarlath> Not at all. Thanks for your help!
[11:07] <hggdh> welcome
[11:40] <askand> bug 25931 is not fixed but it says fix released.
[11:41] <ubotu> Launchpad bug 25931 in dbus "Failed to initalize HAL." [High,Fix released] https://launchpad.net/bugs/25931
[12:08] <askand> Or should I file that in a different bug report?
[12:20] <afflux> Nafallo: bug 205973 seems to be an easy one, do you think we need this for hardy?
[12:21] <ubotu> Launchpad bug 205973 in gajim "gajim show popup with html entities escaped too many times" [Undecided,New] https://launchpad.net/bugs/205973
[12:38] <afflux> anyone knows bugs about /etc/apt/sources.list being replaced by contents of /etc/fstab?
[12:39] <hggdh> huh?
[12:40] <afflux> hggdh: bug 219519
[12:40] <ubotu> Launchpad bug 219519 in update-manager "After update /etc/apt/sources.list error" [Undecided,New] https://launchpad.net/bugs/219519
[12:43] <hggdh> afflux: yes, we need to know what was installed on this update... either a package error, or a filesystem corrupted, or user error
[12:43] <afflux> yep
[12:43] <hggdh> (I tend to the last)
[12:43] <hggdh> but, just in case, we need to follow up
[12:43] <afflux> I think so too, because it's so odd :)
[12:43] <hggdh> :-)
[12:44] <james_w> I hope it wasn't a symlink to /etc/fstab, otherwise he'll have trouble booting
[12:44] <hggdh> we will know in a few, I guess...
[12:45] <afflux> If he does not come back, it was one :)
[12:52] <hggdh> and he will come back spitting mad...
[12:53] <askand> Hi! I just have a quick question, ﻿bug 25931 is not fixed but it says fix released.. Should I file a new bugreport on that or contribute to the old one?
[12:53] <ubotu> Launchpad bug 25931 in dbus "Failed to initalize HAL." [High,Fix released] https://launchpad.net/bugs/25931
[12:57] <hggdh> askand: open a new bug, and refer to this one (and refer to this comment: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/25931/comments/141)
[12:57] <ubotu> Launchpad bug 25931 in dbus "Failed to initalize HAL." [High,Fix released]
[12:58] <hggdh> askand: and, of course, follow the instructions Martin points to
[12:59] <askand> ﻿hggdh: thanks
[13:07] <askand> ﻿hggdh: I dont really know how to save text when running a livecd with HAL out of order really..
[13:11] <hggdh> askand: yes, this is a bit more complex...
[13:11] <hggdh> askand: an option is to take a picture (if you can)
[13:11] <hggdh> the problem is otherwise we do not have enough data to work on
[13:14] <askand> ﻿hggdh: Ill try that
[13:14] <askand> ﻿hggdh: But I already knows what causes it I think...
[13:14] <askand> ﻿hggdh: If I blacklist saa7134_alsa I do not get that error
[13:14] <hggdh> askand: thanks for helping
[13:15] <hggdh> askand: then -- if you can indeed boot blacklisting this module, state that in the bug
[13:15] <hggdh> after booting, try to load it, and see what happens
[13:15] <hggdh> this is good info
[13:17] <askand> ﻿hggdh: Im not really sure how to boot blacklist..do I add something in grub?
[13:18] <hggdh> ah, this is livecd... hold on, let me see if I can find something
[13:24] <Nafallo> afflux: naah. lets wait for the new upstream release.
[13:37] <hggdh> askand: I do not know how to block a dynamic module load from livecd, sorry.  But the saa7174-alsa has some options:
[13:38] <hggdh> MODULE_PARM_DESC(debug,"enable debug messages [alsa]");
[13:38] <hggdh> MODULE_PARM_DESC(index, "Index value for SAA7134 capture interface(s).");
[13:38] <hggdh> MODULE_PARM_DESC(enable, "Enable (or not) the SAA7134 capture interface(s).");
[13:38] <hggdh> askand: so, at least you can try enabling debug and disabling capture to see what happens
[13:39] <hggdh> you can also try #ubuntu+1 or the alsa channels
[13:49] <askand> ﻿hggdh: thanks ill try
[13:58] <afflux> Nafallo: alright
[14:48] <askand> Hggdh: Hi, I talked to you earlier about HAL-error. Could you take a look at this https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/219576 ?
[14:48] <ubotu> Launchpad bug 219576 in dbus "Failed to initialize hal" [Undecided,New]
[14:49]  * hggdh is looking
[14:50] <hggdh> askand: I do not understand what you mean by "I installed anyway"
[14:51] <hggdh> you did install on harddisk?
[14:51] <askand> ﻿hggdh: yes thats right
[14:51] <askand> ﻿hggdh: and then afterinstallation blacklisted that module
[14:51] <hggdh> so now -- if you do not blacklist the module -- you should have the same error, right?
[14:52] <askand> ﻿hggdh: I should have.. havent tried cause I was so happy it disappered :) but I try now
[14:52] <hggdh> :-)
[14:52] <hggdh> please do so -- if you get it again, then you can gather the truckload of data we need ;-)
[15:12] <askand> hggdh: hello again! This was strange, now Im not even able to boot when I have not blacklisted that module.. but as soon as I blacklist it my system boots.. And in the kernel before this one there is no need to blacklist the module
[15:14] <askand> ﻿hggdh:  https://bugs.launchpad.net/ubuntu/+bug/212221 It certainly looks like saa7134 module is the problem
[15:14] <ubotu> Launchpad bug 212221 in ubuntu "[hardy][2.6.24-15] Failed to initialize HAL (dup-of: 212271)" [Undecided,New]
[15:14] <ubotu> Launchpad bug 212271 in linux-ubuntu-modules-2.6.24 "2.6.24-15-generic: saa7134-alsa makes HAL to fail" [High,Fix committed]
[15:24] <askand> ﻿hggdh: There even seems to be a fix availble already from http://ppa.launchpad.net/stefan-bader-canonical/ubuntu/ :)
[15:28] <hggdh> askand: good find for the other bug -- make yours, then a duplicate
[15:29] <hggdh> askand: the fix is in a PPA -- so only use it if you need (PPAs are not supported), or if the bug comments state it should be used as a bypass (while it is not officially made available)
[15:31] <askand> ﻿hggdh: I dont really need it..I just wish to help make this bug disappear from the livecd :)
[15:33] <hggdh> askand: can you make your bug a duplicate of 212271, or you want me to do it?
[15:35] <hggdh> askand: I think it will make it to release...
[15:37] <hggdh> askand: also -- thank you for your work on this... all help is appreciated (too much to do ;-)
[15:40] <askand> ﻿hggdh: I will make it a dublicate :)
[15:40] <hggdh> thank you
[18:17] <jarlath> I think I may have assigned a bug to the wrong package. I assumed because it was a problem with swap, I assumed the kernel was the problem, but I forgot about the Wubi installer (which I don't know anything about). Anyone care to have a look?
[18:17] <jarlath> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/219349
[18:17] <ubotu> Launchpad bug 219349 in linux "Hardy H. RC1 wait so much on "Activating swapfile  swap..." on new instalation" [Undecided,Confirmed]
[18:58] <ffm> Do I report a problem that caused a broken install for me in ubuntu or in the spesific ubuntu package that caused the issue?
[18:59] <james_w> ffm: the specific package please.
[19:00] <ffm> james_w: phpbb2-conf-mysql, part of phpbb2. #218492
[19:00] <ffm> * bug #218492
[19:00] <ubotu> Launchpad bug 218492 in phpbb2 "Hardy Upgrade freezes on phpbb2-conf-mysql " [Undecided,New] https://launchpad.net/bugs/218492
[19:01] <ffm> I can't triage it as the reporter, but it caused me to have to reinstall from scratch.
[19:01] <james_w> thanks for reporting it
[19:02] <ffm> james_w: I've gone on a bit of a bug-reporting splurge, testing hardy is fun.
[19:02] <james_w> :-)
[19:03] <ffm> Sadly we're in RC and frozen like Tux in the winter, so very little will be changed.
[19:04] <james_w> yeah, it's unfortunate
[19:04] <james_w> do you have any more information on what was hanging?
[19:04] <james_w> if you install the package now does it work?
[19:05] <ffm> james_w: Yeah, but that was after I reinstalled.
[19:05] <james_w> so it's not easily reproducible?
[19:05] <ffm> james_w: Hold on, I'll retest.
[19:05] <james_w> that would make it hard to debug.
[19:05] <james_w> great, thanks.
[19:15] <mrooney> is there any way to debug freezes? twice yesterday the system locked up completely except that I could move the mouse around, but no keyboard, mouseclicks, not even ctrl+alt+backspace did anything
[19:15] <mrooney> I just had to hold the power button down until it turned off :[
[19:17] <ffm> mrooney: Did the magic sysreq key work?
[19:18] <mrooney> I have never had any luck with those, what is the magic key?
[19:19] <ffm> mrooney: http://en.wikipedia.org/wiki/Magic_SysRq_key
[19:19] <ffm> james_w: Uh, yeah, its reproducable.
[19:20] <ffm> james_w: I just tried to install, and the package installation hung. This could be an issue if, say, you were in the middle of a distro upgrade? (it should at least time out...)
[19:20] <james_w> mrooney: I've seen that as well, but I haven't had a chance to try and debug it yet
[19:20] <james_w> ffm: is it still hanging?
[19:20] <ffm> james_w: When I apt-get it, yeah.
[19:21] <james_w> ffm: but you've killed it now?
[19:21] <james_w> ffm: can you make it hang again and then try and find the guilty process?
[19:21] <mrooney> ffm: ooh, you have to hold ALT too!
[19:21] <james_w> ffm: "ps aux" will be a good place to start looking.
[19:21] <mrooney> I was doing the REISUB thing but not while also holding alt
[19:22] <james_w> mrooney: twice for me it was when opening a link in firefox from another application, where the page I was loading required authentication
[19:22] <ffm> mrooney: Mhm.
[19:22] <james_w> mrooney: does that match yours?
[19:23] <ffm> james_w: No, I havn't killed it.
[19:23] <mrooney> james_w: I feel like it was when using transmission, actually
[19:23] <ffm> james_w: In any case, I'm not going to reinstall gutsy, install the package, then try to break my install in my dist-upgrade. I think this is the same bug.
[19:24] <james_w> ffm: I'm sure it's the same problem, if you can find the offending process we can find out why it is hanging, which will make fixing it a lot easier
[19:24] <james_w> mrooney: ok, it's not that then.
[19:25] <ffm> james_w: Should I pastebin the output?
[19:25] <james_w> ffm: yes please.
[19:25] <ffm> james_w: http://paste.ubuntu-nl.org/63764/
[19:26] <james_w> ffm: ah, can you pastebin the output of "ps aux" please?
[19:26] <ffm> james_w: Oops, I ment to.
[19:27] <ffm> james_w: http://paste.ubuntu-nl.org/63766/
[19:28] <james_w> ffm: it's been trimmed, if you run "ps aux | cat" does it show the full command lines?
[19:28] <james_w> I guess it's 18933 though
[19:29] <james_w> what does "strace -p 18933" give?
[19:29] <ffm>  Process 18933 attached - interrupt to quit
[19:29] <ffm> read(0,
[19:29] <ffm> And no more.
[19:29] <james_w> cool, it's waiting for input on stdin
[19:30] <ffm> james_w: Ah, that's an easy fix.
[19:30] <james_w> from the ps output can you find the name of the script that it is running?
[19:30] <ffm> james_w: I just had to press "enter" and it started to unfreeze. However, that's not immediately obvious to the user.
[19:31] <james_w> no, and it shouldn't do that anyway
[19:31] <ffm> james_w: Yet it started to work after I pressed enter.
[19:35] <ffm> james_w: I've purged the package config and reinstalled. Still freezes, though this time on "Creating search_time column if it doesn't exist yet...
[19:36] <ffm> james_w: The script that it is running _now_ is "root     19310  0.0  0.0   3820  1300 pts/3    S+   14:34   0:00 /bin/bash /usr/bin/ucf --three-way /tmp/phpbb2.config.php.R19308 /etc/phpbb2/config.php
[19:36] <james_w> ok, thanks, can you add that information to the bug report please?
[19:37] <ffm> james_w: Ok.
[19:38] <james_w> I've seen this fixed elsewhere by changing it to "ucf --three-way --debconf-ok" and removing the </dev/tty
[19:39] <ffm> james_w: I've added a comment to bug 218492. Care to add that?
[19:39] <ubotu> Launchpad bug 218492 in phpbb2 "Hardy Upgrade freezes on phpbb2-conf-mysql " [Undecided,New] https://launchpad.net/bugs/218492
[19:45] <ffm> So, triaging is setting priority, no? What's the magic I need to do to be able to triage bugs? (There's no dropdown for priority in LP)
[19:46] <secretlondon> ffm triaging is getting the bugs to a state where they can be looked at by a developer
[19:46] <secretlondon> ffm you need to have experience of bug traiging to be accepted into the bug control team which can actually set priorities
[19:49] <ffm> secretlondon: Can I mark as "confirmed" bugs that I have reported if I have reproduced them in multiple systems and environments?
[19:49] <secretlondon> ffm no, others should confirm
[19:50] <secretlondon> but adding your experiments really helps
[19:53] <ffm> secretlondon: Ok, would you care to confirm my bug?
[19:54] <secretlondon> ffm I'd need to see if I can reproduce it, and I'm busy
[19:54] <ffm> secretlondon: Ok.
[19:54] <secretlondon> sorry
[19:55] <ffm> Anyone else care to confirm bug 219407 (firefox bug)? It seriously takes less than 20 seconds, and there may be cake.
[19:55] <ubotu> Launchpad bug 219407 in firefox-3.0 "REGRESSION: Firefox does not process some downloads properly" [Undecided,New] https://launchpad.net/bugs/219407
[20:02] <secretlondon> ffm: I'm not sure this is a firefox bug though
[20:02] <secretlondon> if you *save* it and then open in nautilus what happens? do you get offered a program to open it with?>
[20:06] <ffm> secretlondon: Yes.
[20:07] <ffm> secretlondon: It opens with gedit.
[20:07] <secretlondon> ok
[20:11] <secretlondon> i've set it as confirmed
[20:11] <secretlondon> but the ff people will know what extra info they need
[20:16] <ffm> secretlondon: Ok.
[20:16] <ffm> secretlondon: Thanks.
[20:17] <secretlondon> np
[21:31] <mrooney> james_w: oh boy I got the freeze again! when dragging a torrent into transmission, I believe
[21:32] <mrooney> though first I just tried it via firefox, by clicking and opening with transmission, but that did nothing. perhaps that actually caused it to eventually happen, and it IS related to yours
[22:14] <madmetal_spyros> hm.. anybody willing to help with hardy mess?
[22:20] <mrooney> madmetal_spyros: what hardy mess?
[22:24] <madmetal_spyros> i upgraded to hardy
[22:24] <madmetal_spyros> everything went fine
[22:24] <madmetal_spyros> and then restricted manager prompt me to install nvidia drivers
[22:25] <madmetal_spyros> after reboot i x couldnt start "fatal error no monitor found"
[22:25] <madmetal_spyros> i reinstalled xserver and then i could reach log in screen fine
[22:25] <madmetal_spyros> and now i can only enter in xterm failsafe more
[22:25] <madmetal_spyros> mode
[22:26] <madmetal_spyros> mrooney...
[22:28] <mrooney> madmetal_spyros: have you tried uninstallin the restricted drivers?
[22:29] <madmetal_spyros> when i booted without x before reinstalling xserver i removed the drivers
[22:33] <madmetal_spyros> and as i can see its a known bug for former releases
[22:33] <madmetal_spyros> https://bugs.edge.launchpad.net/ubuntu/+bug/136529
[22:33] <ubotu> Launchpad bug 136529 in gdm "Can't log in after upgrading" [High,Triaged]
[22:52] <afflux> good night