[05:47] <Haris> hello all
[05:48] <Haris> I'm getting error msg on moving a directory. mv this /to/path is giving me ----> mv: inter-device move failed: ‘141552’ to ‘/nfs-share/app/assets/attachment/1573414’; unable to remove target: Is a directory
[20:54] <emOne> is ubuntu 18.04 set up for ssh log in
[20:54] <emOne> ?
[21:02] <tomreyn> emOne: only if you installed openssh server
[21:02] <emOne> oh
[21:03] <tomreyn> both the live-server installer and and alternative server installer (also mini.iso, i think) offer this option during the installation.
[21:03] <emOne> E: Unable to locate package openssh
[21:03] <tomreyn> openssh-server
[21:04] <emOne> thanks tomreyn
[21:04] <tomreyn> (maybe the (default) live-server installer did not offer installing openssh-server in version 18.04.2 and earlier, though)
[21:04] <emOne> tomreyn: I am running ubuntu 18.04 through a proxmox VM image
[21:05] <tomreyn> you're welcome, emOne. now install your ssh authentication (public) keys and disable password based authentication.
[21:05] <tomreyn> and move ssh to a different port number than 22.
[21:05] <emOne> going to run a quick update and upgrade first before installing openssh
[21:05] <emOne> tomreyn: what is a good port?
[21:06] <emOne> or does one not speak about that in a public IRC forum?
[21:06] <tds> 22 ;)
[21:07] <emOne> lol hello tds
[21:07] <emOne> tds: how do you know I am here!
[21:08] <emOne>  /nick emTwo
[21:08] <tds> I just happened to be here anyway :)
[21:08]  * emOne is emTwo now. I don't know who this em0ne is that you are talking about
[21:09] <emOne> hehe
[21:10] <tomreyn> emOne: any other non standard port i'd say.
[21:10] <tomreyn> 222 2222 22222 or be more creative
[21:11] <emOne> I guess that is a good enough method to keep automated scans from discovering me
[21:12] <tomreyn> the idea there is just to not have those keep your ports busy
[21:12] <tomreyn> err openssh-server
[21:12] <tomreyn> it's not really a security measure
[21:13] <emOne> ahh ok
[21:13] <emOne> nssh-server is already the newest version (1:7.6p1-4ubuntu0.3)
[21:16] <emOne> I am going to ask tds over at proxmox
[21:17] <emOne> the openssh server must be running
[21:17] <emOne> it is asking for my pass afterall
[21:17] <emOne> tomreyn: thanks for all the help!
[21:18] <tomreyn> you're welcome
[21:35] <tomreyn> emOne: password based root login is not a good idea.
[21:36] <emOne> I am going to change it to public / private key in a minute
[21:36] <emOne> I am happy I got ubuntu booting through proxmox in the first place
[21:37] <emOne> tomreyn: btw is it just me or is the debian SSH console prettier?
[21:37] <emOne> I get colours when I boot into debian
[21:37] <emOne> no colors in ubuntu ssh
[21:39] <tomreyn> emOne: those can be enabled.
[21:40] <tomreyn> https://askubuntu.com/questions/16336/how-to-get-coloured-terminal-over-ssh
[21:53] <Greyztar> hello,a question,my raid controller refuse to show me serial of disk so i cant identify disk when they go bad,i ended up pulling each hard drive and then mark the missing disk with corresponding mountpoint so when a mountpoint fails i sort of know which disk it is that way also i made a id file for mount point in each hard drive root folder so i can properly remount same hard drives to same mount points as some of my program depends on it,my
[21:53] <Greyztar> this be done any other way?
[21:54] <Greyztar> im using my raid controller in jbod mode
[21:56] <tomreyn> Greyztar: depends on the raid controller. most either allow querying / configuration from the running ubuntu system using vendor specific software and / or provide such information from an OOB / remote management system
[21:58] <Greyztar> tomreyn: my controller is an ancient lsi controller im using tw-cli to manage it but seems very limited,it shows me model name but no serial,its no good as ive got many disk of same size so cant differentiate if im using my other sata controller i can use smartctl which properly shows the serial so can id the disk that way
[21:59] <Greyztar> same size and make that is
[22:05] <tomreyn> Greyztar: if the controller / management software doesn't disclose it then you're out of luck, unless it's maybe presented in the bios.
[22:05] <tomreyn> like in an option rom
[22:06] <tomreyn> oh smartctl does show it? ok. then hdparm -I should, too
[22:10] <Greyztar> tomreyn: thanks for input ill try hdparm aswell =)
[22:31] <tds> Greyztar: how were you attempting to get smart data out from the controller?
[22:31] <tds> you may need to poke smartctl with some 3ware-specific arguments iirc
[22:32] <Greyztar> tds: dang it i didnt think of that! Of course that might work cheers!
[22:33] <tds> Greyztar: take a look at the -d TYPE... section of the smartctl man page :)
[22:33] <Greyztar> tds: ill try it tomorrow though im soon signing off thanks for the heads up i used it to pull smart info already but in an automated way to email me and such just didnt think i could just do it manually also on terminal of course
[22:34] <TJ-> usually the serial number is used by udev to create a /dev/disk/by-id/ symlink
[22:34] <Greyztar> ohh wait no that was maybe something else hmm ill look into it tomorrow non the less
[22:36] <Greyztar> TJ-: thanks for that input aswell ill note it all and go at it tomorrow seems weird that the raid controller didnt show it in own software though
[22:38] <TJ-> Greyztar: so tw-cli /cX show didn't list the serials?
[22:38] <Greyztar> TJ-: im afraid no just model number :/
[22:39] <TJ-> Greyztar: was there a "serial" in the header row though?
[22:40] <Greyztar> TJ-: so frustrating as all searches on internet shows serial in tw-cli interface then again im running ancient hardware maybe i should invest in newer controller,hmm im not sure what mean by header row though theres a model number and some other number after but i couldnt correlate it to the serial number on the disk tohugh
[22:42] <Greyztar> TJ-: im fairly certain its nothing to do with serial number as its same number on many disk of same size and make
[22:42] <TJ-> Greyztar: "/cX show" or "/cX show drivestatus" outputs a table with a header-row, e.g. "Port   Status           Unit   Size        Blocks        Serial"
[22:42] <TJ-> Greyztar: I'm wondering if the tooling you have is an older version that doesn't report Serial, or if you get that but only see the drive model listed there
[22:44] <Greyztar> TJ-: yeah i think that might be it also,theres no serial head row only model i can see
[22:48] <TJ-> Greyztar: there are some interesting observations in this https://serverfault.com/questions/683464/get-disk-serial-number-by-smartctl-under-raid0-of-lsi
[22:50] <TJ-> Greyztar: is this a SAS controller? If so, sas2ircu should work
[22:53] <Greyztar> TJ-: interesting that article indeed,i think its a sas controller yes im a little tired so ill have to end here ,ill report back tomorrow if i got it working again thanks for helping
[22:58] <tds> if you're using tw_cli, I think you'll end up wanting -d 3ware,x rather than -d sat+megaraid,x, but give it a poke and find out :)
[23:50] <malina>  after months and months of a passthrough win kvm/qemu, an update? (didn't reboot for a week), now stops gpu(nv) to bepicked up by vfio, unlike before. I added softdep nv/nouv* to ...-load.d/vfio.conf or ratrrher in modprobe.d , and it is agaain caught. However, now when I start the vm, which 'starts' the screen is blank and possibly the passed through controller with trhe hids (kb/m), doesn't seem necessarily to switch over (not sure due to
[23:51] <malina>  scree nbeing all blank). recent qemu updates? apparmour? libvirt? something something? where could I find maintainers of these packages?
[23:51] <malina> [01:34:27] <malina> has passthrough issues soared slightly in past week or so when I didn't reeboot.. or maybe fortnight? :)
[23:53] <malina> wondering if people using server for kvm/qemu  machines with windows might have noticed issues with the vfio after an update of say libvirtd/qemu/apparmour/kernel/initrd or similar in past fortnight or so.
[23:55] <compdoc> windows is hosting?
[23:55] <malina> no , of course not
[23:55] <malina> ubuntu
[23:56] <malina> windows is a guest machine to do sketchup, archicad , things like this
[23:56] <malina> any any other programs in need for gpu, the odd game, and any old fashioned progs etc :)
[23:56] <malina> I had for many months, in modprobe.d : blacklist nouveau and similar
[23:56] <compdoc> oh, youre using passthru
[23:57] <malina> and now I noticed yesterday, that when the card wasn't grabbed it was loaded with nouveau, etc.. so I don't think they
[23:57] <malina> yes
[23:57] <compdoc> I have windows server and win10 running, but use all virtual devices
[23:58] <malina> for a short year o r whatever, and some updates (I htink once before) made some changes so I had to fix, but didn't take too long, but right now, I get aagain an issue and notice withoout any change in configurations, that during boot it would ignore the blacklist and still bind to nouveau.. making me feel4 it was almost like a compiled kernel module.
[23:58] <compdoc> and no virtio
[23:58] <malina> you mean you pass the devices trhough or?
[23:58] <malina> I use a  mix of passthrough and virtio for devices
[23:58] <malina> the windows runs on a nvme
[23:59] <malina> as windows is such a horrible OS for anything computational, I give it as fast stuff as it can have just to make sure it can do simple things.


