[04:35] <iToast> so bazhang decided to change my +q to a +b?
[04:36] <iToast> I already knew He was going to make sure my ticket got no further.
[04:36] <iToast> Can I talk to a oper.
[04:37] <iToast> Elky?
[04:37] <iToast> Corey,?
[04:37] <iToast> I'd like to speak to a oper about this as this is abuse at this point.
[04:38] <IdleOne> if by oper you mean staff, they can't help you.
[04:39] <iToast> yes.
[04:39] <iToast> Staff's are opers...
[04:39] <iToast> IRC Terms Staffer = Network admin Oper = Channel admin
[04:39] <IdleOne> send an email to the IRCC and they will get to it ASAP. we channel ops have no access to the IRCC email.
[04:39] <iToast> I emailed IRCC
[04:39] <IdleOne> now be patient
[04:39] <iToast> I also tried to get the +q removed in here but he told me to leave the channel if I having nothign further
[04:40] <iToast> as I explained to another op how it's oppinion +q'd
[04:40] <iToast> Now he's raised it to a +b over him not liking my oppinion.
[04:40] <IdleOne> right, you tried to resolve the +q and were not satisfied with the outcome. You emailed the IRCC, now wait for them to reply.
[04:40] <iToast> The reason I sent the email is I couldn't get another op when he wanted me to leave
[04:41] <IdleOne> Well you got me now.
[04:42] <IdleOne> I am telling you the +q/+b will not be removed until the IRCC has reviewed the issue.
[04:42] <iToast> That's a first. I get a op that's not a friend of the op who issued the command.
[04:43] <iToast> So how long does it take on average to get a reply or even a view on the ticket.
[04:43] <iToast> hey gry !
[04:43] <IdleOne> all depends.
[04:43] <IdleOne> We are volunteers, there is no schedule.
[04:44] <iToast> I wish canacole could have paid workers be OP's in these channels.
[04:44] <IdleOne> You think that would make it easier for you to get unbanned?
[04:44] <iToast> Any abuse / disputes like this could result in them loosing their job, so there would NEVER be a oppinion based +q or +b
[04:45] <iToast> No, I think it would make sure a OP has a STRONG NON OPPINION based reason for their actions.
[04:45] <IdleOne> all +q and +b are opinion based, you just happen to disagree with the opinion.
[04:45] <iToast> No they are not.
[04:45] <iToast> They are based on rule breaking and abuse...
[04:45] <iToast> That'd be like a Freendode staffer banning you because they don't like your name
[04:45] <IdleOne> iToast: I can see we aren't going to get anywhere. I suggest you wait patiently for the ircc to reply to your email. give them at least 72 hours to reply.
[04:46] <iToast> IDK why It had to be elevated to ircc...
[04:46] <IdleOne> because you disagree with the judgement of the op and wanted to complain to someone in charge.
[04:47] <iToast> I wanted a whole DIFFERENT op to deal with it.
[04:47] <IdleOne> the ircc are the people in charge.
[04:47] <iToast> I wish the IRC ops were paid workers.
[04:47] <IdleOne> So do we.
[04:47] <IdleOne> not going to happen.
[04:47] <iToast> I said paid workers, not the same ops now.
[04:48] <iToast> even if it was the same ops not everyone would be hired.
[04:48] <IdleOne> also, I am a whole different op and I agree with the decision bazhang took
[04:48] <iToast> Would you like to explain how come?
[04:48] <IdleOne> because we have the same opinions.
[04:48] <iToast> How so.
[04:48] <IdleOne> usually
[04:49] <iToast> He banned me as I said I think people should have to try and help themselfs before they come to the IRC channel
[04:49] <iToast> So you think everyone should be spoon fed and not try anything on their own?
[04:49] <iToast> The problem the guy was having was a quick google away but you guys treat it like "GOOGLE FU"
[04:50] <iToast> I even answered his question.
[04:51] <iToast> I'm probably going to get a +Q here for thinking people should help themselfs first.
[04:51] <IdleOne> nope, but I'm going to ask you to part the channel and wait for the ircc to respond to your email.
[04:52] <iToast> Same thing bazhang did. Asked me to leave as there was a differing oppinion... and it was abuse over a oppinion.
[04:52] <iToast> I'l be in #ubuntu-social
[06:36] <bazhang> smartboy is awfully trigger happy with the bot
[06:36] <IdleOne> he's trying to gain points towards membership...
[06:36] <bazhang> yikes
[06:37] <IdleOne> I haven't really been paying attention but from what I see he is not really that helpful. He's trying though.
[06:37] <bazhang> doing a lot of /me after flagging others for ot is not impressive
[06:37] <IdleOne> indeed
[06:38] <bazhang> and redirecting to -server? that seemed out of the blue
[06:38] <IdleOne> well, it kinda sorta makes sense if you don't read the entire question and try to be first to answer
[06:39] <bazhang> and know nothing about the subject matter at hand, yeah
[06:39] <IdleOne> hehe
 ESAD.
[06:43] <IdleOne> haven't seen that one in a long time
[07:15] <IdleOne> bazhang: could you please tell andrew to knock it off with the ot comments. coming from me it will just be the police abusing him.
[08:28] <knome> o.O
[09:02] <bazhang> IdleOne, sorry, had to be away for a bit, missed it. that was andrewh92 or so I am guessing
[12:05] <alexm> we have a user in #ubuntu-cat who has many connections and it's been flooding the channel for a few days
[12:05] <alexm> e.g. http://irclogs.ubuntu.com/2012/08/13/%23ubuntu-cat.html
[12:05] <alexm> all those jaume_off* are connected from the same ip
[12:06] <alexm> i was going to ban the ip but i'd like to hear what you think first
[12:22] <Tm_T> ban the ip if it fits
[12:25] <alexm> ok, thanks, will do and will try to contact the individual behind the bot
[13:45] <bazhang> "I know this is totally offtopic, BUT..."
[14:05] <bazhang> apart from irssi and weechat, ircii is the only terminal based irc client I can seem to find
 I'm wondering: If I'm contributing to Ubuntu Studio, should I apply membership via the normal Ubuntu board or Xubuntu board?
 my server is being used in a botnet, my isp have called me and will soon block my internet connection, how can i fix it?
[14:19] <bazhang> I guess asking if it's ubuntu-server would be a propos
[14:32] <cprofitt> bazhang: did the issue with the botnet get resolved?
[14:38] <DJones> I think the only advise they were given was to reinstall, the only other thing they asked was how to avoid it in future
[15:05] <bazhang> yep, pretty much
[15:09] <cprofitt> I just talked with him... for the last 30 minnutes
[15:09] <cprofitt> it looks like he has IRC traffic coming from his server... and exposed SSH to the Internet w/o properly securing it.
[15:10] <cprofitt> I gave him links to a few things to secure it... and advised him a reinstall is wise when you do not know what has been done to your box
[15:13] <bazhang> ouchie
[15:14] <bazhang> I love it when users say they have tried "everything"
[15:19] <mneptok> they say that, and yet i still have a pen full of goats, and clean, unstained altars.
[15:19] <bazhang> :0
[15:24] <cprofitt> lol
[15:29] <cprofitt> bazhang: they have tried everything they know of...
[15:30] <cprofitt> its a limited set of information, or in some cases, none that they are choosing from
[15:30] <bazhang> cprofitt, he never did get back with the pastebin of what commands in "everything" he tried
[15:30] <bazhang> heh yeah
[15:31] <cprofitt> I think he was a bit nervous that I was a hacker at first...
[15:31] <cprofitt> he was very tight with information... then when I told him I did not have enough to really help him and sent him towards the forums he pasted some information tht helped a bit


