=== dwg_ is now known as dwg [00:56] * BUGabundo $ rsync -av --deleteafter /home/BUGabundo /media/bed/ === jjesse__ is now known as jjesse [04:01] Has anyone been affected by Bug #449888? [04:01] Launchpad bug 449888 in network-manager-applet "[karmic] network manager gnome does not remember wpa enterprise hidden network passwords over reboot, need to re-create network profile each time." [Undecided,New] https://launchpad.net/bugs/449888 [04:01] yes but just updated my system and not haaving that problem [04:05] jjesse, what are you running? [04:05] jbuncher: dell mini 9 w/ the broadcom driver [04:06] i was having some problems with WPA enterprise and WPA regular and now after updates it seems to be better [04:06] jjesse, I meant what release, but that's my fault for not clarifying. === micahg1 is now known as mciahg === mciahg is now known as micahg === NCommander is now known as NC|Mobile === NC|Mobile is now known as NCommander [07:50] good morning === porthose is now known as porthose|afk [08:18] hi i just joined the ubuntu bug squad... and waiting for a mentor any suggestions? [08:21] have you read the wiki page on how to triage yet, shankhs? [09:19] micahg: ya i read the process of triaging? [09:24] anybody online? [09:45] \quit [09:46] hggdh: (rather delayed) pong [10:06] hey guys [10:06] my laptop hotkeys doesnt work under 9.10, should i file a bug against hal or devicekit-power? === simon-o is now known as simon-o|lunch === simon-o|lunch is now known as simon-o === porthose|afk is now known as porthose [13:13] bulletproof x does not seem to work, where should i file a bug? [13:15] dns53, is that related to /etc/gdm/failsafeXServer ? [13:17] yes, bullet proof x is suppose to be a feature that has been in the last few releases where it will try and start x, if that fails it will start x with fail-safe options [13:17] x11-common might be a good option [13:17] in my case i did not have the nvidia kernel driver in my system (got broken somehow) and x would crash because it could not use the proprietary drivers [13:19] there have been some major changes to the boot process, X is started earlier, I am not sure bulletproof was covered [13:19] yeah it does not seem to be [13:24] is there a way of attaching specific log files with apport instead of the previous one? [13:43] is there a manual process to file bugs, the log files sent i need is from 2 reboots ago not the previous log file [13:43] dns53, ubuntu-bug should redirect you to the link for the bug report [13:44] yes but i will have log files where everything is working, so can i remove them when filing the bug? [13:48] yes [13:48] well, or at least attach the relevant ones [15:13] my laptop hotkeys doesnt work under 9.10, should i file a bug against hal or devicekit-power? [15:16] d3xter, there is something on the release notes about hal being dropped and how it would affect hotkeys setups [15:17] joaopinto: ok, thx [15:20] Boo [15:23] joaopinto: in the technicaloverview it says, that laptop hotkeys has been moved to devicekit-power/disks or udev [15:53] maxb: re. bug 394808 -- I do not have the issue when running info GIT [15:54] Launchpad bug 394808 in texinfo "info reader now chokes on tab characters in info files" [Medium,Confirmed] https://launchpad.net/bugs/394808 [15:54] hggdh: That is excellent news [15:54] I was attempting to debug recently, but got rather lost [15:54] maxb: the problem now is finding what fixed it... the version we ship is the last official version, and it is from 2008 [15:55] there are a lot of commits in between :-( [15:55] We could go the other way and try to find out what broke it [15:55] yes, git bisect could help [15:56] or one of the 7 patches we ship with it [15:58] and I specially wonder about ./patches/fix-direntry [15:59] hggdh: It's not in series [16:00] duh. Should have looked at it :-( [16:00] well, it *may* be one to look at, or search on git... [16:01] It seems unlikely - surely the makeinfo code isn't involved in display? [16:03] no, it is not -- it worked on GIT, without re-gen. So it has to be something on display/window [16:07] * maxb sets some bisecting going, then [16:09] and I will have a look at changes to window.c [16:18] i am new to ubuntu bugs help reqd please! [16:18] dont know where to start there are lots of bugs which one to go for first? [16:26] shankhs: please read the topic -- it points to some very good links [16:27] shankhs: see, for starters, https://wiki.ubuntu.com/HelpingWithBugs [16:32] hggdh: I have read that one and I have joined the bugsquad but if you can help me to chose any package to begin with , i will really be grateful. I am programming in c and c++ for 3 years now. [16:33] shankhs: the easiest way is try to find a package you are familiar with -- like something you use. Then start looking at bugs for this package === bdmurray_ is now known as bdmurray [16:33] shankhs: please keep in mind that this is *triaging*, not (necessarily) fixing [16:49] hggdh: there are thousands of apps and their bugs reported can you suggest any app which is written in C so that its easy to understand and debug for a beginner like me. [16:50] shankhs: what do you run (Gnome, XFCE, KDE), and what version (Ubuntu 9.04, 8.10, etc)? [16:54] also, please keep in mind that *before* a bug can be fixed, it must be verified to be a real bug [16:56] hggdh: Bisection results: breakage introduced by the series of 4 changesets beginning with 45badbea, which really represent a single logical changeset. [16:57] so before 4.1.3 [16:58] * maxb commences bisection for the fix [16:59] hggdh: i use Gnome ubuntu 9.04 [16:59] maxb, I am sort of worried -- there are many updates to gnulib in between... [16:59] shankhs: are you familiar with Gnome programming? [17:00] GTK yeah a bit (never developed a huge application using GTK) [17:00] hggdh: only small ones [17:01] hggdh: fo fun [17:02] shankhs: please first get familiar with the bug work process -- see https://wiki.ubuntu.com/BugSquad/KnowledgeBase [17:03] shankhs: then look at https://wiki.ubuntu.com/DebuggingProcedures, and try one of the packages there [17:04] if you do not feel comfortable with one, move to another [17:04] * hggdh booted up a Windows box that has been one year down -- amazing number of HUGE patches to be applied [17:05] hggdh: thanx for the help [17:05] shankhs: we will be here, so please ask if you have doubts [17:05] hggdh: yeah thanx once again [17:33] hi [17:33] every one busy [17:33] ? === marjomercado is now known as marjo [17:37] I think i got a bug in the koala beta 9.10, I am not sure how to report that [17:37] can any one please help me [17:40] Abhlash: what happens? [17:40] and patience helps ;-) [17:41] I have enabled the root user in my system, and [17:41] suppose I use the switch user and then again login as a normal user [17:42] then as the normal user I am trying to shutdown the system [17:42] ubuntu tells me that to do that I mus enter the admin password, as some one is already in the system [17:42] so? [17:43] now I am pressing the cancel button instead of entering the password [17:43] what i can see is i am back in my root desk [17:43] did I confuse you on this? [17:43] not really. Just a bit. BUT... [17:44] (1) you should *never* *ever* log in to X under root; [17:44] yes I know that [17:44] but we can definitely use it, I dont want to type in sudo before every command that I execute [17:45] (2) so you (1) logged in as root; (2) switched over to a new login, and logged in as a normal user; (3) tried to shutdown; [17:45] yes, exactly [17:45] (4) cancelled the authentication (due to another user logged in);l (5) was thrown back into the first login [17:45] correct? [17:46] yes.. exactly [17:46] Abhlash: just a comment -- and I am a very experienced *IX person: login as root is bad. Really bad. You do not need it. [17:47] Abhlash: back to your issue. Please create a new user account -- call it test, for example --; try again your scenario without root (using the new user account and your user account [17:47] ok.. I will disable it .. :) (experience always counts) [17:47] ok.. I will try and get back.. [17:47] and, anyway, you can always 'sudo -i'... [17:50] I will be back hggdh, I am trying what you have said now [17:52] k [17:52] Hi Hggdh [17:52] I am here [17:53] Me just tried it, now I know why I was being logged into the root user :) [17:53] I will disable root right now :P [17:54] Abhlash: what you mean by 'disable root right now'? [17:54] hmm I will disable my root login and use normal user [17:54] login to work [17:55] all you need is *NOT USE IT* [17:55] hggdh: the scenario given by Abhlash isn't bug! why? [17:55] please i am a noob here [17:55] shankhs: I do not know if it is a bug or not, not yet. cancelling the dialog should not drop to the previous session [17:56] I just wanted to know if being root had anything to do with it [17:56] I think its x who plays the trick [17:56] probably, yes [17:56] In X root user can never lock his screen, its some security issue(I am not sure why it do not allow..) but it will not allows [17:59] Abhlash: I think X does not allow lock screen being root because root login is supposed to be in case of high emergency [17:59] Yup , I guess you are correct.. [17:59] Abhlash: and X advises to get out of root login as soon as i possible. [18:00] yah, I had been always using the root login.. I will not use it further.. [18:00] this warning is due to the fact that it is a big security issue [18:00] Abhlash: Probhibiting lock screen in root login is X's way of telling "get the hell out of here as soon as possible" ;) [18:01] one important point in having normal user accounts is to minimise the risk of an user error impacting the whole system [18:01] I am the only user, thas why I was using the root login.. [18:01] any way.. so we guess that this one is not a bug? [18:02] Abhlash: still shounds weird [18:02] Abhlash: i think it is [18:02] s/sho/so/ [18:02] so it is worth opening a bug on it. Describe what happened, and your tests [18:03] yah.. I tried to do it.. But i cant add a new bug in launchpad.. [18:03] hggdh: pretty interesting one and I am sure this is going to attract a lot of moral lectures [18:03] I cant find the exact links [18:03] to report the bug [18:03] oh yes. :-) [18:03] Abhlash: do you have a LP account [18:03] yes shanks I do have one [18:05] go to https://bugs.launchpad.net/ [18:05] and please search if anyone has filed similar bug [18:06] thanks doing it now :) [18:08] Abhlash: use apport to get system information and I think xorg conf file can also be helpful [18:08] ;) [18:27] hggdh: I have isolated the fix :-) [19:21] mzz, Hi [19:21] mzz, can you help me? [19:22] mzz, I just want to know how to disable kms. [19:24] maxb: could you add a blurb on what you found, beefing up the debdiff? [19:25] ? [19:25] on the texinfo bug, I mean [19:25] Yes, but I'm not sure what to say other than: Basic programming bug - fixed upstream - cherrypicked. [19:26] :-) ah well. Good enough, then [19:26] maxb, I have a problem with Karmic, it keeps crashing and logging out. [19:27] maxb, I asked for help here days ago and they told me it has to do with my Radeon card. [19:27] maxb: I subscribed the main sponsors [19:28] So the solution was to either install kernel version 2.6.32 or to disable something called radeon-kms (et. al). [19:29] Can you help me please? [19:46] hey guys [19:49] can someone look through my feature-request and maybe confirm it? :) https://bugs.launchpad.net/indicator-applet/+bug/456394 [19:49] d3xter: Error: Could not parse data returned by Launchpad: The read operation timed out [19:51] d3xter: the best place for this feature request would be http://brainstorm.ubuntu.com/ [19:52] hggdh: oh ok, then i will post it there :) [19:52] d3xter: thank you [19:58] hggdh: is it possible to mark this bug as invalid? [19:58] d3xter: yes, you yourself can do it (or I can do it, as you prefer) [19:59] hggdh: oh well, i found it thanks :) [19:59] d3xter: welcome === asac_ is now known as asac [20:52] Anybody reported any bugs the last few hours? [20:53] I'm sure many people have. [20:53] K [20:53] then its my net [21:03] There are many bugs titled "WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x80/0x90()" although search does not find them. [21:10] This finds some: https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=WARNING+52+suspend_test_finish&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package= [21:35] Is it impossible to add to the packages a launchpad bug affects without confirming that it's been registered upstream? I get to a page that asks me to enter the upstream bug URL, and upstream bug contact, or a choice saying "I just know it's known upstream" [21:35] an* [21:35] hggdh: is a package not being able to be installed a critical bug? [21:35] micahg: no, unless it is a critical package [21:35] ok [21:36] zorael: can you please re-state your question? I am not sure I follow [21:38] hggdh: I have a launchpad bug (415023) that also affects kdebase-workspace, so I want to add that to the packages/projects the bug affects. But when I click "also affects projects" and go through the wizard, I come to a page that assumes the bug is known upstream ("enter URL of upstream bug" / "enter upstream bug contact" / "I just know it's known upstream"), but I don't know if it's known upstream. I can't find it on the upstream [21:38] bug tracker. [21:38] bug 415023 [21:38] Launchpad bug 415023 in gnome-power-manager "brightness is broken on MSI WIND U100" [Undecided,Confirmed] https://launchpad.net/bugs/415023 [21:39] zorael: most likely just a langauge issue [21:39] micahg: English though ; / [21:39] you should select the last one [21:39] micahg: roger [21:39] and it'll open the upstream task [21:39] zorael: you can file a bug for LP [21:39] zorael -- "also affects distribution" [21:39] zorael: https://bugs.launchpad.net/malone/ [21:40] "also affects package" is for upstream, "also affects distribution/packages" is for local [21:40] but hggdh is right, you want to select distro, not project [21:40] hggdh, micahg: doh, I added it as a project; should I remove it? [21:41] but it is really confusing... [21:42] zorael: you cannot remove it. I marked it invalid (and you can also do the same, BTW) [21:42] hggdh: I see it, thanks :3 [21:42] welcome. Thank you for helping out [22:29] boas noites === BUGabundo1 is now known as BUGabundo === MsMaco_ is now known as MsMaco