/srv/irclogs.ubuntu.com/2009/09/08/#ubuntu-bugs.txt

minHi, I wanted to look into a possible ALSA regression in Karmic.  It's Intel HD Audio "00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384]"  no longer has ALSA controls for Analog Loopback. I did not find a bug in launchpad for this.01:37
* crimsun nods01:38
crimsunplease just use "ubuntu-bugs"01:39
crimsunthere's no need to re-announce, since i'm present.01:39
crimsunubuntu-bug*01:39
min@crimson So do you want me to file a launchpad bug report, or just discuss it here?01:41
jjardonhello, could someone confirm this bug? : https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/41474801:41
ubot4Launchpad bug 414748 in epiphany-browser "should depend on epiphany-webkit first" [Wishlist,New]01:41
crimsunmin: please file a bug using "ubuntu-bug alsa-base"01:43
* micahg is looking jjardon01:43
micahgjjardon: do you have a link showing upstream making that move?01:46
jjardonmicahg, mmm, wait a moment please01:47
jjardonmicahg, http://blogs.gnome.org/epiphany/2009/07/01/gecko-end-of-life/01:50
jjardon(micahg, I've updated the bug report with the link)01:50
min@crimsun Bug #426023 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/42602301:51
ubot4Launchpad bug 426023 in alsa-driver "ubuntu-bug alsa-base No analog loopback on HD Audio in Karmic 2.6.31-rc8" [Undecided,New]01:51
hggdh_good catch, jjardon01:52
=== hggdh_ is now known as hggdh
jjardonhggdh, :)01:53
micahgI don't know about that bug01:53
crimsunmin: that's not a bug01:53
crimsunmin: that change is intentional, and it landed in changeset d78d7a90adf793943cc29a414b6f4364a700aad5 (sound-2.6.git)01:53
micahgfor karmic it shouldn't matter jjardon and for karmic + 1, my guess is it will be dropped01:54
crimsunmin: to quote the change:01:54
crimsun    Don't create "Analog Loopback" controls as default since these controls01:54
crimsun    are usually more harmful than useful for normal users.01:54
crimsun    Only created when "loopback = yes" hint is given.01:54
hggdhmicahg: you mean epiphany will be dropped?01:54
micahgepiphany-gecko01:54
hggdhoh, OK01:54
micahgif it's not supported upstream01:54
jjardonthe problem is that people that installing epiphany-browser will fille bug against an unsoported version (gecko)01:55
hggdhindeed. I guess this will be one of these bugs that will bites us back ;-)01:56
jjardonso will be rejected upstream :/01:56
hggdhwell, the triager working on them will have to be careful.  meanwhile, we keep trodding on01:57
micahgwell, right now epiphany browser is gnome, epiphany-browser will probably become webit01:58
micahg*should01:58
micahgor maybe -webkit will provide the epiphany-browser dummy package01:58
micahgin any case, it'll be supported in Ubuntu until it's EOL for SRUs01:59
jjardonfor Gnome 2.28, only webkit backend is supported (all gnome apps are switching to webkit)02:00
micahghmm02:01
jjardonas webkitgtk+ was accepted as external dependency02:01
micahgmaybe epiphany-browser should be removed for karmic?02:01
jjardonI think is better make depend  epiphany-browser on  epiphany-webkit02:02
micahgyou can't do that02:03
* micahg is wondering why it was broken out...02:03
jjardonmicahg, why not? (only curious)02:04
* micahg is referring to the source pacakge02:04
micahglike in intrepid02:04
jjardonI vote for remove epiphany-browser then02:08
micahgok, I changed the bug to EOL of epiphany-gecko02:09
* micahg just had a discussion with asac earlier about but titles having symptoms and not solutions02:10
micahg*bug titles02:12
jjardonmicahg, ok, thank you02:12
micahgthank you for finding this02:13
micahgdoes apport add need-duplicate-ckeck?02:31
micahg*-check02:31
* micahg had apport answer me :)02:33
micahghi03:05
robert_ancellmicahg, hey03:05
micahgso I think we discussed something about old packages and redirecting at some point03:05
robert_ancellmicahg, right. I guess some of these problems will go away once LP stops allowing users to directly report bugs03:06
micahgwhy owuld they do that?03:06
robert_ancellmicahg, in that users will report from the application and that will correctly pick the LP project to file against.  The problem is glchess has a problem, they go to launchpad and search for glchess, then report against the obsolete project03:08
micahgwell, I don't think that's a good diea03:08
micahg*idea03:08
micahgI'd rather have glchess redirect to gnome-games03:08
micahgI don't think everyone should have to be in the app to open the bug03:09
robert_ancellI think that is the direction bug reporting is moving, i.e. using apport to report bugs (so that the bug quality is high)03:09
micahgyes idneed03:09
micahgindeed, but I don't think the other functionality shoudl be closed out03:09
robert_ancellmicahg, I think the plan is to hide it03:10
* micahg will add it to agenda for hte next meeting (tomorrow) :)03:10
robert_ancelli.e. no "report bug" link, or that link will say "run apport pkg-name or go to help->report a problem"03:10
* micahg doesn't like that03:11
micahgbugs right now aren't just bugs but wishlist requests as well03:14
robert_ancellmicahg, yes but it's still important to know what version they are requesting against (which is often ommitted)03:17
micahgnot necesarily if it's an open ended feature request03:17
micahgrobert_ancell: meeting at 16:00 UTC tomorrow03:22
robert_ancellmicahg, thanks03:22
robert_ancellmicahg, oh I am away tomorrow but will read minutes03:23
micahgok03:23
micahgI added this to the agenda and there don't seem to be many other items03:23
micahgso it will probably be discussed03:23
* micahg hopes he can make the meeting :)03:23
dholbachgood morning06:03
thekorngood morning dholbach06:13
dholbachhola thekorn!06:13
thekornoha, dholbach is in spanish mode today ;)06:14
dholbachnot too much :)06:14
matti;]08:13
=== BjornT_ is now known as BjornT
=== dholbach_ is now known as dholbach
james_whola12:46
james_ware the logs Spanish in bug 426083?12:46
ubot4Launchpad bug 426083 in kerneloops "package kerneloops-daemon 0.12+git20090217-1ubuntu2 failed to install/upgrade: el subproceso script post-installation instalado devolvió el código de salida de error 1" [Undecided,New] https://launchpad.net/bugs/42608312:46
=== marjomercado is now known as marjo
mac_vpedro_: hi... how do i run valgrind for this> Bug #423394 it occurs immediately after login and is not consistently reproducible14:35
ubot4Launchpad bug 423394 in gnome-utils "gnome-screenshot assert failure: gnome-screenshot: ../../src/xcb_io.c:378: _XAllocID: Assertion `ret != inval_id' failed." [Medium,Incomplete] https://launchpad.net/bugs/42339414:35
pedro_mac_v, gnome-screenshot starts on login for you?14:36
pedro_that's weird14:36
mac_v that crash has occurred at login only , not any time else14:36
bddebianBoo14:46
=== asac__ is now known as asac
=== marjomercado is now known as marjo
micahgare we having a meeting?16:41
bdmurraymicahg: we could however, the attendance might be low since an announcement was not sent out16:43
bdmurraythen again most people who show up will probably be able to make it anyway ;-)16:44
micahgalso the agenda isn't that large16:46
bdmurrayso lets see how many attendees we have and adjust to later if necessary16:47
bdmurrayHi, we usually have a bug squad meeting on the 2nd Tuesday of the month.  This is today but no announcement was sent out.  Is anybody here for the meeting today?17:05
^arky^o/17:05
* micahg but leaving shortly :(17:05
pedro_i'm here17:06
bdmurrayhggdh: ?17:06
bdmurrayokay, well since the people with adgenda items are here why don't we cover the first 2 items at https://wiki.ubuntu.com/BugSquad/Meeting and have another meeting next week if necessary too17:08
bdmurraymicahg: go ahead17:08
micahgbdmurray: I can't stay too much longer17:08
micahgbut we can start I guess17:09
bdmurrayor we could postpone that until the 15th...17:09
bdmurraywhatever works best for you17:09
micahgmaybe17:09
micahgprobably better to postpone17:09
micahgnext week, I should be available for the whole meeting17:10
bdmurraymicahg: okay, great.  pedro_ then?17:11
pedro_yup so i won't be around next couple of weeks since i'm taking holidays17:11
=== mikefletcher is now known as mikefletcher|out
pedro_so i'm looking for someone who can take care of the hug days on those weeks17:11
bdmurraypedro_: which specific days?17:12
micahgalso any idea which packages?17:12
pedro_there's one for pulseaudio (no date yet though) and we need to look for an extra target17:12
pedro_https://wiki.ubuntu.com/UbuntuBugDay/Planning17:13
bdmurraymaybe not a package but the no package bugs or bugs with patches?17:13
pedro_sure, the last ones we ran about that were in April and May so yeah why not17:14
bdmurraypedro_: do you think one of those targets was more successful than another?17:15
pedro_the bugs without a package is always gets more attention17:16
bdmurrayokay, it could use it more too17:16
bdmurraypedro_: and which thursdays are you gone?17:18
pedro_17 and 24 Sept17:19
bdmurrayI could set the one on the 17th and would prefer it be the no package one17:20
* micahg has to run...see you next week17:23
bdmurraypedro_: does that seem alright?17:26
pedro_bdmurray, yeap sounds good to me17:27
bdmurraypedro_: and maybe sending an e-mail to the list to find someone for the 24th would be best?17:29
pedro_bdmurray, sure I'll do that17:29
bdmurrayand I'll setup another meeting for next week then17:30
* ^arky^ is waiting for his ubuntu-bugcontrol application review 17:39
thekornbdmurray, pedro_ I can do the announcement for the 24th18:42
bdmurraythekorn: and set it up?18:42
thekornbdmurray, yes, sure, why not. did you agree on a target?18:43
bdmurraypedro_: pulseaudio correct?18:43
pedro_bdmurray, thekorn yeah pulseaudio19:13
pedro_thekorn, thanks!19:13
=== Hellow_ is now known as Hellow
=== micahg1 is now known as micahg
BUGabundohey21:20
=== BUGabundo1 is now known as BUGabundo
kklimondachrisccoulson: btw, how can I debug gnome-power-manager/gnome-session/devkit-something crash?  All I get right now is this tail of .xsession-errors: http://pastebin.com/d41a0ecf821:56
kklimondaand a crash log which is a duplicate of.. /me searching for a bug21:57
kklimondaoh, there is a pending gnome-power-manager update, I'll see if I can still recreate it21:57
kklimondachrisccoulson: looks like it's a gnome-session crashing but I can't get a good stacktrace :/22:09
chrisccoulsonkklimonda - that looks more like Xorg crashing22:12
kklimondanow I have two crashes..22:12
kklimondachrisccoulson: but I get no .crash file for X22:12
kklimondaonly for gnome-session and gnome-power-manager22:12
kklimondachrisccoulson: how can I pinpoint it?22:13
chrisccoulsoni've seen someone else say they see a simultaneous crash in gnome-session, g-p-m and dk-power already, but they didn't get a backtrace22:14
kklimondachrisccoulson: here is a report for gnome-session: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-session/+bug/42650122:14
ubot4kklimonda: Error: This bug is private22:14
kklimondaech22:14
kklimondamade it public22:14
chrisccoulsonwill have to wait and see what the retracer makes of it22:15
kklimondaand here is one for g-p-m: bug 42650322:15
ubot4Launchpad bug 426503 in gnome-power-manager "gnome-power-manager crashed with SIGSEGV in g_str_hash()" [Undecided,New] https://launchpad.net/bugs/42650322:16
kklimondasure, I can reproduce it really easily so if you have any questions just ask22:16
chrisccoulsonhmmm, thats wierd. those are both SIGSEGV but your xsession-errors show an assertion, which is what I've seen someone report already22:16
chrisccoulsonactually22:17
chrisccoulsoni don't think there is an assertion there22:17
kklimondachrisccoulson: this pastebin is from crash after update: http://pastebin.com/d7df174ac22:18
chrisccoulsonkklimonda - i'm going to have some dinner now. i will have a look at your bugs when the retracer has dealt with them22:26
kklimondasure, thanks22:26
chrisccoulsonit would be useful though to see where those critical messages come from22:26
chrisccoulsonare you familiar with debugging them?22:26
chrisccoulsonthose messages are likely a precursor to the crash22:27
kklimondano, but I'm a fast learner :)22:27
chrisccoulsonto debug them, you can run apps with "G_DEBUG=fatal_criticals" in the environment. this will make them abort when the message is triggered, leaving a core dump (or a backtrace if you're running in GDB). This can show what led to the message22:28
kklimondachrisccoulson: set a breakpoint for a g_log() and reproduce crash?22:28
chrisccoulsonbut for gnome-session, it's a little trickier22:28
chrisccoulsonto debug gnome-session, you can log in to a failsafe xterm from GDM, then fire up GDB in your xterm like: "G_DEBUG=fatal_criticals gdb"22:29
chrisccoulsonthen you can run gnome-session from GDB - it should start your session as normal, then crash, and you should be able to get a backtrace showing where the message happened22:29
chrisccoulsonit would be useful if you could try that - but gnome-session issues on startup can be tricky to debug22:30
kklimondait's not on startup but after I unplug my usb mouse22:30
chrisccoulsonthat would be easier to debug then22:31
chrisccoulsonyou can attach GDB to the already running gnome-session22:32
chrisccoulsonbut you will still need to start your session from the failsafe xterm with "G_DEBUG=fatal_criticals gnome-session"22:32
kklimondaok, I'll see what I can do.22:32
chrisccoulsonthanks22:33
kklimondachrisccoulson: I got some gdb logs but not full23:02
kklimondachrisccoulson: http://launchpadlibrarian.net/31510719/gnome-session.gdb.log and http://launchpadlibrarian.net/31511412/gnome-power-manager.gdb.log23:04
kklimondafor some reason I have no symbols for dkp_device_get_object_path () and dkp_device_removed_cb () though..23:05
kklimondaand as they are probably most important I'll have to try to dig some more..23:09
kklimondachrisccoulson: any luck? I'm going to sleep soon and I've wondered if you need something more23:58

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