[05:58] <bmg505> gmsa
[05:58] <bmg505> raid5 and double failures FTL
[05:59] <superfly> morning bmg505
[06:41] <linuxboy> bmg505: hot spare
[06:42] <linuxboy> (cause a bunch of new drives will most likely fail at teh same time, throw in a hot spare and it won't be used until needed)
[07:06] <sakhi> moonin
[07:10] <Symmetria> http://www.overclockers.com.au/image.php?pic=images/newspics/11feb11/15.jpg
[07:10] <Symmetria> !
[07:10] <Symmetria> zomg gonna become super 3r33t!
[07:11]  * Symmetria rolls his eyes
[07:12] <sakhi> eish
[07:50] <inetpro> hmm...
[10:11] <sakhi> Symmetria: all is well?
[10:14] <Symmetria> sakhi that I know of
[11:43] <kodez> afternoon all, when is the next ubuntu-za meeting?
[11:44] <kodez> also where do I get the last meeting minutes, i had forgotten the website?
[11:44] <drubin> kodez: next meeting will be some time later this month not sure exact date.
[11:45] <drubin> website it https://wiki.ubuntu.com/ZATeam
[11:50] <kodez> thanks drubin, i will try to keep up with the latest developments
[12:09] <kodez> are there any ubuntu hour coming in pretoria?
[14:40] <kodez> when is ubuntu hour coming to pretoria?
[14:41] <superfly> kodez: they are announced on the mailing list
[14:41] <superfly> either that, or just do it yourself
[14:41] <superfly> don't wait for someone else
[14:42] <drubin> kodez: there was one while maiatoday was there.. but just email the list and tell people I am going to be at XX on YY date at ZZ time :)
[14:42] <tumbleweed> superfly, drubin: ubuntu-za site needs a poke, it's horribly out of date
[14:42] <tumbleweed> I think it may also be responsible for the OOMs we are seeing on soda
[14:42] <kodez> i had not participated before and had been seeing the stellenbosch guys are the ones consistant in organising it
[14:43] <superfly> a news story or two
[14:43]  * drubin can't do it today
[14:45] <superfly> tumbleweed: looks like the cron job is having issues
[14:46] <tumbleweed> superfly: yeah
[14:46] <tumbleweed> so I'm assuming it's the planet bit that's at fault
[14:48] <superfly> probably
[14:49] <tumbleweed> I can upgrade the box to squeeze which would mean we can use a package-managed drupal, but that's going to take some negotiation with frogfoot (we'll need a newer kernel for squeeze's udev)
[14:51] <superfly> it's fine, I prefer non-packaged Drupal
[14:52] <superfly> tumbleweed: I'll upgrade the modules, and perhaps Drupal itself if I have enough time, later this evening, once the munchkin is in bed
[14:53] <tumbleweed> superfly: awesome :)
[14:57] <drubin> sorry guys...
[15:06] <kodez> drubin, do you mean we must wait for maiatoday to have another one?
[15:07] <drubin> kodez: No deffinatly don't do that, maia is it cape town
[15:07] <drubin> kodez: Just start your own one
[15:08] <kodez> drubin, what exactly is happening in ubuntu hour?
[15:31] <kodez> i'm out of here, till we meet next time
[17:27] <silent> hi everyone
[17:27] <silent> anyone can pm me
[17:30] <nlsthzn> r u a stalker?
[17:32] <cocooncrash> Maaz: dns for <IP_ADDRESS>
[17:32] <Maaz> cocooncrash: I couldn't find the domain <IP_ADDRESS>.in-addr.arpa.
[17:32] <drubin> silent: why would we want to ping you?
[17:33] <nlsthzn> :/ who is gives me paris, claims to be from india... am I being hacked :(
[17:34] <cocooncrash> And drubin yields the heavy hand of the law.
[17:34] <drubin> ^^ that was because this channel isn't a dating channel
[17:35] <drubin> btw that was via pm's
[17:36] <nlsthzn> boom
[17:37] <Morganvd> its not a dating channel no one told me
[17:43] <Symmetria> http://ismubarakstillpresident.com/
[17:43] <Symmetria> !
[17:44] <nlsthzn> haha
[17:44] <nlsthzn> love the pop up quassel does for web sites
[17:44] <nlsthzn> llinks
[17:48] <nlsthzn> Q&A in #ubuntu-classroom at the moment... on servers
[18:18] <superfly> nlsthzn: what do you mean, "who is gives me paris"?
[18:19] <nlsthzn> oh, our dating friend, silent, from a while ago... who-is said the IP was in France, but he/she claimed they where from india
[18:24] <Kilos> evening everybody
[18:24] <Kilos> Maaz, coffee on
[18:24]  * Maaz flips the salt-timer
[18:24] <nlsthzn> Hey Mr Kilos
[18:24] <Kilos> hi nlsthzn howzit in ahab land
[18:25] <nlsthzn> all is quiet thx and there?
[18:25] <Kilos> good here as well ty
[18:28] <Maaz> Coffee's ready for Kilos!
[18:28] <Kilos> Maaz, ty
[18:28] <Maaz> You're Welcome I'm sure
[18:28] <Kilos> Maaz, whats for supper
[18:28] <Maaz> Steak , egg and chips. And a free Coke
[18:53] <superfly> nlsthzn: ah, geoip, in otherworse
[18:53] <superfly> *other words
[18:53] <nlsthzn> superfly: if you say so :p
[18:53] <superfly> nlsthzn: geoiptool.com
[18:54] <Kilos> hiya superfly just the man i need
[18:54] <Kilos> got probs with python
[18:55] <nlsthzn> superfly: hmmm, must bookmark
[18:56] <superfly> hi Kilos
[18:56] <superfly> what problems?
[18:56] <Kilos> when i try install something i get an error message
[18:57] <Kilos> or is it dpkg
[18:57] <Kilos> dpkg: error processing python-louis (--configure):
[18:57] <Kilos>  dependency problems - leaving unconfigured
[18:57] <Kilos> No apport report written because the error message indicates its a followup error from a previous failure.
[18:57] <Kilos>                           Errors were encountered while processing:
[18:57] <Kilos>  python-support
[18:57] <Kilos>  python-louis
[18:57] <Kilos> E: Sub-process /usr/bin/dpkg returned an error code (1)
[18:57] <Kilos> sorry for that large post
[19:03] <superfly> Kilos: just run "sudo aptitude -f install"
[19:04] <Kilos> ty superfly
[19:09] <Kilos> same thing superfly
[19:09] <Kilos> http://slexy.org/view/s20qOhXQCi
[19:10] <Kilos> is it because i completely removed midori perhaps
[19:13] <superfly> Kilos: ah, now I see what your problem is
[19:13] <superfly> what were you trying to do?
[19:13] <Kilos> i told midori full page and couldnt see anything else
[19:13] <Kilos> no panels etc
[19:14] <Kilos> so i completely removed it via synaptic
[19:14] <Kilos> thats when the error messages started
[19:56] <superfly> Kilos: it doesn't look like you did it properly
[19:57] <Kilos> ]i did everything via synaptic superfly
[19:57] <Kilos> and install sometimes with aptitude
[19:57] <Kilos> no more foreign stuff
[19:59] <superfly> Kilos: try "sudo aptitude purge midori"
[20:01] <Kilos> nope same errors
[20:02] <Kilos> python-support and  python-louis
[20:13] <Kilos> oh superfly  i had to boot 3 or 4 times till it got to recovery mode and did that and also grub update from there as well. could that be the prob
[20:14] <Kilos> i just did aptitude install python-doc and it downloaded 5.7m
[20:14] <Kilos> but gave same error
[20:14] <Kilos> http://slexy.org/view/s20l7kOFIL
[20:15] <Kilos> how can it download so much if system was up to date
[20:23] <Kilos> is there a key to press to get to boot into the mode where you choose recovery or another version . i just keep rebboting till it stops there on its own
[20:32] <cocooncrash> #
[20:32] <cocooncrash> Package python-support is not configured yet.
[20:32] <cocooncrash> That looks like the root error.
[20:32] <cocooncrash> Kilos: Try aptitude reinstall python-support
[20:33] <Kilos> ok
[20:34] <Kilos> nope. same error report
[20:35] <cocooncrash> Oh, also on man-db
[20:35] <cocooncrash> Something's stuffed, I'm not sure what
[20:38] <Kilos> yip. aptitude reinstall man-db gives same error
[20:38] <Kilos> how do i aptitude reinstall from scratch
[20:38] <cocooncrash> Kilos: Try dpkg-reconfigure python-support
[20:39] <cocooncrash> And dpkg-reconfigure man-db
[20:39] <Kilos> ok
[20:40] <Kilos> miles@P4:~$ sudo dpkg-reconfigure python-support
[20:40] <Kilos> /usr/sbin/dpkg-reconfigure: python-support is broken or not fully installed
[20:41] <Kilos> miles@P4:~$ sudo dpkg-reconfigure man-db
[20:41] <Kilos> Updating database of manual pages ...
[20:41] <Kilos> Segmentation fault
[20:42] <cocooncrash> Hrm, okay, let's try get dpkg out the picture
[20:43] <cocooncrash> sudo /var/lib/dpkg/info/man-db.postinst
[20:43] <Kilos> ok
[20:43] <Kilos> no reports
[20:44] <cocooncrash> So it seems to be dpkg itself, not the scripts.
[20:44] <Kilos> will it give that on cli
[20:45] <Kilos> or is it inna file somewhere
[20:45] <cocooncrash> What do you mean?
[20:46] <Kilos> when i run that command will it report on termial
[20:46] <Kilos> terminal
[20:46] <Kilos> not in logs somewhere
[20:47] <cocooncrash> That last one? It should only output on the terminal.
[20:47] <cocooncrash> If you just got your prompt back then it worked.
[20:47] <Kilos> great
[20:47] <cocooncrash> I'm wondering whether there are some dpkg hooks which are breaking.
[20:48] <Kilos> is there a way to fix broken packages
[20:49] <Kilos> without knowing which one is actually broken
[20:49] <cocooncrash> I don't think it's the package which is broken
[20:49] <cocooncrash> I think dpkg itself is broken.
[20:49] <Kilos> eish
[20:51] <cocooncrash> Kilos: Try "apt-get -f install"
[20:51] <Kilos> ok
[20:52] <Kilos> same errors
[20:57] <cocooncrash> Kilos: Um, try: dpkg -i /var/cache/apt/archive/man-db_*.deb
[20:58] <Kilos> ok
[20:58] <Kilos> dpkg: error processing /var/cache/apt/archive/man-db_*.deb (--install):
[20:58] <Kilos>  cannot access archive: No such file or directory
[20:58] <Kilos> Errors were encountered while processing:
[20:58] <Kilos>  /var/cache/apt/archive/man-db_*.deb
[20:59] <cocooncrash> Sorry, archives
[20:59] <Kilos> ah
[21:01] <Kilos> sudo: /var/cache/apt/archives/man-db_2.5.7-4_i386.deb: command not found
[21:02] <cocooncrash> sudo dpkg -i /var/cache/apt/archives/man-db_*.deb
[21:03] <Kilos> no error message
[21:03] <cocooncrash> Ooh
[21:03] <Kilos> will paste to bin
[21:03] <cocooncrash> That's fine, now do:
[21:03] <cocooncrash> sudo dpkg -i /var/cache/apt/archives/python-support_*.deb
[21:03] <Kilos> ok
[21:04] <Kilos> dpkg: error processing /var/cache/apt/archives/python-support_*.deb (--install):
[21:04] <Kilos>  cannot access archive: No such file or directory
[21:04] <Kilos> Errors were encountered while processing:
[21:04] <Kilos>  /var/cache/apt/archives/python-support_*.deb
[21:04] <cocooncrash> Hrm, you don't have that deb
[21:04] <cocooncrash> aptitude download python-support; sudo dpkg -i python-support_*.deb
[21:05] <Kilos> ok
[21:05] <Kilos> Segmentation fault
[21:05] <Kilos> Errors were encountered while processing:
[21:05] <Kilos>  python-support
[21:06] <cocooncrash> Meh
[21:06] <cocooncrash> I don't know what else to suggest
[21:07] <Kilos> ok ty for the help i will do a clean install
[21:07] <Kilos> is there a way to go straight to the recovery mode
[21:08] <Kilos> at least this time it missed python-louis
[21:18] <Kilos> see you all tomorrow. sleep tight. ty for the help
[21:36] <Kilos> hey guys its fixed
[21:37] <Kilos> seeing as i was gonna do a clean install i decided to play in root
[21:37] <Kilos> sudo -i
[21:37] <Kilos> then aptitude install dpkg and man-db and python support
[21:38] <Kilos> python-support
[21:38] <Kilos> now synaptic is working as well. i so happy. 100m data saved
[21:38] <Kilos> ty
[21:39] <Kilos> sleep well. i will
[21:39] <Kilos> Maaz, coffee on
[21:39]  * Maaz puts the kettle on
[21:40] <Kilos> Maaz, move it
[21:40] <Maaz> Don't rush me Kilos . Making decent coffee is an art
[21:40] <Kilos> cheeky bot
[21:40] <cocooncrash> Kilos: Nice!
[21:41] <Kilos> that was just fluke ty for the help cocooncrash  you taught me to use sudo -i a year ago
[21:41] <cocooncrash> :-)
[21:42] <Kilos> but i normally stuff up there so i stay clear. but now i had nothing to lose and everything to gain
[21:43] <Maaz> Coffee's ready for Kilos!
[21:44] <Kilos> Maaz, thanks man
[21:44] <Maaz> sure thing, Kilos
[21:44] <Kilos> Maaz, night
[21:44] <Maaz> kbye Kilos