[01:00] <ahoneybun> Hello folks! I'm wondering how we can enable git support in a repo like this one: https://code.launchpad.net/kubuntu-docs
[02:34] <mwhudson> RAOF: say are you able to do the tests you described in https://bugs.launchpad.net/ubuntu/focal/+source/glibc/+bug/1951033 comment  1?
[02:34] <mwhudson> we don't have a core20 snap to test with yet but maybe it makes sense to get ready :)
[02:35] <mwhudson> (i don't have any nvidia hardware)
[06:17] <hallyn> rbasak: argh, i *do* try to read my ubuntu.com email, but the replies about the telegram-desktop sru must have slipped by amongst the spam.  glad it got resolved!
[06:18] <hallyn> (so, so much spam there)
[09:06] <RikMills> schopin: FYI, https://paste.ubuntu.com/p/CcZWpcxqsH/
[09:09] <schopin> I'm assuming that's for xypron's kate patch? Thanks for looking into it :)
[09:10] <RikMills> schopin: it is
[09:11] <xypron> shopin: So you can sponsor it now?
[09:12] <schopin> xypron: I'll look at it again later today, yet
[09:13] <schopin> *yes
[09:13] <xypron> thanks
[09:40] <schopin> xypron: I just noticed the last comment on the kate bug regarding an upcoming release. Do you still want me to sponsor, or do you think it can wait 'til then?
[09:43] <RikMills> on reflection, I would say do now. who knows what transition may block things in 2 weeks
[09:45] <schopin> eh. so true.
[09:46] <schopin> glibc 2.35 in particular is looming.
[09:46] <RikMills> urgh
[11:55] <schopin> mwhudson: I'm wondering if we couldn't bump the parallelism value in src:rustc a bit higher than 2 to reduce the pain of working on the package?
[11:58] <schopin> mwhudson: asking because I *think* I've solved the FTBFS issue, but verifying it is of course taking forever.
[13:02] <xnox> or make it depended on whether one is building in launchpad, or outside of it? by like testing for that magic /BuildBlahBlah file
[15:40] <alexghiti> Hi guys, I have a bunch of packages that need a sponsor, if someone outside the ubuntu foundations team can have a look, that would be very nice :)
[15:40] <alexghiti> https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502
[15:40] <alexghiti> https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1958897
[15:40] <alexghiti> https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1958887
[15:40] <alexghiti> Thanks!
[16:12] <xypron> u-boot-menu - 4.0.4ubuntu1 is available in ppa:xypron/merge-from-debian looking for a sponsor. LP #1959241
[16:52] <bdmurray> answering my own question from yesterday this worked for search autopkgtest log files
[16:52] <bdmurray> retry-autopkgtest-regressions --blocks python3-defaults --log-regex EnvironmentVarGuard
[17:12] <xypron> schopin: RikMills: for the ktextedtor package in proposed we now get "https://launchpadlibrarian.net/582482377/buildlog_ubuntu-jammy-riscv64.ktexteditor_5.90.0-0ubuntu2_BUILDING.txt.gz". I guess there has been a toolchain change that will cause trouble for a lot more RISC-V builds due to a mismatch of GNU Binutils / GCC for the new package and already compiled ones. This would mean a whole lot of mackages have to be recompiled?
[17:13] <RikMills> doko: ^ ?
[17:21] <schopin> xypron: this is a bit out of my depth, I'll have to let you sort this out :-/
[17:22] <xypron> schopin: a new binutils has been put into
[17:22] <xypron> jammy which changes the -march flags
[17:22] <xypron> diff -Nru binutils-<IP_ADDRESS>20106/bfd/elfxx-riscv.c binutils-<IP_ADDRESS>20126/bfd/elfxx-riscv.c
[17:26] <RikMills> xypron: is this going to impact a lot of things?
[17:26] <xypron> RisMills: yes
[17:30] <xypron> RikMills: bug 1959325
[17:32] <RikMills> xypron: OpenSBI? excuses says a missing build on amd64 for that
[17:33] <xypron> RikMills: cross compiled for riscv64
[17:33] <RikMills> aha
[17:36] <RikMills> lucky I don't have a huge amount to upload right this minute!
[18:55] <gombara> hello. I have been trying to automate install of Ubuntu 21.10 desktop. All the information I could found online points to modifying grub.cfg to provide command line options to kernel. but for some reason I could not get it working. after the boot it lands in live session desktop instead of starting the install. any ideas?
[21:16] <jawn-smith> exit
[21:16] <jawn-smith> wrong window


