[09:48] hello === RAOF_ is now known as RAOF [10:17] #123305 has been closed in compiz and hardy, but it's "New" in Linux, I can't see a reason why. [10:18] bug #123305 [10:18] Launchpad bug 123305 in gambas "Please sync gambas (1.0.18-1) from debian unstable" [Wishlist,Fix released] https://launchpad.net/bugs/123305 [10:18] bug #123205 even [10:18] Launchpad bug 123205 in compiz "Wrongly placed maximized window with cloned display" [Medium,Fix released] https://launchpad.net/bugs/123205 [10:21] good morning! [10:21] morning. [10:21] mr-russ: the question is: why does this bug have an 'linux' task at all? [10:22] that does surprise me. [10:22] it was added without a comment [10:22] I don't know who/how it got put there. I'm not an lp expert yet. [10:22] and from a user without any further work [10:22] how do you know this stuff? [10:22] so my personal guess: it's spam [10:23] * mr-russ is jealous of the lp wizzardry [10:23] you can click on the very left arrow in the linux task row, [10:23] then the task expands [10:24] and you get a box saying who and when this task was created [10:24] how do you know which comments relate to it? [10:24] ah, filed by jerik [10:24] jurik even. [10:24] it was created an 2008-04-15 [10:25] and the last comment was on 04-11 [10:25] which actually closed this bug [10:26] I think it should be closed as well. Not 100% how to do it except change the status to invalid for Linux. [10:26] so I suggest "Incomplete" and ask jurik for more details, [10:27] why did he choose to open a new task, etc. [10:28] it's not listed on the his bugs page either. [10:29] thekorn: is there somewhere a list which explains the functions of python-launchpad-integration? [10:29] mr-russ: because he is not subscribed, assigned; he just created a new task [10:30] qense: I dont't know python-lp-integration is not related to python-launchpad-bugs [10:31] oh [10:31] I meant the bug thing :P [10:31] my bad [10:31] I must say Linux is a BAD package name for the linux Kernel. [10:31] why? [10:31] What's wrong with Linux Kernel? [10:32] whenever I think linux, I think OS. Maybe others don't. [10:32] but linux is not an OS [10:32] it's the kernel [10:32] I'd add any but to the Linux package as my system isn't doing what I expect. [10:32] Ubuntu is an OS using Linux/GNU [10:32] qense: the bug part is here: https://wiki.ubuntu.com/BugHelper/Dev/python-launchpad-bugs/Bug [10:32] thnx [10:32] you're the one who wrote all this? [10:32] Unfortunately that is technically correct. But users don't always see it that way. I'll adjust my thinking accordingly though. [10:33] well, I think we shouldn't teach users to keep thinking in a wrong way [10:33] we should learn them to think right :) [10:34] qense: https://wiki.ubuntu.com/BugHelper/Dev has an ovverview of all docs [10:34] thanks [10:34] I'm going to rejoin this channel, I accidentatly detached it from the tablist :P [10:34] back [10:37] hmm, reading the bugsquad ML; I really do not like this 'DON'T touch my/our bugs' discussion... [10:38] I'm also trying to work out how to set importances for bugs, I've read the Importance wiki page. I assume it's a little bit of "just knowing". [10:39] nah, I think they should use other statusses [10:39] but I've made myself clear in my mails :) [10:39] we can't smell if the bug is theirs [10:41] right, good point, I think I will reply to this thread too [10:41] thekorn: where are the bitesize bugs of bughelper gone! [10:41] it's bugless! [10:44] ;) [10:44] bugless is not true, but maybe no easy one to fix [10:45] but if you have any questions, feel free to ask me [10:45] ok === qense is now known as qense|lunch [12:11] morning === qense|lunch is now known as qense [12:15] hell afflux [12:15] hi qense [12:15] hell :P [12:15] waaaah :) [12:15] hello* [13:12] hi [13:12] who use kazehakaze web browser ? have you got a crash with GTK error when you want to enter in setting menu? [13:17] s/kazehakaze/kazehakase === gnomefre1k is now known as gnomefreak [13:25] narcan: is ther a bug on it? [13:25] s/ther/there [13:25] i just find it [13:25] but its not really the same [13:25] https://bugs.launchpad.net/ubuntu/+source/kazehakase/+bug/173375 [13:25] Launchpad bug 173375 in kazehakase "kazehakase crashed with SIGSEGV in gtk_tree_model_get_valist()" [Medium,Confirmed] [13:25] narcan: i will be back in a minute or 2 i just need steps to reproduce it [13:26] thanks [13:34] the bug seem to be fixed in the futur version [13:39] ok narcan what version of kaz are you running? [13:41] gnomefreak: 0.5.2 [13:41] narcan: how do you get it to crash [13:42] when i open setting menu [13:42] i have a GTK error [13:42] and kaz crash [13:43] ok let me see if i can reproduce this [13:43] oh yeah if you mena preferences [13:44] :) [13:44] it's good bug ^^ [13:46] latest release is 5.4 so we will have this in intrepid i will talk to the maintainer ans see what he thinks we should do maybe backport a working copy im not sure if this meets SRU [13:47] yes, i have also intrepid, i will test this bug on it, I come back i few minutes [13:49] the latest we have in any of our PPA's is 5.0 but i will ask him if he plans oon updating kaz [13:49] narcan: i am using intrrepid [13:49] -r [13:49] ok :) [13:51] it seems its imported from debian so onceits imported i will build it for hardy and see if it builds and either post it on PPA or get it backported [13:52] i am upgrading now to see that [13:53] ok maybe it will be a while. its the last of the packages we have that dependon xul 1.8 and i was hoping to drop xul 1.8 soonish as im sure he was aswell [13:53] :/ gdm don't want to start ^^ [13:56] i havent done any updates today but my upgrade went flawlessly (its not exactly ready to use you know :) [13:58] yes ^^ the sid import have just beginning [14:00] ok maybe xul support might be fixed, either we import from debian or i will build it with xul support and see how it goes but today is not a good day for working on xul [14:02] gnomefreak: ok thanks [14:02] :) [14:03] gnomefreak: you know new xorg? [14:03] what about it? [14:04] define new [14:04] 7.3 not really all that new [14:04] about configured device [14:04] where can i find the "configured" device conf file? [14:04] i hate this new xorg.conf... [14:05] you dont mean /etc/X11/xorg.conf do you? [14:05] in the xorg.conf you avec some section with "configured device..." [14:06] i think we can find it on other conf file? [14:06] not sure i havent played with xorg 7.3 kmuch i was away for > 3months [14:07] got back 1-2 days before hardy release [14:07] k [14:07] seeing as there havent been any x updates in intrepid your X should work as it did before upgrade [14:08] i think we got 2 driver updates but they were put into hardy as i recall [14:08] i made an upgrade with hardy CD [14:08] now finish it by doing net upgrade to grab packages you missed [14:08] having a mixed system is a good way to not be using it for a long time [14:09] ^^ === qense is now known as qense|backup === qense|backup is now known as qense|away === gnomefre1k is now known as gnomefreak [16:05] hey yo! [16:05] I'm trying to install 5-day-applet but [16:06] its showing some python-central dependency error [16:06] I'm on gutsy at this point... [16:07] ah [16:08] ahve you followed the instructions here: https://wiki.ubuntu.com/5-A-Day ? [16:08] and added all the repos needed? [16:15] yeap... [16:15] 3 repos for gutsy... [16:15] ok [16:15] what's the exact error message you get? [16:16] it's asking me for [16:16] Los siguientes paquetes tienen dependencias incumplidas: [16:16] five-a-day: Depende: python-launchpad-bugs (>= 0.2.27) pero 0.2.21 va a ser instalado [16:16] and if I try to install python-launchpad-bugs alone [16:16] python-central (>= 0.6.5) pero 0.5.15ubuntu2 va a ser instalado [16:17] I think this is a dependency bug [16:17] I'd report it at LP against python-launchpad-bugs and see what happens [16:19] ok that's what I've thought [16:19] I might have an answer [16:19] Just give me a minute [16:19] ok [16:20] anything for a bug less at LP [16:21] five-a-day will only work on Hardy+ [16:21] yeap.. I've just found that python-centrl is at hardy only. [16:21] ok [16:21] I've got to upgrade anyway. no prob [16:23] hi [16:23] hello === LucidFox_ is now known as LucidFox [16:26] hi [16:26] i get random freezes sometimes, no idea why please help [16:28] :( [16:28] you're using a laptop or computer? [16:28] what's the type of laptop, if you're using one [16:29] it's a pc [16:29] ok [16:29] what are the specs? [16:30] it's quiet new, quad core, 512mb 8800 gts gfx card, 4gb ram [16:30] bdmurray can I add the hardy requirement to the wiki page?? [16:30] seaq: I'm not the lead on five-a-day but that seems reasonable to me [16:31] ok.. I'll put it on there. [16:41] mohbana probably you can find some help at #ubuntu [16:41] the thing is, i don't have a clue why it's crashing, it's very _random_ [16:42] I'm guessing you have an Nvidia graphics card, if you are using the Nvidia proprietary driver it would be good to test w/o it. [16:49] if it gets freezed usually that's RAM problems, VIDEO problems, or CPU problems... overheating, unmatched bus speeds... Have you tested windows to check if it's a HW problem? [16:50] i never get a crash on windows vista 64bit (as in total system freeze) [16:52] Hmm.... I joined the group BugSquad but I still don't have the option of marking bugs as triaged... [16:52] hmm hard to tell but you could follow bdmurray suggestions ... [16:52] I believe that's up to bug-control group... [16:53] hrmm... That would be the group that I wanted to join then.... [16:58] first you must be bugsquad member and show your commitment and dedication in order to apply to bugcontrol [17:06] yes [17:07] there is an overview at the wiki page of ubuntu bugcontrol that shows you what the requirements are === pochu_ is now known as pochu [17:14] okay so I am on the right track then.... [17:22] I noticed in some bug reports there seems to be a template used (thanking the reporter for reporting the bug) and such... Is there a link to these templates? [17:22] something that I can go by then I reply to bug reports.... [17:22] err when [17:23] sectech: yes -> http://wiki.ubuntu.com/Bugs/Responses [17:23] great :) Thanks! [17:23] you're welcome [17:38] Boo === geser_ is now known as geser [17:40] hello [17:40] Hello qense [17:45] does anyone know if ati catalyst 8.4 will be included in ubuntu in the near future [17:45] ? === qense is now known as qense|dinner [17:56] wow a lot of new bugs are actually support issues [17:56] I never noticed that until now [18:11] Can anyone help me with Bug #195308 [18:11] Launchpad bug 195308 in linux-meta "unable to resolve host (dup-of: 32906)" [Undecided,Confirmed] https://launchpad.net/bugs/195308 [18:11] Launchpad bug 32906 in sudo "sudo fails if it cannot resolve the local hostname and no MTA is installed" [High,Fix committed] https://launchpad.net/bugs/32906 [18:12] I am recieving - sudo: unable to resolve host [18:13] I have gone through a number of setting changes... from hosts to resovl.conf, to so on and so forth... no dice [18:13] is there a true fix for this? [18:14] There is a package in the -proposed repository that will resolve that bug. [18:14] It is currently going through the SRU verification process. [18:14] yeah... well... that is great... [18:14] I can't get it though... hints I can't update [18:15] or resolve my host [18:15] even after changing my localhost line and so on ... [18:15] does your hostname match what is in /etc/hosts? [18:16] yup [18:16] could you pastebin the results of 'hostname' and your '/etc/hosts' file somewhere? [18:16] I can type hostname and it tells me the correct host name too! [18:17] I have been messing with the hosts file... [18:17] I have gone from [18:18] 127.0.0.1 localhost ... to 127.0.0.1 azuregate.mycomputervisions.local [18:18] hold on and I will paste it === qense|dinner is now known as qense [18:23] oh... my cheese whiz!!!!.... grrr... never mind... I found it.. [18:24] What was the problem? [18:25] bdmurray: Thanks for your advisement. It was a gathering of lost sleep and missing a simple period being in the way... grr... sorry... my fault [18:26] graphx_: no problem, I'm glad it is resolved [18:27] Iulian: I got impatient with the network gui.. so I was adjusting things myself... and in the advent of working with some of my settings in nano... I added more then what was needed... === sectech_ is now known as sectech [18:27] bdmurray: I have to learn to get more sleep... I actually feel like a grouch!!! lol sorry [18:29] graphx_: You should know what you're doing when editing such files. [18:29] graphx_: And yes, you should get more sleep. [18:30] bdmurray: anyone here have an idea if Ubuntu is working to bring together a SMB solution in the near future, besides the ones in thought on the sites community information. [18:31] Iulian: Well, I agree.. but this isn't the first time I have worked with the /etc files.. [18:31] If you know for sure that a bug is specific to the user and that it really doesn't reflect something that is broken, it should be converted to a question right? [18:32] Just confirming.... [18:32] probably what bug are you looking at? [18:32] 226561 [18:32] I converted it to a question... [18:32] bug 226561 [18:32] Launchpad bug 226561 in firefox-3.0 "Can't escape full screen mode" [Undecided,Invalid] https://launchpad.net/bugs/226561 [18:33] Pressing F11 does indeed bring you out of full screen [18:35] oh.. which reminds me... Is there an existing bug for firefox and logmein.. (refreshes when clicking on items on screen) [18:35] I am going by the guidelines for marking triaging bugs... and I also take into consideration if the problem could be handled faster by the support group... [18:35] I just need a bit more confidence when redirecting lol... [18:38] Whether that one is a bug might be debatable but converting it to a question seems fine [18:38] Okay.... [18:39] It just appeared as more of a question, just not worded as such... Figured it would get looked at faster as a question [18:40] I think you gave them enough info that converting it to a question was almost unnecessary [18:41] It doesn't look like they knew that F11 would take you back [18:41] bdmurray, I'm limited in what I can do with it though... short of marking it as invalid. [18:42] I need assistance in writing bug-reports regarding the kubuntu 8.04 installation. [18:43] rbrunhuber: what kind of? [18:45] pjoul, maybe you could just listen to my installation problems and then help me to create bug reports out of it. [18:46] rbrunhuber: have you gone through existing reports? [18:46] pjoul: yes [18:46] nothing similar? [18:49] pjoul: nothing really similar. [18:49] you can start then :) [18:49] rbrunhuber: where are you experiencing an issue? [18:51] the partitioner and grub do not give the same names to the hdds [18:53] pjoul, bdmurray i installed kubuntu with alternate cd to encrypted lvm on second hdd on a asus p5w dh deluxe mobo. [18:54] rbrunhuber: does it not boot now? [18:54] pjoul, bdmurray: yes I'm writing from this machine! [18:54] jwendell: hi, I'm updating vinagre to 2.23.1 and I've noticed that src/vinagre-enum.[ch] don't have Copyright/License info. Would it be possible to add it for the next release? [18:54] vinagre-enums, that is [18:55] rbrunhuber: how did you repair it? [18:55] pochu_, these files don't belong to the tarball, they're generated at compile time [18:56] jwendell: really? I haven't built it yet and they are there :) [18:57] pochu_, then this is a bug :) [18:57] oh, then the question should be 'could you fix that bug for the next release?' ;-) [18:58] pochu_, sure, but, just in case I forget, could you please file a bug in bugzilla then? [18:58] alright, will be there in a minute [18:59] pjoul: booted in rescue mode installed (from alternate cd) installed grub and changed the all the groot and root names from (hd1,0) to (hd2,0) [19:01] rbrunhuber: and does the partitioner suggest correct name for the volume? [19:01] i installed on /dev/sdb and now boot from /dev/sdc [19:02] jwendell: reported, http://bugzilla.gnome.org/show_bug.cgi?id=531593 [19:02] Gnome bug 531593 in general "vinagre-enums.[ch] shouldn't be in the tarball" [Minor,Unconfirmed] [19:02] pochu_, fast guy :) [19:02] pjoul: this means the installer named the volume sdb which would be (hd1,0) [19:02] jwendell: i'll update the manpage to document the new debug option and create a patch in bugzilla too, but that will not be that fast :) [19:02] pochu_, ok :) [19:02] don't know these crazy names (1,0) (2,0) [19:03] what do they mean? [19:03] jwendell: gossip-cell-renderer-expander.[ch], should those be generated at build time too? :) [19:03] pochu_, nope, they belong to the tarball [19:04] alright, I think that's all! [19:04] woot! five-a-day-applet is now in Dutch! :P [19:07] pjoul: this is grubs way to count volumes. so in linux first scsi/sata partition is /dev/sda and in grub-speak (hd0,0) [19:07] pjoul: so /dev/sdb is in grub-speak (hd1,0) and /dev/sdc is (hd2,0) ... [19:07] qense, damned, wat about all these people not speaking dutch ? [19:08] ;) [19:08] well, there is a german version too! [19:08] :) [19:08] rbrunhuber: ah, okay - so the partitioner suggests wrong partition names? [19:08] and UK English [19:09] and grub installer only follows these [19:09] pjoul: I guess so [19:11] rbrunhuber: and how did you know that it should be /sdc instead of sdb? [19:13] because after i booted in rescue mode fdisk -l says my /boot partition is on /dev/sdc1 [19:13] pjoul: see above [19:16] rbrunhuber: it seems that autodetection of encrypted lvm partitions does not work perfect [19:17] pjoul: but all grub has to care about is /boot which is not encrypted and not on lvm?! [19:18] rbrunhuber: but partitioner could write bad fstab entries [19:18] and map /boot into incorrect partition [19:24] pjoul: http://pastebin.com/d6725c5b6 [19:24] hmm, is this original, non-edited? [19:25] pjoul: just shortened [19:25] rbrunhuber: and the types / quantities for devices you had did not change at all? [19:26] bdmurray: no everything original. [19:27] do you have any log files in /var/log/installer ? [19:29] bdmurray: yes for example /var/log/installer/partman [19:32] rbrunhuber: have you altered /boot/grub/device.map at all? [19:32] bdmurray: no [19:32] could you pastebin that? [19:34] bdmurray: what device.map or partman log? [19:34] device.map for now [19:36] bdmurray: just a question does grub touch the device.map if you reinstall it? [19:38] bdmurray: device.map: http://pastebin.com/d2b05b8b1 [19:40] bdmurray: device.map is much older than all the stage* files so should be the original [19:41] Could you report a bug about debian installer include all of /var/log/installer/ , device.map, /etc/fstab, and what you've told us here? [19:42] that'd be debian-installer [19:42] bdmurray: just to confirm this all logfiles in /var/log/installer are from 21:27 and device.map is from 21:26 [19:42] right, device.map was generated during the installation process [19:47] bug #226992 [19:47] Launchpad bug 226992 in ubuntu "gnome-mouse-properties > accessibility is inaccessible" [Undecided,New] https://launchpad.net/bugs/226992 [19:48] could someone take a look at that and tell tell me what that should be marked as.... a little unsure about that one. [19:48] I'm not quite sure if that would be considered a bug or not... [19:48] you have to enable accessibility first, then the reporters issue works. [19:50] sectech: more like a wishlist, the reporter is saying that the checkbox should activate the accessibility too [19:51] sectech: assign it to gnome-control-center, i'll change the importance to wishlist for you [19:51] pedro_, Okay thanks :) [19:51] sectech: thanks you for helping ;-) [19:52] Not a problem... This seems to be an area that I enjoy... [19:53] I may not be able to fix the bugs, but I figure I can at least help direct them to the proper place. [19:55] bdmurray: should i report the bug against the debian installer project? [19:55] pedro_, can you also wishlist bug 227027 and let me know who to assign it to? [19:55] Launchpad bug 227027 in ubuntu "Add pywebkitgtk" [Undecided,New] https://launchpad.net/bugs/227027 [19:55] rbrunhuber: the debian-installer package in ubuntu [19:55] I'll find a url for you [19:56] https://bugs.launchpad.net/ubuntu/+source/debian-installer/+filebug [19:56] bdmurray: thanks, i know my way around in lp [19:56] Okay, there is sometimes confusion between projects and packages [19:57] sectech: sure, do the other part as described here in the meantime https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages [19:58] change title, add a tag [19:59] okay [20:02] pedro_, so you want me to add the "needs-packaging" tag? What would you recommend I add to the title? [20:02] I am still fairly new at this... [20:04] oh... "please sync package from debian " where packagename is the package you would like to see. [20:04] sectech: just look at the first part of the doc for example reports [20:05] sectech: title should be [needs-packaging] package name [20:06] and yeah add that tag to it [20:06] k [20:11] bdmurray: hi, sorry for breaking the py-lp-bugs in the bughelper-dev PPA [20:12] will create a new upload in a few hours [20:14] Done... hopefully I did that right === pochu_ is now known as pochu [20:44] If I think a bug requires more information, and I ask probative questions to get that information it would be appropriate to mark the bug as incomplete right? [20:45] sectech: yes, you're right mark it as incomplete [20:45] pedro_, then when I get that info and it looks like a complete bug report I could get someone from the bugteam to mark it as triaged? [20:46] I have well over a month where I can dedicate quite a bit of time looking at bugs [20:46] sectech: you can mark it as Confirmed if you think that there's enough information [20:46] and later on ask here for someone to review it and mark it as triaged [20:47] great :-) [20:47] Okay, I'll have to keep a list then.... or just look in my own bug list... [20:47] I've got a question about python-launchpad-bugs, is this the best place to ask? [20:47] or subscribe yourself to it [20:47] Hopefully after proving myself I can be eventually granted the privilege of marking them myself? [20:48] sectech: yes sir you're correct [20:48] LaserJock: I know a fair bit about it [20:48] I kinda like doing this, I did a lot of QA work before.... [20:48] I'm trying to pull out what release a specific task is targeted for [20:49] so far .milestone and .target don't give me that [20:49] bug.infotable and then task.targeted_to [20:50] ah, beautiful [20:50] task.milestone too [20:51] milestone doesn't give me release targets [20:53] Okay, if you want release targets then it is task.targeted_to [20:54] One thing to keep in mind is that when a release is targetted it becomes targetted for every task [20:54] huh? [20:54] maybe we aren't talking about the same thing [20:55] if you look at bug 204775 [20:55] Launchpad bug 204775 in evolution-data-server "selecting gnome panel intlclock causes top bar and many other things to not respond" [High,Fix released] https://launchpad.net/bugs/204775 [20:55] you'll see it is targetted to Hardy for both affected Ubuntu packages [20:55] right [20:56] so depending on what you are doing if you have a bug affecting multiple sourcepackages you might run into some issues [20:56] so when somebody nominates it for a release you get a task for each of the packages? [20:57] that's correct nominations are not package specific [20:57] well that's pretty crappy [20:57] doesn't affect what I'm doing, but it doesn't make a lot of sense to me [20:58] I guess you can go back and mark one Invalid if you needed to [20:58] bug 215728 is a better example [20:58] Launchpad bug 215728 in xulrunner-1.9 "[MASTER] Committing to urlclassifier3.sqlite causes excessive CPU usage and disk I/O" [High,Fix committed] https://launchpad.net/bugs/215728 [21:00] fun [21:00] in this case I'm just looking for what Releases tasks have been targeted too [21:01] I'm writing an SRU tracking script [21:01] so I just want to know what release an SRU is targeted for and which ones have not been targeted [21:08] What package does ACPI problems get put in? The linux-source- package? In reference to bug 227007 [21:08] Launchpad bug 227007 in ubuntu "Cannot hear audio after suspend" [Undecided,Incomplete] https://launchpad.net/bugs/227007 [21:10] if someone could review and flag that one as triaged that would be great too [21:17] sectech: the correct package is just 'linux' since it is about the Hardy kernel [21:18] Okay... [21:18] kernel bugs used to belong to linux-source- but for hardy forward we are using 'linux' [21:20] bdmurray, Alright.... I marked 227007 as confirmed as per what pedro_ told me to do, it probably should be marked as triaged though [21:21] I've Triaged it and assigned it to the ubuntu-kernel-acpi team [21:23] um, I'm not so sure it has anything to do with acpi [21:23] I would need the codec info (from /proc/asound/card0/codec*) to look further [21:24]