[05:08] I'm looking at bug 871083, which is a m-a issue caused by gzip compression. [05:08] Launchpad bug 871083 in gzip "gzip -9n sometimes generates a different output file on different architectures" [High,Fix released] https://launchpad.net/bugs/871083 [05:08] Many packages are affected, tracked as tasks under that bug. Most are Fix released in Precise. [05:09] I've come across several more packages which haven't been noticed previously. Should add these also as duplicates and affects: pkg on the same bug? [09:22] bug 985842 [09:22] Launchpad bug 985842 in gcc-4.4 "package gcc-4.4-base 4.4.7-1ubuntu2: arch-specific README.Debian makes package not co-installable with itself" [Undecided,Fix released] https://launchpad.net/bugs/985842 [09:22] still blocking co-installability in precise [09:23] can someone take a look and consider to nominate? === JamesJRH_ is now known as JamesJRH [13:34] can anybody please give me a screenshot of this errors.ubuntu.com page: http://paste.ubuntu.com/1255923/plain/ ? [13:50] and also this one please: https://errors.ubuntu.com/bucket/?id=%2Fusr%2Fshare%2Funity-mail%2Funity-mail%3ANameError%3Adecode_wrapper%3A%3Cmodule%3E%3A__init__%3Aupdate%3Aupdate_single%3Aget_header_wrapper%3Adecode_wrapper [14:26] hello i have a question, if i have to explain an user how to report a bug that already exist, like to add a "me too" what sort of information i should ask him to attach to the message and how should he procure it? [14:26] i know that to create a new bug report they should use ubuntu-bug package, but thats not the case [14:27] GridCube: dpends on the bug, he can "me too" the bug by clicking on "does this bug affect you?" (near the top) [14:28] GridCube: what's the bug number? (just curious) [14:29] roadmr, I was wondering about it, i do lots of user support on #xubuntu, but in this particular case it was this: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1051121?comments=all [14:29] Launchpad bug 1051121 in libreoffice "Spontaneous loss of text selection when dragging cursor." [Undecided,Confirmed] [14:30] GridCube: I suggest saying it affects him (click on "this bug affects 5 people. Does this bug affect you?" [14:30] GridCube: then maybe he can add a comment saying which application he has the problem with. If it happens every time, clear steps to reproduce are very valuable. [14:30] i just wondered what class of information could help the people who fix stuff to have when people reports problems, i think the most information they have its would be better, having more examples to work with and all taht [14:30] :) roadmr thats the kind of thing i needed [14:31] the results of lshw or something like that? [14:31] GridCube: three things: 1- what you did (in as much detail as possible) 2- what you expected to happen, 3- what happened instead [14:31] :) [14:31] GridCube: I don't think that'd be helpful, doesn't sound hardware-related to me [14:31] roadmr, i'm not talking about this particular case [14:32] GridCube: it depends on the bug's nature, if it's hardware related (my system doesn't suspend, video card doesn't work) then hardware information is useful [14:32] as said in general, what kind of information is useful [14:32] okay :D [14:32] GridCube: for software-related problems (some application crashed or is misbehaving), a clear way to reproduce the problem can be more useful than say an error trace [14:32] GridCube: (IMHO of course). But attaching error messages still trumps just saying "I dunno, it crashed" :) [14:33] hehe, i understand, thanks a lot roadmr [14:33] GridCube: here's a very good list of what kind of information is useful depending on the affected package or subsystem: https://wiki.ubuntu.com/DebuggingProcedures [14:40] jtaylor: maybe you can help me again ^^? [15:21] I think it's time to repeat my question [15:21] can anybody please give me a screenshot of this errors.ubuntu.com page: http://paste.ubuntu.com/1255923/plain/ ? [15:50] mitya57, why do you need to see it? [15:50] brendand: retext is my package :) [15:50] brendand_ ^ [15:52] I've already added a workaround for this to retext, but it would be still great to see the source [15:52] (which seems to be in docutils code) === emma is now known as em === e11bits_ is now known as e11bits === yofel_ is now known as yofel [18:22] Hello! [18:22] Can anyone help me "to target the bug to the appropriate Ubuntu releases"? (for SRU request) [18:22] I need it for https://bugs.launchpad.net/ubuntu/+source/netams/+bug/1060320 [18:22] Launchpad bug 1060320 in netams "does not work correctly with mysql 5.5" [Undecided,Fix released] [18:29] d06alexandrov: [18:29] done [18:30] if you need sponsoring you should subscribe ubuntu-sponsors [18:35] jtaylor: [18:35] Thank you! [18:35] Is it enough to subscribe ubuntu-sponsors and ubuntu-sru, for SRU request? [18:35] in principle yes, although a full debdiff would be appreciated [18:36] also the sponsor queue is very long right now and people are busy with the 12.10 release so it might take a while === Ursinha_ is now known as Ursinha === d06alexandrov_ is now known as d06alexandrov [22:55] i just had a crash in 12.10, and apport told me the bug had already been reported. it claims its a private bug though - https://bugs.launchpad.net/bugs/1060171 [22:55] jrgifford_: Error: bug 1060171 not found [23:14] hi i was advised to file a bug due to my webcam not working and i am a little confused about the process since i dont know what package to file against could i get some help [23:15] i Have a samsung webcamera and after looking at the windows inf file i discovered some vid/pids that were not mentioned when i do lsusb http://paste.ubuntu.com/1255860/ specificlly 093a:010f which is listed here http://cateee.net/lkddb/web-lkddb/USB_GSPCA_MR97310A.html my problem is i am not sure how to get this running could any one help me out ? i did find http://moinejf.free.fr/gspca-2.15.18.tar.gz which i was able to make and make install [23:15] how ever i cant modprobe gspca or mars so not sure what to do i am running ubuntu 12.04 [23:16] scatterp: looking [23:16] thanks [23:17] jrgifford_: bug is now public [23:20] scatterp: what is this gspca you downloaded? [23:20] hggdh, it seems to be the latest version by the "new maintainer" [23:21] ref: http://moinejf.free.fr/ "The new gspca maintainer is Hans de Goede." [23:22] my brother told me that gspca should be part of the kernel and it should just work so its a bug but i dunno [23:23] scatterp: yes, this sounds correct -- the linuxtv.org deals with the kernel [23:23] scatterp: open a terminal, and run 'ubuntu-bug linux' [23:24] 'linux' is the kernel [23:24] ok lets see [23:24] so it sounds like you want the new ids (and perhaps more than that) added to the kernel list [23:25] are you saying that if i recompiled the kernel and added the ids to some file it would just work.. because i have no idea how to do that but want to clarify to see if i understand [23:25] scatterp: it might. It might not. It might blow your kernel [23:26] ahh ok [23:26] and then a simpler tempory soloution if its possible might be to "force" the usb id [23:27] any "simpler temporary" solution will require you to do things that you do not sound familiar with -- which means you might not be able to recover from them, if they go wrong [23:27] ok good point [23:28] hggdh: thank you. [23:29] ok i run that command a window opened up asking me to send problem report to developers but it did not give me the chance to explain what the problem was ? [23:29] but you might try the #ubuntu-studio channel, they deal with these things [23:29] scatterp: you will have the chance to explain when the web page opens [23:29] ok === Ursinha is now known as Jorjao === Jorjao is now known as Ursinha [23:41] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1060527 is this ok hggdh [23:41] Launchpad bug 1060527 in linux "Samsung SEW 3035 webcam not working" [Undecided,New] [23:42] scatterp: at least for a start, yes. Which usbid would be your camera? [23:44] device 10 [23:44] scatterp: cuz I cannot see anything I would recognise as a camera in the USB output in your bug [23:44] oh, then 0d98:87a0 [23:45] yes [23:46] run, on the terminal, 'sudo lsusb -d 0d98:87a0 -v', and add the output to the bug [23:47] ok [23:47] this *may* give the kernel folks a bit more of data to work on [23:47] cool ok [23:56] done [23:56] anything else i can do to help ?