[10:25] <xnox> apw, how does linux kernel platform device enumeration happen using ACPI?
[10:25] <xnox> https://www.kernel.org/doc/Documentation/acpi/enumeration.txt
[10:25] <apw> xnox, magic ?  what are you asking ?
[10:25] <xnox> i mean, is it done in order / serially, or in parallel|randomly.
[10:25] <apw> acpi things are found on buses which support things with ids
[10:26] <xnox> in the code for hns_enet.c there is MODULE_DEVICE_TABLE (acpi, match) and that's it really and a probe.
[10:26] <apw> it is done in bus discovery order
[10:26] <xnox> usually, yes. but this is without a bus, as far as I understand.
[10:26] <xnox> because it is a platform device that is simply defined in ACPI because they can.
[10:26] <apw> it is being done against the dtb isn't it in that driver ?
[10:27] <apw> oh hmm, no it has both so who knows which i used
[10:27] <xnox> hm. i think it does both.
[10:27] <apw> it _does_ both but which was used on this platform
[10:28] <apw> HISI00C? appears in your ids i believe yes ?
[10:28] <xnox> good question. /me is n00b; yes, and I see ACPI paths in the sysfs.
[10:33] <apw> xnox, ok acpi is your bus in the kernels mid
[10:33] <apw> nmind
[10:34] <xnox> ok. so is there such a thing as the ACPI "bus" "id" aka order? =)
[10:34]  * xnox feels like these abstractions make no sense at all
[10:35] <apw> that is because you are a userspace engineer :)
[10:35] <apw> i think you caring which order i probe them is stupid
[10:35] <xnox> well, that is because the probe in my device driver allocates devno for the driver, and that is what is exposed in sysfs, and i am pondering to use that for stable device names
[10:36] <apw> the devices have unique identifiers so you can tell them apart
[10:36] <apw> and yet you refuse to use them
[10:36] <xnox> because vendor came back and said that ae-handle and ae-pidx-in-ae or whatever it was, together do identify unique ports
[10:36] <xnox> but do not have any correspondence with the physical board layout.
[10:37] <xnox> the physical board layout corresponds to the ACPI order of those devices.
[10:37] <apw> which likely means it is in the order they are in the acpi tables, whcih come from teh firmware
[10:37] <xnox> and i do want enh2p0 enh2p1 be the first and second ethernet ports. rather than enh2p4, enh2p3 be the first/second ports.
[10:38] <xnox> correct, and if kernel loads the acpi table, does a match, and then fires to create handles in parallel, my devno's will no longer be in acpi order =/ or so i am imagining things.
[10:38] <apw> so are they in reverse order or something
[10:38] <xnox> let me share the bug with you, one second.
[10:39] <apw> xnox, you already did
[10:39] <xnox> there are more comments from the vendor about hte acpi
[10:39] <xnox> https://bugs.launchpad.net/pearl/+bug/1681651
[10:40] <xnox> firmware node path....
[10:42] <apw> are you now able to find the Device (...) bit when you are probed ?
[10:42]  * xnox is afraid that i will get this wrong, and then my stable device names will be unstable.
[10:43] <apw> xnox, which series kernel are we using again ?
[10:43] <apw> xnox, i want to talk line numbers at you
[10:44] <xnox> 4.4
[10:44] <xnox> no
[10:44] <xnox> 4.10
[10:45] <xnox> wait no.
[10:45] <xnox> the yakkety hwe kernel
[10:45] <xnox> in xenial.
[10:45]  * apw stops talking to you
[10:45] <xnox> i have a branch of that checkout.
[10:45] <apw> ok at line 1914 of hns_enet.c ... is where it is handling a probe
[10:45] <apw> note that there we have a dev->fwnode which is an acpi thing
[10:47] <xnox> yeap.
[10:50] <apw> you look to be able to call acpi_device_data_of_node() on that, and that has a name element which i think is the string in the Device() stanza in the table
[10:50] <apw> but is that not available in the acpi information ?
[10:50] <apw> already exposed in sysfs ?
[10:54] <xnox> .... to be continued. The truth is out there.
[10:55] <xnox> i am suspecting that yes, it is all exposed in /sys/bus/acpi/devices
[10:56] <apw> xnox, probabally as a part of the path
[10:56] <xnox> yeah, or symlink targets or some such. but need to login to confirm =/
[10:57] <apw> as in in cat /sys/bus/acpi/devices/PNP0C14\:02/path
[10:57] <xnox> ls -latr view of /sys/bus/acpi/ is nice too.
[10:58] <xnox> ubuntu@ubuntu:~$ cat /sys/class/net/*/device/firmware_node/path
[10:58] <xnox> \_SB_.ETH4
[10:58] <xnox> \_SB_.ETH5
[10:58] <xnox> \_SB_.ETH0
[10:58] <xnox> \_SB_.ETH1
[10:58] <apw> that
[10:58] <xnox> horum, so we do have that. "firmware_node" =)
[10:58] <apw> there you go, that matches where i would expect it to be in the kernel data structures too
[10:59] <apw> and that is telling youu which acpi table it came from, and which object within it
[10:59] <apw> that is what they call them, and likley what we should call them
[10:59] <xnox> right. and somehow my wish is to translate 4 -> 0; 5 -> 1; 0 -> 2; 1 -> 3.
[10:59] <xnox> true.
[10:59] <xnox> (what you say)
[10:59] <xnox> and people will have to learn that they are 4501
[10:59] <apw> they may wish to not call them that, and change teh ACPI tables
[11:00] <xnox> i think acpi tables are fixed.
[11:00] <xnox> but i can ask.
[11:01] <apw> right, but they have picked these rather random names for a reason, what is that reason
[11:02]  * apw wonders how the bios affected names work, ...
[11:03] <apw> i think it is difficult to do anything other than use the names as they are, as as that says that dump is for a specific board
[11:03] <apw> another board will have different layouts of connectors
[11:04] <apw> and looking at that, the ports are in order of attachement to the internal device
[11:04] <apw> as in eth0 is port 0
[11:04] <apw> it really has 6 ports per device
[11:41] <xnox> ack.
[11:41] <xnox> apw, what about this stuff:
[11:41] <xnox> 0	./devices/LNXSYSTM:00/LNXSYBUS:00/HISI00C2:02
[11:41] <xnox> 0	./devices/LNXSYSTM:00/LNXSYBUS:00/HISI00C2:00
[11:41] <xnox> 0	./devices/LNXSYSTM:00/LNXSYBUS:00/HISI00C2:03
[11:41] <xnox> 0	./devices/LNXSYSTM:00/LNXSYBUS:00/HISI00C2:01
[11:41] <xnox> is this platform bus, and is there any guidance as to how things are named on LNXSYBUS? =)
[11:42] <apw> i don't think you can rely on it, as that is in the order the current kernel decides
[11:42] <xnox> http://paste.ubuntu.com/24548405/
[11:42] <xnox> right, and kernel is free to change that.
[11:42] <apw> they are _likley_ to be in the order of the ACPI table
[11:43] <xnox> and current driver does HISI00C2 and HISI00C1, and my guess is that one cannot have two HISI00C2 things defined in the acpi table....
[11:43] <apw> you can and they do
[11:43] <apw> look at ETH6 in the table
[11:45] <xnox> i see.
[11:46] <apw> but the order of teh HISI00C2:nn is in the order of teh acpi table
[11:46] <apw> if that order has meaning, and it may in thie case and not otheres
[11:46] <xnox> but the ETH* names are unique, and have one-to-one mapping with ae-handle + port-idx-in-ae
[11:47] <xnox> i wish networking was actual files in /dev/ such that i would be able to have symlinks to name the same thing in multiple ways, just like we do for hard drivers.
[11:48] <xnox> and then create symlinks by-acpi-name, by-acpi-order, by-ae-hand-port-idx-in-ae
[11:48] <xnox> et.c
[11:49] <xnox> ok. here comes a patch.
[11:51] <apw> xnox, but none of the fact they are 1:1 mappings tels you the intent of the table writer, they may have chosen the numbers randomly because "noone uses those"
[11:51] <apw> xnox, and just because teh writer of this table did one thing, the writer of the next may have done another
[11:52] <apw> xnox, which is why i don't think you can generically map them for any other table than this one
[11:52] <xnox> ..... it will be annoying if they randomly change those names.
[11:53] <xnox> does the  driver make up the HISI00C2:01 name?
[11:53] <xnox> i thought it did. In that case if driver breaks ordering, i can blame them =)
[11:54] <apw> that is acpi i believe, it is the first one of those it found and allocated
[11:54] <apw> which i believe means they are in table order, assuming we do not ever
[11:54] <xnox> parallelise that
[11:54] <apw> change to doing that in another order or parallel or ...
[11:55] <apw> you have no information which is reliable full stop
[11:55] <apw> either you believe the table or you don't
[11:55] <xnox> or acpi should export order in sysfs somehow, which is bonkers.
[11:55] <xnox> right, so. i will go with using 4501 names
[11:55] <apw> but the table order is just as likely to change as the names in teh Device(NNN) stanza
[11:56] <apw> in the sense they could change it.
[11:56] <xnox> i care that (a) systems with the same firmware (b) across reboots (c) get the same names
[11:56] <apw> so you have to pick one, either you enumerate them in order they appear in the table, or by the names they use in the table
[11:56] <xnox> ack.
[11:56] <apw> and if they randomly change those they will piss off their users
[11:56] <xnox> if there is different SKU, i don't chagne.
[11:56] <xnox> if there is different SKU, i don't care.
[11:57] <apw> but the same firmware does not mean the same device for all time
[11:57] <apw> as they can change that table and reboot, so ... you have to hope
[11:57] <xnox> and if kernel parallelises ACPI probing, it better give order hints when it calls and/or executes probes; or i will complain to the vendor to expose the acpi table order as a sysfs attribute.
[11:57] <apw> they will not change whichever key you chose
[12:32] <xnox> apw, digging into code. Udev already does ID_PATH and ID_PATH_TAG which are
[12:32] <xnox> E: ID_PATH=platform-HISI00C2:00
[12:32] <xnox> E: ID_PATH_TAG=platform-HISI00C2_00
[12:32] <xnox> but these are not set as ID_NET_NAME_PATH
[12:33] <xnox> i wonder if I can somehow enumerate _all_ platform nics, and have a table in udev to shortify the HISI00C things.
[15:21] <xnox> apw, in the /devices/LNXSYSTM:00/LNXSYBUS:00/HISI00C2:01 what does the :01 mean? acpi probe order number, or the hns-net driver sequence number? cause hns-net driver handlees both HISI00C1 and HISI00C2
[15:21] <xnox> and i am wondering if i will get:
[15:21] <xnox> HISI00C1:0
[15:21] <xnox> HISI00C2:0
[15:21] <xnox> or if i will get
[15:22] <xnox> HISI00C1:0
[15:22] <xnox> HISI00C2:1
[15:22] <xnox> etc.
[15:23] <xnox> cause in former case my names will get uglier: enahc1d0
[15:27] <apw> xnox, do you have a dmesg ?  or can i get on that box ...
[15:33] <xnox> apw, cause i want to name all of these using this scheme http://paste.ubuntu.com/24549370/
 <a> <short vendor> <short product> <probe number>
[15:34] <xnox> enahc20
[15:34] <xnox> enahc21
[15:34] <xnox> enahc22
[15:34] <xnox> enahc23
[15:35] <xnox> for our case.
[15:36] <apw> xnox, from what i can see we are using instance numbers within that HISI00C2 bus_id
[15:36] <apw> which means you will get HISI00C2:0 and HISI00C1:0
[15:36] <xnox> ack.
[15:37] <xnox> so i should use "instance" variable name as well. if that makes sense.
[15:39] <xnox> =( if system is booted without ACPI and with device tree, my interface names will not work anymore.
[15:39] <xnox> i wish i could generate the same names for these, irrespective if it was booted with devicetree or the ACPI
[15:41] <xnox> ...
[15:41] <xnox> i am wondering if i am in fact on the platform bus:
[15:41] <xnox> /sys/bus/platform/devices/HISI00C2
[15:42] <apw> there is the concept of companion devices in acpi so you may be on both
[15:42] <apw> on acpi and on whereever you are actuall
[15:43] <xnox> right. i wonder what syspath udev will return me, and i will go from there.
[15:59] <apw> xnox, variously all of them probabally


[05:26] <cpaelzer> good morning
[05:27] <lotuspsychje> hey cpaelzer
[05:27] <utkarsh2102> cpaelzer: o/
[05:28] <bryceh> hi
[05:30] <utkarsh2102> bryceh: hellu!
[05:33] <bryceh> hi utkarsh2102
[05:33] <bryceh> pinot is back up (power outage)
[05:36] <utkarsh2102> woooot!
[05:43] <cpaelzer> wow activity - hi lotuspsychje bryceh and utkarsh2102
[05:51] <bryceh> hi cpaelzer, trying to get lightning talk notes written for tomorrow
[05:55] <cpaelzer> which is my later today :-)
[05:55] <cpaelzer> so please get some sleep, we'll be a forgiving audience
[05:56] <cpaelzer> bryceh: if you have a lot to do left we can even swap our sessions of this/next week
[05:56] <cpaelzer> I do not want you to go too late for this
[05:57] <bryceh> cpaelzer, if you don't mind, that would actually be kinda great, I'm rather behind where I wanted to be
[06:01] <cpaelzer> bryceh: ok I'll switch us then ...
[06:02] <bryceh> cpaelzer, thanks so much
[06:04] <cpaelzer> np, sleep well please
[06:17] <cpaelzer> athos: sergiodj: FYI https://github.com/Segfault-Inc/Multicorn/pull/260
[06:18] <cpaelzer> this should sooner or later end in new releases that cause less pain when transitioning PG
[07:26] <mirespace> good morning
[08:25] <utkarsh2102> mirespace: o/
[08:26] <utkarsh2102> cpaelzer: kinda interesting to see how much of adding compatibility is just adding a bunch of if and endifs, haha
[09:32] <athos> thanks for the heads-up, cpaelzer :)
[10:31] <yurtesen> utkarsh2102: have you had a chance to look at my debdiff?
[10:35] <utkarsh2102> yurtesen: hey, it'll not be before Friday, I'm afraid.
[10:35] <utkarsh2102> also, I'm going to get this in Debian first.
[10:36] <utkarsh2102> I'll probably upload to Debian and let it sync. And once that happens, I'll subsequently sponsor the upload to Focal and other stable releases.
[10:48] <yurtesen> utkarsh2102: ok thanks, I guess you have noticed but I submitted the change to debian also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008668
[11:03] <utkarsh2102> yurtesen: yep, I did :)
[11:03] <utkarsh2102> thank you!
[11:45] <athos> good morning! :)
[12:25] <mirespace> good morning athos o/
[12:59] <rbasak> I uploaded a fix for https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1961092 but for Jammy only. It probably wants a fix in Focal, although collectd is in universe so not a priority for the server team. However if someone is needing some experience in SRUs - say for an upcoming uploader application - then that's a fairly straightforward one to do.
[12:59] <athos> Could anyone import cl-plus-ssl to git ubuntu?
[12:59] <athos> rbasak: ^
[12:59] <rbasak> Sure
[13:01] <schopin> athos: working on the pgloader OpenSSL issue?
[13:01] <rbasak> On its way.
[13:14] <athos> schopin: yes :)
[13:16] <rbasak> athos: import done
[13:16] <athos> schopin: I will forward that patch upstream now and propose merging cl-plus-ssl from debian with the patch on top (this should be an FFe), wdyt?
[13:16] <athos> thanks, rbasak
[13:22] <athos> schopin: nvm, it just got merged in Debian; We can just sync it whenever it lands (FFe needed, I will follow-up with it); then I will forward upstream
[13:27] <schopin> athos: I had a look at the diff a few days ago, it seemed fairly substantial. OTOH, the package is probably useless rn :D
[13:35] <athos> schopin: well, the autopkgtest suite was OK with it :) Do you mean we should not sync the new version yet for some reason?
[13:38] <schopin> Well, the only other two options I can think of are removing pgloader and friends (and possibly more packages) or cherry-picking the openssl3-specific changes from upstream, which I'm definitely NOT volunteering for
[13:39] <schopin> so FFe-ing a sync from Debian sounds like the best choice, I'm just saying that it's a tougher sell to the release team ;)
[14:55] <bryceh> good morning
[18:01] <ahasenack> bryceh: do you remember how to make new "chapters" in the server guide? So it appears in the index?
[18:02] <ahasenack> bryceh: I just added "NFSv4 with Kerberos" to https://ubuntu.com/server/docs/service-nfs, but have been wondering if that wouldn't be better placed in its own chapter, instead of just under "NFS"
[18:02] <ahasenack> I had a cheat sheet for this in some trello board, long deleted/archived
[18:02] <bryceh> I think so yeah, one sec
[18:04] <sarnold> ahasenack: our IS folks have some trello creds they can use to ressurect data if it would help
[18:04] <bryceh> I *think* all we need to do is add an entry in the nav list, I don't think there's anything to do on the page itself, but I'm looking up
[18:05] <ahasenack> sarnold: I wouldn't even know in which board, at this point
[18:06] <sarnold> ahasenack: oh that's not a great starting point :( heh
[18:07] <bryceh> ahasenack, so generally how the guide is structured is to create an 'Introduction' page as your top level for the new category.  Then add an entry to https://discourse.ubuntu.com/t/introduction/11322 pointing to it
[18:08] <bryceh> that page also has a collapsed Navigation subsection where you add the pages that are under that intro page
[18:08] <ahasenack> ah, right, that page has some "hidden" bits about navigation
[18:08] <ahasenack> I'll try that
[18:08] <ahasenack> thanks
[18:08] <bryceh> yep, there's also a Redirects hidden thing but you may not need that


[00:00] <RAOF> Yup.
[00:00] <cnd> hmm, ok, that will help with xorg-gtest
[00:00] <cnd> though we still have to do gtest.m4 since gtest doesn't ship a pkgconfig
[00:00] <RAOF> Right.
[00:04] <cnd> RAOF, do you know if there's any standard name for a source dir in a pkgconfig file?
[00:05] <RAOF> I don't think so.
[00:05] <cnd> I'm using sourcedir
[00:07] <RAOF> Sounds reasonable.
[00:07] <cnd> RAOF, how do you get the variables out of a pkgconfig file?
[00:07] <cnd> PKG_CHECK_MODULES only does CFLAGS and LIBS
[00:07] <cnd> IIUC
[00:07] <RAOF> pkg-config --variable=$VARIABLE $PACKAGE
[00:07] <cnd> ok
[00:08] <cnd> so you have to do it a bit manually
[00:08] <RAOF> So you'll be doing something like ‘XORG_GTEST_SRC_DIR = $(shell $(PKG_CONFIG) --variable=sourcedir xorg-gtest)
[00:08] <RAOF> Yeah, a little manually.
[00:08] <RAOF> You can hide it behind your m4 macro, though.
[00:11] <cnd> yeah
[00:48] <eruditehermit> sforshee, hey are you about?
[14:51] <sforshee> cnd, I just took a look at the bug that I think was filed by eruditehermit (bug 950496). From playing back the evemu-record capture everything looks normal. I updated the bug; if there's any other useful information he could supply please add a comment.
[14:51] <sforshee> cnd, that should be bug 950469
[14:51] <cnd> sforshee, interesting
[14:51] <cnd> thanks
[14:52] <cnd> though if it worked for you, I'm not real sure what could be wrong
[14:55] <sforshee> cnd, the first time I played it back it was from on my desktop and the pointer started moving all over the place :)
[14:55] <sforshee> I'll know better than to do that again
[14:56] <cnd> heh
[17:20] <apw> bryceh, about?  am looking for a relativly safe (perhaps quite low resolution) edid for some testing, as in the binary data for one
[17:22] <apw> bryceh, as i believe they have checksums right ?
[18:32] <bryceh> apw, heya
[18:32] <apw> bryceh, hey, i sent you an email on the edid thing
[18:32] <bryceh> apw, just read it -- awesome!!
[18:32] <apw> cool
[18:32] <bryceh> apw, sure I can dig up edids for you
[18:32] <apw> bryceh, i probabally don't need it now, i used my existing one
[18:33] <apw> bryceh, which i deliberatly corrupted in the text fields
[18:33] <bryceh> apw, ah ok.
[18:34] <apw> bryceh, then loading it, triggered a checksum warning so i think it worked at least at a basic level
[18:35] <bryceh> apw, if I have time today I'll bang on it a bit myself
[18:35] <apw> bryceh, i am hoping you'll be able to load a low res edid into something and show it restricts resolution or something
[18:35]  * apw only has a 1024x600 display here with him, rather annoyingly
[18:38] <bryceh> apw, would be awesome if we could get this in for P, but I agree given the late date it might be safer to leave to Q.  What more would need done to get it into the P kernel?
[18:39] <apw> bryceh, i am sure the patch is not yet 'ready' pretty sure it leaks memory, but overall its pretty safe looking, so i think with some twiddling we could get it up to scratch (assuming you find value in it)
[18:39] <apw> bryceh, and i think if you find value in it we can get it in
[18:39] <bryceh> ok
[18:40] <apw> bryceh, as it is pretty benign if its not used
[18:40]  * bryceh nods
[18:40] <bryceh> as it happens there is an active bug right now I've been looking at, where the user's monitor is providing crap edid
[18:42] <bryceh> apw, https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/927155
[18:44] <apw> bryceh, yeah if it "fixes" that sort of thing, then its even easier to justify it as effectivly a bug fix
[18:44] <bryceh> exactly
[18:45] <bryceh> I can definitely scare up a few such bugs.
[18:45] <bryceh> I probably also have a kvm or two here that truncates edid, which this will fix.
[18:46] <Sarvatt> oh man, Viewsonic VA2012w
[18:46] <Sarvatt> i had that same monitor and the EDID got killed on it too
[18:48] <apw> Sarvatt, as in the thing just decided to forget its own edid ?
[18:48] <apw> bryceh, is that popey on that bug?
[18:48] <bryceh> apw, yup
[18:50] <Sarvatt> apw: yeah, there was a problem where the edid would get corrupted when using them on nvidia gpu's with some  buggy windows drivers
[18:51] <apw> Sarvatt, the mind boggles, i'd expect them to be r/o in hw
[18:52] <Sarvatt> you can rewrite those viewsonic ones from that era, i remember having to do that a bunch of times
[18:55] <apw> bryceh, RAOF, while i remember, once you have put an edid in there it is pinned, you echo an empty line into there to let it be replaced by the real edid again
[19:03] <apw> bryceh, ok i think its actually not leaking there is some background blob management
[19:03] <apw> bryceh, i think it should be adding edid/ on the firmware filename though for safety, other than that its prolly close
[19:05] <bryceh> apw, ok.  got it loaded on a system.
[19:08] <apw> bryceh, although it easy to see how one could automatically fix broken edids with this, letting udev check bad ones and replace them, its not clear how the 'all 0xff' case can be fixed
[19:10] <bryceh> yeah.  probably still would require some manual user action
[19:12] <Sarvatt> ah hah finally found the magic that fixed my old viewsonic,  Power up the monitor connected to the VGA and DVI outs both. Once fully powered up, power the machine back down, disconnect the monitor from the power outlet for ~30 seconds, and boot up with only the DVI input connected.
[19:12] <bryceh> Sarvatt, I also found an edid.exe on the viewsonic site
[19:12] <Sarvatt> this was like 5 years ago so memory was fuzzy, that really reset the edid on my viewsonic
[19:12] <apw> bryceh, anyhow, having reviewed it i am happier its something we can accept, if your testing is good, i'll work on getting the prefix added for next week
[19:12] <bryceh> no directions on how to use it though.
[19:13] <bryceh> apw, excellent.  I'll plan on banging on it in the meantime.
[19:21] <apw> bryceh, only three cycles ... sigh
[19:23] <apw> Sarvatt, that is some arcane magic indeed
[19:25] <Sarvatt> apw: yeah asked him to try it, those viewsonics from around 2006 when they first started doing the 20" widescreens were so crappy
[19:25] <Sarvatt> google viewsonic bad edid
[19:25] <Sarvatt> its full of fun
[19:26] <apw> bryceh, it'd would be good to know if get-edid can get the edid when the kernel bit bashing cannot... i guess in the short term udev could use that to fill it in :/
[19:26] <apw> bryceh, allllll assuming the edid is useful once you've 'rit it in your testing
[19:28] <bryceh> right
[19:29] <apw> and did it, did it, did it?  /me needs to drink less coffee
[19:29] <bryceh> yeah I've been finding get-edid isn't super reliable.  Maybe only 10-25% of the time do we get something worthwhile
[19:29] <bryceh> sorry, got called away to breakfast
[19:30] <apw> heh, i am just starting on the G&Ts so i'll stop making sense shortly
[19:31] <bryceh> well deserved!
[19:31]  * Sarvatt is jealous
[19:32] <apw> yeah its been one of those weeks, though my not wanting to work has gotten me on these 'small' tasks which got you your edid kernel ...
[19:32] <apw> and leann about 4 wi's closed ...
[19:34] <bryceh> ok, why am I not finding the edid file
[19:35] <bryceh> ok, it's there on an -ati system but not an -nvidia??
[19:35] <bryceh> find /sys/devices -name edid gives nothing there.  weird
[19:36] <bryceh> moving on... intel next
[19:45] <apw> bryceh, oh, only tested it only intel myself, but it comes from common code
[19:46] <apw> bryceh, so i would expect them all to express one
[19:47] <bryceh> yeah nfi with the nvidia box.  I'll have to investigate that more
[19:47] <apw> /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1/edid
[19:47] <apw> bryceh, binary drivers by accident perhaps
[19:47] <bryceh> could be
[19:48] <bryceh> well, I mean it definitely has a binary driver loaded.  could be it just doesn't provide edid.  I'll try with nouveau
[19:48] <apw> didn't the installer get changed back in 'o' or something to install them by default
[19:48] <apw> doesn't the nvidia binary driver supply its own way to futsz with the edid ...
[19:52] <Sarvatt> yea or at least it did at one point
[19:52] <apw> bryceh, so .... the ultimate question, does it work
[19:53] <cnd> RAOF, if you want a MIR for gtest without shipping the precompiled libs, then we'll have to do a FF exception to get the latest xorg-gtest in
[19:54] <cnd> after I get stuff reviewed and merged on #xorg-devel
[19:59] <bryceh> apw, well...  the edid file is empty (but get-edid is able to read it)
[20:06] <mlankhorst> noon
[20:06] <bryceh> heya mlankhorst
[20:11] <mlankhorst> hi :)
[20:22] <bryceh> apw, ok so copying in edids seems to work ok, except on the nvidia system where it doesn't work even if -nvidia is uninstalled.
[20:23] <bryceh> apw, and on one system I get the proper resolutions, so it hasn't broken it.  I'm not 100% certain the written edid is overwriting the old though.
[20:24] <bryceh> apw, third system is unable to detect the proper resolutions across the kvm, so is a great candidate for testing the fix.  However, so far the edid doesn't appear to take effect, I just get vesa modes.
[20:24] <bryceh> in all cases I'm using edid gathered from get-edid and assuming that's a valid blob
[20:25] <apw> bryceh, cirtainly when i hexedit'd the one i had, it started saying there was an edid checksum erorr
[20:25] <bryceh> apw, so, I think I can give a light confirmation that it works so far.  I'll play with it more next week to get a stronger confirmation.
[20:26] <apw> bryceh, sounds good.  i am done now for the week anyhow, lets catch up monday
[20:27] <bryceh> sounds good
[21:15] <cnd> bryceh, whot has picked up the clickpad patches and has an attempt at fixing the clickaction vs clickpad issue
[21:16] <cnd> he wants to merge it all for this release of synaptics
[21:16] <bryceh> ok
[21:16] <cnd> if that happens, we will probably want to go with upstream
[21:16] <cnd> but that means re-enabling the clickpad stuff, but hopefully in a better working form
[21:16] <cnd> should I propose an FFe for it?
[21:17] <cnd> or reopen the first FFe?
[21:17] <cnd> or?
[21:17] <bryceh> either way, reopen the first one if that'd save you some time
[21:18] <cnd> ok
[21:21] <Sarvatt> the first FFe got approved, maybe thats good enough? :P
[21:23] <cnd> yeah, I was wondering the same, but one factor in an FFe approval is timin
[21:23] <cnd> timing*
[21:23] <cnd> so I think we can't rely on the earlier approval
[22:14] <eruditehermit> sforshee, hey
[22:14] <sforshee> eruditehermit, hi
[22:15] <eruditehermit> sforshee, so my kernel driver is working but my mouse isn't moving?
[22:15] <sforshee> eruditehermit, that's how it looks to me. In fact, I played back your capture and watched my pointer move :)
[22:15] <eruditehermit> lol
[22:16] <eruditehermit> sforshee, any ideas why?
[22:17] <sforshee> eruditehermit, not yet. X seems to see your touchpad, so I don't know what's happening.
[22:17] <sforshee> apport-collect didn't attach the xorg log though
[22:18] <sforshee> can you attach /var/log/Xorg.0.log from a session when the mouse doesn't work?
[22:18] <eruditehermit> http://paste.ubuntu.com/
[22:18] <sforshee> and if cnd has any ideas of what to look at, I'm all ears
[22:18] <eruditehermit> err
[22:19] <eruditehermit> http://paste.ubuntu.com/876687/
[22:19] <eruditehermit> so I have sections where my mouse was proto=any
[22:19] <eruditehermit> and sections where it was proto=exps
[22:19] <eruditehermit> its really hard to give you a completley clean log
[22:19] <eruditehermit> since I need my mouse!
[22:19] <eruditehermit> lol
[22:20] <eruditehermit> can't pastebin stuff without it
[22:20] <eruditehermit> lol
[22:20] <cnd> sforshee, are any evdev device properties set for alps trackpads?
[22:20] <sforshee> Using input driver 'evdev' for 'ImPS/2 Generic Wheel Mouse'
[22:20] <cnd> evdev properties aren't captured by evemu yet
[22:20] <sforshee> this is when the mouse isn't working?
[22:21] <sforshee> eruditehermit, ^
[22:21] <cnd> sforshee, I bet that's when it is working
[22:21] <sforshee> that's what I think
[22:21] <eruditehermit> that is when it is working
[22:21] <eruditehermit> ok
[22:21] <eruditehermit> tell you what
[22:21] <eruditehermit> I'll reboot
[22:21] <eruditehermit> with the mouse not working
[22:22] <eruditehermit> VT switch
[22:22] <eruditehermit> cp log
[22:22] <eruditehermit> then reboot again
[22:22] <eruditehermit> brb
[22:36] <eruditehermit> sforshee, cnd: http://paste.ubuntu.com/876712/
[22:37] <sforshee> cnd, why would X not be using the synaptics driver?
[22:40] <Sarvatt> eruditehermit: umm, xorg-edgers, might be broken
[22:40] <Sarvatt> is xserver-xorg-input-synaptics installed?
[22:40] <cnd> eruditehermit, you're using xorg-edgers?
[22:40] <Sarvatt> i've been too focused on precise to keep up with edgers lately
[22:41] <Sarvatt> hmm xserver-xorg-input-evdev in edgers doesn't work right now too from the looks of it
[22:41] <Sarvatt> since it thinks the input abis are the same
[22:42] <eruditehermit> ah
[22:42] <eruditehermit> I forgot about edgers
[22:42] <eruditehermit> let  me ppa-purge
[22:43] <Sarvatt> ppa-purge wont work because you're on x86_64, will take a lot of manual downgrades :(
[22:43] <eruditehermit> wait what?
[22:44] <eruditehermit> :(
[22:44] <eruditehermit> brb
[22:46] <Sarvatt> i'm just gonna upload upstream evdev and synaptics driver updates, too many friggin patches to fix and check for this late on friday night :)
[22:46] <Sarvatt> (to use ubuntu branches)
[22:49] <eruditehermit> disregard bug
[22:49] <eruditehermit> I'm stupid
[22:49] <eruditehermit> =p
[22:49] <eruditehermit> xorg-edgers
[22:50] <cnd> eruditehermit, I'm glad we figured it out :)
[22:50] <cnd> thanks!
[22:50] <cnd> be sure to move the bug to invalid if you haven't already
[22:50] <eruditehermit> I will
[22:50] <eruditehermit> also
[22:51] <eruditehermit> it seems the pointer acceleration and sensitivity can't be set via gnome
[22:51] <eruditehermit> is that known?
[22:53] <Sarvatt> eruditehermit: really sorry about that, didn't realize edgers was broken because i stopped using it for the past few weeks to test precise stuff, uploaded new checkouts now though
[22:55] <Sarvatt> i'm waiting for mesa to settle the heck down wrt the autoconf changes on master before going back to it, redoing the packaging every other day gets old when there isnt enough time in a day as it is :)
[22:56] <sforshee> cnd, what do the the acceleration and sensitivity sliders actually change? Is it something that trickles down to the kernel driver?
[22:56] <Sarvatt> eruditehermit: which ones, the ones in the mouse or the touchpad tab?
[22:56] <cnd> sforshee, I think gnome is broken
[22:57] <cnd> it doesn't do anything for me either
[22:57] <cnd> but I've never taken the time to look into it
[22:57] <sforshee> cnd, the acceleration one seems to make a difference on the macbook air at least
[22:57] <cnd> it doesn't work for my magic mouse
[22:57] <cnd> it may work for synaptics but not evdev?
[22:58] <sforshee> when alps is working correctly it's using synaptics
[22:59] <cnd> yeah
[22:59] <cnd> maybe eruditehermit was seeing the issue while he was using evdev?
[22:59]  * sforshee boots up his crappy old dell to see what happens
[23:03] <eruditehermit> Sarvatt, the ones in mouse
[23:04] <cnd> those would be the ones for evdev then
[23:05] <cnd> eruditehermit, please file a bug for that and paste it here
[23:05] <cnd> I can mark it as a bug that needs to be looked at by beta 2
[23:06] <eruditehermit> cnd, err I've got to run now
[23:06] <eruditehermit> cnd, will be back later
[23:07] <cnd> ok
[23:07] <eruditehermit> I need to understand what to file so I will ask questions
[23:07] <cnd> sure
[23:07] <eruditehermit> bbl
[23:07] <eruditehermit> thanks for all the help!
[23:07] <sforshee> eruditehermit, the acceleration slider seems to have an effect on this dell with an alps touchpad
[23:08] <sforshee> i still have no idea what the sensitivity slider is supposed to be changing
[23:10] <Sarvatt> eruditehermit: really though, is xserver-xorg-input-synaptics installed? it doesn't look like it is from your log
[23:10] <Sarvatt> AlpsPS/2 means its in synaptics mode and should be using -synaptics
[23:10] <Sarvatt> its ImPS/2 when its in the old mode that needs evdev
[23:11] <cnd> sforshee, eruditehermit was referring to the slider in the mouse tab
[23:11] <cnd> I think :)
[23:12] <sforshee> cnd, that would explain it :)
[23:12] <Sarvatt> also acpi_osi=Linuxi is a typo
[23:13]  * sforshee -> EOW, have a good weekend everyone
[23:19] <mlankhorst> Sarvatt: generally just want to mimmick windows..
[23:52] <Sarvatt> sforshee: dont suppose you know any magic to fix DFS on wl? :P brcmsmac is so horrible


[00:14] <bluesabre> evening everyone
[00:45] <Unit193> Howdy.
[21:14] <ochosi> evening everyone
[21:16] <flocculant> hi ochosi
[21:17] <ochosi> how're thingsß
[21:17] <ochosi> ?
[21:17] <flocculant> pretty good thanks - week off :)
[21:19] <ochosi> oh that sounds nice
[21:19] <ochosi> would love to have that :)
[21:21] <flocculant> :)


[13:11] <cjwatson> tomreyn: more than we can handle with a casual IRC request - please file a bug and quote the OOPS ID (which also causes the OOPS log to stick around rather than be garbage-collected).  I think the problem is that that CVE is attached to a bazillion bug tasks and/or source packages
[14:31] <tomreyn> I filed bug 1802728
[14:32] <tomreyn> let me post this url here again just to see whether ubot gets it this time https://launchpad.net/bugs/cve/CVE-2017-5753?test2
[14:32] <tomreyn> weird.
[15:15] <cjwatson> Thanks.  The bot might well use the API to look up the description in a way that involves less work than rendering the page.
[16:01] <tomreyn> oh, right, good point, hadn't considered the api.
[16:02] <tomreyn> thanks, too
[22:57] <wgrant> It also needn't necessarily get the CVE information from LP at all.
[23:19] <cjwatson> That too.


[17:01] <knkski[m]> Luke Marsden: would you actually be able to transfer the charms repo to the canonical org?
[17:01] <knkski[m]> That might be easiest
[17:11] <LukeMarsden[m]> sure


[00:16] <Ahmuck> wow, i broke my ltsp server
[01:19] <LaserJock> stgraber: while you're up, I'm slowly getting https://wiki.ubuntu.com/Edubuntu/StrategyDocument going
[01:19] <LaserJock> comments on the outline would be appreciated
[01:20] <stgraber> LaserJock: ok, I'll have a look
[01:29] <stgraber> LaserJock: looks good, I guess objective #3 will also be to have different set of softwares depending on the target to avoid having gcompris and rasmol with the same install :)
[01:30] <LaserJock> stgraber: yeah, good point
[11:36] <saliom> this room is not to do support?
[15:34] <Ahmuck> saliom, yes, you can get support here if you wait
[15:37] <sbalneav> Ahmuck: I think he's gone :)
[15:39] <Ahmuck> k, i followed nubae's script for fat clients, and now my ltsp server is borken :(
[15:39] <Ahmuck> so i'm missing something
[18:54] <Ahmuck> nubae: i tried your fat client setup and borked my ltsp server
[18:55] <nubae> Ahmuck: and how did u do that exactly?
[18:56] <ogra> he used the --bork option :)
[18:56] <Ahmuck> lol
[18:56] <nubae> fatclient doesnt touch the existing ltsp setup
[18:56] <Ahmuck> exactly as you had it in your blog
[18:56] <nubae> unless you indeed use the --bork option
[18:57] <nubae> :-)
[18:57] <Ahmuck> let me pull up the blog entry
[18:57] <Ahmuck> http://www.nubae.com/ltsp-linux-terminal-server-project-netbooted-fat-client-for-ubuntu-hardy-and-intrepid
[18:57] <nubae> Ahmuck: what did u type to install fatclient script
[18:57] <nubae> thanks for pointing to my own blog...
[18:58] <nubae> I'm asking what YOU typed to install the script
[18:58] <Ahmuck> touch 030-fatclient
[18:58] <Ahmuck> sudo nano 030-fatclient
[18:58] <Ahmuck> paste
[18:58] <Ahmuck> save
[18:59] <Ahmuck> reboot
[19:00] <Ahmuck> Edit /etc/ltsp/dhcpd.conf - in this file, it appears i need to specify each thin client
[19:00] <Ahmuck> by mac address
[19:00] <Ahmuck> anywho, my dhcpd.conf file looks exactly as yours with the exception that is set the mac address and the ip address of the client
[19:01] <nubae> how did u install the fatclient script?
[19:01] <Ahmuck> the client is booting pxe and starts looking for a dhcp address, but cannot find one.  looking at the instructions, the ip address are set, so it appears that they are static?
[19:01] <nubae> after editting and all...
[19:01] <Ahmuck> nubae: copy/past
[19:01] <Ahmuck> copy/paste
[19:01] <Ahmuck> save
[19:02] <Ahmuck> so i copied it from your blog, pasted it into a file and saved
[19:02] <nubae> no... something along the lines of sudo ltsp-build-client --fatclient Ubuntu
[19:02] <nubae> or did u not build a chroot?
[19:03] <nubae> because without one, it would be hard for dhcp to find it...
[19:03] <Ahmuck> er, yes.  but now that i think about it, i may have placed the script in the directory after building chroot.  i'll run through the processes again
[19:03] <Ahmuck> though, it did download a ton of stuff
[19:04] <nubae> Ahmuck: the script must be put into the /usr/share/ltsp/plugins/ltsp-build-client/Ubuntu
[19:04] <nubae> directory
[19:04] <nubae> and then u must do ltsp-build-client --chroot name-of-chroot --fatclient Ubuntu --highfat
[19:05] <nubae> the dhcp file must then contain entries to load up both normal clients and fat clients as outlined
[19:09] <nubae> also, paste me your dhcpd.conf file so I can take a look: pastebin.be
[19:10] <Ahmuck>  /usr/share/ltsp/plugins/ltsp-build-client/ubuntu/030-fatclient - on your website
[19:10] <Ahmuck> so i assume that ubuntu should be Ubuntu
[19:10] <nubae> right, is it lower case on my site?
[19:10] <Ahmuck> yes
[19:10] <nubae> let me go fix that, good catch... :-)
[19:11] <Ahmuck> i did however get it in the right directory.  removing /opt/ltsp/fati386 now for rebuild
[19:11] <Ahmuck> ya, about the paste.  i have no gui at the moment on the server
[19:11] <Ahmuck> :(
[19:12] <nubae> ok, then email or use links
[19:12] <Ahmuck> i'll fiddle with it and see if i can't get a thin client to come up and then firefox and paste
[19:12] <nubae> info at nubae dot com
[19:12] <Eghie> nubae: thanks for the howto on your blog, I've just read it
[19:12] <nubae> Eghie: cool
[19:12] <Eghie> that same kind of idea has been on my mind for a while
[19:13] <Eghie> performance whise, it could be working out very well
[19:14] <nubae> it does yes... if you have powerful clients, it certainly makes a difference
[19:14] <Eghie> brainstorm of my on this: http://developer.thuis-online.nl/thinfatclient.txt
[19:14] <Ahmuck> nubae: what is the difference in your proceedure and the other one listed on ubuntu's website?
[19:15] <nubae> which one on the ubuntu site? UbuntuLTSP/fatclient ?
[19:15] <nubae> Eghie: I'll take a look and see if I cant integrate some of that stuff in the next version
[19:16] <nubae> but overall looks like most of that is what I've done :-)
[19:16] <Eghie> I guess so yes
[19:17] <nubae> except this: - Use (if harddrive exists) the harddrive, to store all the things
[19:17] <Eghie> but performance wise, and also easier for clustering, I will check if I can intergrate OpenAFS to use that to share home directories
[19:17] <nubae> the point is its netbooted, but local hard drive access is enabled
[19:17] <Eghie> well, you also need permissions from the administrator of the machine to write to the harddrive
[19:17] <Eghie> so, that should be optional
[19:18] <nubae> no, I disable those on setup of client
[19:18] <Eghie> ah
[19:18] <nubae> I figure, if its a fat client, local access should be for a storage area or access area to global files
[19:19] <Eghie> swap could also be handy
[19:19] <nubae> local swap u mean?
[19:19] <Eghie> yes
[19:19] <nubae> yep indeed
[19:19] <nubae> but not every fatclient will have a hard drive
[19:19] <Eghie> no that's correct
[19:19] <nubae> Id need to detect if it does, and then if it is there use local swap
[19:19] <nubae> but its a good idea
[19:21] <nubae> Ahmuck: the stuff on the ubuntu site was written by me too
[19:22] <Ahmuck> ah.  there are two ways for fat clients ?
[19:23] <Eghie> I guess the old and the new way ;)
[19:23] <nubae> not really, more like a manual and automatic way
[19:23] <nubae> or the old and new way like Eghie says
[19:24] <Ahmuck> ah, ok
[19:25] <nubae> but if ltsp is not working at all for u... then its probably a problem with your dhpcd.conf
[19:30] <Eghie> nubae: the script mentioned on the blog, expects NFS as homedirectory, right?
[19:31] <Eghie> uses i mean
[19:31] <Eghie> does that crash the client on network hickups?
[19:32] <Eghie> because 2 years ago I had my own homedirectory connected via CIFS to the server
[19:32] <Eghie> but when there was a network hickup, my client crashed
[19:32] <nubae> yes
[19:32] <Eghie> because, I think it didn't heard of caching that much
[19:32] <nubae> well, not
[19:32] <nubae> hicupps so much as turning off the server
[19:32] <nubae> on hiccupps there is a lag
[19:33] <nubae> and then comes back
[19:33] <nubae> but since its only home mounted, it generally recovers ok
[19:33] <Eghie> as in, switch off, hmm reboot and stuff like that
[19:33] <nubae> I've not had problems with it, lets put it that way
[19:33] <nubae> right
[19:33] <Eghie> or restarting NFS service/ samba service
[19:33] <Eghie> those kind of hicups
[19:34] <Eghie> or restarten /etc/init.d/networking
[19:34] <Ahmuck> wouldn't that be done at night and users would not be present?
[19:35] <Eghie> nah, it could be recovery work for your network services, or adding a network client, or messing with IPtables, or some things like that
[19:35] <Eghie> or even unstable switches
[19:36] <nubae> that generally is ok, its turning off the server that kills it
[19:37] <nubae> other elements it recovers from
[19:37] <nubae> again, in my experience
[19:37] <Eghie> hmm ok
[19:37] <Eghie> guess that NFS has enough caching support to handle that
[19:44] <Eghie> wireless PXE boot is still not possible, or is it?
[19:46] <nubae> pxe boot, no
[19:46] <nubae> but there are workarounds
[19:47] <Eghie> installing a basic variant of the LTSP client OS on the client, and setup the network service via wireless
[19:47] <nubae> more like usb sticks
[19:47] <Eghie> or via initrd and then load the rest via network
[19:47] <nubae> right
[19:48] <Eghie> well, I don't use wireless clients
[19:48] <Eghie> but could be usefull
[19:48] <Eghie> if it worked though
[19:49] <nubae> it would work ok with netbooted fatclients
[19:59] <Eghie> seems not many people tried LTSP fat client
[20:00] <Eghie> not that many sources/articles/questions on that one on the internet
[20:00] <nubae> nah, but I get a lot of hits to the blog so enough...
[20:04] <Eghie> did you also have quota problems?
[20:04] <Eghie> or not using quota's?
[20:18] <Ahmuck> actually, i need quota's 4 sure
[20:20] <Eghie> well, what do you do, when a user his homedirectory is full?
[20:20] <Eghie> he will not be able to login agai
[20:20] <Eghie> n
[20:23] <Eghie> so he will not be able to cleanup his own homedirectory
[22:09] <Ahmuck> rm -rf *.mp3 from home directory :)
[23:41] <Ahmuck> :(, i'm going to re-install
[23:50] <Ahmuck> i've been looking at some ltsp client machines, however with intels atom proc and boards, one can build a ful fledge fat client for the same price they are asking


[19:53] <paulnoise> Hi all, I'm trying to install some programs, I installed Convos from the snap store but i cannot find it in the applications menu. does anyone have any ideas?
[19:53] <paulnoise> sudo snap list shows: convos 0.99.34 4 jhthorsen -
[19:55] <paulnoise> I tried google, but was unable to find anything of help sadly


[00:00] <Reid> How do u change your name in IRC?
[00:00] <Reid> I'm trying to /msg nickserv register ReiBuntu
[00:00] <Reid> and it's saying "Reid is already registered."
[00:05] <iamlindoro> You're signed in as reid, and trying to set reid's password to Reibuntu
[00:10] <iamlindoro> so sign in as who you want to be (/nick ReiBuntu) and then do the above where ReiBuntu = password
[01:38] <jst> Is the site down?
[02:49] <puff> Hi.
[02:51] <puff> I have a mythbuntu box that _was_ connected to a TV via s-video.  However, we replaced that TV with an HD and I need to order new hardware for HD-out... meanwhile, I'd like to just watch shows on this LCD monitor. H owever, after mythtv startup, the LCD goes blank, presumbly because it's switching to s-video-out.
[02:59] <mattjackets> Hi all, I upgraded to 0.22 a few weeks ago, and mythmusic isn't reading id3 info from files with id3v1 tags.  thoughts?
[03:43] <puff> How do I stop mythbuntu from kicking over into s-video-out mode on bootup?
[03:43] <puff> _Bearing in mind that, sinc eit's in s-video out and I don't have an s-video device, I can't just use the GUI contorl to change it.
[04:56] <cal_> anyone use mythbrowser?
[05:40] <puff> Hm, okay, so I have the video just going to an LCD monitor, but  I'm not getting any audio out of the headphone jacks.
[05:41] <puff> Now admittedly, some films I know so well I can hear the soundtrack in my head, but for most of them, I'd like audio :-).
[06:08] <cjtinant> New install Mythbuntu v9.10 64 bit
[06:10] <cjtinant> Ran 1 day without system crashing, then started again  ---> had to reinstall a day ago as the crashes broke MYSQL.
[06:10] <cjtinant> Bythbackend.log has a lot of enteries:   [mpeg2video @ 0x7ff14dac5820]Missing picture start code
[06:11] <cjtinant> Starting college soon and do not want to mess with it turing spring semester.  Any help???
[06:13] <cjtinant> Also, seeing :   Error parsing: /home/mythbox/.mythtv/config.xml at line: 1  column: 1
[06:13] <cjtinant> Configuration::Load - Error Msg: unexpected end of file
[07:06] <Balsaq> where cani download the free version of mythbuntu?
[08:45] <puff> Hi, anybody home?  I'm trying to get audio out on the headphone jack of my mythbuntu box.
[08:45] <puff> Actually there are three headphone jacks;  one on the front panel, one on the motherboard on the back, and one on a separate sound card on the back.
[09:02] <com_h> I always have trouble working out audio from ubuntu, I just play something turn up software volumes then try all holes until I find one with something coming out.
[09:04] <puff> Sigh...
[09:13] <puff> com_h: Any suggestions as to what to try, to get sound working?
[09:18] <com_h> Have you tried my method of turn up all levels and then frantically plug into every hole?
[12:50] <Scrooby> !help
[12:50] <Zinn> !help For a  complete list of my knowledge visit: http://www.baablogic.net/Zinn.cgi  Other available commands: !status, !about, !bug [bug_number].
[12:51] <Scrooby> hi
[12:52] <Scrooby> Got a question regarding a mythtv backend hardware.
[12:52] <Scrooby> I plan on using a hauppauge hvr-4000 in an backend only system
[12:53] <Scrooby> Now i am still unsure about what processor speed to get. Some sources mention the processor speed to be rather irrelevant for the backend, others advice to use at least 2.4 Ghz ...
[12:55] <Scrooby> The backend should be able to record HD material and stream it to one/multiple frontends
[13:20] <rhpot1991> Scrooby: well the backend will do your commflagging and such, so that will go quicker with a better CPU, but if you aren't using it for HD playback then you don't really need top of the line
[13:21] <rhpot1991> Scrooby: with VDPAU around now the HD playback issue isn't so much of an issue any longer either
[13:21] <rhpot1991> hope that helps
[13:24] <Scrooby> thanx
[17:14] <immudium> !help
[17:14] <Zinn> !help For a  complete list of my knowledge visit: http://www.baablogic.net/Zinn.cgi  Other available commands: !status, !about, !bug [bug_number].
[17:21] <alecj> anyone here an expert on Dibcom 3000 m-b, I lost support for the device since upgrading to 9.10?
[17:39] <mrand> alecj: if no-one responds, other places to check out: #mythtv-users , or search on the mythbuntu forums or mythtv mailing list archive (http://www.gossamer-threads.com/lists/mythtv/)
[17:40] <mrand> also perhaps possible that the way the device is named/addressed is different.  udev?
[17:40] <mrand> Best of luck!
[19:12] <dmfrey> hi all. I enabled the weekly auto builds and wanted to install nvidia 190, i see it in the repos, but it doesn't appear in the hardware driver manager
[19:13] <dmfrey> is the most appropriate way to install them from apt-get install nvidia-glx-190
[19:13] <dmfrey> simulating removes 185
[19:13] <dmfrey> i am questioning this as when i previously did this from the nvidia-vdpau ppa, it still seemed to need 185 installed as well
[19:25] <dmfrey> nevermind, if i installe nvidia-190-modealiases it now registers in the hardware driver manager
[20:11] <rhpot1991> dmfrey: didn't I tell you that already :)
[20:13] <dmfrey> rhpot1991: sorry, it was late and I have been sick :)
[20:30] <dmfrey> rhpot1991: i also upgraded the firmware on my hdpvr in my windows vm in virtualbox
[20:30] <dmfrey> rhpot1991: it worked good and seems to have a better picture now in live tv
[20:30] <rhpot1991> nice
[20:31] <rhpot1991> I need to check mine again, pretty sure there is a newer one out
[20:31] <dmfrey> rhpot1991: last one was dated in november 2009
[20:32] <rhpot1991> ya mine was done before that I think
[20:33] <dmfrey> rhpot1991: i still seem to have one outstanding issue with vdpau
[20:33] <rhpot1991> dmfrey: whats that?
[20:33] <dmfrey> rhpot1991: on fast motion, it shows a single line tear horizontally through the middle-upper portion of the screen
[20:34] <rhpot1991> dmfrey: try disabling composite
[20:34] <dmfrey> rhpot1991: seems to be a vdpau issue as the other profiles don't havve this
[20:34] <dmfrey> i think it is already off
[20:34] <rhpot1991> fast motion as in regular playback speed and not something silly right?
[20:34] <rhpot1991> dmfrey: well its on by default unless you disable it
[20:34] <rhpot1991> let me pastebin
[20:34] <dmfrey> yes, fast motion from side-to-side in normal playback
[20:35] <rhpot1991> http://mythbuntu.pastebin.com/d56e913df
[20:36] <dmfrey> what's the TripleBuffer do?
[20:38] <rhpot1991> dedicates more memory to 2d IIRC
[20:38] <rhpot1991> supposed to help VDPAU
[20:38] <dmfrey> nice, i will add that as well
[20:38] <dmfrey> i thought i did previously, but it must have been before i wiped this frontend box
[20:40] <dmfrey> i wonder if the compositing could have also been affecting the live tv in general...choppiness, etc
[20:41] <dmfrey> i forget, are you running an 8400 card as well?
[20:44] <dmfrey> rhpot1991: that looks much better
[20:45] <rhpot1991> I have an ion box and a 9600gt
[20:45] <dmfrey> rhpot1991: that's right
[20:46] <dmfrey> rhpot1991: i will have to play around with that triplebuffer on this 8400 card
[20:47] <dmfrey> rhpot1991: one of my girl's shows is in hd and seems to be a little choppy
[20:49] <dmfrey> rhpot1991: i will have to look at some of these other settings on the vdpau wiki page as well
[20:49] <rhpot1991> dmfrey: my ion box was pretty clean, but I needed those tweaks for my other one to stop tearing
[20:50] <dmfrey> rhpot1991: i am hoping that intel wifi 5300 gets here todayd so i can finish setting up my ion box
[20:53] <quinten> hi, i'm wondering if someone can help me think through a hardware problem i'm experiencing
[20:53] <quinten> i build a myth box about 1 year ago. it just stopped working
[20:53] <quinten> symptoms: sometimes it will display a POST screen, and sometimes it won't
[20:53] <dmfrey> quinten: how's your powersupply?
[20:54] <quinten> it appears the power supply is working
[20:54] <quinten> but i'm not positive--it's a low wattage supply i guess
[20:54] <quinten> 270 watts
[20:54] <dmfrey> quinten: have you blown out any dust build up inside the case?
[20:54] <quinten> at least the cd-rom lights up sometimes even if i have no POST
[20:55] <quinten> i did blow out dust from the power supply
[20:55] <quinten> not much in there
[20:55] <dmfrey> quinten: was working on a server recently and it ended up blowing out the dust out of the heatsink/fan on the processord helped a lot
[20:55] <quinten> first thing i tried was taking out the pvr-150 card, which did not lead to it consistently booting
[20:56] <quinten> but worked the first time which made me suspect power supply could be an issue
[20:56] <quinten> i also tried taking out one of the paired ram modules
[20:56] <quinten> basically it seems like a lot of potential parts could be swapped out...
[20:56] <quinten> new power supply will be a pain as it's custom and i'll have to pay almost the price of a new case to replace it
[20:57] <quinten> does this sound at all like it could be motherboard failure related?
[20:57] <dmfrey> quinten: can you get it to boot with just a bare minimum of hardware in it (i.e. no capture cards, minimum ram, etc)
[20:57] <quinten> not consistently
[20:57] <quinten> well, i take that back--i've tried once with one ram module and it worked, i haent' tried again
[20:58] <dmfrey> quinten: are all your fans working?  could it be heat related?
[20:58] <quinten> the other symptom is when i boot it says "no operating system found"
[20:58] <quinten> on the times it gets to POST
[20:58] <quinten> which could be a hard drive failure, but i've tried booting from the dvd drive with no success either
[20:58] <dmfrey> quinten: you said the mobo is only about a year old?
[20:58] <quinten> even though i've made sure its set to boot from CD in the bios
[20:59] <quinten> yep, just over a year
[20:59] <dmfrey> quinten: when that happens, does the post screen look ok?
[20:59] <quinten> yes, it looks normal--except the message about no OS found
[20:59] <quinten> i'm going to try booting from a USB stick tonight to see if that works
[21:00] <dmfrey> rhpot1991: btw...how loud is that 9600gt?
[21:00] <dmfrey> rhpot1991:  been thinking about upgrading, but want a silent card (not too many options out there)
[21:01] <quinten> so, there are enough points of failure that appear possible it's hard for me to figure out what to replace
[21:01] <quinten> i can't think that the hard drive failure along would stop it from POSTing
[21:01] <dmfrey> quinten: true
[21:01] <quinten> *alone
[21:02] <quinten> i kind of remember that i couldn't install the OS from CD the firs time i set it up, i think i needed to use USB
[21:02] <dmfrey> quinten: can you get into your bios and see what the temp is?
[21:03] <quinten> it's cool, 45 degrees
[21:03] <dmfrey> quinten: that is odd
[21:03] <dmfrey> quinten: ok
[21:03] <quinten> that was my very first guess
[21:03] <quinten> temp
[21:04] <quinten> i guess if i get it to boot from USB and find out hte hard drive is actually dead, that's one thing that will help
[21:04] <dmfrey> quinten: barring the powersupply is not sending enough juice out, i would first guess ram then mobo
[21:05] <quinten> here's what happens: i get it to POST once or twice, then it stops
[21:05] <rhpot1991> dmfrey: I got a silent version, it takes up 2 slots though
[21:05] <quinten> then it may start working an hour or two later
[21:05] <dmfrey> rhpot1991: do you recall make/model?
[21:05] <quinten> it worked for a year with that power supply with no problem. still a possibility?
[21:06] <dmfrey> rhpot1991: i did see an zotac zone 220 that is silent, however it is only abailable in UK right now
[21:06] <rhpot1991> gt 220 that is righ?
[21:07] <rhpot1991> right now there is a msi 220 on newegg
[21:07] <rhpot1991> lets see
[21:07] <Shadow__X> superm1: so i enabled the testing ppa and installed mythtv-status and i can run it but it still doesnt show up in my motd what else do i need ot do
[21:07] <rhpot1991> Shadow__X: do you have screen or byobu installed?
[21:08] <Shadow__X> 6i have screen installed
[21:09] <rhpot1991> Shadow__X: launch screen see if it shows up there
[21:09] <rhpot1991> dmfrey: http://www.newegg.com/Product/NewProduct.aspx?Item=N82E16814125273&cm_re=silent_9600-_-14-125-273-_-Product
[21:09] <Shadow__X> i am using screen now
[21:09] <rhpot1991> thats what I have
[21:09] <rhpot1991> asus also makes a model thats similar, but it has a weird heat pipe that didn't fit into my fusion case
[21:10] <rhpot1991> dmfrey: this may or may not work as well: http://www.newegg.com/Product/NewProduct.aspx?Item=N82E16814127454&cm_re=msi_210-_-14-127-454-_-Product
[21:10] <rhpot1991> VDPAU page says it will be similar to a 9500
[21:10] <Shadow__X> isnt 120 alittle high for a 9600
[21:11] <dmfrey> rhpot1991: nice looking card
[21:11] <rhpot1991> dmfrey: http://www.newegg.com/Product/NewProduct.aspx?Item=N82E16814500072&cm_re=zotac_9500-_-14-500-072-_-Product
[21:11] <rhpot1991> you have a few choices now
[21:11] <rhpot1991> I'm waiting for a silent gt 2xx for my next one
[21:12] <rhpot1991> Shadow__X: 1gb of ram and silent, but ya its pricey
[21:12] <Shadow__X> yeah but 1gb ram isnt really helping you as much as it would if it was a better card
[21:12] <dmfrey> rhpot1991: i would like to wait for that zotac silent 220
[21:13] <Shadow__X> rhpot1991: it doesnt show up in screen why did you ask
[21:13] <rhpot1991> dmfrey: I think they have a 220 and gt 220 coming out
[21:13] <rhpot1991> Shadow__X: it does for me when I launch byobu
[21:13] <rhpot1991> figured it might be similar
[21:13] <dmfrey> rhpot1991: looks like newegg just changed their site around a bit
[21:15] <Shadow__X> rhpot1991: nope
[21:16] <Shadow__X> rhpot1991: even did dkpg reconfigure
[21:16] <dmfrey> rhpot1991: http://zotac.com/index.php?option=com_wrapper&view=wrapper&Itemid=100025&lang=un
[21:18] <dmfrey> rhpot1991: i kinda wish that one had ddr3 memory on it, however
[21:18] <quinten> if i upgrade the motherboard, is there a good choice w/ onboard support for vdpau and hdmi audio?
[21:19] <quinten> i bought this one because it has an 8200 chip, but i've never been able to get vdpau working with it
[21:19] <dmfrey> quinten: i would use a card with dedicated memory on the card
[21:21] <Shadow__X> quinten: according to wiki for vdpau it should work
[21:21] <Shadow__X> just install the correct drivers
[21:26] <rhpot1991> dmfrey: link doesn't work
[21:26] <rhpot1991> dmfrey: http://pden.zotac.com/index.php?page=shop.browse&category_id=55&option=com_virtuemart&Itemid=1
[21:29] <dmfrey> rhpot1991: first one in the list on the link you just posted
[21:29] <rhpot1991> dmfrey: ya either of those top 2 should be good
[21:30] <rhpot1991> just need to wait for them to sell the stupid things here
[21:31] <dmfrey> rhpot1991: i hear ya
[21:32] <dmfrey> rhpot1991: the same model with a fan/heatsink was only about $60-70 or so on newegg a few weeks ago
[21:53] <quinten> Shadow__X: i did install the drivers. i think it may not have enough dedicated memory, but ther'es no place to change allocation of video memory in the bios
[21:53] <quinten> i also read after the fact that the 8200 has limited vdpau capabilities, and i was trying to throw 1080i at it
[22:22] <tuv0k> What should I check if my recordings are not showing up on my xbmc
[22:23] <tuv0k> wouldn't that be the upnp server of mythtv?
[22:39] <hackman> I don't have my "permanent" mythbox hardware yet.
[22:40] <hackman> and I had this crazy idea to run mythbuntu from a USB stick, with /var/lib/mythtv mounted on (or symlinked to) an external eSATA drive, for example.
[22:40] <hackman> crazy, right?
[22:43] <rhpot1991> hackman: not really, I do similar with a frontend, usb stick and then nfs share for some videos
[22:57] <]Oscar> I'm having very often segfault with frontend. last line in log are about failed bobdeint. It's "normal"??
[22:59] <]Oscar> I have just updated to last nigthly build of mythbuntu 9.10
[23:14] <mrand> ]Oscar: maybe try a different theme, then switch back to the one you are trying to use right now?  If you can reproduce it after that, please follow the directions here: http://www.mythtv.org/wiki/Debugging#Debugging_with_Ubuntu_packages
[23:18] <]Oscar> Changed theme, it's the same... I'm going to debug... :(
[23:34] <]Oscar> uhm,.. changing again theme solved,...
[23:35] <yfwork> join #xbmc
[23:36] <yfwork> sorry