/srv/irclogs.ubuntu.com/2009/10/20/#ubuntu-bugs.txt

=== dwg_ is now known as dwg
* BUGabundo $ rsync -av --deleteafter /home/BUGabundo /media/bed/00:56
=== jjesse__ is now known as jjesse
jbuncherHas anyone been affected by Bug #449888?04:01
ubot4Launchpad 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/44988804:01
jjesseyes but just updated my system and not haaving that problem04:01
jbuncherjjesse, what are you running?04:05
jjessejbuncher: dell mini 9 w/ the broadcom driver04:05
jjessei was having some problems with WPA enterprise and WPA regular and now after updates it seems to be better04:06
jbuncherjjesse, I meant what release, but that's my fault for not clarifying.04:06
=== 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
thekorngood morning07:50
=== porthose is now known as porthose|afk
shankhshi i just joined the ubuntu bug squad... and waiting for a mentor any suggestions?08:18
micahghave you read the wiki page on how to triage yet, shankhs?08:21
shankhsmicahg: ya i read the process of triaging?09:19
shankhsanybody online?09:24
shankhs\quit09:45
maxbhggdh: (rather delayed) pong09:46
d3xterhey guys10:06
d3xtermy laptop hotkeys doesnt work under 9.10, should i file a bug against hal or devicekit-power?10:06
=== 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
dns53bulletproof x does not seem to work, where should i file a bug?13:13
joaopintodns53, is that related to /etc/gdm/failsafeXServer ?13:15
dns53yes, 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 options13:17
joaopintox11-common might be a good option13:17
dns53in 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 drivers13:17
joaopintothere have been some major changes to the boot process, X is started earlier, I am not sure bulletproof was covered13:19
dns53yeah it does not seem to be13:19
dns53is there a way of attaching specific log files with apport instead of the previous one?13:24
dns53is there a manual process to file bugs, the log files sent i need is from 2 reboots ago not the previous log file13:43
joaopintodns53, ubuntu-bug should redirect you to the link for the bug report13:43
dns53yes but i will have log files where everything is working, so can i remove them when filing the bug?13:44
joaopintoyes13:48
joaopintowell, or at least attach the relevant ones13:48
d3xtermy laptop hotkeys doesnt work under 9.10, should i file a bug against hal or devicekit-power?15:13
joaopintod3xter, there is something on the release notes about hal being dropped and how it would affect hotkeys setups15:16
d3xterjoaopinto: ok, thx15:17
bddebianBoo15:20
d3xterjoaopinto: in the technicaloverview it says, that laptop hotkeys has been moved to devicekit-power/disks or udev15:23
hggdhmaxb: re. bug 394808 -- I do not have the issue when running info GIT15:53
ubot4Launchpad bug 394808 in texinfo "info reader now chokes on tab characters in info files" [Medium,Confirmed] https://launchpad.net/bugs/39480815:54
maxbhggdh: That is excellent news15:54
maxbI was attempting to debug recently, but got rather lost15:54
hggdhmaxb: the problem now is finding what fixed it... the version we ship is the last official version, and it is from 200815:54
hggdhthere are a lot of commits in between :-(15:55
maxbWe could go the other way and try to find out what broke it15:55
hggdhyes, git bisect could help15:55
hggdhor one of the 7 patches we ship with it15:56
hggdhand I specially wonder about ./patches/fix-direntry15:58
maxbhggdh: It's not in series15:59
hggdhduh. Should have looked at it :-(16:00
hggdhwell, it *may* be one to look at, or search on git...16:00
maxbIt seems unlikely - surely the makeinfo code isn't involved in display?16:01
hggdhno, it is not -- it worked on GIT, without re-gen. So it has to be something on display/window16:03
* maxb sets some bisecting going, then16:07
hggdhand I will have a look at changes to window.c16:09
shankhsi am new to ubuntu bugs help reqd please!16:18
shankhsdont know where to start there are lots of bugs which one to go for first?16:18
hggdhshankhs: please read the topic -- it points to some very good links16:26
hggdhshankhs: see, for starters, https://wiki.ubuntu.com/HelpingWithBugs16:27
shankhshggdh: 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:32
hggdhshankhs: the easiest way is try to find a package you are familiar with -- like something you use. Then start looking at bugs for this package16:33
=== bdmurray_ is now known as bdmurray
hggdhshankhs: please keep in mind that this is *triaging*, not (necessarily) fixing16:33
shankhshggdh: 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:49
hggdhshankhs: what do you run (Gnome, XFCE, KDE), and what version (Ubuntu 9.04, 8.10, etc)?16:50
hggdhalso, please keep in mind that *before* a bug can be fixed, it must be verified to be a real bug16:54
maxbhggdh: Bisection results: breakage introduced by the series of 4 changesets beginning with 45badbea, which really represent a single logical changeset.16:56
hggdhso before 4.1.316:57
* maxb commences bisection for the fix16:58
shankhshggdh: i use Gnome ubuntu 9.0416:59
hggdhmaxb, I am sort of worried -- there are many updates to gnulib in between...16:59
hggdhshankhs: are you familiar with Gnome programming?16:59
shankhsGTK yeah a bit (never developed a huge application using GTK)17:00
shankhshggdh: only small ones17:00
shankhshggdh: fo fun17:01
hggdhshankhs: please first get familiar with the bug work process -- see https://wiki.ubuntu.com/BugSquad/KnowledgeBase17:02
hggdhshankhs: then look at https://wiki.ubuntu.com/DebuggingProcedures, and try one of the packages there17:03
hggdhif you do not feel comfortable with one, move to another17:04
* hggdh booted up a Windows box that has been one year down -- amazing number of HUGE patches to be applied17:04
shankhshggdh: thanx for the help17:05
hggdhshankhs: we will be here, so please ask if you have doubts17:05
shankhshggdh: yeah thanx once again17:05
Abhlashhi17:33
Abhlashevery one busy17:33
Abhlash?17:33
=== marjomercado is now known as marjo
AbhlashI think i got a bug in the koala beta 9.10, I am not sure how to report that17:37
Abhlashcan any one please help me17:37
hggdhAbhlash: what happens?17:40
hggdhand patience helps ;-)17:40
AbhlashI have enabled the root user in my system, and17:41
Abhlashsuppose I use the switch user and then again login as a normal user17:41
Abhlashthen as the normal user I am trying to shutdown the system17:42
Abhlashubuntu tells me that to do that I mus enter the admin password, as some one is already in the system17:42
hggdhso?17:42
Abhlashnow I am pressing the cancel button instead of entering the password17:43
Abhlashwhat i can see is i am back in my root desk17:43
Abhlashdid I confuse you on this?17:43
hggdhnot really. Just a bit. BUT...17:43
hggdh(1) you should *never* *ever* log in to X under root;17:44
Abhlashyes I know that17:44
Abhlashbut we can definitely use it, I dont want to type in sudo before every command that I execute17:44
hggdh(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
Abhlashyes, exactly17:45
hggdh(4) cancelled the authentication (due to another user logged in);l (5) was thrown back into the first login17:45
hggdhcorrect?17:45
Abhlashyes.. exactly17:46
hggdhAbhlash: just a comment -- and I am a very experienced *IX person: login as root is bad. Really bad. You do not need it.17:46
hggdhAbhlash: 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 account17:47
Abhlashok.. I will disable it .. :) (experience always counts)17:47
Abhlashok.. I will try and get back..17:47
hggdhand, anyway, you can always 'sudo -i'...17:47
AbhlashI will be back hggdh, I am trying what you have said now17:50
hggdhk17:52
AbhlashHi Hggdh17:52
hggdhI am here17:52
AbhlashMe just tried it, now I know why I was being logged into the root user :)17:53
AbhlashI will disable root right now :P17:53
hggdhAbhlash: what you mean by 'disable root right now'?17:54
Abhlashhmm I will disable my root login and use normal user17:54
Abhlashlogin to work17:54
hggdhall you need is *NOT USE IT*17:55
shankhshggdh: the scenario given by Abhlash isn't bug! why?17:55
shankhsplease i am a noob here17:55
hggdhshankhs: I do not know if it is a bug or not, not yet. cancelling the dialog should not drop to the previous session17:55
hggdhI just wanted to know if being root had anything to do with it17:56
AbhlashI think its x who plays the trick17:56
hggdhprobably, yes17:56
AbhlashIn 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 allows17:56
shankhsAbhlash: I think X does not allow lock screen being root because root login is supposed to be in case of high emergency17:59
AbhlashYup , I guess you are correct..17:59
shankhsAbhlash: and X advises to get out of root login as soon as i possible.17:59
Abhlashyah, I had been always using the root login..  I will not use it further..18:00
hggdhthis warning is due to the fact that it is a big security issue18:00
shankhsAbhlash: Probhibiting lock screen in root login is X's way of telling "get the hell out of here as soon as possible" ;)18:00
hggdhone important point in having normal user accounts is to minimise the risk of an user error impacting the whole system18:01
AbhlashI am the only user, thas why I was using the root login..18:01
Abhlashany way.. so we guess that this one is not a bug?18:01
hggdhAbhlash: still shounds weird18:02
shankhsAbhlash: i think it is18:02
hggdhs/sho/so/18:02
hggdhso it is worth opening a bug on it. Describe what happened, and your tests18:02
Abhlashyah.. I tried to do it.. But i cant add a new bug in launchpad..18:03
shankhshggdh: pretty interesting one and I am sure this is going to attract a lot of moral lectures18:03
AbhlashI cant find the exact links18:03
Abhlashto report the bug18:03
hggdhoh yes. :-)18:03
shankhsAbhlash: do you have a LP account18:03
Abhlashyes shanks I do have one18:03
shankhsgo to https://bugs.launchpad.net/18:05
shankhsand please search if anyone has filed similar bug18:05
Abhlashthanks doing it now :)18:06
shankhsAbhlash: use apport to get system information and I think xorg conf file can also be helpful18:08
Abhlash;)18:08
maxbhggdh: I have isolated the fix :-)18:27
Omar87mzz, Hi19:21
Omar87mzz, can you help me?19:21
Omar87mzz, I just want to know how to disable kms.19:22
hggdhmaxb: could you add a blurb on what you found, beefing up the debdiff?19:24
maxb?19:25
hggdhon the texinfo bug, I mean19:25
maxbYes, but I'm not sure what to say other than: Basic programming bug - fixed upstream - cherrypicked.19:25
hggdh:-) ah well. Good enough, then19:26
Omar87maxb, I have a problem with Karmic, it keeps crashing and logging out.19:26
Omar87maxb, I asked for help here days ago and they told me it has to do with my Radeon card.19:27
hggdhmaxb: I subscribed the main sponsors19:27
Omar87So the solution was to either install kernel version 2.6.32 or to disable something called radeon-kms (et. al).19:28
Omar87Can you help me please?19:29
d3xterhey guys19:46
d3xtercan someone look through my feature-request and maybe confirm it? :) https://bugs.launchpad.net/indicator-applet/+bug/45639419:49
ubot4d3xter: Error: Could not parse data returned by Launchpad: The read operation timed out19:49
hggdhd3xter: the best place for this feature request would be http://brainstorm.ubuntu.com/19:51
d3xterhggdh: oh ok, then i will post it there :)19:52
hggdhd3xter: thank you19:52
d3xterhggdh: is it possible to mark this bug as invalid?19:58
hggdhd3xter: yes, you yourself can do it (or I can do it, as you prefer)19:58
d3xterhggdh: oh well, i found it thanks :)19:59
hggdhd3xter: welcome19:59
=== asac_ is now known as asac
del_diabloAnybody reported any bugs the last few hours?20:52
PiciI'm sure many people have.20:53
del_diabloK20:53
del_diablothen its my net20:53
jarnosThere 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:03
jarnosThis 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:10
zoraelIs 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
zoraelan*21:35
micahghggdh: is a package not being able to be installed a critical bug?21:35
hggdhmicahg: no, unless it is a critical package21:35
micahgok21:35
hggdhzorael: can you please re-state your question? I am not sure I follow21:36
zoraelhggdh: 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 upstream21:38
zoraelbug tracker.21:38
hggdhbug 41502321:38
ubot4Launchpad bug 415023 in gnome-power-manager "brightness is broken on MSI WIND U100" [Undecided,Confirmed] https://launchpad.net/bugs/41502321:38
micahgzorael: most likely just a langauge issue21:39
zoraelmicahg: English though ; /21:39
micahgyou should select the last one21:39
zoraelmicahg: roger21:39
micahgand it'll open the upstream task21:39
micahgzorael: you can file a bug for LP21:39
hggdhzorael -- "also affects distribution"21:39
micahgzorael: https://bugs.launchpad.net/malone/21:39
hggdh"also affects package" is for upstream, "also affects distribution/packages" is for local21:40
micahgbut hggdh is right, you want to select distro, not project21:40
zoraelhggdh, micahg: doh, I added it as a project; should I remove it?21:40
hggdhbut it is really confusing...21:41
hggdhzorael: you cannot remove it. I marked it invalid (and you can also do the same, BTW)21:42
zoraelhggdh: I see it, thanks :321:42
hggdhwelcome. Thank you for helping out21:42
BUGabundoboas noites22:29
=== BUGabundo1 is now known as BUGabundo
=== MsMaco_ is now known as MsMaco

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!