[02:10] <vinh10490> I cannot connect FB with Pidgin @@
[02:27] <arthurfiggis> out of curiousity, is kubuntu planning on going with mir/xmir along with the main distro, or are they sticking with wayland? i'm liking 13.10 so far, but mir i'd rather avoid if i could :/
[02:28] <shadeslayer> Depends on whatever upstream recommends
[02:28] <shadeslayer> plus, seeing how either xmir and wayland are not production ready for desktops, that's something we don't have to answer this cycle
[02:30] <arthurfiggis> shadeslayer: oh, i see...that's unfortunate, i remember some time ago the idea was to go with wayland over mir :( https://blogs.kde.org/2013/06/26/kubuntu-wont-be-switching-mir-or-xmir
[02:30] <shadeslayer> well yeah
[02:31] <shadeslayer> upstream will *most likely* go with wayland
[02:33] <arthurfiggis> perhaps, i'd rather not risk being locked in myself though...i think i'll reinstall debian as i planned and hope i can get the ati drivers working :) but thanks very much for the response!
[02:35] <qdata> kde/kwin will not be supporting mir, remains to be seen how that's going to play out but I'd imagine if there is going to continue to be a Kubuntu with kde as a desktop they will either have to use X or Wayland to do it
[02:38] <arthurfiggis> qdata: that's a rather unstable position to be in though, i would think :( if upstream did go with mir then all the packages would be built against it, so if kubuntu were to continue to exist as you say, they'd also have to fork a whole lot of the software as well
[02:39] <qdata> well, the kwin developer has already siad "no" to mir
[02:42] <qdata> http://blog.martin-graesslin.com/blog/2013/05/mir-in-kubuntu/
[02:50] <arthurfiggis> qdata: sorry...was just in another window reading that link :) it seems as if the only conclusion anyone's able to come to yet is "we'll have to wait and see," though, which is...not encouraging for the upcoming LTS :(
[02:51] <arthurfiggis> in fact the conclusion he came to was that "I’m not really optimistic that it will still be possible to provide the Ubuntu flavors once the transition to Mir is done."
[02:54] <qdata> well he works on KDE, which is upstream from Kubuntu - the people who will choose X or Wayland are the people who package Kubuntu - that is if they desire to keep a KDE centered distro
[02:56] <qdata> and yes - a lot of 'wait and see' going on here   :-)
[02:58] <arthurfiggis> a shame really, kubuntu seems to suit all my needs at the moment but that's a rather fine line to be hanging on...granted the packages in debian i were using were old, but at least i know debian will be around in a year's time :/ ah well, only six months left on 13.10 anyway
[02:59] <arthurfiggis> i think when people like mark shuttleworth are calling people who would rather not buy into mir the 'open source tea party' it's not a good sign for upstream's future direction :P
[03:00] <qdata> I spent some fairly good size chunks of time between Thanksgiving and New Years looking around at other distros and kept coming back to my Kubuntu image because out of everything I tried Kubuntu is still the best KDE distro
[03:02] <arthurfiggis> qdata: oh, i find it's quite good as well, at least from what i've tried so far :) unfortunately with moves like mir and the dash lens in unity, canonical is putting a lot of good projects like this one in jeopardy as well...it's certainly making me reconsider anyway :(
[03:03] <shadeslayer> arthurfiggis: fwiw X everyone is going to ship with X in 14.04
[03:03] <qdata> the mark s. disrespect and the way he did it - he didn't follow his own rules for the Canonical community itself and never apologized once he was caught out turned me off
[03:04] <arthurfiggis> qdata: yeah, that's what makes me concerned about the future of the other 'flavours' of ubuntu in particular...he seems more interested in trying to take a bite out of android's market share than the whole "community promise" everyone seems to have forgot about :(
[03:05] <qdata> if there was something better out there to run KDE on that wasn't using ubuntu repos I'd move to it. Tried even, but kept coming back to what works best
[03:05] <arthurfiggis> shadeslayer: ahh, well that's good to know..at least things will be relatively safe with the lts version for a while
[03:05] <shadeslayer> yep
[03:06] <arthurfiggis> qdata: the best that i found personally was debian stable :) there are downsides though, mainly the older packages, you have to configure some things on your own...kubuntu is definitely more polished, but if it's a choice between a polished Mir and an unpolished Debian, so to speak.. :(
[03:06] <qdata> gives me a year to find something better   :-)
[03:11] <arthurfiggis> qdata: if an experienced user is looking for something better already, i should probably be doing the same :( not many options left for my system, fedora is a bit too unstable and the installer for opensuse didn't work
[03:11] <qdata> I've used KDE since about 1.45 version
[03:12] <qdata> for years it was on FreeBSD, but it became to where I was spending more time maintaining it and not using it to do $real_life work
[03:13] <arthurfiggis> wow...i think the first version of it i used was 2.2.2, but i always liked it :) i don't know why so many distributions decided to go with gnome 3 as a default...i would still be using freebsd myself but the last machine i bought i made the mistake of getting a uefi/secure boot based system, still not working on there :(
[03:13] <qdata> so I tried Linux with package management systems and settled on opensuse for about 2 and a half years
[03:14] <qdata> they kind of lost focus with the Attachmate buyout and I made the move to Kubuntu at that time
[03:16] <qdata> much earlier I had taken a look at Kubuntu but didn't like the way they had dumbed down KDE to the point I had to undo everything, but over time it got better and my the time I looked at it again I liked what I was seeing
[03:17] <arthurfiggis> qdata: i've tried out various releases of kubuntu and i've always been impressed by it, though this latest version is much more stable than the ones i used previously :) the threat of canonical shooting themselves and every other derivative in the foot is a pretty big detractor though, all the same
[03:18] <qdata> yup, I had high hopes for Fedora 20 but the first time I tried to set up the KdePIM Akonadi server wouldn't start
[03:19] <arthurfiggis> qdata: i can't remember what specific issue i had with fedora 20 that turned me off it, but in general the problem with fedora is that they'll get to a point where a lot of the bugs are fixed and its usable..then somewhere along the line upgrade everything for the sake of upgrading, and blow up half the stuff on your system until the next release
[03:19] <qdata> I use Clonezilla and a second storage drive to keep an image of what works so I can always revert to it if things go wrong, my main drive is an SSD
[03:20] <qdata> this includes updating, if updates break something I roll back
[03:20] <arthurfiggis> i was really hoping kubuntu i could stick with but it sounds as if the mir situation isn't as clear cut as "we're not using it" any more :( hmm...that's a good idea, i do something similar but with a more traditional external usb drive
[03:21] <qdata> and Kubuntu has a good history with me of updates not breaking things
[03:30] <shadeslayer> arthurfiggis: qdata fwiw there is no indication of which display server is going to 'win' so to speak
[03:31] <shadeslayer> it could be that other distros adopt Mir since it becomes production ready first
[03:31] <shadeslayer> who knows ...
[03:31] <qdata> true enough
[03:31] <qdata> and if all distros did then Martin would rethink kwin support
[03:31] <shadeslayer> s/since/if/
[03:31] <arthurfiggis> shadeslayer: possibly...highly doubtful considering that it would require signing over one's code to the CLA
[03:31] <shadeslayer> qdata: correct
[03:31] <shadeslayer> arthurfiggis: *shrug* people have done that in the past
[03:32] <shadeslayer> I don't think it's as big a deal as it's made out to be
[03:32] <shadeslayer> look at Qt, if you contribute to Qt you have to sign a similar CLA
[03:32] <shadeslayer> and it has no shortage of contributors
[03:32] <qdata> true this
[03:33] <arthurfiggis> hmm...i thought qt was licensed under lgpl 2.1?
[03:34] <shadeslayer> dual licensed, and you have to sign a CLA for a patch to be accepted
[03:35] <Unit193> Can't you just BSD it?  Or otherwise license in such a way they can relicense?
[03:37] <shadeslayer> dunno, possibly too permissive that patches don't get open sourced or whatever
[03:39] <shadeslayer> Unit193: FWIW the commercial license is relicensing the LGPL code
[03:39] <shadeslayer> ( I think )
[03:40] <arthurfiggis> shadeslayer: hmm...so if i understand right, if you're not writing a commercial application or providing a patch to qt itself, you don't have to sign a CLA...that's a lot different than "sign this CLA or youdon't participate in this project, period" :P
[03:41] <arthurfiggis> (at least I would think so)
[03:42] <shadeslayer> Isn't that how Mir works as well? If you're writing something ontop of Mir ( kwin ) , then you don't have to sign the CLA
[03:43] <arthurfiggis> shadeslayer: i would assume from the almost universal rejection of it by the community at large that it's probably more complicated than that, but perhaps not
[03:46] <James0r> can't seem to change my compositing type to OpenGL
[03:46] <James0r> just keeps reverting back to XRender
[03:46] <shadeslayer> arthurfiggis: I think the major cause of resentment on the licensing side is that Canonical can relicense your code to whatever ...
[03:48] <shadeslayer> whereas there are provisions on the Qt side to release the code under LGPL 2.1
[03:48] <shadeslayer> see http://www.kde.org/community/whatiskde/kdefreeqtfoundation.php
[03:48] <arthurfiggis> shadeslayer: that's a pretty legitimate bone to pick, though, isn't it? :) i mean if you're submitting your code under one license and then they have the right to relicense it as they please?
[03:49] <shadeslayer> arthurfiggis: true, though in practicality a minor one tbh, I believe it's there so that they can convince ARM vendors to ship Mir
[03:49] <shadeslayer> since those vendors just love closed platforms
[03:50] <arthurfiggis> shadeslayer: canonical in general seem to be gravitating toward closed platforms :( i think shuttleworth took a look at what google was doing with android and started seeing dollar signs
[03:50] <arthurfiggis> ah well...at least debian was relatively usable, i'll have to install it again this evening :) trying kubuntu was certainly pleasant though!
[03:53] <shadeslayer> \o/
[03:55] <shadeslayer> arthurfiggis: what happens if Debian chooses to go with upstart though :P
[03:57] <arthurfiggis> shadeslayer: well, debian has the advantage of being a community-based distro that isn't backed by a group of people looking to sell tablets and cellphones...they may wel go with upstart over systemd and that might make good technical sense, but i have more faith in their protecting my end user freedoms than ci do in canonical :(
[03:57] <ghs> I'm trying to install the Kindle on Kubuntu. However, is not working. Any idea ?
[03:58] <shadeslayer> arthurfiggis: fwiw Kubuntu is also a community backed distro
[03:58] <shadeslayer> ghs: I'm sorry what
[03:58] <shadeslayer> usually ebook readers just show up as usb storage devices on Linux
[03:59] <ghs> shadeslayer: On Ubuntu it works well.
[03:59] <shadeslayer> ghs: I don't understand ... I've never heard of a software called Kindle
[04:00] <ghs> shadeslayer: http://www.amazon.com/gp/feature.html?docId=1000426311
[04:00] <shadeslayer> and that works fine with Wine in Ubuntu but not on Kubuntu?
[04:00] <ghs> shadeslayer: yes
[04:01] <shadeslayer> ghs: what's the issue exactly under Kubuntu?
[04:01] <shadeslayer> doesn't start?
[04:01] <arthurfiggis> ghs: you could try playonlinux, i've found that it's quite good for both programs and games...usually downloads and installs the best version of wine for the package you're using, if it's supported
[04:01] <ghs> shadeslayer: doesn't install.
[04:02] <shadeslayer> ghs: release?
[04:02] <ghs> shadeslayer: what ?
[04:03] <shadeslayer> I found https://www.kubuntuforums.net/showthread.php?50471-Kindle-App-on-Kubuntu-%28success!%29
[04:03] <shadeslayer> ghs: which release?
[04:03] <ghs> shadeslayer: do you says which version of wine ?
[04:04] <shadeslayer> ghs: wine and Kubuntu
[04:04] <ghs> shadeslayer: wine 1.4 and kubuntu 12.04 lts
[04:05]  * shadeslayer would recommend updating wine to whatever is latest
[04:06] <shadeslayer> https://launchpad.net/~ubuntu-wine/+archive/ppa/+index?field.series_filter=precise
[04:06] <ghs> shadeslayer: This is the latest version.
[04:06] <shadeslayer> I see wine 1.7 there
[04:08] <ghs> shadeslayer: yes.
[04:08] <shadeslayer> isn't that the latest then?
[04:24] <arthurfiggis> shadeslayer: sorry, i missed that...yes, you're right, my apologies for the mistake :) you bring up a good point about upstart though, but i think half of debian's renewed popularity these days is in all the ways that they -aren't- ubuntu, if you know what i mean...i could only see them going with upstart if the licensing were liberal enough for debian, the most strict distro out there when...
[04:24] <arthurfiggis> ...it comes to free and open source :)
[04:25] <arthurfiggis> on the other hand as you pointed out, with the LTS using X none of it will really be a problem for another five years...and if someone hasn't figured it out by then we're all lost ;)
[04:31] <ghs> shadeslayer: After install the kubuntu, my network is always dropping.
[04:32] <ghs> shadeslayer: really, my wine version not is latest.
[04:32] <shadeslayer> arthurfiggis: heh, yeah
[04:33] <shadeslayer> hopefully in ~5 years we'll have one dominating the others :P
[04:33] <ghs> shadeslayer: what mean that ?
[04:34] <arthurfiggis> shadeslayer: hopefully...i'm hoping that valve's steam consoles take off personally, they're basing steamos off wheezy so at least they're likely to go with what the community at large wants
[04:34] <shadeslayer> arthurfiggis: not necessarily, they'll probably go with what fits their business model and what game developers want
[04:34] <shadeslayer> consumers don't particularly care what display server the steam box is running
[04:37] <arthurfiggis> shadeslayer: oh ultimately they'll go with what suits the bottom line of course, that only makes sense when you're a business :) hopefully they'll look at the community good-will lost by canonical, but ultimately steamos is a semi-proprietary platform anyway
[05:28] <arthurfiggis> arg...looks like handbrake isn't working properly either, that's unfortunate :( builds just fine but when you run the gui it crashes out with an error stating it can't instantiate a class of "GtkBox"
[07:27] <Dr_No> i used xrandr to activate the proper screen resolution but how do i make this permanent in xubuntu 13.10?
[07:51] <lordievader> Good morning.
[08:14] <silvea12> Hey, I have some wierd HDMI audio issues, and I can't seem to find anything anywhere that relates to my specific problem. It's to do with HDMI output. Can anyone here help me?
[10:33] <MarinaMioka> ciao
[10:34] <eagles0513875> !it MarinaMioka
[10:34] <eagles0513875> humm
[10:34] <eagles0513875> !it
[10:34] <eagles0513875> MarinaMioka: ^
[10:35] <lordievader> eagles0513875: You need to use a pipe ;)
[10:35] <lordievader> !info | eagles0513875
[10:35] <eagles0513875> ya sorry been a while since ive needed that
[10:35] <lordievader> !bot | eagles0513875
[10:35] <eagles0513875> :D
[10:36] <lordievader> Forgot that !info wanted an argument...
[12:03] <BluesKaj> Hiyas all
[13:38] <eagles0513875> lordievader:
[13:38] <eagles0513875> lordievader: you remember the issue of my track pad
[13:38] <eagles0513875> and the fix that i found
[13:38] <lordievader> eagles0513875: Yes?
[13:39] <lordievader> Was that bug 737856?
[13:39] <eagles0513875> https://bugs.launchpad.net/ubuntu/precise/+source/linux/+bug/967399
[13:39] <eagles0513875> lordievader: there is a patch and i finally got a response form upstream kernel input mailing list
[13:39] <eagles0513875> i need help on how to patch the kernel + recompile it
[13:40] <lordievader> eagles0513875: Hehe, you've come to the wrong address...
[13:40] <eagles0513875> :-/ ok out of all people im a bit suprised :p
[13:40] <eagles0513875> you hang out in the dev channel and dont know how to patch and compile a kernel :p
[13:40] <lordievader> eagles0513875: Ask in #ubuntu-kernel or #linux.
[13:41] <eagles0513875> already in ubuntu-kernel dealing with a very nice person apw :D
[14:00] <BluesKaj> eagles0513875, what did you do now , that you need to patch a kernel >
[14:00] <eagles0513875> nothing BluesKaj
[14:01] <eagles0513875> its the issue of my multitouch track pad BluesKaj
[14:01] <eagles0513875> found a fix which has been about since 11.10
[14:01] <eagles0513875> the patch was submitted upstream for kernel mainline inclusion but it fell through the cracks
[14:01] <BluesKaj> ok
[14:01] <eagles0513875> i want to test and confirm and potentially submit it upstream again
[14:08] <BluesKaj> odd that lenovo brags about it's linux support , but leaves something this important to the open source devs to fix
[14:10] <BluesKaj> altho this new lenovo latop's touchpad works fine
[14:12] <BluesKaj> touchpad, trackpad, wonder what the proper name is, seems to depend on the mfgr
[14:20] <eagles0513875> BluesKaj: the issue isnt with standard track pads its with the fancy multitouch ones
[14:23] <BluesKaj> ok, I immediately installed a wireless minimouse ...my only problem with laptops is the trackpad, just don't like them
[14:24] <BluesKaj> anyway ..brb
[14:29] <MarinaMioka> hi
[15:50] <eagles0513875> ikonia: how would i go about determining the exact model of my trackpad
[15:50] <eagles0513875> lsusb shows nothing of use there
[15:50] <ikonia> any of the hardware probe commands should be usful
[15:51] <ikonia> lsusb is based of id's - not hardware models, it's pattern matching
[15:52] <eagles0513875> ok ill do some googling there
[15:52] <BluesKaj> lshw?
[15:52] <eagles0513875> wow i didnt even know that command existed
[15:54] <BluesKaj> tried lshw -C USB, but it doesn't show anything
[15:54] <eagles0513875> BluesKaj: it works
[15:54] <BluesKaj> sudo
[15:54] <eagles0513875> no need for sudo wiht lshw
[15:55] <eagles0513875> lshw doesnt show my trackpad at all there
[15:55] <BluesKaj> oh yes, a warning pops up here without sudo
[15:55] <Pici> ditto
[15:56] <eagles0513875> BluesKaj: 14.04
[15:59] <BluesKaj> on 14.04 , but loaded a 13.10 image, want to show my friends what kubuntu is all about, and some don't have optical drives on their lappies
[15:59] <eagles0513875> BluesKaj: lol could have made a bootable usb
[16:00] <eagles0513875> lordievader: ping
[16:00] <BluesKaj> ok here goes , lets see if it boots
[16:11] <lordievader> eagles0513875: pong
[16:12] <eagles0513875> lordievader: you had mentioned i think a way i can determine my exact model of track pad. can you remind me what the command would be. Google is returning me lshw which is showing up nothing in terms of my trackpad device
[16:13] <lordievader> eagles0513875: lspci?
[16:13] <lordievader> eagles0513875: How is it connected?
[16:15] <eagles0513875> lspci shows nothing lsusb shows nothing
[16:15] <eagles0513875> all i do know is its an elantech multitouch trackpad
[16:17] <lordievader> eagles0513875: Could you pastebin the output of both the commands?
[16:18] <eagles0513875> one moment please
[16:20] <nlsthzn> just tried to install the latest version of plex media center in kubuntu 13.10, used QAPT Package Installer... it doesn't give any errors but plex isn't installing or installing correctly?!
[16:20] <eagles0513875> lordievader: http://pastebin.com/wbkPpNaw
[16:20] <eagles0513875> lordievader: included lshw as well
[16:23]  * nlsthzn sucks at linux but I tried dpkg and got this - http://slexy.org/view/s20cBIEdnZ
[16:27] <lordievader> eagles0513875: Hmm, try "cat /proc/bus/input/devices|grep -i name"
[16:28] <eagles0513875> N: Name="ETPS/2 Elantech Touchpad" <-- is the etps/2 does that mean its a ps2 device?
[16:29] <lordievader> eagles0513875: That or it emulates one.
[16:37] <genii> I wonder if xinput shows it
[16:37] <trung_> hi can I ask something about shell programming
[16:38] <Pici> trung_: you can, but #bash might be a better resource.
[16:38] <trung_> oh I'm actually using pid
[16:38] <trung_> I mean fish
[16:39] <trung_> but the command could be understood by either
[16:39] <genii> trung_: #fish channel also exists :)
[16:39] <trung_> I'd like to try here first though :P
[16:39] <trung_> I have 2 shells running
[16:39] <trung_> 1 running python shell
[16:39] <trung_> I checked the python shell with os.getpid() and wants the other shell to talk to it
[16:40] <trung_> I tried echo "command" > /proc/<pid>/fd/1
[16:40] <wxl> nlsthzn: see whomever manages the package. something is wrong with it.
[16:40] <trung_> the command is shown in the python shell
[16:40] <trung_> but I could not interact with it
[16:40] <trung_> cannot backspace to delete
[16:40] <trung_> cannot enter to let python run it
[16:42] <Pici> trung_: er.. maybe #python could help... you need to be registered/identified to join though.
[16:42] <Pici> !register
[16:43] <trung_> ok thx!
[16:43] <trung_> actually I was on the python-unregistered channel but nobody responded
[16:43] <genii> eagles0513875: Does xinput show it?
[16:43] <trung_> xinput?
[16:43] <eagles0513875> genii: yes
[16:43] <trung_> I am not aware of that program
[16:44] <eagles0513875> trung_: its not you need to identify your self on the network before you can go in the proper python channel
[16:45] <genii> eagles0513875: Can you pastebin wht it shows for --list-props of the pad?
[16:45] <eagles0513875> genii: xinput --list-props
[16:46] <genii> eagles0513875: xinput --list-props #        where # is the number it shows for the device when you just do xinput without arguments to it
[16:46] <genii> ( the id=1234 or such part)
[16:46] <eagles0513875> got it
[16:47] <eagles0513875> genii: http://pastebin.com/3Va3jMMU
[16:49]  * genii reads
[16:53] <genii> eagles0513875: Hm. Nothing odd in there. But I might try: xinput --set-prop 11 "Device Enabled" 0   ...to turn it off, see if maybe that property is reversed. If it doesn't work then the same command again but with 1 instead of 0 to turn it back on.
[16:53] <eagles0513875> ok
[16:53] <eagles0513875> ok no response no movement out of the trackpad
[16:56] <genii> eagles0513875: OK. Did you make some xorg.conf thing for it?
[16:56] <nlsthzn> ok thanks wxl
[16:58] <eagles0513875> genii: no
[16:58] <eagles0513875> this was how the 13.10 installer set it up for me
[16:58] <genii> eagles0513875: Is kde-config-touchpad installed?
[17:00] <eagles0513875> genii: synaptiks too
[17:00] <nlsthzn> just for info... re-downloaded a 3rd time and this time installed no problem :/
[17:00] <eagles0513875> genii: i think i might try in a kvm guest
[17:00] <eagles0513875> to see if i encounter the issue there
[17:02] <genii> eagles0513875: I'm going more carefully now over the --list-props to see if there's maybe some odd setting like speed is set to zero or some weirdness
[17:02] <eagles0513875> ok thanks :)
[17:05] <lordievader> trung_: You could use a socket to communicate to the python process.
[17:06] <trung_> lordievader: I am trying to do that
[17:06] <trung_> lordievader: I am considering zeroMQ
[17:07] <trung_> lordievader: is there another alternative that you recommend? Oh, and why does it not work by echoing into the file descriptor?
[17:07] <eagles0513875> wow genii im using qemu as kvm seems to be depreciated in virt manager damn thing wont even boot to the desktop :-/
[17:09] <lordievader> trung_: This is the documentation for Py2 but in Py3 it works similair: http://docs.python.org/2/howto/sockets.html
[17:09] <lordievader> trung_: Sockets can also be files ;)
[17:09] <lordievader> trung_: It might work by echoing, but I've never done it ;)
[17:09] <eagles0513875> genii: things keep getting stranger and stranger here :(
[17:46] <genii> eagles0513875: I might try: sudo modprobe -r psmouse && sudo modprobe psmouse force_elantech=Y
[19:45] <roadfish> How do I reset the desktops after switching monitors?
[19:45] <roadfish> Just replaced 1200x1024 monitor with 1920x1080.
[19:46] <roadfish> But now my desktop backgrounds are spanning different desktops.
[19:47] <roadfish> Ok, I found a work around: add a new virtual desktop ... and then immediately remove it. And I'm guessing logging-out and logging-back-in would also work.
[19:53] <roadfish> quit
[20:05] <wxl> so i'm trying to use kftpgrabber with a public key (openssh format) and it fails to work. this same key works fine on the command line. kftpgrabber asks for the password (so it seems to be able to read it) but then says "unable to decrypt the public key or public key has been rejected by server." wth? ;)
[21:39] <Payne> Hello, I'm looking to get a little help in configuring my Kbuntu Desktop. My goal is to have my Windows PC connect via ethernet to the kbuntu system via Remote desktop and then use kbuntu to browse the web. I have xdrp already installed but having issues with ethernet portion
[21:42] <Payne> any point in the right direction is a plus even if it's just the verbage to search for
[21:49] <Payne> anyone able to help
[21:53] <wxl> Payne: you mean you can't get your kubuntu connected to ethernet?
[21:54] <qdata> Payne: I doubt I can really help, not all that familiar with the linux/windows remote desktop stuff
[21:54] <qdata> but ethernet connectivity depends on some basic stuff
[21:55] <qdata> first off can the windows machine ping the kubuntu machine by IP address
[21:55] <Payne> WXl i can connect kbuntu to internet...
[21:55] <Payne> Qdata good question let me check
[21:56] <qdata> you'll want the machines to both be in the same subnet
[21:56] <qdata> just makes things somewhat simpler
[21:56] <Payne> Qdata, thats the thing.... the Windows PC is only going to connect to the Kubutu machine
[21:56] <qdata> right
[21:56] <Payne> Oh ok yeah both are 255.255.255.0
[21:57] <Payne> Ok no it's can't ping the K box
[21:57] <qdata> so both are like 192.168.10.x /24  M- eg the first three octets are same?
[21:57] <wxl> Payne: you aren't trying to connect the ethernet cable from the windows machine to the kubuntu machine you?
[21:58] <Payne> Yeah 192.168.2.1 (K box) and 192.168.2.2 (windows Box)
[21:58] <Payne> wxl yes I am
[21:58] <qdata> if it's not 1GB/s adapters you need a crossover cable
[21:58] <wxl> yep
[21:59] <Payne> Hmm let me look and see then
[21:59] <wxl> i'd just connect them both to the network
[21:59] <wxl> would be way easier
[21:59] <Payne> the guy i'm doing this for doesn't want the windows pc to direct connect to the internet
[21:59] <qdata> in theory gigabit adapters should auto configure, but that doesn't always happen correctly if the manufacturers are different
[22:00] <Payne> Ok the jetway has 2 gigbit adapters
[22:00] <Payne> looking at the asus
[22:01] <qdata> also the firewall on the kubuntu box may be blocking stuff, if it's blocking an incoming ping it should still allow an outgoing -> eg ping the windows box from the kubuntu box
[22:01] <Payne> ok the ASUS is a gigbit also
[22:02] <qdata> firewalls can be problematic in both directions and I'm not all that familiar with linux firewalling, for me it's openbsd/freebsd pf I'm most familiar with
[22:02] <Payne> SO both have gigE
[22:02] <Payne> ok
[22:04] <Payne> if i need to i'll kill both firewalls to make sure it's not a issue. i just wanted to make sure i was going in the right direction
[22:04] <qdata> yeag - that's what I was going to suggest by way of elimination
[22:05] <qdata> if you drop any/both that might be problematic and now you can ping you know where to look
[22:06] <Payne> OK Firewall on K is not on
[22:07] <qdata> eliminate variables until you get something to change - if the firewalls are completely out of the picture I'd try a crossover cable next to see if different NIC chips aren't autoconfiguring
[22:07] <Payne> how can i make sure my setting are right to allow autocionfigure
[22:08] <Payne> eth0
[22:08] <qdata> gigabit adapters should configure themselves automagically and not require a crossover cable but they don't always work right when the chips are from different manufacturers
[22:08] <Payne> the reason i ask is that i made changes to manually assign IPs
[22:08] <qdata> without firewalls if a crossover cable all the sudden made things talk then you'd know you hit this
[22:09] <qdata> ping by IP first, then ping by hostname later to see if dns works
[22:09] <Payne> So should i reset the Network connection to be automatic again?
[22:10] <qdata> the default nsswitch.conf usually looks at hosts file first, and if can ping by IP and not by hostname you could just put the IP to hostname mappings in hosts
[22:10] <qdata> I'm going to take a guess gere and say "No"
[22:11] <qdata> if 'automatic' is meaning going back to dhcp probably not
[22:11] <Payne> yeah thats what it would mean
[22:12] <qdata> if you're configuring ethernet manually you've already put both IPs in the same subnet
[22:12] <qdata> maybe need to look at other field such as default route
[22:13] <qdata> you might need to point the default route on the windows machine to point at the IP of the kubuntu box
[22:13] <Payne> Oh i think i found something... it's not keeping the manually assigned IP on the K box
[22:13] <qdata> you can look at this on windows in a Dos prompt with ipconfig /all
[22:13] <qdata> lol - that doesn't sound too good   :-)
[22:14] <Payne> nope
[22:14] <Payne> I finally got it to stick
[22:14] <qdata> but yeah - if the kubuntu box IP isn't staying what it's suppsoed to be that's a problem
[22:16] <Payne> hmm keep getting destionation host unreachable..
[22:16] <Payne> I'm guessing i'm missing the crossover cable
[22:16] <Payne> I want to thank you for your time
[22:17] <qdata> have you looked at ipconfig /all on the windows machine?
[22:18] <qdata> look at the default gateway entry
[22:19] <Payne> yeah it shows 192.168.2.2 for ip and subnet is 255.255.255.0 and gfateway is 192.168.2.1
[22:20] <qdata> if 192.168.2.1 is the kubuntu box that's what you want
[22:20] <Payne> it is
[22:21] <qdata> if the kubuntu box has 2 Nics you also need to be sure about which/where you have your cables plugged up - but it's probably good if the kubuntu box still has Inet connectivity
[22:21] <Payne> Yeah the Kbuntu box does have INet
[22:22] <qdata> if you had the cables plugged up backwards you wouldn't
[22:22] <Payne> and it's working
[22:22] <Payne> it must be a cabling issue then
[22:23] <Fudge> hi what is the package called that makes kubuntu show up in the grub menu? guessing its a grub.d script
[22:23] <Payne> IE crossover
[22:24] <qdata> well if you can snag a crossover cable it could eliminate it as a problem - but in theory gigabit adapters shouldn't need it
[22:24] <ChogyDan> my keyboard shortcut for opening a browser window makes the current window go to my home page.  How can I make it open a new window?
[22:24] <Payne> Fudge have you tried to gedit?
[22:24] <Fudge> Payne:  Gedit what?
[22:26] <Payne> Fudge is grub showing even?
[22:30] <Fudge> yeah, it says Kubuntu, because I installed kubuntu-desktop on my Ubuntu system, I am just curious what makes kubuntu show up in grub instaled of ubuntu
[22:34] <ChogyDan> Fudge: probably the grub scripts
[22:38] <Fudge> maybe in package plymouth-theme-kubuntu-text
[22:40] <keithzg>  dpkg -S /etc/default/grub.d/50_kubuntu.cfg
[22:40] <keithzg> kubuntu-settings-desktop: /etc/default/grub.d/50_kubuntu.cfg
[22:40] <keithzg> Looks like it's kubuntu-settings-desktop that provides that.
[22:40] <Unit193> Yep.
[22:42] <Fudge> thanks very much, learn something new every day :D