[17:18] <red98> hii... global shortcut conf isn't working
[17:21] <red98> do i need to restart
 Do you have this issue with other distributions?
 What lubuntu version are you on?


[00:33] <RAOF> Fascinating! If I scroll rapidly in gnome-control-center it cleanly quits.
[00:49]  * arraybolt3 imagines the horror of a DE wherein which windows have no close button and the way to close an app is to scroll down quickly
[01:06] <RAOF> LP: #2016441 is the bug, for those playing at home :)
[01:06] -ubottu:#ubuntu-desktop- Launchpad bug 2016441 in gnome-control-center (Ubuntu) "Scrolling with the mouse wheel beyond the top or bottom causes gnome-control-center to exit" [Undecided, New] https://launchpad.net/bugs/2016441
[01:31] <Eickmeyer> RAOF: Cannot.... reproduce....?
[01:31] <RAOF> Hm. I'll spin up a livecd.
[01:32] <RAOF> I don't think I've done anything weird (to the gnome-control-center stack, at least 😉), maybe it's this particular mouse?
[01:32] <Eickmeyer> ? ¯\_(ツ)_/¯
[01:34] <RAOF> Or maybe I have done something weird to g-c-c, but it's weird that it, you know, doesn't crash.
[01:42] <RAOF> Ah!
[01:42] <RAOF> Yes.
[01:42] <RAOF> LD_LIBRARY_PATH, my old nemesis.
[01:53] <Eickmeyer> oof
[01:53] <Eickmeyer> I avoid that guy like the plague.
[02:58] <KGB-2> gnome-session Janitor 394617 * commented merge request !12 * https://deb.li/8hUs
[05:51] <Guest4> hi there
[05:52] <Guest4> I i'm on ubuntu 22.04, I have struglling with the lost of 'CTRL+V' for paste, anyone could help troubleshooting? please
[23:21] <KGB-0> cheese upstream/latest 1e5286f Jeremy Bicha data/org.gnome.Cheese.appdata.xml.in * appdata: List 44.0 release * https://deb.li/4ouU
[23:21] <KGB-0> cheese upstream/latest 7dbce9f Jeremy Bicha NEWS data/org.gnome.Cheese.appdata.xml.in meson.build * Prepare 44.0.1 * https://deb.li/3WlSF
[23:21] <KGB-0> cheese upstream/latest e266018 Jeremy Bicha NEWS data/org.gnome.Cheese.appdata.xml.in meson.build * New upstream version 44.0.1 * https://deb.li/e4Q7
[23:21] <KGB-0> cheese pristine-tar cbbd333 Jeremy Bicha cheese_44.0.1.orig.tar.xz.delta cheese_44.0.1.orig.tar.xz.id * pristine-tar data for cheese_44.0.1.orig.tar.xz * https://deb.li/3dobC


