/srv/irclogs.ubuntu.com/2008/06/14/#ubuntu-bugs.txt

persiaqense: I'm not finding enough context from backscroll.  Ping me again, or send me email about your idea.  Something about team coordination?00:59
=== asac_ is now known as asac
calcyipee OOo 44% triaged now :)05:54
calcthere are only a few packages with higher percentage in the top 10005:57
calc122 more bugs to have it have the highest triaged percentage :)05:58
lifelesscool05:58
calc122 bugs will probably take a few days though05:58
calcanyone happen to remember the top 100 package bug report url for lp?07:14
calci can't find a link to it on lp itself07:14
HewHi. I'm trying to verify bug #221673. I've created the .asoundrc correctly, but now I get: 'ALSA lib pcm.c:2106:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so' instead of the assertion failed error.08:08
ubottuLaunchpad bug 221673 in alsa-plugins "ALSA failing with PulseAudio in Hardy" [Undecided,Fix committed] https://launchpad.net/bugs/22167308:08
HewI have not yet installed the version in hardy-proposed. I have also checked that the file in the error I get does not exist.08:09
=== asac_ is now known as asac
HewI applied to be a member of ubuntu-bugcontrol a week ago, but I haven't heard anything yet. I notice there are 58 of us waiting, and the team is being advertised in this channel's topic. Can anyone provide some info on how long the process usually takes? No doubt bdmurray is busy, but I'm eager to take my triaging to the next level ;-) Thanks!08:33
=== asac_ is now known as asac
=== asac_ is now known as asac
=== gnomefre1k is now known as gnomefreak
affluxhi10:41
thekornhey afflux11:03
affluxhi thekorn11:03
\shmoins thekorn11:06
emgentheya \sh :)11:07
thekorn\sh, hi, I'm just reading the code of leonov11:07
thekornand try to understand how this pykde and pyqt thing work11:08
\shthekorn: ah..too early...I'm just setting up the real directory structure to make things happen much faster :)11:10
\shthe ui is totally changed now..11:10
thekorn\sh, one idea: if you really would like to have a pygtk version, it might make sense too use a kind of generic (pyqt independent) data-model11:12
\shthekorn: backend :)11:12
\shthekorn: the idea is to have all needed infra inside backend...but gtk/qt specific stuff (this applies to the listviews data models) are bound to the frontend...11:13
thekorn\sh, ok, makes sense, so the structure will be something like qt/{model,view} and gtk/{model,view} plus the generic backend/11:15
\shyepp11:16
\shI don't see an other way to do that11:17
\shthe same goes for the configuration...11:17
thekorn\sh, some time ago I wrote a small gnome applet to trigger changes of someones bugs, given that leonov should be the "one and only" desktop client11:26
thekornand I have currently no time to maintain the code11:26
thekornI'm fine with merging this applet into leonov :)11:27
thekornhttps://edge.launchpad.net/lp-bugs-applet11:27
\shthekorn: cool :)11:28
thekorn\sh, what I really wanted to say is: having a notification functionallity in leonov like 'you are subscribed to bug xxx, this bug changed' would be really cool11:31
thekornand that's what lp-bugs-applet is about11:32
qensehello11:44
=== Mez|DPC is now known as mez
=== qense is now known as qense|lunch
=== asac_ is now known as asac
HewHi. Bug #206992 has been fixed upstream, but has not reached Ubuntu. Should this bug now be "fix committed"? I'm unsure since the fixed version doesn't seem to be on the Ubuntu radar yet.11:52
ubottuLaunchpad bug 206992 in supertuxkart "SuperTuxKart doesn't remember fullscreen setting" [Undecided,Confirmed] https://launchpad.net/bugs/20699211:52
Hobbseeyes11:58
Hobbseefix committed == "there is a fix.  somewhere.  not in any ubuntu version yet"11:59
* Hobbsee wonders when supertuxkart will make another release.11:59
HewHobbsee: Thanks for the reply. I was unsure since Bugs/Status says "For an Ubuntu package, the changes are pending and to be uploaded soon"11:59
=== mez is now known as Mez|DPC
HewHobbsee: 0.5 is out, I have it via getdeb and it's pretty cool :-)11:59
Hewbut Debian is still on 0.4, I checked12:00
* Hobbsee kicks debian's rmadison12:02
Hobbseethey've had a bug about it, is ee.12:04
HewHobbsee: Sorry for not understanding, but what's ee?12:05
Hobbsees/is ee/i see/12:05
Hobbseesorry :)12:06
=== qense|lunch is now known as qense
Hewah gotcha12:06
* Hobbsee tries the old poke-and-it-shall-be-fixed approach.12:07
* Hew watches on in hope12:08
gnomefreakee is a basic text editor ;)12:28
affluxI wonder why we still use fix committed for "fixed upstream". I thought that using a project task for it was the launchpad'ish way.12:29
gnomefreaki use confirmed until i fix it or until someone else is working on it12:29
gnomefreakbut thats just mozilla team12:29
qenseThere are a lot of bug reports about brightness controls lately12:32
qensesome about key action reported twice or more at once12:33
qenseor no reaction at all12:33
qenseI've lost the overview a bit, so I'm going to create an overview page at my blog12:33
qensedo you know any bug reports about this to include?12:33
=== Mez|DPC is now known as mez
=== mez is now known as Mez|DPC
james_wqense: hi, do you have a reference?13:04
james_wqense: it seems I may be seeing that testing now, and my media keys don't seem to work either.13:04
qenseI've got five bugs now, and they are a bit reporting the same problems, or two at the same time:13:04
qensebug 20747313:04
ubottuLaunchpad bug 207473 in kde-guidance "Screen brightness double level changes" [Medium,Confirmed] https://launchpad.net/bugs/20747313:04
qensebug 23941313:04
ubottuLaunchpad bug 239413 in hal "Four steps of brightness changing after pressing a brightness key only once" [Undecided,New] https://launchpad.net/bugs/23941313:04
qensebug 20309613:04
ubottuLaunchpad bug 203096 in gnome-power-manager "Max brightness is not max brightness" [Low,Triaged] https://launchpad.net/bugs/20309613:05
qensebug 21273313:05
ubottuLaunchpad bug 212733 in hal "[hardy] [regression] LCD brightness control (Dell) no longer works" [Medium,Confirmed] https://launchpad.net/bugs/21273313:05
qenseand bug 23970613:05
ubottuLaunchpad bug 239706 in hal "Multiple key presses being reported after pressing an Fn key only once" [Undecided,New] https://launchpad.net/bugs/23970613:05
qensethere are also others of course, but this are the bug reports that seem related somehow13:05
=== Everget3 is now known as Evergete
=== Mez|DPC is now known as mez
=== mez is now known as Mez|DPC
HewHey guys. seb128 just closed my wishlist bug #227350 because I have not set the "locale" time to 24h format. I've asked in #ubuntu, but nobody knows where this "locale" time can be set. Before I reopen the bug, could someone give their opinion on whether it should be opened or closed? Thanks.15:43
ubottuLaunchpad bug 227350 in rhythmbox "rhythmbox ignores 24h time setting" [Wishlist,Invalid] https://launchpad.net/bugs/22735015:43
* Hew gives his question a first and final bump15:51
thekornHew, it should definitely be closed15:55
thekornif you want to change the locale setting for one program, run15:55
thekornLC_TIME=en_GB rhythmbox15:55
Hewthekorn: Thanks for your reply. I just tried that, and along with some "locale not supported" messages, the time is still in 12h format. I'm not concerned about changing the setting for one program though, but in changing the global system value to 24h format so all programs follow it.15:58
HewI thought I already had with the standard clock preferences, but seb128 says this isn't the case15:58
thekornHew, sorry I've some guests here, please ask in a support channel on how to change your locale settings16:04
Hewthekorn: no worries, thanks for your help16:04
thekornor convert this bug into a question, and I'm sure somebody will give you the right answer soon16:05
LimCoreit seems k8 cpu freq support is broken?16:33
=== _jason is now known as jrib
=== qense is now known as qense|away
=== dodger_ is now known as Hurtz
=== qense|away is now known as qense
danagesince a few days, my external USB drive turns off a few seconds after i connect it. also, i have suspend issues with khubd. anybody familiar with the bug? if it's new, where should i file it?19:06
leoquantdanage you have not reported the bug? so no bug nr.?19:08
danageleoquant: not yet. i wanted to avoid duplicates and also find out how to gather more info before i submit19:08
leoquanti see19:09
danageleoquant: is there a usb syslog?19:09
james_wusb information appears in /var/log/syslog19:09
leoquanthmm i don´t think so19:10
leoquantjames_w indeed19:10
danagejames_w: ok let me check19:10
james_wdanage: have you installed a kernel update in the last few days?19:11
danagehttp://pastebin.ca/104797319:11
danagethen, the drive spins down19:11
leoquantthe hardy -19 james_w?19:11
james_wprobably19:11
danagejames_w: yes, i have. but i rolled back the kernel to -17 and it still has the problem19:11
danagei am running -1819:12
danagewhy is network manager fuzzing with usb devices?19:12
james_wa kernel upgrade would be a likely cause, but if the old one no longer works then we can rule that out19:13
leoquantik think you should report it19:13
james_wdanage: can you use another pastebin please, I can't get to pastebin.ca.19:13
james_w!paste19:13
ubottupastebin is a service to post multiple-lined texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu.com (make sure you give us the URL for your paste - see also the channel topic)19:13
danagehttp://paste.ubuntu.com/20185/19:15
james_wthanks19:15
danageno error message. i find that strange19:15
james_wdanage: can you check if you upgraded hal-info or a related package in the last few days?19:16
danagejames_w: i think i have. let me check19:17
danagejames_w: i am using 20080317+git20080318-1ubuntu419:19
danagewhich packages are related?19:19
greg-gw00t! just closed out a bug from the 3000 range (opened 2005-10-10)19:22
james_wdanage: sorry, got to go out, but someone else might be able to help.19:22
james_wdanage: does downgrading hal-info to the hardy release version fix it, if so then I would suggest filing a bug against that.19:23
=== asac_ is now known as asac
james_wdanage: and https://wiki.ubuntu.com/DebuggingHal should help you file a good bug report if that is the case.19:24
calcalmost 50% triaged for OOo :)19:47
jjesseyay20:11
LimCorecalc: including my wish for odt+pdf \o/20:11
crimsundanage: have you pastebinned your lsusb -v somewhere?20:19
danagecrimsun: let me do that20:20
crimsun(I'm also tracing a hal-info hardy-proposed regression, so this is good.)20:20
danagecrimsun: it stalls20:20
danagecrimsun: no output20:20
danagethere is something seriously wrong here20:20
crimsundanage: meaning lsusb -v stalls?20:20
danageyes20:21
crimsunok, does just plain lsusb complete?20:21
danageno20:21
danagenot as root, either20:21
crimsunok, can you reboot and just issue lsusb?20:21
danagele tme detach the usb and try20:21
crimsunok20:21
danageno workie20:21
danageusb GENERALLY works though. i can print20:22
danagealso i am using a usb mouse20:22
danageok i will reboot into -18 kernel20:22
crimsunexcellent.  These changes to fdi/information/10freedesktop/30-keymap-hp.fdi in hardy-proposed's hal-info fubars at least three different HPs.20:25
danagecrimsun: as soon as i start the usb, it stalls20:27
danagethe usb drive20:27
danageneedless to mention, under windows it works20:27
crimsunok, so it persists across -18 and -19 kernels.  Have you confirmed that it also persists when you downgrade to hardy's hal-info?20:28
danagecrimsun: -17 and -18 kernels20:28
danagecrimsun: i do not know how to do that20:28
crimsunah, ok.20:28
danagecrimsun: i tried to google it, but there seems to be no older version in the repos20:28
crimsunsudo apt-get -thardy --reinstall install hal-info20:28
danageno space between -t and hardy?20:29
crimsun(that's just one way)20:29
crimsunsure, you can, but I normally omit it.20:29
danagecrimsun: another restart?20:29
crimsunrestarting hal /may/ suffice, but I recommend that you reboot.20:30
danagei think it reinstalled the same version?20:30
crimsundpkg -l hal-info|awk '/^ii/ {print $3}'20:31
danage20080317+git20080318-1ubuntu420:31
danageso20:32
crimsunright, that's correct.  That's hardy's version, which is what you want to use to test.20:32
danagethat's the one i had20:32
danageis it not?20:32
crimsunah, yes, just saw from backscroll20:32
danage(11:19:00 AM) danage: james_w: i am using 20080317+git20080318-1ubuntu420:32
crimsunso your issue isn't hal-info related at all20:32
danagewhat is khubd? i get a khubd error when trying to suspend. that i didn't get before20:33
crimsunthere's a usb issue matching yours, let me try to find it.20:33
danagecrimsun: brb20:35
danagesorry crimsun i had to reboot20:38
danagecrimsun: i have virtualbox-non-ose running. it needs some tweaks for usb support. could that be related?20:39
crimsunhmm, I don't track virtualbox, so I don't know, sorry.20:39
crimsunI presumed you were testing this on the host OS.20:39
danagecrimsun: yes, of course. but the host usb support needed some tweaking. but that has been working (and remained unchanged) for months now20:46
crimsundanage: ok, to help narrow down some possible causes, is ehci_hcd loaded?20:49
danagehci_usb, ehci_hcd and uhci:hcd20:49
crimsundanage: ok, let's try the simpler workaround, then.20:50
crimsunsudo rmmod ehci_hcd && echo -n -1|sudo tee /sys/module/usbcore/parameters/autosuspend && sudo modprobe ehci_hcd20:51
danageyes20:52
danageno output20:52
crimsunok, and does plugging in the drive exhibit the same symptom?20:52
DanielRMHello?20:53
crimsunhi20:53
danagecrimsun: not sure i understand. pluggin it in after these commands?20:53
crimsunyes20:53
DanielRMHello. :)20:55
danagecrimsun: it works now20:55
danagecrimsun: thanks for the temp workaround!20:55
DanielRMCan I report a bug, or else get help in submitting the bug to Launchpad?20:55
crimsunsure20:55
crimsunI was just reading scrollback from #launchpad20:55
danagecrimsun: let me sport a lsusb now!20:56
DanielRMcrimsun: ah, so you know what my dilemma is, if not the bug itself?20:56
danagecrimsun: lsusb works now20:56
crimsunDanielRM: well, I haven't finished reading20:56
danagefriggin autosuspend20:56
DanielRMcrimsun: have you got to the side-topic regarding faeces yet? XD20:56
crimsundanage: ok, that is fixed in 2.6.25 (and also in intrepid's kernel)20:57
danagecrimsun: THANK you20:58
danagecrimsun: ETA?20:58
crimsundanage: intrepid has built kernels; in the meantime, I recommend you use that workaround.20:59
danagemeh, no backports?20:59
crimsunI don't think so, but I'm a bit distant from Ubuntu development these days.20:59
danagecrimsun: ok one last think. which startup file do i put that in?20:59
danagething21:00
DanielRMWait, .25? I'm still on .24. :(21:00
crimsunDanielRM: that's correct (2.6.24) for hardy.21:00
crimsundanage: I don't know of one; you can either modify the udev rule(s) or use /etc/rc.local21:02
danagethank you21:02
crimsunDanielRM: am I correct in understanding that you're attempting to file a bug against Ubuntu Hardy's nautilus source package?21:02
crimsun...ok.21:03
DanielRMWhat did I last say? :S21:03
DanielRMJust had a connection issue.21:03
crimsun16:00     DanielRM > Wait, .25? I'm still on .24. :(21:03
DanielRMAh.21:04
DanielRMDid you say anything after that?21:04
crimsun16:02      crimsun > DanielRM: am I correct in understanding that you're attempting to file a bug against Ubuntu Hardy's nautilus source package?21:04
DanielRMOK. :)21:04
DanielRMcrimsun: that's probably correct, although what part of Nautilus or even, exactly, if it is Nautilus or more some other part of GNOME I can't profess to know.21:05
crimsunDanielRM: ok, can you describe the symptom(s) you're experiencing?21:05
DanielRMI was trying to access a USB stick using the '3.9 GB media' label in an open file dialog when I got the error: 'You are not supposed to show G_IO_ERROR_FAILED_HANDLED in the UI'21:05
DanielRMAnd that's it.21:06
crimsunok, so that symptom actually has several components21:06
crimsunthe first component is linux and is, coincidentially, what danage and I just discussed.21:07
crimsunthe second component is nautilus as you correctly surmised.21:07
crimsunthe third component is gvfs.21:07
DanielRMOh?21:07
danagemulti layer problems, how wonderful21:08
DanielRMI'm using 2.6.24-19 kernel, BTW.21:08
DanielRMI'd quite like to know how to get .25 :P21:08
crimsunDanielRM: well, let's see if we can just work around the root cause for now, which is in linux.21:09
crimsunI need to grab a phone call, but if danage doesn't mind, he could help you through it21:09
DanielRMOK. :)21:09
crimsundanage: if you have a few minutes and don't mind, DanielRM just needs to issue those commands I referred to you21:10
danagecrimsun: i don't mind21:10
crimsun15:51      crimsun > sudo rmmod ehci_hcd && echo -n -1|sudo tee /sys/module/usbcore/parameters/autosuspend && sudo modprobe ehci_hcd21:10
danageDanielRM: that's basically what you run in shell before you activate your usb device21:11
danage(i.e. plug it in)21:11
danageand that does the trick21:11
danagei will look for a more permanent solution soon21:11
DanielRMWait, I only understand some of that command. We're removing the kernel module ehci_hcd, which is what exactly? Then we're echoing... something... to tee, which is... searching?... for that path/status, and then we're loading the kernel module again?21:13
danageyeah21:13
danageyou got it21:13
DanielRMSorry, I just like understanding things as well.21:13
danagecrimsun: i reported in #ubuntu-california about the usb bug and someone said you are a guru. so thanks again21:16
crimsun(nah, I'm no guru, just a disaffected Ubuntu user.)21:17
DanielRMDisaffected? Why?21:17
crimsunDanielRM: you're unloading a usb driver, changing a usb setting, and reloading a usb driver.21:18
DanielRMI didn't get your answer, if you gave one, but I'm becoming disaffected now. :P21:19
crimsun16:18      crimsun > DanielRM: you're unloading a usb driver, changing a usb setting, and reloading a usb driver.21:19
DanielRMWrong window was selected after I closed a window, so when I pressed alt-f4 the thing which didn't close happened to be what I wanted to and thing which did happened to be the IRC client. :P21:20
marnanelSomeone did raise a bug recently asking for an "undo close" command.21:20
DanielRMAh, OK.21:21
DanielRMmarnanel: hmmm. An interesting thought.21:31
DanielRMmarnanel: what sort of functionality did they want with it?21:32
marnanelDanielRM: Just a button that if you pressed it, the window would spring back to life again21:34
marnanelI suppose it would be a lot easier in OS X than here21:34
DanielRMI just wondered whether they were thinking of something like recovering the program's status at time of close... that would be quite difficult.21:34
* marnanel nods, as far as I could make out they were21:35
marnanelthat's what I meant about OS X -- closing windows never terminates an application there21:35
DanielRMOh?21:40
=== Mez|DPC is now known as mez
=== mez is now known as Mez
marnanelDanielRM: yes, you have to specifically close the application from the menu22:09
marnanelDanielRM: closing all the windows, or the main window, to close the app is an X and Windows idea22:10
thekorn\sh, FYI I created a package of the latest version of py-lp-bugs in the bughelper-dev team PPA22:38
thekornhttps://edge.launchpad.net/~bughelper-dev/+archive22:38
=== Pici` is now known as Pici

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