[08:46] <lubotu2`> In lubotu2`, maxery said: how is feeling
[16:27] <erUSUL> can someone kick wd409 ?
[16:27] <erUSUL> virtual kick XD
[16:45] <erUSUL> ikonia: kuni and katoe have/had the same ip FWIW
[16:45] <ikonia> nice !
[16:45] <ikonia> erUSUL: thank you
[16:47] <erUSUL> surprised that wd409 does not have the same too. looked like a sofisticated troll ;P
[16:47] <ikonia> yes


[05:07] <drew212> vish: are you around?
[06:26] <mistrynitesh> for sound related issues like headphones not working, https://wiki.ubuntu.com/Bugs/FindRightPackage#Sound asks to file the bug against 'alsa-base' package. However, http://packages.ubuntu.com/maverick/alsa-base asks bug to be filed against 'alsa-driver'. Does wiki needs updating? Also launchpad does not have 'alsa-base' in it search list of packages that can be assigned to a bug in ubuntu.
[06:33] <persia> "alsa-driver" is the source package that generates the "alsa-base" binary package.
[06:33] <persia> `ubuntu-bug alsa-base` will correctly file a bug against the "alsa-driver" source package.
[06:34] <mistrynitesh> but if someone has filed a bug without specifying the package, and I want to assign it, then I have two different suggestions at these two resources.
[06:35] <persia> It's the same thing.
[06:35] <mistrynitesh> actually i was looking at a list of bugs without package specified and trying to assign bugs to appropriate package
[06:37] <persia> Right, but "alsa-base" and "alsa-driver" are the same package from the viewpoint of LP bugs (which tracks source packages).
[06:37] <persia> It's important to tell folk to file their bug with `ubuntu-bug alsa-base` to collect the right information.
[06:38] <persia> That ends up being tracked in launchpad under https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bugs
[06:38] <mistrynitesh> yes, like in bug 659200, the reporter did not specify the package
[06:38] <ubot2> Launchpad bug 659200 in alsa-driver (Ubuntu) "No headphone sound after upgrading from 10.04 to 10.10 (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/659200
[06:38] <persia> And you set it.  Good job.
[06:39] <mistrynitesh> so checking the wiki page I gave 'alsa-base' in the package field, but launchpad gave it 'alsa-driver' and returned the message "'alsa-base' is a binary package. This bug has been assigned to its source package 'alsa-driver' instead."
[06:39] <persia> Right.
[06:40] <persia> You might find the output of `apt-cache showsrc alsa-base` interesting as further information about this.
[06:40] <mistrynitesh> so my point is, should wiki be modified to say 'alsa-driver' directly? For whatever it is worth
[06:40] <persia> No.
[06:41] <persia> Because the binary package actually installed on user systems is "alsa-base".
[06:41] <persia> That the source package ("alsa-driver") has a different name isn't important.
[06:41] <persia> But if one runs `ubuntu-bug alsa-driver`, apport will point out that the "alsa-driver" package isn't installed, which is expected, as it doesn't exist as a binary package.
[06:41] <mistrynitesh> ok, got it... because the ubuntu-bug will have to use the binary package
[06:42] <mistrynitesh> thanks persia for clarifying
[06:42] <persia> Right.
[06:42] <persia> Thanks for helping make sure all the bugs are assigned to the right packages.
[06:44] <mistrynitesh> hope it doesn't bother too much on the channel, but since I am 'technically' challenged, I find it imperative to double check here
[06:48] <persia> No, it's really appreciated, for a few reasons.
[06:50] <persia> Firstly, lots of other people may be unsure, and too shy to ask.  Secondly, it's better to ask here before committing the change to launchpad and sending mail to a bunch of folk that can never be unsent.  Thirdly, it helps build your interactions with others, so you folk consider you part of bugsquad and you feel connected to them: this will help a lot when you apply for bug control.
[06:54]  * mistrynitesh is wondering if he will ever be able to join bug control
[07:05] <mistrynitesh> now that you have encouraged me so much, I am going to spam this channel for a while :P
[07:06] <mistrynitesh> for bug 659668, i intend to assign it to 'linux' and ask the reporter to do the following: "Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it without more information.
[07:06] <ubot2> Launchpad bug 659668 in ubuntu "Ubuntu does not suspend for Lenovo Thinkpad T500 (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/659668
[07:06] <mistrynitesh> Please run the following command which will attach necessary information:
[07:06] <mistrynitesh> apport-collect 659668
[07:06] <mistrynitesh> Bear in mind that you may need to install the python-launchpadlib package from the universe repository with 'sudo apt-get install python-launchpadlib'. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.
[07:06] <mistrynitesh> We would also like to know if you are facing this problem for the first time in 10.10 or did you have same issues in 10.04 as well (in case you were using 10.04 before installing 10.10)?
[07:08] <mistrynitesh> sorry that was unintended. I just copied the text from launchpad :(
[07:09] <persia> Assigning to linux makes sense.  Asking the reporter to submit details if you don't have the same T500 makes sense.  Too much text in the channel isn't ideal :)
[07:09] <persia> Often, when asking for confirmation of a specific response, it's best to point to an entry in the wiki or use the pastebin.
[07:12] <RedSingularity> Anyone know when the next bug meeting is?
[07:12] <mistrynitesh> I am using the launchpad-improvment scripts. It makes life really easy
[07:13] <persia> RedSingularity, They tend to happen about monthly, but it's rarely worth waiting for one for most issues.
[07:13] <persia> RedSingularity, Why do you ask?
[07:15] <RedSingularity> persia: I know there was one today but I couldnt attend.  I want to make sure I attend the next one.
[07:16] <persia> Do you have something specific you want to raise at it, or just curious what happened?
[07:16] <RedSingularity> Just curious
[07:16] <persia> Attendance at the meetings is very much not required, or I'd be in trouble with my membership in Bug Control :)
[07:16] <persia> There's logs at irclogs.ubuntu.com
[07:17] <RedSingularity> Oh ok, I thought it was a requirement.  I will have a look at the logs though.  Thanks :)
[07:22] <persia> I think I manage to make maybe two meetings a year.  I do check the agendas, and read the logs though: if I have something to say that wasn't represented in the meeting, I'll share it, and if I have input I think is essential to go into a meeting I'll ask someone else to please mention it.
[07:23] <persia> But 90% of the time just sending something to the mailing list is enough: the meeting is mostly only useful for quick summaries, discussion of stuff that got stalled, or cleanly handling arguments about how to implement something.
[07:32] <mistrynitesh> if a reporter complains about poor sound quality in the latest release and not 'no sound', should it be assigned to 'linux' or 'alsa-base'? also should the reporter be asked to apport-collect the bug?
[07:35] <persia> "poor sound quality" needs a lot more information.
[07:35] <persia> It's usually alsa-base, and once set, needs apport-collect, but there are corner cases.
[07:36] <persia> I saw a libmad bug recently where only libmad caused sound quality issues (now fixed).
[07:36] <persia> Make sure the bug details precisely what the user did to create the "poor sound quality" experience.
[07:37] <persia> Attempt to replicate that.  If you can, and you have different hardware, then start looking at other sound generation techniques.
[07:37] <RedSingularity> persia:  If i am looking for someone in particular to look at a bug can i send a message out on the mailing list.  For example someone who works with transmission.
[07:37] <persia> If you can't, then go the alsa-base route.
[07:38] <persia> RedSingularity, There's no such set of folks reliably.  We don't have maintainers in Ubuntu, and we use self-selection to indicate which bugs interest us.  Everyone interested in bugs in transmission will already be subscribed to any bug with a transmission task, and have been notified about it.
[07:38] <RedSingularity> persia:  I can subscribe to all bugs that have to do with update-manager?
[07:39] <persia> RedSingularity, Yep.
[07:39]  * persia digs up the link
[07:39] <RedSingularity> How?
[07:40]  * RedSingularity waits
[07:40] <persia> https://launchpad.net/ubuntu/+source/update-manager/+bugs : on the upper right there ought be a "subscribe to bug mail" link.
[07:40] <persia> That should get you autosubscribed to all messages about update-manager bugs.
[07:41] <RedSingularity> Ah very nice!  Thanks so much.  This makes looking for them a lot easier!
[07:43] <persia> RedSingularity, Happy to help.  The central guiding principle of bugsquad is ASK!  There's almost always someone here who knows the answer (although I think none of us have all the answers).
[07:43] <persia> And when there isn't, there's usually someone who knows how to get it.
[07:44] <RedSingularity> I have found that to be the case here.  Its great.  I dont even log out of IRC anymore because thats where all the answers are.
[08:05] <RedSingularity> persia:  Can you mark a Wishlist item for me?  If you consider it worthy of course.
[08:08] <persia> Wishlist isn't about worthiness :)  Which bug?
[08:08] <RedSingularity> bug 659696
[08:08] <ubot2> Launchpad bug 659696 in update-manager (Ubuntu) "Terminal screen grows too big (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/659696
[08:08] <persia> (and it's best practice to ask "could someone please mark bug #nnnn wishlist: ${why it ought be wishlist}", rather than highlighting an individual)
[08:09] <persia> RedSingularity, I won't.  The request from the user is clearly wishlist, but is at odds with every other user.
[08:10] <RedSingularity> persia:  what do you mean?
[08:10] <persia> What is needed is detailed information about the user's environment: the resolution, DPI, current drag size of the terminal about which they complain, etc.
[08:10] <persia> If the configuration is changed to make the terminal smaller for that user, it might be too small for another user.
[08:10] <persia> If the configuration is changed to better handle DPI and resolution hinting, it is likely to be better for all users.
[08:11] <persia> But there's not enough information in that bug to verify that it can be actionable in that sense, so I won't mark it wishlist yet.
[08:11] <persia> Also, it probably belongs to python-vte or something, rather than update-manager.
[08:11] <RedSingularity> hmmmm how could I find what package it really belongs to?
[08:12] <persia> It is worth noting that we can't and won't support anyone who enables PPAs and extras, so it may be that this becomes an Invalid bug, depending.
[08:12] <persia> I think it's python-vte: you can verify by checking which handler update-manager uses for the embedded terminal (looking at the update-manager source).
[08:13] <persia> (note that we *can* support some extras users, when they aren't using any of the extras apps, so it's not quite like PPA users, who we often can't support at all)
[08:13] <RedSingularity> persia:  So if they are using a PPA then whatever bug it is should be considered invalad?
[08:14] <persia> No, but you have to do lots of extra research to make sure the package they are reporting the bug against isn't from a PPA, and none of the packages int he recursive dependency set of that package are from a PPA.
[08:15] <persia> And even if you've done all that, it might be that the bug is caused by some completely other package they got from a PPA that interacts badly with the package the bug is reported against (which isn't even interesting to fix, as PPAs aren't part of Ubuntu)
[08:15] <persia> So, I guess I shouldn't say we can't support all PPA users, but it's a lot more work for us, and we can't support a heap of problems that end up being related to PPA packages.
[08:16] <RedSingularity> ohh, interesting.  So a dependency list from the user would be good to see if it is dependent on a PPA that we dont support?
[08:17] <persia> What I usually do is to try to replicate the bug in normal Ubuntu first.
[08:17] <persia> If we have the bug, and we can replicate it, we no longer care about the user environment, because we can ask ourselves all the questions we need to triage it.
[08:17] <persia> And then provide clear documentation of how to reproduce, what component is affected, expected and observed behaviour, etc.
[08:17] <persia> If I can't replicate it, I ask for instructions from the user, and try harder.
[08:18] <persia> If I still can't replicate, I might start hunting down which packages the user has installed and the sources of those packages, but, in practice, I usually hunt for a bug I can usefully work on at that point.
[08:20] <RedSingularity> Is there a way to get a full dependency list from the user?  A command?
[08:21] <persia> Hey majeru.  Did you file a bug about it yet?
[08:21] <majeru> hi there, I'm having a problem with 10.10 on my Dell T3500. it constaltly panics with the default 10.10 kernel, from what I can tell the panic occurs while modprob-ing the AHCI driver
[08:22] <majeru> persia: where should I file it?
[08:22] <persia> RedSingularity, I think there is something, but I forget how: look at apport or requestbug source.
[08:22] <persia> RedSingularity, Often, if the bug is assigned to the right package, apport-collect will collect it.
[08:22] <persia> majeru, Launchpad, preferably with `ubuntu-bug linux`.  Just have patience with the annoying set of questions you will be asked.
[08:23] <majeru> ok, thanks
[08:23] <RedSingularity> persia:  ok
[08:23] <persia> s/requestbug/reportbug/
[08:25] <majeru> persia: is it ok if I post photos with the crash?
[08:28] <persia> majeru, If you can't get the logs any other way, yes.
[08:30] <majeru> ok, I found someone posted the same bug a few days ago
[08:41] <persia> Be careful: sometimes similar symptoms have different causes.
[08:41] <persia> Double-check that you have the same hardware, etc.
[09:41] <jibel> chrisccoulson, Hello, I'm a bit confused by the comments in bug 625793. When the users talk about g-s-d 2.32.0-0ubuntu4 they are referring to a version from a PPA ?
[09:41] <ubot2> Launchpad bug 625793 in gnome-settings-daemon (Ubuntu Maverick) (and 4 other projects) "Regression: Multiple Keyboard Layouts unusable: continuously changes layout + 100% CPU usage [updated] (affects: 288) (dups: 23) (heat: 1356)" [Critical,Fix committed] https://launchpad.net/bugs/625793
[09:42] <chrisccoulson> jibel, yes, klattimer uploaded a version to his PPA with ubuntu3 and ubuntu4 version numbers
[09:42] <chrisccoulson> which makes it a little confusing
[09:42] <chrisccoulson> we have to be sure when users are commenting that they are using the right version
[09:42] <jibel> chrisccoulson, 2.32.0-0ubuntu3 in -proposed is the correct version to test ?
[09:43] <chrisccoulson> jibel, yeah, that one fixes the most obvious reason for that bug, and it's working here
[09:43] <chrisccoulson> so i'd be surprised if people still have issues with that version :)
[09:44] <jibel> chrisccoulson, we have at least 3 positive comments. I'll mark it as verification-done for publication to -updates asap and stop useless metooing.
[09:44] <jibel> chrisccoulson, thanks.
[09:44] <chrisccoulson> jibel - excellent, thanks
[09:45] <chrisccoulson> jibel, it's still awaiting verification on bug 658777 too, but seb128 said he would have a look at that today
[09:45] <ubot2> Launchpad bug 658777 in gnome-settings-daemon (Ubuntu Maverick) (and 1 other project) "Invalid reads in keyboard plugin (affects: 1) (heat: 10)" [Medium,Fix committed] https://launchpad.net/bugs/658777
[09:45] <chrisccoulson> that's just a case of running it through valgrind to verify
[09:46] <chrisccoulson> there's a lot of other invalid reads in g-s-d, but those are pretty much all because of ubuntuone
[09:46] <chrisccoulson> somebody should probably investigate those ;)
[09:46] <jibel> chrisccoulson, that'd be great if he could do that.
[09:46] <seb128> is that python warnings?
[09:46] <seb128> ubunutone
[09:46] <chrisccoulson> seb128 - no, the ubuntuone g-s-d plugin causes lots of errors in valgrind
[09:47] <chrisccoulson> they don't look like python warnings
[09:47] <seb128> could you open a bug with the errors?
[09:47] <chrisccoulson> seb128 - yeah, sure
[09:47] <seb128> I will get it assigned to the u1 guys
[09:47] <chrisccoulson> thanks
[09:47] <seb128> I sort of disliked them to add g-s-d code to start
[09:47] <seb128> g-s-d is doing enough things, especially that any crasher in any of the .so bring it down
[09:48] <chrisccoulson> yeah, that's a bit of a pain, especially when things like nautilus don't restore the correct theme ;)
[09:49] <seb128> I'm wondering why
[09:49] <seb128> they pick themes changes dynamically no?
[09:52] <chrisccoulson> seb128 - i'm not sure how that's meant to work. it seems weird that it picks up theme changes, but doesn't restore the theme after g-s-d crashes
[09:52] <chrisccoulson> i would have thought it would all be the same events and the same codepaths ;)
[12:02] <alvin> Can I set bug 562742 to new again after it was 'fix released'? (It was fixed for only a week or so) What is the proper procedure to do this? I have a whole network suffering badly from this and seeing 'fix released' doesn't give peace of mind that this will get resolved eventually. (Also, I want to draw some attention to the bug. I have been receiving phone calls about this issue almost everey day now since Lucid came out.)
[12:02] <ubot2> Launchpad bug 562742 in linux (Fedora) (and 2 other projects) "r8169 ethernet MAC address changes in 2.6.32 kernel (affects: 14) (heat: 90)" [Unknown,Unknown] https://launchpad.net/bugs/562742
[12:07] <persia> alvin, It's very rare to go from "Fix Released" to "New".
[12:09] <persia> alvin, Based on comment #34, I'm certain that you have a slightly different bug with nearly identical symptoms.  Please file a new bug.
[12:10] <alvin> persia: ok, will do.
[12:10] <persia> Check against 2.6.32-25, and if you can replicate, just follow that bug to ensure you have attached all the right logs, etc.
[12:11] <persia> Sometimes with hw-related bugs it's tricky to know when it's the same and when it's different, but if the kernel was changed in a way that did fix it for the original reporter and didn't fix it for you, that's a fairly strong indication that yours is different.
[12:11] <alvin> Yes, symptoms are the same. I'll update them all again and file the new bug as soon as I can. (all machines are the same) Since lucid, all the mac addresses changed and eth1 was created. On top of that, several reboots are needed until the network goes up.
[12:12] <persia> I know the second part of that to be false: there are other ways to reset the network interface initialisation (although reboot might be easy)
[12:12] <persia> But if your mac addresses are changing, then that's not ideal.
[12:41] <alvin> Yes, there are other ways, but none that do not require root access. The users don't have that.
[14:31] <mistrynitesh> can bug 659668 marked confirmed/triaged?
[14:31] <ubot2> Launchpad bug 659668 in linux (Ubuntu) "Ubuntu does not suspend for Lenovo Thinkpad T500 (affects: 2) (dups: 1) (heat: 20)" [Undecided,Incomplete] https://launchpad.net/bugs/659668
[15:19] <hggdh> mistrynitesh: I would defer to JFo on that (kernel issues)
[15:20] <hggdh> mistrynitesh: BTW, thank you for resetting the package and asking for data collection
[15:22] <mistrynitesh> hggdh: sorry I was away for a while... JFo? whats that?
[15:24] <nigelb> its a who, not what
[15:25] <hggdh> mistrynitesh: he is the kernel interface for triaging
[15:26] <mistrynitesh> oops!
[16:50] <jibel> pedro_, I'll organize the regression bugday next week (Oct. 21rst) What do you think ?
[16:51] <pedro_> jibel, sounds fine to me
[16:51] <pedro_> jibel, may you please add the date to the planning page?
[16:52] <jibel> pedro_, Yep.
[16:52] <pedro_> thanks jibel
[16:54] <bbordwell> vish, hello, you are familiar with light-themes correct?
[17:06] <xteejx> Afternoon all :)
[17:06] <ngi> afternoon
[17:06] <xteejx> ngi: Hi
[17:06] <xteejx> :)
[17:08] <xteejx> Shouldn't the topic be changed? Our meeting was yesterday :)
[17:09] <hggdh> aye, by someone with access to it :-)
[17:10] <xteejx> hggdh: I like the way you just pop up with a comment lol :)
[17:10] <xteejx> How we doing?
[17:10] <hggdh> good, I guess. I am still alive, so this is good
[17:10] <ngi> that is always a plus
[17:10] <xteejx> heh true I suppose
[17:11] <xteejx> Weird...my emails aren't getting thru to ubuntu-uk mailing list
[17:13] <ngi> the server must be more than 500 miles away :p
[17:15] <jpds> ngi: Thank goodness for the speed of light.
[17:15] <ngi> :)
[17:22] <ngi> hmm... this is interesting ...
[17:23] <ngi> I'm tyring to compile a 32bit in lucid, statically linked, and I get "illegal instruction" upon execution
[17:24] <popey> xteejx: they are :)
[17:24] <xteejx> Probably on the moon
[17:24] <xteejx> popey: I wasn't too abusive was I?
[17:24] <xteejx> ngi: A 32 bit what?
[17:25] <ngi> opps, missed a word, a 32bit program
[17:25] <xteejx> ;) ermmm if you say exactly what you're trying to do, maybe someone can reproduce it
[17:26] <popey> xteejx: was a bit harsh
[17:26] <ngi> there we go, compiling an program that uses strspn() and linking statically
[17:27] <xteejx> popey: The apology should come thru sometime today, but it just pees me off that people think and say we're useless
[17:27] <xteejx> Wouldn't be here if we didn't care
[17:28] <xteejx> Oh well, I suppose MCSE can be offensive to some hehe :D
[17:29]  * xteejx hides and goes back to triaging
[17:58] <eboyjr> http://pastie.org/1218527
[17:58] <eboyjr> Would that be considered a bug in 10.10? It was fixed by logging out and then back in
[17:59] <ngi> eboyjr: which shell were you under ?
[17:59] <eboyjr> ngi: bash
[17:59] <ngi> hmm, strange I thought bash really looked into all the PATH paths all the time
[17:59] <eboyjr> I _did_ accidentally install the package `node` and then purged it
[18:00] <eboyjr> and then installed the `nodejs` package and then purged it
[18:00] <ngi> ah, well, maybe it need a refresh
[18:00] <ngi> in zsh it's the "rehash" command
[18:00] <eboyjr> and then i just compiled from source
[18:00] <ngi> no idea about bash :p
[18:00] <eboyjr> compiled nodejs from source, and okay thanks ngi :)
[18:01] <eboyjr> in bash it's logout and ssh $SERVER in my case :p
[18:21] <ngi> http://pastie.org/1218614
[18:22] <ngi> opps, forgot to specify this was on a amd64 version of ubuntu
[18:26] <ngi> not sure under which package I should submit this bug ...
[18:30] <xteejx> ngi: Is the package with those includes an Ubuntu package?
[18:33] <xteejx> Probably file it against php5 or gcc - php5 if it's the same as is in our php packages
[18:34] <xteejx> (assuming its the php strspn of course)
[18:58] <rusivi> Regarding Ubuntu bug 147203 was looking around and found that BSD already made the WG11T USB driver for their platform via http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/if_uath.c?rev=1.10&content-type=text/x-cvsweb-markup I am not familiar with the code (one step at a time), just wanted to check in on it see what the chat thought.
[18:58] <ubot2> Ubuntu bug 147203 in linux (Ubuntu) (and 1 other project) "Netgear WG111T not auto-sensed (dups: 2) (heat: 26)" [Undecided,Confirmed] https://launchpad.net/bugs/147203
[18:58] <rusivi> WG11T = WG111T
[19:20] <hggdh> rusivi: add the link in (at minimum it will be a reference). But please be aware that the *BSD and Linux kernels are not quite compatible
[19:22] <rusivi> hggdh: Ok.
[20:00] <jibel> QA meeting at #ubuntu-quality
[21:15] <BUGabundo> bah
[21:15] <BUGabundo> still no #ubuntu+1
[21:26] <charlie-tca> nope
[23:00] <moldy> hi
[23:01] <moldy> i am trying to use apport-collect from the command line. i cannot figure out how to use the launchpad login form. i can enter my username and password, but "continue" does not seem to be a link i can follow. any hints?
[23:04] <jibel> moldy, LP is under maintenance for 2 hours.