[16:59] <wdop_> Hello, I have a problem bridging ethernet on Ubuntu 21.04 (Host) into kvm/qemu. I had a working configuration until for some reason I deleted the bridge using nm-connection-editor. Now the "wired connection" inside the vm is not working anymore. Anyone could help me?
[17:01] <wdop_> I asked in #ubuntu and someone sent me here..
[17:03] <wdop_> I tried setting up a bridge but when I want to add a bridged connection "ethernet" on the next dialog I cannot choose a device.
[17:41] <tomreyn> wdop_: you can also use brctl to set it up
[18:00] <wdop_> @tomreyn, I look into that now. Thanks!
[18:05] <wdop_> @tomreyn, "brctl show" returns:
[18:05] <wdop_> virbr0		8000.525400423a34	yes
[18:06] <wdop_> just one line. I am wondering how to proceed from here. In fact, my knowledge is very limited concerning this things.
[18:16] <tomreyn> wdop_: you can create a bridge using "brctl", then optionally attach interfaces to it using "brctl addif", btut you can actually do this with "ip", too.
[18:17] <tomreyn> either command provides help on usage and a man page
[18:18] <wdop_> Thanks, I barely understand the terms :( Are there good examples of how to do this?  Thanks again. I will try my best!
[18:22] <wdop_> I am on 21.04 on a laptop and have 20.04 running inside kvm (w/o working wired connection)
[18:24] <wdop_> One more question: What is the type of bridge that is used when first installing kvm on a clean system and then running another Ubuntu in the vm?
[18:24] <TJ-> wdop_: that's not done with kvm; I think what you may be using is libvirt/virt-manager ?
[18:24] <wdop_> yes
[18:25] <TJ-> wdop_: in which case if it's the virbr0 you deleted, restarting libvirtd service will recreate it
[18:25] <TJ-> virbr0 is used as part of the default network for the hypervisor
[18:26] <wdop_> How would I check if it is recreated?
[18:27] <TJ-> wdop_: restart the service (stop the guest first) "sudo systemctl restart libvirtd"
[18:27] <wdop_> done
[18:27] <TJ-> wdop_: then "ip link show dev virbr0" should show it has been recreated
[18:28] <wdop_> 5: virbr0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
[18:28] <wdop_>     link/ether 52:54:00:42:3a:34 brd ff:ff:ff:ff:ff:ff
[18:28] <TJ-> wdop_: now restart the guest and you should be OK
[18:28] <wdop_> really? ok, lat's see
[18:28] <TJ-> wdop_: first guest using that bridge should cause the bridge to be put into state UP
[18:29] <wdop_> no
[18:29] <wdop_> In the UI it shows Wired connecting...
[18:29] <TJ-> wdop_: then it is possible you have some other form of network configured in libvirt/virt-manager
[18:30] <wdop_> how would I check?
[18:31] <TJ-> wdop_: what does "virsh net-list" report?
[18:31] <wdop_>  Name      State    Autostart   Persistent
[18:31] <wdop_> --------------------------------------------
[18:31] <wdop_>  default   active   yes         yes
[18:32] <wdop_> ip link show dev virbr0
[18:32] <wdop_> 5: virbr0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
[18:32] <wdop_>     link/ether 52:54:00:42:3a:34 brd ff:ff:ff:ff:ff:ff
[18:32] <TJ-> wdop_: show us "virsh net-dumpxml default" (in a pastebin)
[18:33] <wdop_> https://pastebin.com/VasyuLs4
[18:34] <TJ-> wdop_: now lets check the guest(s) and what they are connected to. " virsh list --all | nc terbmin.com 9999 "
[18:35] <TJ-> oops, typo
[18:35] <TJ-> wdop_: now lets check the guest(s) and what they are connected to. " virsh list --all | nc termbin.com 9999 "
[18:35] <TJ-> got the m and b swapped!
[18:35] <wdop_> https://termbin.com/qg8j
[18:36] <TJ-> so it'll be ubuntu20.04 ?
[18:36] <wdop_> Both are the same image.
[18:36] <wdop_> Let's take the MPI-Ae
[18:37] <TJ-> " virsh dumpxml MPI-AE | nc termbin.com 9999 "
[18:37] <wdop_> virsh dumpxml MPI-AE | nc termbin.com 9999
[18:38] <wdop_> https://termbin.com/fn54
[18:40] <TJ-> you've got the correct linkage in there " <interface type='network'>"
[18:41] <TJ-> so starting the guest should work
[18:42] <TJ-> if the problem is solely the guest cannot get to the Internet, then you may affected the host iptables rules
[18:42] <TJ-> libvirt sets up IP Masquerading for IPv4 via iptables
[18:42] <wdop_> It is in state "connecting" again. no luck
[18:43] <TJ-> wdop_: what is 'it' ? the guest's GUI network applet ?
[18:44] <wdop_> sorry! yes. the applet on the top right says "Wired Connectiong" and also under Settings -> Network
[18:45] <TJ-> wdop_: ok, in the guest start a terminal, then check the log with "journalctl -u NetworkManager -n 50"
[18:45] <wdop_> Now on the guest: "Activation of the network connection failed"
[18:45] <TJ-> that'll show the last 50 messages, and in there should be a clue as to why
[18:45] <wdop_> You give me hope!
[18:46] <wdop_> Should I pate the output? patebin?
[18:46] <wdop_> *paste
[18:46] <TJ-> if the interface is set to use IPv4 DHCP and that is what is failing, then there's a problem with the hypervisor's DHCP service
[18:47] <TJ-> If I recall correctly, the libvirt makes uses of private dnsmasq instances
[18:47] <TJ-> so on the host check if any are active, with "ps -efly | grep dnsmasq "
[18:47] <wdop_> https://pastebin.com/vKnmM8uc
[18:48] <TJ-> "dhcp4 (enp1s0): request timed out"
[18:48] <TJ-> so we've now confirmed that is the cause
[18:48] <wdop_> ps -efly | grep dnsmasq
[18:48] <wdop_> S libvirt+    1513       1  0  80   0  1948  2439 -      03:36 ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
[18:48] <wdop_> S root        1514    1513  0  80   0   332  2432 -      03:36 ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
[18:49] <TJ-> wdop_: other than deleting the virbr0 using nmcli, did you do anything else network related, like add/remove iptables rules?
[18:49] <TJ-> wdop_: those are the expected processes, owned by libvirt too
[18:49] <wdop_> 1. I deleted the bridge using the nm-connection-manager
[18:50] <wdop_> 2. I installed/purged protonvpn
[18:51] <wdop_> 3. Then installed protonvpn again
[18:51] <TJ-> wdop_: I'm thinking you've altered something in iptables by doing that. Show us "sudo iptables-save | nc termbin.com 9999 "
[18:51] <wdop_> Currently it is not running
[18:52] <wdop_> https://termbin.com/8fli
[18:55] <TJ-> wdop_: that all looks correct too
[18:55] <wdop_> To ansswer your question from before, I didn't execute any iptables commands before.
[18:55] <TJ-> I'm wondering if it is routing, which the vpn may have messed with
[18:56] <TJ-> show us " ip route show | nc termbin.com 9999 "
[18:56] <wdop_> ip route show | nc termbin.com 9999
[18:56] <wdop_> https://termbin.com/jbh4
[18:58] <TJ-> It's a while since I used IPv4 networking but that looks correct; nothing there affecting the virbr0 network
[18:59] <wdop_> hm. I will now completely purge the protonvpn, in the meantime
[18:59] <TJ-> I don't see anything affecting it right now
[19:00] <wdop_> ok
[19:04] <wdop_> Would a "apt purge" for kvm/qemu maybe help in resetting the configuration? Thanks so much for your help so far.
[19:04] <TJ-> is the guest active right now? if so, is the bridge in state UP? "ip lnk show dev virbr0"
[19:04] <TJ-> oops, another typo. "ip link show dev virbr0"
[19:05] <wdop_> 5: virbr0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
[19:05] <wdop_>     link/ether 52:54:00:42:3a:34 brd ff:ff:ff:ff:ff:ff
[19:05] <wdop_> no problem, a realized this ;)
[19:05] <TJ-> hmmm, it's still down! try "sudo ip link set up dev virbr0"
[19:06] <wdop_> done
[19:06] <wdop_> ip link show dev virbr0
[19:06] <wdop_> 5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
[19:06] <wdop_>     link/ether 52:54:00:42:3a:34 brd ff:ff:ff:ff:ff:ff
[19:06] <TJ-> !!
[19:06] <wdop_> I return nothing, btw
[19:06] <TJ-> wdop_: have you by chance enabled systemd-networkd on this host?
[19:06] <wdop_> idk
[19:07] <TJ-> if there were a config, and it is somehow set to manage virbr0, then it could be forcing this
[19:07] <TJ-> that interface should be UP now
[19:08] <TJ-> wdop_: show us " ip -d link show | nc termbin.com 9999 "
[19:09] <wdop_> https://termbin.com/f13hk
[19:10] <TJ-> ahhh "vnet1" is "tun type tap"
[19:11] <wdop_> If I knew what this means really..
[19:13] <TJ-> I'm setting up an identical config here to compare
[19:14] <wdop_> wow
[19:15] <wdop_> I will copy the chat history and work through this again to understand the steps we took!
[19:17] <TJ-> is it working for you? I'm seeing identical results here to commands but the guest got an address from DHCP without a problem
[19:18] <TJ-> turns out virbr9 showing state DOWN is correct :s
[19:19] <wdop_> How should I check, just starting the guest and "journalctl -u NetworkManager -n 50"
[19:19] <TJ-> actually no, virbr0 is state UP here
[19:19] <wdop_> aha
[19:21] <TJ-> I'm not sure what you've done!
[19:23] <TJ-> let's see if the host's NM is doing something. " journalctl -u NetworkManager -n 250 | nc termbin.com 9999 !
[19:24] <wdop_> https://termbin.com/b97oa
[19:26] <wdop_> doing nothing...
[19:27] <wdop_> >Reminder: Host is 21.04, Guest is 20.04
[19:29] <TJ-> that looks ok;I can see you deleted the 2 NM connections that were attached to the bridge and vnet port
[19:29] <TJ-> so NM isn't trying to manage them as far as that log shows
[19:30] <TJ-> I'd have thought that "device (virbr0): carrier: link connected" would imply "ip link show dev virbr0" should show state UP now
[19:30] <wdop_> 5: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
[19:30] <wdop_>     link/ether 52:54:00:42:3a:34 brd ff:ff:ff:ff:ff:ff
[19:30] <wdop_> It is up now.
[19:30] <wdop_> ?
[19:32] <TJ-> aha!
[19:32] <TJ-> so has the guest been able to get an IPv4 address ?
[19:32] <wdop_> No.
[19:33] <TJ-> hmmph
[19:33] <TJ-> when (date/time) did you delete the working config? I want to find the log entries from before then to learn how it was configured when it worked
[19:34] <wdop_> hwo to I check? dhclient?
[19:34] <TJ-> was it today? yesterday?
[19:34] <wdop_> yesterday.
[19:34] <TJ-> so 3rd Oct
[19:34] <TJ-> roughly what time of day?
[19:34] <wdop_> yes
[19:35] <wdop_> start from 18:00, but not 100% sure
[19:37] <wdop_> Should I reboot the guest?
[19:37] <TJ-> no, it doesn't look to be the problem
[19:38] <TJ-> show us " journalctl -u NetworkManager --since="2021-10-03 12:00" --until="2021-10-03 22:00" | nc termbin.com 9999 "
[19:39] <wdop_> https://termbin.com/aojo
[19:40] <wdop_> hmmm, too big?
[19:40] <TJ-> ow, looks like loads of VPN errors
[19:40] <wdop_> I grep them out?
[19:41] <TJ-> lets filter it:  " journalctl -u NetworkManager --since="2021-10-03 12:00" --until="2021-10-03 22:00" | grep -v AEAD | nc termbin.com 9999 "
[19:41] <wdop_> https://termbin.com/nrp2
[19:45] <wdop_> I had this problem with the pvpn-killswitch that was still there in the table of connections after uninstalling protonvpn yesterday. This prevented wifi from connecting. So I deleted the bridge first. but this didn't help. Then deleted the two protonvpn connections that were still there. After that WIFI on the host worked again.
[19:45] <wdop_> But the guest then had this current issue which we are working on now.
[19:46] <TJ-> hmmm. Can't see anything useful in the log, aside from an apparent confirmation it was working at "Okt 03 21:23:49 nador NetworkManager[1332]: <info>  [1633289029.9938] device (virbr0): bridge port vnet5 was attached"
[19:46] <wdop_> Wait maybe it was after midnight?
[19:47] <wdop_> https://termbin.com/c1xy
[19:47] <TJ-> unfortunately there's not enough info in the logs to reconstruct how it was configured
[19:56] <wdop_> I am thankful for your help, even when we cannot solve it. What would you advice me to do?
[19:57] <TJ-> one thing we haven't done is look at the libvirtd log
[19:57] <wdop_> ok
[19:57] <TJ-> show us " journalctl -u libvirtd -n 500 | nc termbin.com 9999 "
[19:58] <TJ-> I notice here it reports some dnsmasq DHCP actions
[19:58] <wdop_> https://termbin.com/9wwu
[19:59] <TJ-> aha! "DHCP packet received on virbr0 which has no address"
[19:59] <TJ-> so, either libvirt isn't adding the address, or something is removing it whwn libvirt does
[20:00] <TJ-> lets try it manually to begin with, from the options we saw earlier
[20:00] <TJ-> " sudo ip addr add <IP_ADDRESS>/24 dev virbr0 "
[20:00] <TJ-> then ensure it 'stuck' with "ip addr show dev virbr0 "
[20:01] <wdop_> ip addr show dev virbr0
[20:01] <wdop_> 5: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
[20:01] <wdop_>     link/ether 52:54:00:42:3a:34 brd ff:ff:ff:ff:ff:ff
[20:01] <wdop_>     inet <IP_ADDRESS>/24 scope global virbr0
[20:01] <wdop_>        valid_lft forever preferred_lft forever
[20:01] <wdop_>     inet6 fe80::5054:ff:fe42:3a34/64 scope link
[20:01] <wdop_>        valid_lft forever preferred_lft forever
[20:01] <TJ-> good, now poke the guest see if it'll get an address
[20:01] <wdop_> yeah!!!!
[20:01] <TJ-> the libvirt 'default' network config you showed earlier says it should be setting that address
[20:02] <TJ-> https://pastebin.com/VasyuLs4
[20:02] <TJ-> so either that had a glitch, or something else is removing the address when it is added
[20:03] <wdop_> just reboot and see if it is permanently fixed?
[20:03] <TJ-> last time it worked: "Okt 03 21:23:59 nador dnsmasq-dhcp[1946]: DHCPACK(virbr0) <IP_ADDRESS> 52:54:00:e2:cb:27 franks"
[20:03] <wdop_> ok
[20:04] <TJ-> reboot should never be needed on Linux, just stop/start the correct services
[20:04] <TJ-> so, lets manually clean up and stop things then start them again
[20:04] <wdop_> yes I know ;) it has always been "networking" but this is gone in 21.04, no?
[20:04] <TJ-> 1. Shutdown the guest  2. on host "sudo systemctl stop libvirtd"
[20:05] <TJ-> 3. check if virbr0 has gone "ip link show dev virbr0"
[20:06] <wdop_> 1. DONE 2. sudo systemctl stop libvirtd
[20:06] <wdop_> Warning: Stopping libvirtd.service, but it can still be activated by:
[20:06] <wdop_>   libvirtd-admin.socket
[20:06] <wdop_>   libvirtd-ro.socket
[20:06] <wdop_>   libvirtd.socket
[20:06] <wdop_> ip link show dev virbr0
[20:06] <wdop_> 5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
[20:06] <wdop_>     link/ether 52:54:00:42:3a:34 brd ff:ff:ff:ff:ff:ff
[20:07] <TJ-> hmm
[20:07] <TJ-> make sure the service stopped "systemctl status libvirtd"
[20:07] <wdop_> Start it manually?
[20:08] <TJ-> we want virbr0 to disappear
[20:08] <wdop_> ● libvirtd.service - Virtualization daemon
[20:08] <wdop_>      Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
[20:08] <wdop_>      Active: inactive (dead) since Mon 2021-10-04 22:06:07 CEST; 1min 54s ago
[20:08] <TJ-> good, dead
[20:08] <TJ-> let's manually remove the interface: "sudo ip link del dev virbr0"
[20:09] <wdop_> DONE
[20:09] <TJ-> check if has gone "ip link show dev virbr0"
[20:09] <wdop_> Device "virbr0" does not exist.
[20:09] <TJ-> great
[20:09] <TJ->  "systemctl start libvirtd" and then "ip link show dev virbr0; ip addr show dev virbr0"
[20:11] <wdop_> systemctl start libvirtd
[20:11] <wdop_> efemha@nador:~$ ip link show dev virbr0; ip addr show dev virbr0
[20:11] <wdop_> Device "virbr0" does not exist.
[20:11] <wdop_> Device "virbr0" does not exist.
[20:11] <TJ-> it's not re-adding it is it?
[20:11] <TJ-> I'm doing the same ops here
[20:12] <wdop_> sudo systemctl status libvirtd
[20:12] <wdop_> ● libvirtd.service - Virtualization daemon
[20:12] <wdop_>      Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
[20:12] <wdop_>      Active: active (running) since Mon 2021-10-04 22:10:39 CEST; 1min 24s ago
[20:13] <wdop_> ip link show dev virbr0; ip addr show dev virbr0
[20:13] <wdop_> Device "virbr0" does not exist.
[20:13] <wdop_> Device "virbr0" does not exist.
[20:13] <TJ-> ok do "virsh net-start default" and that should do it
[20:13] <wdop_> Network default started
[20:13] <TJ-> check it has an IP address
[20:13] <wdop_> ip link show dev virbr0; ip addr show dev virbr0
[20:13] <wdop_> 57: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
[20:13] <wdop_>     link/ether 52:54:00:42:3a:34 brd ff:ff:ff:ff:ff:ff
[20:13] <wdop_> 57: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
[20:13] <wdop_>     link/ether 52:54:00:42:3a:34 brd ff:ff:ff:ff:ff:ff
[20:13] <wdop_>     inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global virbr0
[20:13] <wdop_>        valid_lft forever preferred_lft forever
[20:13] <shibboleth> wdop_, also: i highly recommend apt-get install virt-manager
[20:13] <TJ-> yes!
[20:14] <TJ-> wdop_: so, that seems to have solved it. Make sure the 'default' libvirt network is set to autostart. "virsh net-autostart default"
[20:15] <wdop_> virsh net-autostart default
[20:15] <wdop_> Network default marked as autostarted
[20:15] <wdop_> ok
[20:15] <wdop_> start the guest?
[20:16] <TJ-> so, from now on we know the key is that the bridge must have the IP address set
[20:16] <TJ-> Yes
[20:16] <wdop_> ok, it is not everything 100% clear to me but I will go through it again.
[20:17] <TJ-> I'm not clear why libvirt didn't add the address to the bridge, but that was the cause
[20:17] <shibboleth> wdop_, install virt-manager on your client and you'll have a local gui to administer this on the server/host through ssh
[20:17] <TJ-> shibboleth: please don't interfere; you lack context
[20:18] <wdop_> @shibboleth I have it already installed.
[20:18] <shibboleth> or, read up on ifupdown, bridges, vlans, and... woldermort/netplan :P
[20:18] <shibboleth> TJ-, 10-4
[20:19] <TJ-> shibboleth: we use virsh since it is precise in giving commands and seeing output via pastebins
[20:19] <shibboleth> sure
[20:19] <shibboleth> 10-4: police code/rtx for received and understood
[20:19] <wdop_> @TJ so rebooting the host should not change anything ?
[20:20] <TJ-> wdop_: in theory, it should remain good (libvirt/default network)
[20:21] <TJ-> wdop_: good to know we fixed your issues faster than Facebook are fixing theirs :D
[20:21] <wdop_> OK, I will do the restart shortly. How can I thank you / tipp you. Are you paid fior this service you are giving.
[20:22] <wdop_> ?
[20:22] <TJ-> no, it's community support (and education)
[20:24] <wdop_> I want to give something back, but don't know how. This is the least I can do. I am so thankful!
[20:28] <TJ-> pay forward; give your expertise in whatever areas you're good at to others
[20:32] <wdop_> @TJ-, Yes, will do. These experiences strengthen altruism.
[20:33] <wdop_> @TJ-, I will now reboot... and pray ;)
[20:34] <TJ-> wdop_: :D
[20:35] <wdop_> @TJ-, Bye. It was a pleasure having you as someone getting me out of this mess!