[07:42] <aelen_v> gnome-session-properties does not run my command to get rid of those nasty Flash & Java cookies. It fails whether there is a command (rm -rf ~/.adobe/Flash_Player/AssetCache/*) or an executable bash script containing those rm commands. Though, gnome-schedule seems to do the job (and occasionally gnome-session-properties also...). Could it be a bug or am I missing something?
[08:04] <aelen_v> Occasionally means that after I "cleaned" ~/.gnome2/autostart/sh.desktop file it worked for a couple of logins/reboots. Then it again stopped to work without any evident reason.
[14:46] <om26er> 'huday current' says the available hugday is https://wiki.ubuntu.com/UbuntuBugDay/20110210 how to set it to today's hugday?
[14:47] <om26er> pedro_, ^^
[14:49] <charlie-tca> where?
[14:50] <charlie-tca> nm, nothing I can do
[14:50] <charlie-tca> pedro_: ^ ^
[14:52] <pedro_> om26er, it says 20110203 here
[14:52] <pedro_> om26er, try the ubuntu-qa-tools from the bzr repo
[14:52] <pedro_> bzr branch lp:ubuntu-qa-tools
[14:52] <pedro_> that bug is fixed there, bug in question is bug 592074
[14:52] <ubot4> Launchpad bug 592074 in ubuntu-qa-tools (Ubuntu) (and 1 other project) "hugday current returns next hugday (if available) on a hugday (affects: 1) (heat: 13)" [Undecided,New] https://launchpad.net/bugs/592074
[14:54] <om26er> thanks i'll update :)
[14:54] <pedro_> you're welcome
[16:36] <ScottK> Is that proper tag for a bug with a regression now regression-natty (for a Natty regression from Maverick)?
[16:36] <micahg> ScottK: it's regression-release natty and open a natty task
[16:37] <ScottK> Thanks
[18:02] <charlie-tca> hm, just getting started on the bug day and already seem to be about 50 behind... :-)
[18:02] <charlie-tca> glad to see we have people working this!
[18:44] <bdmurray> chrisccoulson: did that debug version of firefox get uploaded?
[18:44] <Darxus> My bug for alpha 2, which I marked public, was just automatically marked a duplicate of a private bug.  Mine is bug #712660.
[18:45] <yofel> lp 712660
[18:45] <yofel> bug 712660
[18:46] <yofel> jpds: ^
[18:46] <Darxus> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/712660  plugininstall.py crashed with IOError in command(): [Errno 32] Broken pipe
[18:46] <Darxus> Basically install fails.  Possibly just before updating grub.
[18:47] <ddecator> hggdh, charlie-tca, vish: looks like you three (and pedro) are the admins for the bugsquad-mentorship lp team. vish mentioned there being some changes happening to the team (not sure what they are) but i'm currently working with RedSingularity to help get him both into the beginners team and ready for -control. i updated the wiki to show him as my bugsquad mentee, but could one of you approve him into the lp team so it's official? (assuming t
[18:47] <yofel> yep, and it is a duplicate of the other one looking at the backtrace
[18:48] <Darxus> yofel: Yeah, I expected it really was a duplicate.  But it's annoying that I can't get to the one it's a duplicate of.
[18:49] <yofel> well, there might always be some private data from the installation in one of the binary files, that's why it's private
[18:49] <yofel> the bug would need looking at by someone that knows ubiquity before it's marked public
[18:50] <vish> ddecator: done! thanks.. i dint know the link/lp id/member name yesterday :)
[18:50] <ddecator> vish: thanks much :)
[18:50] <charlie-tca> Darxus, yofel : looking
[18:51] <vish> hggdh: charlie-tca approved RedSingularity as ddecator's mentee for the old team
[18:51] <yofel> charlie-tca: thanks, I don't know scratch about ubiquity
[18:51] <ddecator> old team?
[18:51] <yofel> ddecator: btw, you need an IRC client that supports oversized messages :P
[18:52] <vish> ddecator: yea.. now there is a new team where it is not just one on one.. more of a classroom
[18:52] <vish> with a bunch of mentors..
[18:52] <ddecator> vish: oh, interesting. is there a wiki page describing it?
[18:52] <Darxus> I know there's no private data in mine.   Why did Bug Watch Updater go through and set the importance on some upstream tasks from Medium to Unknown last week and then turn around and undo that change today?
[18:53] <vish> ddecator: https://launchpad.net/~bugsquad-mentorship-group-alpha
[18:54] <vish> greg-g: it is a silly little thing, i believe it sometimes forgets what it is has already done  ;p
[18:54] <vish> -is
[18:54] <greg-g> unfortunately I heard from a member of the michigan loco that it is annoying the heck out of him :/
[18:55] <vish> yea.. me too :S
[18:55] <ddecator> vish: interesting idea. any restrictions for joining the new team?
[18:56] <vish> ddecator: nope. it was basically an idea to have several sub-teams …
[18:56] <vish> ddecator: not sure what restrictions you are thinking of though..
[18:57] <bdmurray> greg-g: it was a bug in Launchpad itself and the parsing of upstream bug reports
[18:57] <ddecator> vish: i guess "requirements" would have been a better word. i'd be willing to join that new team and help out any way i can :)
[18:58] <charlie-tca> Darxus: public now, you should be able to see bug 705359
[18:58] <ubot4> Launchpad bug 705359 in ubiquity (Ubuntu) "plugininstall.py crashed with IOError in command(): [Errno 32] Broken pipe (affects: 10) (dups: 9) (heat: 82)" [Undecided,New] https://launchpad.net/bugs/705359
[18:58] <charlie-tca> vish: thanks
[18:58] <vish> like Bug #575774 , it one day changed the status and then today it updated the priority.. that too for an invalid bug o.0
[18:58] <Darxus> charlie-tca: Cool, thanks.
[18:58] <ubot4> Launchpad bug 575774 in linux (Ubuntu) (and 1 other project) "2.6.32-21-generic CE: hpet increasing min_delta_ns flood (affects: 2) (heat: 24)" [Low,Incomplete] https://launchpad.net/bugs/575774
[18:59] <charlie-tca> yofel: no problem
[18:59] <Darxus> Yup, I can see it.
[19:00] <greg-g> bdmurray: sad. Oh well. I'll make sure the guy who was annoyed doesn't get too annoyed ;)
[19:00] <greg-g> bdmurray / vish: thanks for the info, though!
[19:01] <vish> np.. i got spammed today too :)
[19:01] <vish> well often, whenever it has its tantrums ;p
[19:02] <vish> hehe, *ONE year* later it checked for the importance of this fix released bug  Bug #406167  ;p
[19:02] <ubot4> Launchpad bug 406167 in kdebase-runtime (Ubuntu) (and 2 other projects) "[karmic] Strigi indexer notifications after suspend/hiberbation (affects: 4) (heat: 6)" [Low,Fix released] https://launchpad.net/bugs/406167
[19:03] <yofel> heh
[19:06] <vish> ddecator: sure, you can join in the new team as well.. or maybe we can start a new beta mentoring team too, depending on what the others think …
[19:07] <ddecator> vish: no rush. you guys talk it over and decide where you want to things to go, and we can go from there
[19:07] <bdmurray> I think one team is enough for now as we are just testing it out
[19:09] <vish> bdmurray: should we make it mandatory that mentees need to report biweekly?(just mentioning the bugs they triaged or even if they dint ) there seems little activity in the team.. :s
[19:11] <bdmurray> vish: it seems like more work for the mentee which my increase the burden of triaging if you will.  I'd rather something (smart) were done like that automatically.  Perhaps subscribing the team to the bug or an auto generated summary of activity.
[19:11] <Darxus> Has anybody gotten alpha 2 64 bit to install?
[19:12] <vish> hmm, automatically.. interesting idea..!
[19:13] <ddecator> bdmurray: +1
[19:14] <vish> bdmurray:  why i thought making them submit was because i noticed that some havent triaged even a single bug.. :(
[19:15] <vish> https://launchpad.net/~adiratiu00/+karma none
[19:15] <vish> https://launchpad.net/~bolster/+karma no recent activity..
[19:16] <bdmurray> vish: well it'd be good to follow up and find out why.  is due to lack of time or something about the triaging process?
[19:16] <vish> yea..
[19:17] <vish>  i'll send out a mail today, asking how it is going on
[19:17] <bdmurray> I wouldn't necessarily trust +karma
[19:18] <vish> nah, not karma.. its the no bug activity i'm looking it
[19:18] <bdmurray> I wouldn't necessarily trust the +karma page
[19:18] <vish> oh!
[19:19] <vish> (gmane doesnt show any difference either..)
[19:19] <Darxus> Alpha 2 was released with an amd64 image that *never* successfully installs without a workaround?
[19:19] <bdmurray> vish: okay if both say that then okay ;-)
[19:20] <vish> ;)
[19:21] <yofel> alpha2 was released? where?
[19:21] <vish> !
[19:21] <yofel> Darxus: btw. you can find ISO testers in #ubuntu-testing, they might know more
[19:22]  * vish was just typing : Darxus: you'd have better luck in #u+1 … and realized what yofel said :D
[19:22] <yofel> well, #ubuntu+1 too as vish wanted to say ;)
[19:23] <vish> yofel: Darxus is trying to trick us like pitti ;p
[19:23] <yofel> hahah
[19:23] <Darxus> yofel: Thanks.
[19:23] <Darxus> vish: How is pitti trying to trick you?
[19:24] <vish> Darxus: he pre-announced archives being closed for alpha2  ;)
[19:24] <vish> jolted the heck out of a lot of folks ;p
[19:24] <Darxus> vish: Huh?
[19:24] <yofel> oh yeah, that was funny :D
[19:25]  * yofel fetches the mail
[19:27] <yofel> Darxus: 1) https://lists.ubuntu.com/archives/ubuntu-devel-announce/2011-January/000811.html
[19:27] <yofel> Darxus: 2) https://lists.ubuntu.com/archives/ubuntu-devel-announce/2011-January/000812.html
[19:27] <bdmurray> Darxus: the issue is documented in the TechnicalOverview for Natty
[19:27] <bdmurray> https://wiki.ubuntu.com/NattyNarwhal/TechnicalOverview
[19:27] <bdmurray> if its the one I am thinking of
[19:27] <Darxus> yofel: Nice, thanks :)
[19:27] <Darxus> bdmurray: I saw that.  It's actually a different bug.  I'm trying the workaround listed for it.
[19:27] <bdmurray> Additionally the known issues on that page are something we all should be familiar as duplicates may come in
[21:56] <bcurtiswx> bug watch updater is sick again
[21:56] <bcurtiswx> or well.. its better and catching up