[05:54] <brinzhang> hello team, I would like to using launchpad to tracing OpenStack Cybrog's the bug, feature, but I cannot add each milestones for Cyborg, anyone can give some help?
[05:54] <brinzhang> How to add the stable/* branch and master branch as it's milestones
[05:56] <brinzhang> the index for openstac-cyborg project https://launchpad.net/openstack-cyborg
[07:34] <ricotz> hello :), it seem the PPA "cleaner" is not working correctly, deleted or superseded packages/binaries are not removed, which causes the repository size to exceed its limits
[07:53] <ricotz> e.g. https://launchpad.net/~ubuntu-mozilla-daily/+archive/ubuntu/ppa/+packages
[07:54] <ricotz> ilasc, hi ^ (sorry, I am aware it is a holiday)
[08:22] <ilasc> hey ricotz : no problem,  will be with you in a few minutes for this
[08:42] <ricotz> ilasc, thank you
[09:00] <ilasc> ok back here ricotz : this sounds familiar to me - I believe we do have a bug opened for it but can't remember which one, any chance you do ?
[09:06] <ricotz> ilasc, sorry, I am not aware of an existing report
[09:08] <ricotz> it seems to have start last weekend while looking at the context of http://ppa.launchpad.net/ubuntu-mozilla-daily/ppa/ubuntu/pool/main/f/firefox-trunk/
[09:08] <ilasc> ricotz: yeah I'm not having much luck finding here either, could you please file a bug on this and once the more senior folks on the team are back from holiday I can ask for help in finding it and I will link your report to existing bug
[09:08] <ricotz> *content
[09:09] <ilasc> right, indeed seems that way yes
[09:10] <ricotz> ilasc, I would assume this problem creates a lot of issues soon
[09:11] <ricotz> ilasc, thank you for your time
[09:12] <ilasc> ricotz: agreed and will be looking into this today - just not sure how much I can actually help at moment though
[09:15] <ricotz> ilasc, I guess look for the script which is responsible for cleaning old packages and make sure it is running :)
[10:41] <brinzhang> ricotz: hi, did you answer my question?
[11:06] <cjwatson> ricotz: it's intentionally disabled right now due to a spam problem
[11:07] <cjwatson> ricotz: I've bumped your quota a bit
[11:30] <ricotz> cjwatson, thank you
[11:31] <ricotz> brinzhang, hi, hmm, I don't think so
[11:32] <brinzhang> ricotz: yeah, I have resolved that issue, whatever thanks
[11:33] <brinzhang> do you know how to interaction between gerrit project and launchpad?
[11:33] <brinzhang> the other words, how to create the relations between gerrit project and launchpad?
[13:31] <zyga> hello
[13:31] <zyga> I have a login.ubuntu.com SSO account but I cannot see any options to add my 2FA devices
[13:32] <zyga> but I know this is supported for a launchpad account
[13:32] <zyga> is there a way to use this or enable it on a select account
[13:41] <ilasc> hi zyga : does this help in terms setting up or have you been through it already ?  https://help.ubuntu.com/community/SSO/2FactorAuthentication?action=show&redirect=SSO%2FFAQs%2F2FA
[13:41] <zyga> ah I see
[13:41] <zyga> thank you
[13:41] <zyga> so I need to join a launchpad group
[13:43] <zyga> I will give that a try, thank you
[13:44] <ilasc> indeed, you're welcome and we're here if that doesn't work please come back with questions
[13:45] <zyga> ilasc two comments on that
[13:46] <zyga> ilasc first, the group of 2fa enabled accounts is a public list so its' easy to see if someone doesn't have it
[13:46] <zyga> I wonder if that group should not be private
[13:47] <zyga> the second question is about why this is not enabled by default, it would be a great security benefit to many users
[15:23] <zyga> are landscape bugs tracked on https://launchpad.net/landscape?
[15:23] <zyga> cjwatson ^ (sorry for pinging former colleagues)
[15:24] <zyga> I would like to report a trivial bug in text visible inside the landscape product pages
[18:30] <sarnold> zyga: re 2fa enabled by default, I believe there are plans to make that more available; when people are employees, there's a chain of "talk with the person's manager and coworkers and verify that the person requesting 2fa token resets is the right person", but for community members, dealing with lost 2fa tokens requires just burning the account when the 2fa token is lost..
[18:31] <sarnold> zyga: so there's been efforts towards making it very easy to get backup auth codes to store away from the 2fa token, and stressing the importance of having multiple 2fa mechanisms
[18:38] <zyga-mbp> sarnold I see, that's an interesting perspective
[18:38] <zyga-mbp> sarnold I was setting up some SSO accounts for my work and I was puzzled by what controls availability of this feature
[18:38] <zyga-mbp> sarnold perhaps there is some middle ground, 2fa is fairly common now, so lack of transparency on this issue may look like simply lack of the feature in general
[18:39] <sarnold> zyga-mbp: yeah; it's documented on the wiki, but like everything else onthe wiki it's not clear if it's still relevant, and even *finding* the thing can be hard :) https://help.ubuntu.com/community/SSO/2FactorAuthentication?action=show&redirect=SSO%2FFAQs%2F2FA
[18:40] <zyga-mbp> sarnold yeah, I was expecting to find it on login.ubuntu.com somewhere
[18:40] <zyga-mbp> I was especially puzzled because my personal, ex-canonical account has 2fa
[18:40] <zyga-mbp> but my work account does not
[18:41] <sarnold> zyga-mbp: yeah, you're not the first leaver to be surprised by this :)
[18:41] <zyga-mbp> sarnold do you know how other commonly used services do 2fa reset? like git[hl]ab or others?
[18:43] <sarnold> zyga-mbp: not well enough; I know github has some recovery codes that they strongly recommend you write down
[18:44] <sarnold> (making sure I've got 2fa and backup codes on all my services has been on my todo list for far too long)
[18:48] <zyga-mbp> sarnold thank you for looking after this!
[18:48] <zyga-mbp> I know there's a lot of thankless work behind this
[18:50] <zyga-mbp> sarnold is there any remaining difference between launchpad.net sso and login.ubuntu.com sso?
[18:50] <zyga-mbp> as in if an account is first created here or there?
[18:50] <sarnold> zyga-mbp: ah, really, it's not me, I just gave some feedback to the folks who were doing the actual work, played rubber ducky/sounding board a few times
[18:50] <sarnold> zyga-mbp: ah, sorry, no idea there
[18:51] <zyga-mbp> just curious, mainly because i have a rather old account
[18:51] <zyga-mbp> thank you :)
[18:53] <zyga-mbp> sarnold one last question tonight, how do I report landscape bugs?
[18:53] <zyga-mbp> there's a trivial text error in a tootip
[18:53] <zyga-mbp> tooltip*
[18:53] <zyga-mbp> and I wanted report that somehow
[18:53] <zyga-mbp> is landscape project on launchpad the place?
[18:58] <sarnold> zyga-mbp: yes, it is; I filed a few bugs there recently and they did eventually get some attention :)
[18:58] <zyga-mbp> sarnold pefect, thank you!


[03:27] <Eickmeyer> OvenWerks: The Ubuntu Update Manager automatically uninstalls old (older than the previous version) of the kernel. I let it do it.
[16:37] <OvenWerks> Eickmeyer: my old kernels are removed and the old modules are removed but the old kernel module directories remain.
 Got any custom drivers installed or proprietary ones?
 Package manager doesnt delete folders which have crap in them still and they could be held other packages or added jn after by dkms modile
 Modules*


[10:28] <thevariousJ> gday
[10:28] <thevariousJ> y r firefox & firefox-4.0 seperate ?
[10:28] <thevariousJ> I thought firefox-4.0 already had rc-status
[10:33] <thevariousJ> hmm...o.k just clicked on your link which directed me to ppa:mozillateam/firefox-stable
[10:33] <thevariousJ> y r there 2 ppas ?
[12:17] <thevariousJ> :\
[14:06] <BUGabundo> why does FF4 always opens new windows when I have it set to tabs???????
[14:38] <chrisccoulson> fta - http://bazaar.launchpad.net/~chrisccoulson/libindicate/lp736240/revision/410 fixes your liferea issue
[14:40] <fta> chrisccoulson: thanks
[14:41] <fta> chrisccoulson, somehow, i would have used a define for the "com.canonical.indicate" prefix
[14:41] <chrisccoulson> possibly ;)
[14:41] <chrisccoulson> it doesn't matter too much though
[14:41] <fta> sure
[14:42] <fta> in my own code, i hate duplications
[14:42] <chrisccoulson> fta - if you change the interface name at a later date, it still needs to be changed in 2 files anyway
[14:42] <chrisccoulson> (it also needs to be changed in the xml description for the interface too)
[14:44] <fta> 1 line in 2 files, vs 16 lines in 1 file ;)
[14:45] <fta> damn, compiz re-organized my workspaces.. again
[14:45] <fta> i thought it was fixed :(
[18:22] <fta> micahg, jdstrand: http://ubuntuforums.org/showthread.php?t=1715928  :(
[18:23] <jdstrand> that is unfortunate, but the password regression would be even more unfortunate and people would complain about a lack of testing or care with the update
[18:24] <jdstrand> micahg is investigating the issue so we can provide the update
[18:25] <jdstrand> the idea being to revert the new behavior with the last update to be that of what is in the archive now. if that can be done, we'd push it out (talk to micahg for details)
[18:25] <micahg> jdstrand: should I respond on the forum?
[18:26] <jdstrand> micahg: probably a good idea. just say the update hasn't happened because of a regression and link to the upstream bug. then say the problem is being investigated by us and google
[18:27] <jdstrand> micahg: and by 'us', I mean 'Ubuntu', not the security team or you or anyone specifically
[18:27] <jdstrand> s/ally//
[18:27] <jdstrand> my two cents anyway :)
[18:42] <micahg> fta: sorry, I've been sick the past couple days and haven't been moving as fast as I would like, I'll try to get this sorted out today
[18:43] <fta> ok
[18:43] <fta> in the meantime, i will update natty for the arm ftbfs
[18:43] <micahg> fta: sounds good
[18:44] <fta> bug 745854
[18:44] <ubot2> Launchpad bug 745854 in chromium-browser "chromium-browser version 10.0.648.204~r79063-0ubuntu1 failed to build on armel" [High,In progress] https://launchpad.net/bugs/745854


[00:44] <CoreDreamSol> Hi friends, I am trying to join the Linux revolution, slowly but surely. :-)
[00:44] <CoreDreamSol> Also good afternoon/evening/morning.
[00:44] <Unit193> Howdy.
[00:45] <CoreDreamSol> I am being told Looking Glass is a good KVM companion so I can use my Nvidia GPU in a VM?
[00:45] <CoreDreamSol> I still need my Steam games and certain Adobe products so I'm forced to use Windows 10 as a vm anyway,
[00:45] <CoreDreamSol> Hi hi
[00:50] <CoreDreamSol> Is it hard to set that up?
[00:50] <CoreDreamSol> I assume I can use either QEMU or VirtualBox, both have KVM
[01:44] <user______> nyess
[01:44] <user______> hollo world
[01:44] <CoreDreamSol> hello
[01:45] <CoreDreamSol> love flybys
[02:02] <GSMarquis> I dropped Windows, Mac OS, for proper Ubuntu and its flavors 8 years ago today. It was a start of a Christmas extended vacation break from work and had the time to play. I boot Windows once a year for Turbo Tax. Other than that, its been an Ubuntu or flavor ever sense.
 4585
[03:03] <joe__> hello
[03:05] <joe__> hhenlo so
[03:07] <joe__> hio
[03:10] <joe__> hello people
[03:11] <juano-M> <juano-M "kdeconnect in Kubuntu is not det"> Ok, I just discover by try and error, it appears that the new company's router may have a hidden firewall. It was installed 2 weeks ago. 😏
[03:50] <magic_ninja> how should I upgrade to 20.10 if packages have been held back?
[03:50] <magic_ninja> Should I just wait until they are not held back anymore?
 What packages are held back?  If the held packages are due to a ppa  package, you may need to  ppa-purge .
[05:12] <Hash> When I click downloaded files in chrome, they don't open in the associated program in KDE. They used to in 18.04
[05:12] <Hash> In 20.04 it no longer works
[05:12] <Hash> How to fix this? Any ideas?
[05:13] <Hash> When I double click archive, I want it to open in ark, not anothe folder in dolphin
[05:13] <Hash> What all changed, this is very annoying
 We Used to Be Friends … https://www.google.com/search?kgmid=/g/1q5jfbj9z&hl=es-ES&q=the+dandy+warhols+we+used+to+be+friends&kgs=d7a81969afd8aee9&shndl=0&source=sh/x/kp/osrp&entrypoint=sh/x/kp/osrp
 216A
[11:33] <tomreyn> ?
[11:52] <BluesKaj> Hi folks
[12:02] <kab0m> Hi everyone. My sister accientally deleted th package wireless-regdb and panically shutdown her laptop with ubuntu while processing. after that the laptop stays black after the grub prompt. i booted via liveusb and did a "apt dist-upgrade". Now i can only boot via rescue mode and acpi=off, no audio device is found, no network device is found and the touchpad does not work...how can i fix this machine? Thanks in advance
[12:08] <tomreyn> reinstalling the package may help
[12:09] <tomreyn> if it has ethernet, this may work without this package installed.
[12:11] <kab0m> @tomreyn i only have ethernet via liveusb, and i already reinstalled that package, but nothing chnaged...still no network devices, audio devices and touchpad.
[12:12] <kab0m> i have no idea what has gone wrong with this machine. is there a way to "fix" or reinstall ALL packages without reinstalling the whole system?
[12:14] <tomreyn> kab0m: reinstalling all packages could be done, but this doesn'T really serve any purpose. if you are having data loss due to a broken storage you should replace the storage and do a full new installation instead.
[12:15] <kab0m> tomreyn: im not so sure about a real data loss, as i can still boot in rescue mode with acpi=off flag.
[12:15] <tomreyn> kab0m: if just reinstalling this package didn'T fix the problem then something else is wrong, or you made additional changes after it broke which you have not yet reverted.
[12:15] <tomreyn> i would start yby taking a look at the logs.
[12:16] <tomreyn> if you want to share them: journalctl -b | nc termbin.com 9999
[12:18] <kab0m> tomreyn: i did a "apt dist-upgrade" and a "apt full-upgrade" in a booted live-usb when chrooted into the system.
[12:19] <tomreyn> that's fine with me.
[12:19] <kab0m> tomreyn: should i run the journal command at any time when the system is running in rescue mode?
[12:20] <tomreyn> journalctl -b    displays what was logged by your system (kernel and systemd, the init system / process manager) and the running processes since the latest boot.
[12:21] <tomreyn> it doesn't matter whether or not this was a rescue boot, unless /var/log/journal wasn't made writable, then there's be no logs.
[12:21] <tomreyn> actually there's still be logs, but just from memory,
[12:22] <tomreyn> not about previous boots, as systemd-journald normally provides.
[12:25] <kab0m> ok. how can i export the logs to a file so i can transfer it via usb from the machine that has no network device?
[12:26] <tomreyn> journalctl -b > /path/to/logfile 2>&1
[12:27] <kab0m> tomreyn: ok, thank you ;)
[12:28] <tomreyn> you're welcome
[12:36] <kab0m> Ok, here is the logfile: https://paste.ubuntu.com/p/3XWkNsRFSD/ i dont really what i should look out for.
[12:46] <kab0m> when i try to boot "normally" (non rescue mode) the boot process always stops at "hid-generic 0003:048D:C100.0002: input,hiddev0,hidraw0: USB HID v1.10 Keyboard [ITE Tech. Inc. ITE Device(8910)] on usb-0000:00:14.0-9/input0"
[12:58] <tomreyn> can you boot into rescue without acpi=off though?
[12:58] <tomreyn> it seems the nvidia driver doesn't like this option too much
[13:00] <tomreyn> you have a service called "pipewire-pulse.service" which tried to run software that ios not available ("Failed at step EXEC spawning /usr/bin/pipewire-pulse: No such file or directory")
[13:04] <tomreyn> in line 2014 you see network-manager starting but failing to do so since another copy of its DBus service is already active.
[13:05] <tomreyn> in line 961, NetworkManager starts the first time
[13:07] <tomreyn> it seems like no wireless device is detected by network manager, and probably the kernel as a whle.
[13:07] <tomreyn> you should run    lspci -knnv    and see whether there is one listed
[13:08] <tomreyn> kab0m: ^
[13:10] <kab0m> tomreyn: when i try to boot in to rescue mode without acpi=off the screen stays black and nothing happens after grub.
[13:13] <tomreyn> kab0m: hmm, maybe try without "acpi=off" but with "nomodeset" or "nvidia.modeset=0"
[13:16] <tomreyn> actally i thinkt he latter should be "nvidia.drm.modeset=0"
[13:16] <tomreyn> (instead of "nvidia.modeset=0")
[13:17] <tomreyn> so this looks like an nvidia issue to me, not one related to the wireless regdb
[13:18] <kab0m> tomreyn: did not work. none of them...hmmm
[13:18] <tomreyn> kab0m: did you do an "apt update" before the "apt dist-upgrade"?
[13:19] <tomreyn> and did you have initrds rewritten?
[13:19] <kab0m> tomreyn: i tried but kde was telling me: in kde neon please use pkcon instead of apt update
[13:20] <kab0m> tomreyn: i did a "update-grub and "update-initramfs -u -k all"
[13:20] <tomreyn> okay, and did you run pkcon?
[13:21] <kab0m> tomreyn: pkcon did not work in the chroot environment because o any service missing...it was a real pain haha
[13:22] <tomreyn> it's usually better not to update *all* initrds in such situations so you 'll still have older kernels with their older initrds available.
[13:22] <kab0m> ohhhh
[13:22] <tomreyn> thats just a suggestion for next time you'rein this situation
[13:23] <kab0m> tomreyn: thank you ;)
[13:24] <kab0m> should i try to uninstall the nvidia driver in live usb mode? maybe it boots with the default nuoveau driver
[13:24] <tomreyn> it would be good to see a log from when the screen remained black, if you can produce this and make it available.
[13:24] <tomreyn> maybe temporarily uninstalling the nvidia driver could help, yes. or disabling secure boot is thats enabled
[13:25] <kab0m> tomreyn: i dint know how i should produce a logfile from the state of a blackscreen.
[13:26] <tomreyn> you boot into the blkackscreen, wait a while for it to boot up fully, then ctrl-alt-f to switch toi a tty, then ctrl-alt-del to trigger a reboot. journalctl -b -1 should then have the previous log.
[13:26] <tomreyn> i'm afraid i need to leave it there for a bit, i need an hour of beauty sleep ;-)
[13:26] <tomreyn> good luck.
[13:35] <kab0m> tomreyn: thank you very much for your help so far. Sleep well ;_)
[13:35] <kab0m> ;-)
 hello everyone. single ssd with win10 and kubuntu and leap. opensuse's grub recognizes and install all 3 OSs. kubuntu 's grub only itself and win10. my mistake, or bug? regards
 @Max, I have seen issues with Kubuntu install failing to find all boot devices.  This video may help fix it: https://www.youtube.com/watch?v=r7meKJsjqfY
 👍 tnx
 Kdeconnect is amazing. I even have it on my macbook
 @DarinMiller, can't we use os-prober for that ?
 Yes, OS prober should work.  We need to fix the installer so no repair is required, However, I don't test multiple non-*buntu installations very often, so this issue misses our normal test procedures.
 (Photo, 513x745) https://irc-attachments.kde.org/XW5vRTgb/file_39793.jpg
 @Ren Will, What kind of stuffs?
[22:56] <joe_schmoe> sup faggots
[23:09] <joe_schmoe> hello
[23:10] <voxeltek> hey
[23:10] <joe_schmoe> how are you
[23:10] <voxeltek> good
[23:10] <joe_schmoe> that's good
[23:11] <joe_schmoe> do you have discord
[23:11] <voxeltek> yep
[23:11] <joe_schmoe> what is it
[23:11] <voxeltek> uhh
[23:11] <voxeltek> id prefer not to reveal it just yet
[23:11] <joe_schmoe> y
[23:11] <joe_schmoe> add meh
[23:11] <joe_schmoe> INfoUpgraders#0001
[23:14] <joe_schmoe> hi
[23:17] <joe_schmoe> hi
[23:20] <joe_schmoe> hello
[23:21] <joe_schmoe> hi
[23:22] <voxeltek_> hey
[23:22] <joe_schmoe> y
[23:22] <joe_schmoe> o


[01:29] <achiang> what is the process for requesting a backport into currently shipping kernel? say i have a patch i'd like to see in karmic...
[01:30] <achiang> hm, and i guess i'd want to see it backported to lucid too, since /subject says it's based on .32
[01:30] <achiang> http://bugzilla.kernel.org/show_bug.cgi?id=15064
[01:30] <ubot3> bugzilla.kernel.org bug 15064 in Config-Processors "no deep C-states on core-i7, thus no turbo" [Normal,Resolved: code_fix]
[01:32] <achiang> without that patch, lots of folks are experiencing issues on the new batch of Intel Core i7 laptops
[01:32] <crimsun> achiang: is it in a .32.x point release?
[01:35] <achiang> crimsun: hm, no. we did not mark it for -stable
[01:35] <achiang> crimsun: i mean, linus hasn't even pulled it yet, but even after he does, we didn't tag it with -stable, so it won't get picked back up by gregkh
[01:36] <crimsun> I suppose the most straightforward way is to file a bug affecting linux and get it into a point release
[01:37] <achiang> crimsun: you mean a launchpad bug?
[01:37] <crimsun> yes, https://bugs.launchpad.net/ubuntu/+source/linux/+filebug
[01:39] <achiang> crimsun: reading the KernelTeam homepage to try and find the policy; do ubuntu only backport patches in the -stable trees?
[01:41] <crimsun> achiang: I'm unfamiliar with the precise SRU policy/policies for each Ubuntu release; smb/rtg/apw would be best to ping on that.
[01:46] <dhillon-v10> ogasawara: ping regarding glibc changed in the lucid kernel
[01:49] <JFo> dhillon-v10, can you elaborate for the channel at large? perhaps someone here can help you.
[01:51] <JFo> and I am also not sure what you mean about glibc changing in the kernel... it isn't in the kernel
[01:57] <dhillon-v10> JFo: hi there, sorry for the delay, a friend of fine and a lot of other people are experiencing this problem: when they use kvm with lucid images it breaks kvm, that's because of a commit made upstream to glibc which changed all calls that previously pointed to about() to free() now
[01:57] <dhillon-v10> JFo: and free() returns an aborting signal breaking kvm
[01:58] <dhillon-v10> JFo: I have a fix for it, but its a dirty hack, it involves adding a line to /etc/profile
[02:11] <cooloney> dhillon-v10: that looks like an glibc issue
[02:12] <dhillon-v10> cooloney: yup :) I read a conversation on LKML where they made this change to glibc so I was wondering how do I go about fixing it
[02:25] <cooloney> dhillon-v10: is there any bug tracker on launchpad for this issue, maybe we can help that.
[02:25] <cooloney> dhillon-v10: i guess ogasawara is going to sleep now.
[02:27] <dhillon-v10> cooloney: ahh right, sorry ogasawara, I will get you the link in a sec.
[17:51] <less1> Hi, I am sure if this is right place to ask this question.  I am working on ubuntu booting over http.  I have working prototype up at http://www.etherboot.org/share/pravin/UbuntuNet/  Can someone guide where can I get more feedback about this?
[18:13] <JFo> less1, you are looking for #ubuntu
[18:14] <JFo> someone in there should be able to help or at least point you in the right direction. :)
[18:14] <less1> JFo: thanks.. I will check it out.
[18:15] <JFo> certainly
[23:30] <crimsun> bjf: hi, some questions about the git packaging of cod alsa: firstly, is there supposed to be a metapackage in debian/control.d/flavour-control.stub? linux-alsa-driver-modules-PKGVER-ABINUM-FLAVOUR doesn't do anything useful, so I guess it's supposed to be renamed and a proper Depends added?
[23:31] <crimsun> bjf: I can push those changes for alsa-driver-cod-{karmic,lucid}.git to my tree on zinc
[23:40] <bjf> crimsun, I tried to just take the LBM packaging and reuse it, but I may have messed it up, I'm pretty green w.r.t. packaging
[23:40] <bjf> crimsun, I'd welcome any changes you have


 if you have time, I'd really appreciate it
[16:22] -queuebot:#ubuntu-quality- Builds: Lubuntu Desktop amd64 [Focal 20.04.5] (20220829) has been added
[16:24] -queuebot:#ubuntu-quality- Builds: Xubuntu Desktop amd64 [Focal 20.04.5] (20220829.1) has been added
[16:26] -queuebot:#ubuntu-quality- Builds: Ubuntu Kylin Desktop amd64 [Focal 20.04.5] (20220829) has been added
[16:27] -queuebot:#ubuntu-quality- Builds: Kubuntu Desktop amd64 [Focal 20.04.5] (20220829.1) has been added
[16:27] -queuebot:#ubuntu-quality- Builds: Ubuntu Budgie Desktop amd64 [Focal 20.04.5] (20220829) has been added
[16:30] -queuebot:#ubuntu-quality- Builds: Ubuntu Desktop amd64 [Focal 20.04.5] (20220829.1) has been added
[16:30] -queuebot:#ubuntu-quality- Builds: Ubuntu MATE Desktop amd64 [Focal 20.04.5] (20220829.1) has been added
[16:34] -queuebot:#ubuntu-quality- Builds: Ubuntu Studio DVD amd64 [Focal 20.04.5] (20220829) has been added
[16:39] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity amd64 [Focal 20.04.5] (20220829.1) has been added
[16:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity arm64 [Focal 20.04.5] (20220829.1) has been added
[16:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity s390x [Focal 20.04.5] (20220829.1) has been added
[16:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity ppc64el [Focal 20.04.5] (20220829.1) has been added
[17:49] -queuebot:#ubuntu-quality- Builds: Ubuntu Base amd64 [Focal 20.04.5] (20220829.1) has been added
[17:49] -queuebot:#ubuntu-quality- Builds: Ubuntu Base armhf [Focal 20.04.5] (20220829.1) has been added
[17:49] -queuebot:#ubuntu-quality- Builds: Ubuntu Base arm64 [Focal 20.04.5] (20220829.1) has been added
[17:49] -queuebot:#ubuntu-quality- Builds: Ubuntu Base ppc64el [Focal 20.04.5] (20220829.1) has been added
[17:49] -queuebot:#ubuntu-quality- Builds: Ubuntu Base s390x [Focal 20.04.5] (20220829.1) has been added
[17:49] -queuebot:#ubuntu-quality- Builds: Ubuntu Base riscv64 [Focal 20.04.5] (20220829.1) has been added
[18:50] -queuebot:#ubuntu-quality- Builds: Ubuntu Server arm64+raspi [Focal 20.04.5] (20220829.1) has been added
[18:50] -queuebot:#ubuntu-quality- Builds: Ubuntu Server armhf+raspi [Focal 20.04.5] (20220829.1) has been added
[18:50] -queuebot:#ubuntu-quality- Builds: Ubuntu Server riscv64+unleashed [Focal 20.04.5] (20220829.1) has been added
[18:50] -queuebot:#ubuntu-quality- Builds: Ubuntu Server riscv64+unmatched [Focal 20.04.5] (20220829.1) has been added


[00:16] <RAOF> thopiekar: I'm not entirely sure what you're trying to do, or what the actual problem is.  Pastebinning the complete error message is generally useful.
[00:17] <thopiekar> RAOF: got it now working.. I want to build Xorg 1.9 with ABI 8 on natty..
[00:17] <thopiekar> basicly a downgrade for emgd drivers..
[00:17] <thopiekar> see ppa:thopiekar/emgd
[00:18] <thopiekar> I still needed to downgrade libxi and some other x11proto packages..
[00:18] <thopiekar> xorg-server will follow when the deps I uploaded are built
[00:18] <RAOF> Ah, right.
[00:19] <RAOF> Yeah, to actually install xorg 1.9 you'll need to rebuild all the drivers.
[00:20] <thopiekar> sure worked well, too. I set as version xorg-server-dev (uploaded version)  as dep for the drivers..
[00:21] <thopiekar> finally I'll add a meta-package keeping these packages from upgrading to nattys packages..
[00:21] <thopiekar> here Xorg 1.10 with ABI 10
[12:48] <soren> Are these USB<->VGA things supposed to "just work"?
[13:01] <RAOF> soren: No, in *so* many ways.
[13:02] <RAOF> soren: The kernel DRM doesn't know about them, and until recently didn't accept anything not hanging off something which looks sufficiently like a PCI bus (although Dave Airlied has done some work here) and X doesn't know how to probe USB devices.  An xorg.conf is mandatory.
[13:08] <soren> RAOF: ..but it can be made to work?
[13:08] <soren> RAOF: I mean, without writing a driver myself :)
[13:08] <RAOF> soren: In theory, yes.
[13:09] <soren> I have a Lenovo USB port replicator with a DVI output on it. I'm trying to work out which driver it's supposed to work with.
[13:10] <RAOF> Maybe displaylink?
[13:11] <RAOF> But it's entirely possible that the Lenovo USB port thingy doesn't currently have a driver, actually.  All USB video devices are not necessarily the same.
[13:12] <soren> RAOF: Darn it. I went with the Lenovo in spite of the lacking details on chipsets, because Lenovo stuff tends to be very well supported.
[13:13] <RAOF> Does it only plug into USB, or does it plug into the docking port thingy?  Presumably you've tried just plugging it in and seeing if it works? :)
[13:15] <soren> Just USB.
[13:15] <soren> ...and yeah, just plugging it in doesn't do much (in terms of video).
[13:15] <soren> at all.
[13:18] <soren> Oh, well.. I guess I could use another door stop.
[13:20] <RAOF> :/
[13:21] <RAOF> There either might already be a driver or it might be easy to modify an one to work.
[13:22] <soren> Smells like something that needs both time *and* motivation. Two scarce resources.
[13:26] <RAOF> Yup.
[13:26] <RAOF> Googling for whatever chipset's on the other end of the USB tree might yield a low investment reward.
[13:47] <soren> RAOF: Information seems very, very limited.
[13:47] <soren> 17ef:3033 is the USB id of the port replicator. http://paste.ubuntu.com/602251/
[13:48] <soren> search for "USB Video".
[14:00] <soren> Ok, since I declared it a door stop anyway, I decided to void the warranty and take the thing apart to find out which chip is in it.
[14:04] <soren> Silicon image 164ctg64
[14:06] <tjaalton> try setting up the -sisusb driver
[14:07] <soren> tjaalton: I tried. It just said it didn't find any supported device, but I guess that could just mean it didn't recognize the USB vendor/product.
[14:10] <soren> Hm.... /me treis
[14:10] <soren> tries, even
[14:10] <tjaalton> is sisusbvga module loaded?
[14:10] <tjaalton> +kernel