[04:42] <mup> Bug #1437280 changed: maas 1.8.0alpha7 two machines have same ip address <openstack> <uosci> <juju-core:Invalid> <MAAS:Expired> <https://launchpad.net/bugs/1437280>
[13:40] <kiko> hey there
[13:40] <kiko> sto: could you vote me up? :)
[13:40] <kiko> http://askubuntu.com/questions/646278/how-to-ask-curtin-to-use-gpt-instead-of-mbr-with-maas/646839#646839
[14:04] <rbasak> kiko: here, have an upvote :)
[18:14] <kiko> thanks rba
[18:14] <kiko> thanks rbasak
[18:41] <mup> Bug #1474083 opened: Node disappeared after upgrade from 1.5 to 1.7 <MAAS:New> <https://launchpad.net/bugs/1474083>
[19:17] <mup> Bug #1474083 changed: Node disappeared after upgrade from 1.5 to 1.7 <MAAS:Invalid> <https://launchpad.net/bugs/1474083>
[19:29] <mup> Bug #1474083 opened: Node disappeared after upgrade from 1.5 to 1.7 <MAAS:Invalid> <https://launchpad.net/bugs/1474083>
[19:32] <mup> Bug #1474083 changed: Node disappeared after upgrade from 1.5 to 1.7 <MAAS:Invalid> <https://launchpad.net/bugs/1474083>
[20:05] <evilrob> so I've got a datacenter with several systems booting off PXE boot through dnsmasq.  I'm wanting to deploy openstack using canonnical's autopilot which uses maas.  How can I segregate maas and dnsmasq for netbooting in the same environment?
[20:50] <wolverineav> so I've seen this behaviour periodically - if I leave the maas environment running over the weekend and then try to add a new node or release an existing, I run into this error of 'too many files open' : http://paste.ubuntu.com/11874322/
[20:51] <wolverineav> there is an existing bug which is currently in fix-commited state, but I thought I should mention this so it helps in the fix.
[22:20] <kiko> evilrob, I think you need to set up a separate VLAN; you can't have more than one DHCP listener on a segment
[22:20] <kiko> wolverineav, this is a problem that has affected OIL at canonical; jhobbs is the one who is tracking it
[22:20] <evilrob> kiko: that's what I'm thinking I'll have to do.
[22:23] <evilrob> all of our production boxen have 2 interfaces.  I may just make dnsmasq only listen on the first
[22:56] <CTWill> So I build a MAAS server and it does not seem to want to boot the pxe image on any of my clients
[22:57] <CTWill> after much google'ing I am here and stuck
[22:59] <CTWill> does anyone have some MAAS foo they can share?
[23:12] <wolverineav> kiko: thanks for the info!


[00:04] <LjL> teadict always makes me smile =)
[01:23] <arand> Hello, I suggested a !bootinfoscript (& alais !bootinfo) a while ago, would it be possible to add that one or was it not added for a particular reason?
[01:29] <Jordan_U> +1 from me for having a boot info script factoid. I know I would use it often.
[01:47] <IdleOne> !bootinfoscript is <reply> To diagnose boot issues, you can use the Boot Info Script available from http://sourceforge.net/projects/bootinfoscript/ Run the script with !sudo and then look at RESULTS.txt (or !pastebin it for others to look at).
[01:47] <IdleOne> arand: good?
[01:47] <arand> IdleOne: Excellent! :)
[01:49] <arand> Add !bootinfo is <alias> !bootinfoscript as well?
[01:51] <IdleOne> !bootinfo is <alias> !bootinfoscript
[01:51] <IdleOne> !bootinfoscript
[01:51] <IdleOne> !bootinfo is <alias> !bootinfoscript
[01:52] <IdleOne> !bootinfo
[01:52] <IdleOne> hmm
[01:52] <IdleOne> !bootinfo is <alias> !bootinfoscript
[01:52] <IdleOne> !bootinfo is <alias> bootinfoscript
[01:52] <IdleOne> !bootinfo
[01:53] <IdleOne> there we go
[01:54] <arand> Thanks!
[01:54] <IdleOne> thank you.
[01:56] <IdleOne> Jordan_U: you should be capable of adding factoids also
[01:57] <Jordan_U> IdleOne: I am, just wanted agreement from at least one other person :)
[01:57] <IdleOne> ah ok
[01:57] <IdleOne> next time I will just +1 and let you do it :)
[01:58] <Jordan_U> This time particularly as I probably ask people to use boot info script a *lot* more than anyone else, so I wanted to be sure it was more generally useful.
[04:35] <Omega> spammer in #ubuntu
[04:35] <Corey> Floodbot is busted?
[04:36] <Omega> Well, there were multiple spammers.
[04:36] <Omega> (multiple nicks atleast)
[04:38] <Corey> Looks like it's an emergency mode issue.
[04:42] <IdleOne> Corey: why would lorez be allowed to curse and not you :P
[04:42] <IdleOne> also don't think I won't remove either of you just cuz your staff :P
[04:44] <IdleOne> you're*
[04:44] <IdleOne> heh
[04:49] <Corey> IdleOne: Hey, you can remove him if you'd like.  Frankly he scares the hell out of me, so... :-)
[04:49] <IdleOne> haha
[04:49] <IdleOne> I need a reason to remove.
[04:53] <Corey> Nah, LoRez is good people.
[04:53] <IdleOne> he is a little to brusque sometimes
[04:54] <Omega> (Can I squeeze a few words in?)
[04:54] <Omega> May I even.
[04:55] <Omega> I don't know either party, but I think it's best if you tell him that he is a little too brusque sometimes, so he knows what he should work on.
[04:55] <IdleOne> hahahah I removed lorez
[04:59] <IdleOne> I don't think he appreciates my humour :/
[08:48] <oCean> good morning
[08:48] <oCean> please notice <k|oWn> in #ubuntu
[08:50] <oCean> also andyland suggesting the rm command (if you're stupid enough to try it. you get what you deserve)
[10:37]  * ikonia wakes
[10:57]  * jussi waves in ikonia's direction
[11:02]  * Tm_T surfs in shallow water
[12:25] <bazhang_> Omega, was there anything else we could help you with?
[13:31] <ikonia> Omega: ping
[13:54] <bazhang_> bilal is cdbs right?
[13:54] <Pici> Yes.
[14:01] <Pici> lars_t_h isn't larstorben btw.
[14:01] <bazhang_> right
[14:01] <bazhang_> laaaaaa at last check
[14:19] <bazhang_> icecat? isn't that the debain one?
[14:56] <bazhang_> what is pentaho
[14:57] <Pici> I could be mistaken, but I thought it was some DTS engine for doing exports from databases and things
[14:57] <bazhang_> libpentaho-reporting-flow-engine-java-openoffice.org is the only thing I found
[14:58] <bazhang_> * [Blockcold] (~jack@<IP_ADDRESS>): Jack    <-- bet thats jungli
[14:58] <Pici> hrm
[15:02] <bazhang_> so cedric_ is saying that he really does not like unity, it seems
[15:21] <ikonia> bazhang_: it is
[15:21] <Pici> which is?
[15:21] <ikonia> as long as he keeps out of ubuntu he can do what he wants
[15:21] <Pici> oh, him
[15:21] <ikonia> blockcold/jungli
[15:28] <jussi> Pici: who was that?
[15:28] <Pici> jussi: larstorben
[15:28] <jussi> oh.
[15:28] <ikonia> I wish he'd play elsewhere
[15:29] <Pici> Me too
[15:31] <ikonia> not quite sure what he gets out of it
[15:32] <bazhang_> still in #ubuntu
[15:32] <ikonia> where ?
[15:33] <Pici> bazhang_: hes muted. See -ops-monitor
[15:33] <bazhang_> Pici, okay, my mistake
[15:35] <ikonia> Pici: you ubuntard helping him !
[15:35] <ikonia> help from the very thing he mocks
[15:38] <LjL> what do you all think about the floodbots being all opped? scary, less mode spam, too much spam, quicker response, useless?
[15:39] <ikonia> not noticed much difference to the idle eye to be honest
[15:40] <genii-around> LjL: It makes me feel like bowing to my floodbot overlords
[15:40] <LjL> if there is a difference, it's subtle, ideally they should ban/mute spammers after one line instead of after several, by virtue of the fact that each bot sets the mode on its own server
[15:41] <genii-around> The thing i noticed most actually is that now they don't have an +o barrage of spam
[15:41] <LjL> that should be an advantage, yeah
[15:49] <Pici> ikonia: Honestly, I didbn't even notice that he was the one asking the question.  I thought it was some other user without a clue.
[15:53] <ikonia> Pici: I'm only teasing
[15:53] <ikonia> Pici: about two line up he called #ubuntu ubuntards for "stealing" his cloak
[15:53] <ikonia> hence my comment to you, just joking
[15:53] <Pici> ikonia: yep )
[15:54] <ikonia> I love the pushing of responsibility "#ubuntu took my cloak" - rather than, I behaved like a fool so freenode took it
[16:11] <Da|Mummy> why cant i send msg to #ubuntu?
[16:11] <Da|Mummy> i have a question, but it wont let me ask
[16:12] <ikonia> hi there Da|Mummy
[16:13] <ikonia> one moment and we'll look into it for you
[16:13] <Da|Mummy> thanks
[16:14] <ikonia> Da|Mummy: it appears to be because you pust swastickers into the channel
[16:15] <Da|Mummy> bah
[16:15] <Da|Mummy> i cant deny that :{ i was toying around with unicode :|
[16:15] <ikonia> any reason you randomly did that ?
[16:15] <ikonia> ok, so if I remove the mute, can you please keep it a bit more under control ?
[16:16] <Da|Mummy> of course
[16:16] <Da|Mummy> sorry about that
[16:16] <ikonia> give me a minute please
[16:16] <ikonia> Da|Mummy: try it now
[16:16] <Da|Mummy> thank you
[16:17] <ikonia> Da|Mummy: no problem, happy to help
[16:18] <jussi> I wish they were all that easy
[16:18] <ikonia> hello totem
[16:18] <totem> oh hi, wrong channel
[16:19] <ikonia> no problem
[17:01] <Pici> IdleOne: tneva82 has been told a few times to stay on-topic
[17:01] <IdleOne> ok
[17:03] <IdleOne> looks like we got a troll in the making
[17:05] <IdleOne> @mark #ubuntu tneva82 warned about off topic. possibly running unsupported version of ubuntu. appears to want to waste time and complain.
[17:12] <IdleOne> any reason to allow tneva82 to continue ranting? He has made it clear he plans on installing an unsupported version.
[17:13] <Pici> no reason.
[17:13] <popey> Ender_nothome isnt helping here
[20:12] <LjL> hmm is maroccain ban evading again?
[20:15] <IdleOne> where?
[20:15] <LjL> h4x0rs in #ubuntu
[20:19] <IdleOne> FloodBot2 sets mode: +zq h4x0rs!*@*
[20:19] <IdleOne> don't see anything else
[20:19] <LjL> he's maroccain, and i think he's banned
[20:19] <IdleOne> can't find anything for that nick
[20:20] <IdleOne> you sure?
[20:20] <IdleOne> if he isn't breaking any rules right now...
[20:20] <LjL> no, that's why i said "i think" :P but i thought someone (ikonia?) yesterday was complaining that he was ban evading
[20:21] <LjL> http://ubottu.com/bans.cgi?channel=&operator=&query=h4x0r&kicks=on&bans=on&oldbans=on&mutes=on&oldmutes=on&floodbots=on gives "please don't evade bans, join #ubuntu-ops if you want to seriously discuss your ban"
[20:23] <IdleOne> you want to handle it if he shows up?
[20:24] <LjL> IdleOne: tbh it's not clear to me what the original ban that ikonia was acting on *was*, i'm with you in not being able to find it. i do know this guy is pretty obnoxious in general, though
[20:24] <IdleOne> well, we can leave it to ikonia in that case :)
[20:24] <IdleOne> I suspect he will be back with a different nick soon if not already
[20:38] <LjL> well flood is maybe excessive innit
[21:09] <LjL> onjoin spam?
[21:09] <Pici> yeah.
[21:09] <Pici> 16:06:28 <?guuqjw> free games www.pregames.info
[21:30] <Flannel> mang0 is not abusive.  Has also not been muted.
[21:31] <LjL> yeah i don't get it. that he wasn't abusive, well, that's bad if the bot triggers on something like that, but i guess it's possible... but i have no idea how it would give that message and not actually mute
[21:31] <Flannel> I'm more worried about the false positive than the broken muting :)
[21:32] <LjL> oh i know why there was no mute - webchat user
[21:32] <LjL> you're right about the false positive
[21:33] <LjL> uhm, it was lagging it seems. changing it so that it bans even while in emergency mode (a change i just did) was probably not such a good idea.
[21:33] <LjL> i guess there was a valid reason why i initially did it the other way, even though it favors spammers :P
[22:00]  * genii-around makes a pot of coffee for the crew before leaving
[23:18] <LjL> hell no
[23:18] <LjL> !ops
[23:21] <Andy_C> hi, i copied and pasted some output from terminal into #ubuntu and was blocked by the floodbot
[23:21] <LjL> Andy_C: yeah, fixed. sorry
[23:21] <elky> Andy_C, you should use pastebin in the future though
[23:21] <elky> !paste
[23:21] <Andy_C> i will
[23:24] <LjL> christ i messed this up horribly
[23:24] <Andy_C> did my post go through?
[23:24] <Andy_C> or was it completely blocked?
[23:24] <LjL> Andy_C: no
[23:24] <Andy_C> okay thanks
[23:26] <LjL> Andy_C: in case you don't know, you can probably hit your up-arrow to post it again
[23:26] <Flannel> Unmuted shmup_ and sent him a query explaining.
[23:26] <LjL> i'm opped as floodbot (that's probably obvious), will put the bots back after fixing them
[23:27] <LjL> hope pirates don't assault right now
[23:27] <Flannel> That's what we have operators for.
[23:28] <Andy_C> LjL: I am using pidgin, the up arrow doesn't seem to work
[23:28] <Andy_C> also, i am still getting a response of 'Cannot send to channel' after each post
[23:28] <LjL> are you?
[23:28] <LjL> maybe i unmuted you incorrectly
[23:28] <LjL> a moment
[23:28] <Flannel> Yeah
[23:28] <Flannel> LjL: You -b not -q
[23:28] <LjL> yeah thanks
[23:28] <LjL> Andy_C: try now please
[23:29] <Flannel> Andy_C: got that one
[23:29] <Andy_C> muchas gracias (it is after all cinco de mayo)
[23:29] <LjL> :)
[23:29] <LjL> sorry again