[00:36] <Scunizi> I'm revamping an old laptop ridding it of Win XP that has failed.. Installed xubuntu and I'm trying to activate the Nvidia 173 legacy drivers via the GUI.. No dice. After hitting apply and waiting a few secs, it reverts. no download or install. how do I fix this behavoir?
[00:38] <Troller> Anyone knows a channel I can get help with a virus?
[00:39] <Scunizi> on a linux machine?
[00:40] <Troller> im on linux now so Im immune to it but I want to learn about it because I use windows at my school
[00:40] <Troller> and most comptuers there are infected
[00:41] <GeekDude> "so Im immune" Not completely true, just immune to windows and mac infections
[00:41] <GeekDude> If you want help with an infection on a windows machine, you should probably ask a windows support channel
[00:41] <Scunizi> check the #ubuntu channell for building a live cd/usb with virus check on it.  You'll have to boot a machine to the live environment, run the virus check on the windows drive and let it do it's magic.  You could probably Google this info as well on how to create it with a normal live Ubuntu environment.
[00:41] <Troller> all right, thanks
[00:42] <GeekDude> I rather like malwarebytes (chameleon if necessary)
[02:17] <xubuntu981> hello
[02:17] <xubuntu981> i have a question
[02:17] <xubuntu981> anybody here?
[02:18] <xubuntu981> please i really need help
[02:22] <GeekDude> Hi
[02:22] <xubuntu981> hi
[02:22] <bazhang> ask a question
[02:22] <GeekDude> I'd help but I have to sleep. Best of luck!
[02:22] <xubuntu981> ok so i'm trying to install xubuntu on my laptop
[02:22] <xubuntu981> installation works fine
[02:23] <xubuntu981> but when it comes to booting, no bootable device is found
[02:25] <xubuntu981> what can i do about it?
[02:28] <xubuntu981> that's my main pc
[02:29] <xubuntu981_> hi
[02:30] <xubuntu981_> oh you're back
[02:33] <xubuntu981_> please tell me :((
[05:18] <xubuntu73i> this is amazing
[05:18] <xubuntu73i> whoa!
[05:24] <mtyamantau> Hey peeps. What is the proper way to script a particular program in a specific workspace on Xfwm4? I've tried looking online, and all I can find is wmctrl, which I am not satisfied with
[05:24] <mtyamantau> Seems hacky
[05:25] <mtyamantau> *script to open a particular program
[06:33] <RavinduL> Hi! How would I add a launcher that runs the command `thunar "~/Documents"` into the Xubuntu applications view? I created a launcher on the desktop with that command and it worked perfectly, but when I moved it to the ~/.local/share/applications/ directory it gave me error "Error when getting information for file '/home/username/~/Documents': No such file or directory."
[06:34] <RavinduL> Oh wait I just fixed it.
[06:35] <RavinduL> Changed the path of the .desktop file to ~ and changed the exec to `thunar "Documents"`
[06:35] <RavinduL> Yay
[08:23] <GrandCouillon> Hello guys, I am under 15.10 and after the installation of "codeblocks" from standard repo I can't start it : "codeblocks: relocation error: /usr/lib/libcodeblocks.so.0: symbol _ZThn776_N17wxGenericListCtrl31GetSizeAvailableForScrollTargetERK6wxSize, version WXU_3.0 not defined in file libwx_gtk2u_core-3.0.so.0 with link time reference". I have made lots of "cleaning" without success. Does anyone have an idea ?
[08:26] <cfhowlett> GrandCouillon, more eyes in #ubuntu.  ask there.
[08:26] <GrandCouillon> cfhowlett, Ok, thanks
[10:34] <xubuntu15w> hello
[10:34] <xubuntu15w> good day
[10:35] <xubuntu15w> just want to ask
[10:36] <xubuntu15w> does anybody here experiencing a shutdown issue after upgrading to wily werewolf
[10:43] <franco_> hello just want to ask how to resolve a shutdown issue, shutdown becomes reboot after upgrade to wily werewolf
[11:45] <xubuntu681> hi
[11:45] <xubuntu681> can anybody help me?
[11:52] <Meerkat> xubuntu681, please write your question and we'll see what we can do
[11:56] <xubuntu681> okay so i am currently trying to install xubuntu on my laptop
[11:56] <xubuntu681> the installation works fine, but when i try to boot, there's no bootable device
[11:57] <bazhang> the installation was not fine then
[11:57] <Meerkat> xubuntu681, did you manually partition the disk or did you let Xubuntu do that?
[11:58] <xubuntu681> i let xubuntu do that
[11:58] <bazhang> first, md5 the iso, use an appropriate tool to burn the iso to usb
[11:58] <xubuntu681> @bazhang i used uNetbootin
[11:59] <bazhang> md5 the iso first
[11:59] <xubuntu681> how do i do that?
[11:59] <bazhang> !md5
[11:59] <bazhang> see above
[12:00] <xubuntu681> on my main computer is windows running
[12:00] <xubuntu681> oh
[12:00] <xubuntu681> now i see ^^
[12:08] <xubuntu681> wow
[12:08] <xubuntu681> i even fail to navigate to another hard drive
[12:10] <xubuntu681> okay
[12:10] <xubuntu681> it says md5sum: WARNING: 334 of 334 listed files could not be read
[12:10] <Spass> AFAIK unetbootin installs boot loader on a pendrive instead on your drive
[12:11] <xubuntu681> umm i tried to install using an usb stick
[12:11] <Spass> you must manually choose right device on this screen http://i.stack.imgur.com/5JkQX.png
[12:11] <Spass> yep, i've recently had same issue
[12:11] <Spass> with unetbootin
[12:11] <xubuntu681> so what do i have to do exactly?
[12:12] <Spass> well, i don't know any other way than reinstall
[12:12] <Spass> maybe someone knows how to install a boot loader from livecd?
[12:13] <xubuntu681> i dont have a cd drive in the laptop
[12:13] <Spass> there's no need
[12:13] <xubuntu681> oh thats what you mean now i understand it
[12:14] <xubuntu681> ok so the problem is not the installation but the boot? does it even copy the files to the hard drive??
[12:14] <Spass> i think your installation is ok, but you don't have boot loader installed on the right drive
[12:15] <Spass> unetbootin installed it on the pendrive... that's my guess
[12:15] <xubuntu681> what's pendrive?
[12:15] <xubuntu681> the usb stick?
[12:15] <Spass> yes, usb stick
[12:15] <xubuntu681> hmm
[12:16] <xubuntu681> how do i fix this?
[12:16] <Spass> unless you find a way to install boot loader from livecd (or someone here knows how to do it) try to reinstall
[12:16] <xubuntu681> i did
[12:16] <xubuntu681> 4 times or so
[12:17] <Spass> using the same usb stick, but choose to manually partition your drive
[12:17] <xubuntu681> i even tried using debian
[12:17] <xubuntu681> okay
[12:17] <Spass> and choose right device for a boot loader
[12:18] <Spass> drop list under "Device for boot loader installation:" http://i.stack.imgur.com/5JkQX.png
[12:18] <Spass> or... try to install boot loader from live cd
[12:18] <Spass> live usb ;)
[12:19] <Spass> but i don't know how, but google knows i suppose
[12:19] <xubuntu681> you mean start the live OS and then use the link on the desktop to install? i did that
[12:19] <xubuntu681> didn't work aswell
[12:20] <Spass> start live cd and use command line (terminal) to install grub on your drive
[12:20] <Spass> with no need to reinstall then
[12:20] <xubuntu681> ok wait a second i start the live device now
[12:21] <xubuntu681> ok good
[12:21] <xubuntu681> i'm in the terminal
[12:21] <Spass> but like i said, i'm a casual user and i don't know the correct command to do that :)
[12:22] <Spass> i'm googling it
[12:22] <xubuntu681> ok
[12:27] <Spass> sudo blkid
[12:28] <Spass> to find out what drives/partitions you have
[12:28] <xubuntu681> i see
[12:28] <xubuntu681> there
[12:28] <xubuntu681> 's sda1-sda3
[12:28] <Spass> btw, i'm basing in this HowTo https://help.ubuntu.com/community/Grub2/Installing
[12:28] <Spass> "via the LiveCD terminal" part
[12:29] <Spass> *basing on this
[12:30] <Spass> sda3 is swap i suppose, what are sda1 and sda2 in your case?
[12:31] <xubuntu681> sda1: UUID="C838-7D50" TYPE="vfat"
[12:31] <xubuntu681> sda2: Type ext4
[12:32] <Spass> you have windows on sda1 right?
[12:32] <xubuntu681> no
[12:32] <xubuntu681> i dont
[12:32] <xubuntu681> the computer has absolutely no OS
[12:33] <xubuntu681> oh and there's /dev/loop0: TYPE="squashfs"
[12:36] <Spass> well i think it will be easier to just reinstall then :D
[12:36] <Spass> from the shortcut on live cd
[12:37] <Spass> but this time partition your drive manually
[12:41] <Spass> i blame unetbootin for your problems
[12:41] <cfhowlett> strangely enough, unetbootin creates a very different USB than the default ubuntu startupUSBCreator
[12:42] <xubuntu681> okay
[12:42] <Spass> when you create your livecd on windows, consider Win32 Disk Imager, i think it;s much better for liveusb
[12:42] <xubuntu681> i did use it but the stick was not bootable then
[12:42] <xubuntu681> umm should i format the hard drive before reinstalling?
[12:42] <Spass> strange, i never had problems with it
[12:43] <Spass> if you don't have anything important on this drive then yes
[12:43] <xubuntu681> ok good
[12:43] <xubuntu681> as i said the pc is brand new there isn't anything on it
[12:43] <Spass> choose sda for your boot loader device
[12:44] <Spass> on the bottom of the partitioning screen
[12:45] <xubuntu681> 1 second...
[12:46] <xubuntu681> good so there's only one device for the bootloader installation
[12:46] <xubuntu681> and in the upper window there's /dev/dsa and unused storage
[12:47] <xubuntu681> */dev/sda
[12:47] <xubuntu681> which one should i select?
[12:49] <Spass> if you want to use whole drive on linux first i suggest to delete all existing partitions
[12:49] <Spass> and then create 2 main partions on 'unused starage'
[12:49] <xubuntu681> there is only /dev/sda with no memory size and free disk space
[12:50] <Spass> create primary sda1 ext4 for whole system (/) and sda2 as a swap
[12:50] <xubuntu681> how big should those patitions be each?
[12:51] <Spass> how big is your drive? how much ram do you have on this computer?
[12:51] <xubuntu681> 500 107 MB
[12:52] <xubuntu681> 4 GB
[12:54] <Spass> first you should consider one thing - do you need two separate partitions for system files (/) and you user files (/home)
[12:54] <Spass> when you have it separate it can help you in the future when you will want to install other linux distribution
[12:55] <Spass> or... when you just want to install it "windows style" create one big partition
[12:55] <Spass> I personally have all files on one partition
[12:56] <xubuntu681> okay and which file system does it have to be?
[12:56] <cfhowlett> default = ext4
[12:56] <Spass> ext4 is default
[12:56] <Spass> yes
[12:57] <xubuntu681> what about the option below? (don't know how it's called in english) where i can select "/", "/home", "/tmp" etc.
[12:57] <Spass> "/" for whole system on one partition
[12:57] <Spass> default
[12:58] <xubuntu681> well default is empty
[12:58] <Spass> select "/"
[12:58] <xubuntu681> ok
[12:59] <Spass> and swap should be couple of GB i think, maybe 5GB? i don't know today trends
[12:59] <xubuntu681> now there's "/dev/sda" with no space, then 1MB of empty space, then "/dev/sda1", and then another MB
[13:01] <Spass> resize sda1 ext4, you should free some space for swap partition
[13:01] <Meerkat> you dont really need swap these days?
[13:02] <Spass> you don't?
[13:02] <Meerkat> the kernel will kill programs if the computer runs out of RAM. The swap will only make the last few minutes really slow until that runs out too.
[13:03] <Spass> oh, ok
[13:03] <Spass> and how about hibernate function on laptops?
[13:03] <xubuntu681> umm now there's two options for the bootloader installation
[13:04] <Spass> "/dev/sda"
[13:04] <Meerkat> Spass, you'll need the amount of RAM you have on the computer for that. But I haven't run into a situation where those features actually work on Ubuntu.
[13:04] <xubuntu681> okay good
[13:04] <xubuntu681> should i install now?
[13:05] <Spass> go for it :) let's see how it goes
[13:05] <xubuntu681> does it matter which drive i select in the upper windows?
[13:05] <xubuntu681> window*?
[13:05] <xubuntu681> like /dev/sda1?
[13:06] <Spass> what do you mean select? highlight?
[13:06] <xubuntu681> yes
[13:07] <Spass> no, i don't think that's important at this point
[13:07] <xubuntu681> okay
[13:07] <xubuntu681> ok now theres a message
[13:08] <Spass> Meerkat, ok, so i remembered it correctly
[13:10] <xubuntu681> "the partition table format in use on your disks normally requires you to create a separate partition for boot loader code. this partition should be marked as use as an 'EFI boot partition' and should be at least 35 MB in size. Note that this is not the same as a partition moundted on /boot. If you do not go back to the partitioning menu and correct this error, boot loader installation may fail later, although it may still be pos
[13:10] <xubuntu681> a partition."
[13:11] <Spass> looks like you have to create 3 partitions on your system
[13:12] <xubuntu681> so...?
[13:17] <Spass> you could try to: delete all partitions, create sda1 100MB marked as an 'EFI boot partition', sda2 495GB ext4 for "/" and sda3 5GB for swap
[13:17] <Spass> and install boot loader on "/dev/sda1"
[13:18] <xubuntu681> 100 MB?
[13:18] <Spass> but i'm just guessing at this point, i've never before encountered 'EFI'
[13:18] <Spass> yes 100 MB
[13:19] <Spass> it's just for boot loader code
[13:19] <Spass> like in this messege above you pasted
[13:20] <Spass> *message
[13:21] <xubuntu681> okay now there's the partitions and in the bottom i can choose the device for the bootloader installation
[13:21] <xubuntu681> which one should i choose there?
[13:25] <Spass> you marked (somewhere) this 100mb partition as EFI boot partition
[13:25] <xubuntu681> yes
[13:25] <xubuntu681> sda1
[13:25] <Spass> choose "/dev/sda1"
[13:25] <Spass> if possible
[13:25] <xubuntu681> okay
[13:25] <xubuntu681> continue?
[13:25] <xubuntu681> and hope?
[13:26] <Spass> yes :)
[13:26] <Spass> no strange message = good news
[13:27] <xubuntu681> data is copying
[13:31] <Spass> what version are you installing? just curious
[13:33] <xubuntu681> you mean distribution?
[13:34] <Spass> yes, and version
[13:34] <Spass> 15.10?
[13:34] <xubuntu681> i guess the latest one
[13:35] <xubuntu681> oh no it's 14.04
[13:36] <cfhowlett> still supported
[13:37] <xubuntu681> well i will probably update as soon as everything is running smoothely
[13:37] <Spass> 14.04 is a good option for start
[13:38] <Spass> it is stable and have long time support (LTS)
[13:38] <xubuntu681> hm well i actually need the computer for university only so it's not that big of a deal as long as the terminal works fine
[13:38] <cfhowlett> xubuntu681, 14.04 is long term support.  if you really NEED the lastest shiny stuff, OK, but otherwise you might find LTS the sanest option
[13:39] <xubuntu681> ok that's good then
[13:39] <Spass> yes i agree, you should stick with lts versions for stability
[13:40] <Spass> next LTS will be 16.04 so it will be released around april 2016
[13:40] <Spass> then you should upgrade
[13:40]  * cfhowlett upgrades only on the first LTS point release 14.04.1 > 16.04.1
[13:43] <xubuntu681> okay good i'll do that then
[13:43] <xubuntu681> @spass installation still in progress
[13:44] <Spass> fingers crossed
[13:48] <xubuntu681> ok restart or do i have to do something else?
[13:50] <Spass> nope
[13:50] <xubuntu681> ok wish me luck
[13:52] <xubuntu681> can i pull out the usb stick?
[13:52] <Spass> yes, after the reboot
[13:52] <Meerkat> xubuntu681, if the install is done and you have restarted then you can remove it.
[13:53] <xubuntu681> i'm in the bios to set the boot order
[13:53] <xubuntu681> so can i remove it safely?
[13:53] <Meerkat> yes
[13:53] <Spass> yes
[13:53] <Spass> :)
[13:53] <xubuntu681> good
[13:53] <xubuntu681> no bootable device.
[13:53] <Meerkat> now I have a question. Why does patching have to be so darn difficult?! :/
[13:54] <Spass> you can try to find option called 'legacy boot' in the bios
[13:54] <Meerkat> xubuntu681, what is first in your bios boot order?
[13:54] <Spass> or something like that
[13:55] <xubuntu681> hdd
[13:55] <xubuntu681> should i try legacy boot?
[13:56] <Spass> that could help
[13:56] <xubuntu681> nope
[13:56] <xubuntu681> doesn't
[13:59] <Spass> well, i'm really sorry i couldn't help you, i tried my best
[14:01] <xubuntu681> well, sh*t
[14:02] <Spass> the only possibility i can think right know is to leave legacy boot 'on' for the whole process, and try to reinstall once again, but it could be just a waste of time...
[14:03] <xubuntu681> i already tried that
[14:03] <Spass> install on sda1 ext4 "/" 495gb and sda2 swap 5gb and boot device on "/dev/sda" (not sda1) and ignore strange messages and try to boot on legacy mode
[14:04] <Spass> or try to get in touch with some linux guru lurking on this channel
[14:05] <xubuntu681> how do i know who is a linux guru :D
[14:06] <artag> by their beards and sandals
[14:06] <xubuntu681> xDD
[14:06] <Spass> :)
[14:06] <cfhowlett> NECKbeards ...
[14:08] <artag> btw no offence intended. I have a neckbeard, and a selection of far less attractive descriptions of windows geeks
[14:08] <cfhowlett> :)
[14:09] <artag> tbh though, I think what you really want is a BIOS geek. Not sure how to recognise them.
[14:12] <artag> I have a similar problem myself, where I had a perfectly working ubuntu laptop and tried to make it dual-boot win7 and mint, for largely bogus reasons. I find I'm having to change from UEFI for windows to legacy BIOS for Mint, which shouldn't be necessary
[14:12] <artag> If I ever find I actually want to use the win7 part I mihgt have to try harder to fix that
[14:16] <Unit193> You need to install Xubuntu under secureboot then, don't install in legacy mode.
[14:16] <Unit193> Specifically, the 64bit version.
[14:18] <artag> I'll try it again. Ideally I should do that before there's much stuff to backup
[14:19] <xubuntu681> does anybody have any idea for me?
[14:28] <xubuntu681> please?
[14:31] <krytarik> xubuntu681: I didn't follow the whole thing, but did you read Unit193's message? Also, you can try in #ubuntu for that too.
[14:32] <Unit193> krytarik: I didn't either. :3
[14:32] <krytarik> Heh.
[14:32] <xubuntu681> so i have to uefi boot with secure mode turned ON?
[14:36] <xubuntu681> ?
[14:43] <krytarik> xubuntu681: Doesn't Unit193's message imply that?
[14:45] <xubuntu681> krytarik: yes, english = shit :D
[14:55] <krytarik> xubuntu681: Would you rather #ubuntu-de then?
[14:56] <xubuntu681> krytarik it's fine, but i'm sometimes not sure about commands and stuff you guys write :D
[15:02] <Unit193> krytarik: He's in #ubuntu, all good.
[15:06] <xubuntu681> i'm in #ubuntu-de aswell but they don't seem to answer
[15:09] <krytarik> xubuntu681: Just have a bit patience, it's usually pretty active there.
[15:09] <xubuntu681> ok
[15:12] <williangarcia> Hi , Can i fix my restart option , when I will restart my computer screen just hangs, but when I will shutdown my PC work fine...
[15:12] <williangarcia> how can i fix **
[17:20] <kozukumi> how do i edit the grub menu from xubuntu 15.10?
[17:20] <kozukumi> actually i dont even need it, can i make it just boot to linux now?
[17:23] <kozukumi> is there a gksu for xfce that is built in?
[17:35] <krytarik> kozukumi: "pkexec mousepad /etc/default/grub"
[17:36] <kozukumi> krytarik, thanks but i cant seem to figure out everything from /etc/grub.d/ files
[17:38] <krytarik> kozukumi: Huh, aren't you following like this?: http://askubuntu.com/questions/143500/how-can-i-boot-directly-to-ubuntu-after-removing-windows-from-a-dual-boot
[17:43] <kozukumi> how can i stop it detecting the windows partition when it does an update?
[17:50] <krytarik> kozukumi: "GRUB_DISABLE_OS_PROBER=true" from here: https://help.ubuntu.com/community/Grub2/Setup#Configuring_GRUB_2
[17:50] <kozukumi> awesome, thank you!
[17:50] <krytarik> Sure.
[17:55] <kozukumi> works perfectly, thanks krytarik
[17:55] <krytarik> Alright. :)
[17:58] <kozukumi> it seems to wait a couple of seconds on a "black" screen tho which is a bit odd, im gonna see if i can get grub to just fire up the default instantly
[18:04] <krytarik> kozukumi: I think that's the time it loads the kernel though.
[18:04] <kozukumi> ah ok
[18:04] <kozukumi> strange because if i have it prompt me and i hit enter right away it boots faster
[18:04] <kozukumi> hmmm
[18:07] <kozukumi> is it possible to disable grub and just have it boot right into linux or do i need to use grub to do that?
[18:15] <krytarik> kozukumi: You need some sort of boot loader, yes - and Grub is the default on Ubuntu.
[18:16] <kozukumi> ok cheers
[18:16] <kozukumi> gonna try and get an image on it now lol
[18:30] <kozukumi> right well everything is almost perfect :)
[18:30] <kozukumi> last thing is to work out how to get window edge for resizing a bit bigger
[18:32] <drc> kozukumi: The only way I know (with deep voodoo) is Settings>Window Manager>Theme=Greybird-accessibility
[18:32] <drc> s/with/without
[18:32] <kozukumi> drc yeah
[18:33] <drc> Which make the windows about 3 pixels too big for the way I do thing :(
[18:33] <kozukumi> sucks
[18:33] <kozukumi> i wish i could set it to 5 pixels or something but without fucking up the theme
[18:34] <krytarik> kozukumi: Just work around it :P - http://xubuntu.org/news/window-resizing-in-xubuntu-and-xfce/
[18:34] <kozukumi> yeah i use alt+rightclick
[18:34] <kozukumi> works ok 90% of the time for my needs
[18:34] <kozukumi> bit of a pain when i am just using the mouse
[20:18] <J_EDGAR_HOOVER> Hi
[20:18] <J_EDGAR_HOOVER> Does anyone know what happened with the whole wireless-regdb thing in Xubuntu/ubuntu
[20:18] <J_EDGAR_HOOVER> I'm on 14.04
[20:18] <J_EDGAR_HOOVER> I wanted to make my own regulatory.bin
[20:18] <J_EDGAR_HOOVER> but I have no idea where to put it
[20:19] <J_EDGAR_HOOVER> What does iw reg get/set rely on?
[20:34] <bekks> wireless-regdb? Never heard of it.
[20:35] <ochosi> J_EDGAR_HOOVER: that doesn't sound like it's xubuntu specific
[20:37] <J_EDGAR_HOOVER> It's maybe part of the linux kernel or.. GNU project
[20:37] <J_EDGAR_HOOVER> It seems that Xubuntu must have some specific place where the regulatory domain file is
[20:37] <J_EDGAR_HOOVER> When you type as su ... <iw reg get> you get your domain location
[20:38] <J_EDGAR_HOOVER> if you do <iw reg set NZ> you uncap it a bit.
[20:38] <Unit193> Are you actually asking or is this the same stuff you were going over in ##linux?
[20:38] <J_EDGAR_HOOVER> I'm actually asking.
[20:38] <J_EDGAR_HOOVER> Like I know as much as I just said.. and that in the past you could compile your own regulatory.bin file, then verify it.
[20:39] <J_EDGAR_HOOVER> But now it's like they "obfuscated it" and i'm not sure if that's Xubuntu doing it or the Linux/GNU team
[20:39] <J_EDGAR_HOOVER> They probably don't publish much about it because the more they do, the more people will uncap their NIC's tx power and violate the FCC or applicable government regulation body
[20:39] <J_EDGAR_HOOVER> So I'll just assume that, until I hear anything else.
[20:39] <Unit193> Perhaps see regulatory.bin(5) and /lib/crda/regulatory.bin
[20:40] <J_EDGAR_HOOVER> Oh wow I think it's right there. Thank you so much
[20:40] <J_EDGAR_HOOVER> It could be one I put there, but I think that's the location in Xubuntu :D ty
[20:42] <J_EDGAR_HOOVER> if anyone's interested following this should allow you to make your own replacement regulatory.bin , but keep in mind you munst make another file too to "verify" it. http://null-byte.wonderhowto.com/how-to/set-your-wi-fi-cards-tx-power-higher-than-30-dbm-0149606/
[20:46] <J_EDGAR_HOOVER> How do I untar these kinds of files
[20:46] <J_EDGAR_HOOVER> crda-latest.tar.bz2               wireless-regdb-2015.10.22.tar.xz
[20:46] <J_EDGAR_HOOVER> wireless-regdb-2015.10.22.tar.gz
[20:46] <J_EDGAR_HOOVER> Well other than the bz2
[20:46] <J_EDGAR_HOOVER> im trying tar xvjf
[20:48] <J_EDGAR_HOOVER> nvm ill just open thunar as root
[20:50] <hoodedice> I mapped SuperUser to whisker menu -- it makes it easier to open programs.
[20:51] <hoodedice> The thing is, Mousepad is something I use often, but when I type "Mouse", the selector is on "Mouse and Touchpad"
[20:51] <hoodedice> Is there a way to add an alias to the Mousepad entry in the whisker menu settings so I can type, say, "text" and it will open mousepad?
[20:53] <mrkramps> hoodedice, no and yes
[20:54] <mrkramps> just create a new menu entry
[20:55] <hoodedice> gotcha
[20:55] <hoodedice> thanks
[20:55] <mrkramps> hoodedice, copy /usr/share/applications/mousepad.desktop to ~/.local/share/applications/texteditor.desktop
[20:56] <mrkramps> edit the copy and change name to "Text Editor"
[20:56] <mrkramps> optionally, delete all content from this file not required
[20:57] <hoodedice> okay, I'll try it out
[21:24] <J_EDGAR_HOOVER> Think I did it...
[21:24] <J_EDGAR_HOOVER> root@network:/home/cia/Desktop/WirelessRegNew/crda-1.1.3# make
[21:24] <J_EDGAR_HOOVER>   CHK  /usr/lib/crda/regulatory.bin
[21:24] <J_EDGAR_HOOVER> root@network:/home/cia/Desktop/WirelessRegNew/crda-1.1.3# make install
[21:24] <J_EDGAR_HOOVER>  GZIP crda.8
[21:24] <J_EDGAR_HOOVER>  GZIP regdbdump.8
[21:24] <J_EDGAR_HOOVER>   INSTALL  crda
[21:24] <J_EDGAR_HOOVER>   INSTALL  regdbdump
[21:24] <J_EDGAR_HOOVER>   INSTALL  85-regulatory.rules
[21:24] <J_EDGAR_HOOVER>   INSTALL  crda.8.gz
[21:24] <J_EDGAR_HOOVER>   INSTALL  regdbdump.8.gz
[21:24] <hoodedice> uh
[21:28] <J_EDGAR_HOOVER> Problem is i'm not sure wher eit put the new regulatory.bin
[21:28] <Unit193> !pastebin | J_EDGAR_HOOVER
[21:28] <J_EDGAR_HOOVER> it wants /usr/lib/cdra but in xubuntu its /lib/crda
[21:28] <J_EDGAR_HOOVER> crda*
[21:28] <J_EDGAR_HOOVER> Ok.
[21:28] <J_EDGAR_HOOVER> sorry
[21:30] <J_EDGAR_HOOVER> Well I replaced the regulatory.bin
[21:30] <J_EDGAR_HOOVER> and got the pubkeys right
[21:30] <J_EDGAR_HOOVER> should be OK on reboot. wish me luck :)
[23:12] <kozukumi> can i remove the lock screen button from the main whisker menu?
[23:14] <kozukumi> ah yes i can :D
[23:39] <xubuntu29w> Hi ! I have a basic question...
[23:40] <drc> xubuntu29w: You're in luck, we are overstocked in Basic Answers...just ask :)
[23:42] <xubuntu29w> I connect my android phone to my laptop with a usb cable and wants to open some pictures but I cannot look at them
[23:42] <xubuntu29w> when I click on them
[23:42] <xubuntu29w> nothing is displayed...
[23:42] <xubuntu29w> any reason?
[23:42] <hoodedice> you need to mount your sd card
[23:43] <xubuntu29w> I have to save them first and after click on them to be abe to look at them...
[23:43] <hoodedice> on your desktop, there should be a greyed out drive
[23:43] <hoodedice> save them?
[23:43] <hoodedice> oh, you already mounted it, missed that, sorry
[23:44] <xubuntu29w> yes already mounted...
[23:44] <xubuntu29w> and yes... I need to save them on my hard drive to look at the pictures..
[23:47] <xubuntu29w> but if I click on a folder the pictures are displayed in the folder andca look at them all as view icons or view as detailed list...
[23:47] <xubuntu29w> but when I click on oe of them in this case it doesnt work. the picture is not displayed


[02:57] <hyperair> does anyone here frequently hotplug monitors into an ivb laptop?
[06:32] <pitti> slangasek: thanks for the PAM bug analysis!
[06:32] <pitti> infinity: ah, good to know; I'll fix that
[06:33] <infinity> pitti: Thanks.
[06:33] <pitti> infinity: filed bug 1300031 as a reminder
[06:33] <pitti> Noskcaj: if there isn't too much difference to g-i-t 3.10, sure
[06:34] <infinity> pitti: I imagine the easiest way is just to grep -v '^#' before parsing debian/control.
[06:34] <infinity> pitti: Unless it also has issues with comments at the end of lines (didn't check).
[06:35] <infinity> pitti: In which case, maybe the equivalent of sed 's/#.*$//'
[06:35] <pitti> infinity: not sure whether you got my psql comment from Friday; but I guess today we can release the lot?
[06:35] <pitti> infinity: yep, should be simple
[06:35] <infinity> pitti: Yeah, we'll release it all today.  Your comment came a bit too late for me to be comfy releasing pre-weekend.
[06:36] <infinity> I guess we can just let it fly now, there will be enough people (including you) around to deal with something if it explodes.
[06:37] <infinity> pitti: Do these go to both updates and security, or is the psql-8.4 publishing history special?
[06:37] <pitti> infinity: no -security this time, just -updates
[06:37] <infinity> Kay.  For all of them?
[06:38] <pitti> infinity: yes
[06:38] <pitti> infinity: back in 30 mins
[06:40] <RAOF> pitti: Any chance of a umockdev release with the “don't wait for 48 days when given an evemu trace from a device that doesn't report events in chronological order” bug? :)
[06:58] <dholbach> good morning
[07:06] <zyga> good morning
[07:07] <pitti> RAOF: yes, I was going to do that
[07:08] <pitti> RAOF: sorry, forgot about it on Friday
[07:08] <pitti> RAOF: dinstall runs in 43 mins, I should catch that; so I can sync around noon
[07:14] <pitti> RAOF: umockdev 0.8.1 released and uploaded to sid
[07:59] <doko> tvoss, I think you / the phone team is the biggest user of valgrind (as a build dependency). I want to propose a new valgrind for trusty (having support for AArch64), maybe as a sru after the release. but it would be nice to check the valgrind package in the ubuntu-toolchain-r/test PPA.
[08:00] <tvoss> doko, cool, thanks for the heads up. I think the Mir team is using it in quite sophisticated ways, also the unity scopes team. I will dispatch your rfc for testing to them
[08:00] <doko> tvoss, let me file the bug, then the replies can be tested there
[08:00] <doko> posted ...
[08:00] <tvoss> doko, got a link for me?
[08:05] <doko> tvoss, https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1300070
[08:06] <doko> so maybe subscribe to the issue
[08:06] <tvoss> doko, ack
[08:18] <tvoss> doko, will ask the Mir and unity-scopes-api team for feedback specifically and extend the heads up to ubuntu-phone upstreams
[08:27] <seb128> shrug
[08:27] <seb128> update-manager stopped to debconf prompt me about openssh-server configuration
[08:27] <seb128> it displays a checkbox "disable ssh password authentification for root?"
[08:28] <darkxst> yeh I saw that too, imported from debian ?
[08:28] <seb128> cjwatson_, hey, is that ^ known/wanteD?
[08:29] <darkxst> seems rather odd when we don't have root accounts by default!
[08:29] <infinity> s/accounts/passwords/
[08:38] <infinity> cjwatson_: Maybe you could skip the debconf question and JFDI if '$(getent shadow root | cut -d: -f2) = "!"'
[08:40] <infinity> cjwatson_: That is, if root doesn't currently have a password, you won't be locking me out of my machine by surprise by not allowing password logins.  If I set one later, I can debug why it no workie myself.
[08:46] <infinity> seb128: ^ That seem like an acceptable compromise between no default prompting and not locking people out on upgrade?
[08:47] <seb128> infinity, seems fine to me, I'm unsure what changed though/how we were handling things before
[08:47] <seb128> (e.g why is that prompt showing up today)
[08:48] <seb128> k, the changelog answers that question :p
[08:48] <infinity> seb128: Our default config has/had PermitRootLogin yes.  The new default is without-password, which is saner, but automatically upgrading would lock out people who rely on the password auth.
[08:48] <seb128> right
[08:49] <infinity> (At least, I assume it used to be yes... Maybe it used to be no, and all of us hitting the prompt manually changed it at some point and forgot...)
[08:50] <infinity> No, it was definitely yes, I have a fresh precise VM with that setup.
[08:51] <seb128> I'm sure I didn't change that config
[08:52] <pitti> smoser, infinity: wolfe-05 and -06 are offline; do you know what happened to them?
[08:52] <infinity> pitti: I have no idea.  Lemme see if I remember how Scott's setup works.
[08:53] <infinity> ... and which IP wolfe is.
[08:55] <infinity> pitti: 06 looks alive to me.  05 is in an rcu_sched hang.
[08:55] <infinity> Oh, wait.  06 is spewing on the console too.  Whee.
[08:55] <infinity> pitti: Bouncing both.
[08:56] <infinity> pitti: Should be back.  I don't have accounts on either, so you'll have to confirm.
[08:59] <jibel> infinity, thanks, they are both back
[09:01] <jibel> pitti, I'll bring 3 down, because dpkg segfaults and it cannot provision a new container
[09:01] <jibel> s/down/offline/
[09:01] <infinity> jibel: A reboot should fix that.
[09:02] <infinity> jibel: I've never been able to reproduce that bug to try to figure out WTF is happening. :/
[09:02] <infinity> jibel: You're seeing that on one of wolfe's VMs?
[09:03] <jibel> infinity, yes on wolfe-03 but I just rebooted it
[09:03] <pitti> infinity: thanks for bouncing
[09:03] <infinity> jibel: Yeah, that's fine, I don't think I can get anything useful out of the VM anyway.  Just odd that you've seen it on another host.  I've only ever seen it on postal, and was close to blaming the machine.
[09:04] <infinity> (I've seen it on all of postal's VMs, but never on denneed or fisher, which is confusing as heck)
[09:04] <seb128> @pilot in
[09:04] <jibel> infinity, indeed it's dpkg'ing happily after a reboot.
[09:06] <infinity> jibel: It might act up again at some point.  It seemed to happen to postal's VMs every few hundred builds or so (couldn't ever identify any specific thing as the trigger, though), which is why those buildds are on manual right now. :/
[09:07] <infinity> As bugs go, it's pretty much my least favourite kind.  Not enough useful info to report to kernel (or qemu?) people, and no sane way to make it happen to try to get useful info.
[09:07] <infinity> And it may well just be a bug in the qemu endian-flip madness, which would make it something that really doesn't matter once we get off POWER7 hardware.
[09:08] <infinity> At least the symptom is so catastrophic that it doesn't cause any subtle bugs elsewhere. :P
[09:13] <jibel> infinity, yes hard to say, first failure of this type started 2 days ago but without any specific thing done to the VM
[09:18]  * hyperair wonders if he's the only one experiencing black-screen-on-monitor-plugged-in syndrome.
[09:33] <GunnarHj> cjwatson_: ping?
[09:43] <seb128> GunnarHj, you might want to let some context with pings ;-)
[09:44] <GunnarHj> seb128: Makes sense...
[09:45] <GunnarHj> cjwatson_: Time to talk about bug 1294858?
[09:46] <GunnarHj> seb128: Do you have time for a package question?
[09:47] <seb128> GunnarHj, sure
[09:48] <GunnarHj> seb128: What's the best way to distinguish Ubuntu from Debian in debian/rules?
[09:48] <GunnarHj> dpkg-vendor --is ubuntu
[09:48] <GunnarHj> ?
[09:49]  * apw feels this new ssh message is confusing, and the name of the option it tells you about just fuels that, and i don't feel advised as to the right option; i felt compelled to read the manual for it to decide
[09:49] <seb128> GunnarHj, yes
[09:49] <infinity> apw: See backscroll.
[09:49] <infinity> apw: About an hour ago.
[09:50] <GunnarHj> seb128: So the builders will always understand?
[09:50] <apw> infinity, ahh thanks
[09:50] <infinity> GunnarHj: The buildds have the same dpkg installed that you do.
[09:50] <seb128> GunnarHj, why wouldn't they? that's what e.g udisks is using
[09:50] <seb128> (just giving an example of package where we are using that if you want to check it out)
[09:51] <infinity> GunnarHj: You might want --derives-from though, if you want Ubuntu and all derivatives to get the setup.
[09:51] <pitti> didrocks: apport with that crash fix uploaded, now waiting in unapproved
[09:51] <infinity> GunnarHj: (Depends on if it's legitimately Ubuntu-specific, or rather just "not the Debian way")
[09:51] <didrocks> pitti: ok, I'll keep an eye to kick an image once available
[09:52] <GunnarHj> infinity, seb128: It's basically 'not the Debian way' in this case. Most important is that it works for Ubuntu Kylin.
[09:53] <infinity> GunnarHj: Well, kylin is "just Ubuntu", from the POV of them using the same dpkg from the same archive.
[09:53] <infinity> GunnarHj: But if Ubuntu derivatives should also default to the same setup (eg: because our packaging is forked in other fun ways, and derivatives should inherit that default), then you want --derives-from.
[09:54] <infinity> Thing, eg: Mint.
[09:54] <infinity> s/Thing/Think/
[09:54] <infinity> Not sure if Mint actually bothers to fork dpkg origin, but they should if they don't. :P
[09:54] <GunnarHj> infinity: Does --derives-from include all the 'normal' *ubuntu flavours?
[09:55] <infinity> GunnarHj: Flavours are all Ubuntu.
[09:55] <infinity> GunnarHj: They all use the same dpkg, cause they build from the same archive.
[09:55] <GunnarHj> infinity, seb128: Ok, think I've got it. Thanks!
[09:55] <infinity> GunnarHj: It's only derivatives (ie: people with their own archives) who can be different in this case.
[09:57] <infinity> GunnarHj: So, basically, antyhign built from ftp.debian.org both --is and --derives-from debian.  Anything built from archive.ubuntu.com --is ubuntu and --derives-from both debian and ubuntu.  Other out-of-archive derviatives might derive from debian or both (or, if they're weird, neither).
[09:58] <cjwatson> seb128: It's wanted in general, but infinity's suggestion seems like a nice option.
[09:59] <GunnarHj> infinity: Then it's indeed --is in this case (i.e. not Debian). Thanks for the lesson. :)
[10:02] <cjwatson> GunnarHj: I only work on ubiquity at the moment when it's an emergency and nobody else is available.
[10:02] <cjwatson> GunnarHj: Too many other plates to juggle.
[10:03] <GunnarHj> cjwatson: Anybody else I could talk to? (It's not exactly an emergency, but would be nice to have it fixed in 14.04.)
[10:03] <cjwatson> GunnarHj: Slightly reluctant to unconditionally volunteer him, but maybe xnox has time?
[10:03] <infinity> GunnarHj: I think I was trying to point out that you want "--derives-from ubuntu" so that both ubuntu and downstreams who use our packages mostly unmodified would get the same thing, but if it's really Ubuntu-specific, you want --is (like, say, Apache server tokens).
[10:04] <GunnarHj> cjwatson: Can't hurt to ask. :) Thanks!
[10:07] <GunnarHj> infinity: It's code intended to be added in debian/rules upstream (Debian) but only take effect when built for Ubuntu.
[10:07] <infinity> GunnarHj: Right, I get that.  But if someone were to build the package on an Ubuntu derivative that is mostly Ubuntu, but with a few tweaks, would they want the Ubuntu rules behaviour, or the Debian?
[10:08] <infinity> GunnarHj: If you use --is, they'll get the Debian behaviour.  Would that be wrong in the context of all their other packages being Ubuntuish?
[10:09] <GunnarHj> infinity: Maybe, maybe not. It's not a very Ubuntuish think. It's just that we (unlike Debian) want fcitx to be the default before ibus if fcitix is installed. :)
[10:10] <caribou_> cjwatson: I saw that you fixed the btmp bug in Debian (Debian bug #341883), thanks
[10:11] <GunnarHj> infinity: Still appreciate your clarifications.
[10:12] <cjwatson> caribou_: you're welcome
[10:12] <caribou_> cjwatson: now how should I proceed for Ubuntu ? This will not be automatically synced in Trusty
[10:12] <cjwatson> caribou_: I already synced it.
[10:13] <caribou> cjwatson: thanks!
[10:13] <infinity> cjwatson: Hrm.  That btmp thing didn't really address the "might use password as username" issue, though.  I'm still not super keen on root having a log of unhashed passwords in the clear.
[10:14] <caribou> cjwatson: then looks like I should get going with the SRU work
[10:14] <infinity> cjwatson: I liked login's solution of logging UNKNOWN for accounts that don't exist.
[10:14] <cjwatson> infinity: Yeah, that's cute, though really ought to be done upstream
[10:14] <cjwatson> caribou: Be my guest
[10:14] <infinity> Though, login fails in other ways, it would seem...
[10:15] <infinity> UNKNOWN  tty1                          Mon Mar 31 04:14   still logged in
[10:15] <infinity> test123  ssh:notty    localhost        Mon Mar 31 04:12    gone - no logout
[10:15] <infinity> Still logged in, my ass. :P
[10:15] <pitti> Laney: does bug 1278284 sound ok to you? Otherwise I'll need to fork off Ubuntu and upload the other fixes without that new debugging option
[10:15] <pitti> Laney: (I suppose it's ok, but asking early before I sync it)
[10:15] <pitti> Laney: sorry, bug 1300092
[10:15] <infinity> Oh, fun, it continues to say that until the getty dies (ie: due to a successfuly login)
[10:16] <infinity> s/successfuly/successful/
[10:16] <Laney> pitti: Yeah, new feature you have to opt in to use in a QA-ish package sounds fine
[10:16] <Laney> go wild
[10:17] <pitti> Laney: thanks
[10:17] <Laney> thanks for committing that sessioninstaller fix too ;-)
[10:46] <seb128> dholbach, hey, is https://bugs.launchpad.net/ubuntu/+bug/1294891 ready for upload? ;-)
[11:03] <highvoltage> froztbyte/win 13
[11:03] <highvoltage> (oops)
[11:03] <Laney> nice password :P
[11:03] <zyga> heh :)
[11:08] <tkamppeter> xnox, hi
[11:13] <xnox> tkamppeter: hello!
[11:27] <Sweetshark> doko: libreoffice update is in main, -voikko build against it here ...
[11:27] <Sweetshark> s/build/builds/
[11:28] <Sweetshark> pls ping me if there are issues remaining.
[11:39] <dholbach> seb128, I didn't look at it after my pilot shift again
[11:40] <seb128> dholbach, can you upload it? if I do it I need to find another archive admin to do the NEWing...
[11:40] <dholbach> seb128, ok, I'll review it again
[11:40] <seb128> dholbach, danke!
[11:52] <dholbach> seb128, followed up: https://bugs.launchpad.net/ubuntu/+bug/1294891/comments/8
[11:53] <seb128> dholbach, thanks
[11:59] <tkamppeter> xnox, can you have a look at bug 1276713 and also at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742666. It is abot getting equal Upstart support with socket activation in both Debian and Ubuntu.
[12:00] <tkamppeter> xnox, can you especially answer Cameron's questions in the Launchpad bug.
[12:00] <xnox> tkamppeter: ack.
[12:04] <xnox> tkamppeter: responded
[12:13] <tkamppeter> xnox, thanks.
[12:18] <seb128> @pilot out
[13:01] <seb128> doko, hey, do you have any openjdk upload coming? there is a patch in the sponsoring queue that would be nice to get in trusty, but since openjdk takes ages to build better to batch that with other changes if you have some ;-)
[13:02] <doko> if this is 937200, then yes
[13:17] <seb128> oh, seems like pitti is attacking the sponsoring queue from the other side ;-)
[13:17] <pitti> seb128: sorry, I saw your @pilot out and thought to run through some items
[13:17] <pitti> seb128: i. e. sorry if I stepped on your toes
[13:17] <seb128> pitti, no worry, help is welcome ;-)
[13:18] <mardy> Mirv: hi! Do you think you can add the fix to bug 1299712 as a patch against qt 5.2?
[13:18] <seb128> pitti, no, I'm glad you got some, I stopped for lunch and I was planning to get a few extras, but I would probably not have reached the most recent ones
[13:19] <pitti> seb128: grabbing light-locker* and gnome-documents MP, ok?
[13:20] <pitti> seb128: I try to do the easy syncs and some "5-a-day"ish these days
[13:20] <seb128> pitti, yes please, I just synced the audiocity ones and tali, sponsored gnome-online-account and I'm doing easytag
[13:20] <psusi> the ddebs for libparted0debian1 are empty in the last 3 revisions.  anyone have any idea what went wrong? or how to figure it out?
[13:20] <seb128> pitti, just stating the ones I'm touching so we don't duplicate
[13:21] <seb128> pitti, 5 a day ftw ;-)
[13:28] <psusi> cjwatson: re: the loop regression: I think you had some magic in partman to deal with lvm volumes, which parted used to report as having a single partition on them named /dev/mapper/xxxp1.  The patch dropped the incorrect p1 suffix.  Could that have broken partman?
[13:29] <xnox> psusi: partman used to report /dev/mapper/volume-group-name with volumes under that device name (as if they are partitions)
[13:31] <pitti> seb128: grabbing https://code.launchpad.net/~noskcaj/ubuntu/trusty/gnome-video-effects/0.4.1/+merge/212248, then finishing
[13:32] <pitti> RAOF: umockdev 0.8.1 is now in trusty, with the timestamp going backwards fix
[13:33] <seb128> pitti, danke
[13:35] <psusi> xnox: not how I remember it... it reported each /dev/mapper/vg-lv as a disk, with a single partition on it named /dev/mapper/vg-lv1
[13:36] <psusi> partman apparently knew it had to strip off the bogus 1 to refer to the actual device name... I fixed libparted to not add the bogus 1 in the first place
[13:44] <cjwatson> psusi: None of that rings a bell
[13:46] <psusi> cjwatson: darn.. was hoping it would.  Guess I'll just have to play around with it tonight.
[13:47] <pitti> didrocks: the apport cgroup crash fix landed in trusty now, FTR
[13:47] <cjwatson> psusi: thanks
[13:48] <seb128> doko, thanks ;-)
[13:48]  * davmor2 rings his bell to see if helps cjwatson remember
[13:49] <pitti> stgraber, kirkland: byobu's keys (F2 etc.) don't work in a container, i. e. with "lxc-start"; is there a trick how to get this functionality?
[13:50] <kirkland> pitti: hmm, interesting, is this screen or tmux backend?
[13:51] <pitti> kirkland: hm, both screen and tmux are installed (I think I just did "apt-get install byobu"), how do I tell?
[13:51] <pitti> tmux -f /usr/share/byobu/profiles/tmuxrc new-session -n - /usr/bin/byobu-shell
[13:51] <pitti> kirkland: ah, tmux
[13:51] <kirkland> pitti: tmux
[13:51] <kirkland> pitti: yeah, the easy visual queue is "1 line, or 2 of status at the bottom"
[13:51] <pitti> kirkland: ah, heh; yes, one line
[13:51] <kirkland> pitti: otherwise, its ps -ef | grep byobu
[13:52] <pitti> kirkland: I'm fairly sure it's nothign with gnome-terminal or my unity config etc, I use F2/F3 etc. on ssh sessions all the time
[13:52] <pitti> kirkland: curiously, F9 works
[13:53] <kirkland> pitti: right;  oh, now that is weird
[13:53] <kirkland> pitti: I was thinking something might be wrong with how lxc handles the tty...but if F9 works...
[13:53] <pitti> kirkland: shift-f2/f3 etc. seem to work, too
[13:53] <kirkland> pitti: this is latest/greatest trusted?
[13:53] <pitti> kirkland: yes, trusty du jour on both host and container
[13:54] <stgraber> pitti: what's F2 supposed to do?
[13:54] <kirkland> pitti: is this a recent regression in lxc?
[13:54] <kirkland> stgraber: create a new window in byobu
[13:54] <stgraber> ok, then it works fine here
[13:54] <pitti> kirkland: I'm not sure, but it's at least like that for two weeks or longer
[13:54] <pitti> stgraber: interesting
[13:54] <stgraber> I'm sshed into a trusty container on a trusty host running byobu and F2 gets me a new window
[13:54] <stgraber> using terminator as my terminal emulator here
[13:54] <pitti> stgraber: so maybe ssh sets up the terminal differently in some way than a direct "lxc-start" in gnome-terminal?
[13:55] <stgraber> pitti: that's entirely possible, yes
[13:55] <pitti> anyway, it seems this isn't already known
[13:55] <pitti> I can do lxc-attach to get a second shell in it, it's just way more cumbersome
[13:55] <stgraber> though both should be pts devices in the end, maybe tmux special-cases devices called /dev/ttyX somehow?
[13:57] <ochosi> pitti: thanks for sponsoring light-locker* !
[13:57] <pitti> kirkland: FTR, broken in byobu-screen as well
[13:57] <pitti> ochosi: yw!
[14:00] <kirkland> pitti: okay, I'm trying to reproduce this now
[14:00] <kirkland> pitti: what's your escape key?  the default ctrl-a?
[14:01] <kirkland> pitti: can you try this... ctrl-a then ":" then type "new-window" and hit enter
[14:01] <kirkland> pitti: does that create a new window?
[14:01] <pitti> kirkland: hm, I think I set it to emacs mode, so that ctrl+a = go to beginning of line
[14:01] <kirkland> pitti: okay, so ctrl-b then
[14:02] <pitti> kirkland: argh, that's taken by my window manager; can I reset ctrl+a somehow?
[14:02] <pitti> ah, byobu-ctrl-a :)
[14:02] <pitti> F12 doesn't work, FTR
[14:02] <pitti> kirkland: :new-window works fine; F3 doesn't switch
[14:03] <kirkland> pitti: okay, now, ctrl-b then ":" then "bind-key -n F2 new-window"
[14:03] <kirkland> pitti: then try pressing F2
[14:04] <pitti> kirkland: no change
[14:06] <kirkland> pitti: okay, and you're in a shell on your container using lxc-attach?
[14:07] <pitti> kirkland: not lxc-attach, lxc-start (not sure if that's any different)
[14:07] <pitti> sudo lxc-start -n debci
[14:07] <pitti> and then log into that through the usual getty
[14:08] <pitti> kirkland: a local byobu on my VT1 works fine, btw
[14:09] <didrocks> pitti: yeah, we kicked an image as soon as it was promoted (building), thanks for the head's up
[14:13] <seb128> xnox, hey, could you review https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1298220 ?
[14:14] <seb128> xnox, I'm asking you because I know you had a look at some of the issues with the new bash
[14:15] <seb128> doko, ^ or maybe that's something you are interested in as well
[14:16] <xnox> seb128: damn, did I forget to revert bash ?! *sigh*
[14:17] <seb128> xnox, now I'm unsure if you are trolling me :p
[14:17] <seb128> xnox, well, doko is back at least, so you can talk to him about fixing it
[14:18] <xnox> seb128: i think we can sync bash-completion, but it will not solve all the bash problems.
[14:18] <seb128> :-(
[14:19] <pitti> xnox: FTR, there's a sync request in the sponsoring queue; but I checked the diff between D and U and it's horribly long, so that would need to be done with some care
[14:19] <pitti> I found a few fixes/changes which aren't in Debian yet
[14:19] <pitti> (i. e. maybe better merge/sync that next cycle?)
[14:21]  * dholbach hugs seb128 and pitti
[14:21] <xnox> pitti: yeah, i also see that some things need to be merged.
[14:21]  * seb128 hugs dholbach and pitti
[14:21] <xnox> pitti: agree, that it's better to post-pone this.
[14:21] <cjwatson> slangasek: Can you advise on where bug 1298653 should be reassigned?
[14:24] <xnox> seb128: hm, although doko did upload two bugfixes.
[14:24] <seb128> xnox, right
[14:24] <bdmurray> pitti: did you see I updated my apport-retrace package versions merge proposal?
[14:25] <xnox> seb128: i think we are all good. major bugs in bash-completion and bash are fixed.
[14:25] <pitti> bdmurray: ah no, I didn't; thanks! (LP doesn't send out notifications for new commits)
[14:25] <seb128> xnox, if you say so
[14:25] <pitti> at least ~/... completion shows files again
[14:30] <kirkland> pitti: okay, I've reproduced your issue
[14:31] <kirkland> pitti: I'm checking saucy now
[14:32] <pitti> kirkland: I can't say whether this is a regression at all; I never used byobu with lxc before
[14:32] <kirkland> pitti: k
[14:42] <kirkland> pitti: I do see this error, "<4>init: setvtrgb main process (409) terminated with status 1"
[14:42] <kirkland> pitti: just before the login prompt
[14:43] <pitti> kirkland: yes, me too
[14:43] <kirkland> pitti: confirmed on saucy too
[14:45] <bdmurray> infinity: could you have a look at bug 1298393?
[14:47] <ogra_> cjwatson, hmm, i just noticed that i can start sshd even if there are no existing host keys, is that wanted (i remember the old sysv init script had a check and created keys on demand)
[14:49] <cjwatson> ogra_: I'm afraid your memory is faulty.
[14:49] <ogra_> was that always a postinst thing ?
[14:49] <cjwatson> We've never created host keys in the init script, and if it ever checked it would only have been by way of sshd -t.
[14:49] <cjwatson> Yes.
[14:50] <ogra_> hmm, kay
[14:50] <cjwatson> I would expect sshd to exit early if it has no host keys.
[15:17] <bdmurray> barry: were you looking at gdebi recently?
[15:18] <barry> bdmurray: yes, i have a branch wip for switching it to py3
[15:18] <bdmurray> barry: might that fix bug 1295872?
[15:18] <barry> bdmurray: not directly
[15:21] <bdmurray> barry: okay, looking at the errors bucket it seems to occur pretty frequently
[15:22] <barry> bdmurray: i'll try to take a look when i'm working on the new branch
[15:23] <bdmurray> barry: thanks
[15:39] <hallyn> holy cow.  unity is just losing windows left and right...  they're still running, but they don't show up in the switcher
[16:01] <rbasak> cjwatson: triaging bug 1300133: Won't Fix?
[16:04] <cjwatson> rbasak: I've left it in the state I intend
[16:04] <cjwatson> rbasak: (i.e. it's OK for there to be discussion)
[16:05] <cjwatson> rbasak: (I don't understand this thing where the server team feels obliged to triage openssh bugs but doesn't contribute to maintenance, TBH)
[16:05] <cjwatson> seems weird :)
[16:11] <balloons> ping xnox
[16:13] <rbasak> cjwatson: to try and keep a handle on bugs, I end up triaging far more bugs than I do deep dives into.
[16:14] <xnox> balloons: hey
[16:14] <rbasak> cjwatson: for some reason our triage process involves handling New/Undecided bugs, but IMHO that's never really been right. It's just on the queue, and I thought we could do something about it.
[16:14] <rbasak> I suppose set the Importance at least, since then it doesn't appear on the first triage report we have.
[16:14] <balloons> xnox, hey. So a couple things to discuss with you.
[16:14] <xnox> balloons: shoot! =)
[16:14] <balloons> xnox, first, can you push stuff to the store now? Can you build clicks on s-jenkins? did that get sorted out?
[16:15] <cjwatson> rbasak: importance something less than high would be fine, yeah
[16:16] <rbasak> thanks
[16:16] <xnox> balloons: i have access to upload clicks into the store, i can download them from s-jenkins. I don't have any special privilidges on s-jenkins (e.g. triggering/controlling jobs etc)
[16:17] <xnox> balloons: e.g. i was the one who uploaded gallery app click fetched from s-jenkins for the last upload.
[16:17] <balloons> xnox, good enough. Ok, would you be willing to work with fginther this week on having those builds be autotested after building?
[16:17] <balloons> xnox, I'll be out and he wants to get it in ;-)
[16:18] <xnox> balloons: sure. All I do locally is: $ click-run-checks on the generated .click.
[16:18] <balloons> xnox, secondly, I'd think your opinion on this issue popey is seeing. https://bugs.launchpad.net/music-app/+bug/1300230
[16:18] <xnox> fginther: can we integrate "click-run-checks" on the generated .click? it's about equivalent to running "lintian" against a deb.
[16:19] <xnox> balloons: right, let me look into that music-app error.
[16:19] <balloons> xnox, I'm wondering if the new phablet-tools release might have impacted the bug I linked from popey. The tldr is, there are now unicode errors running tests that used to work
[16:23] <xnox> balloons: if a click declares autopilot directory in the manifest, it must be python3 compliant tests.
[16:23] <xnox> balloons: one way to solve this is to remove that stanza from the manifest, and then the tests will revert to using python2.
[16:23] <balloons> did we miss music in the conversion?
[16:23] <xnox> balloons: or I'll look into fixing this.
[16:23] <balloons> xnox, ahh.. kk..
[16:23] <xnox> balloons: to make it python3 compatible again.
[16:24] <balloons> xnox, I'd prefer the latter if you are willing
[16:24] <xnox> balloons: it did pass under python3 a week ago =)
[16:24] <balloons> xnox, wild.. I haven't checked the revision history to see what all got changed
[16:24] <balloons> let's look
[16:25] <fginther> xnox, adding click-run-checks is do-able
[16:26] <xnox> fginther: having that output as artifact should be sufficient. Possibly bail/fail the job if that has errors. Warnings are harder, as some of them are expected.
[16:27] <balloons> fginther, xnox please just keep me in the loop on what's implemented. I'll be back at the end of next week
[16:27] <fginther> xnox, I'll let you know once I have something started so you can have a peek at the results
[16:28] <xnox> fginther: thanks!
[16:31] <Laney> bah
[16:31] <Laney> keeping build-deps cross-installable is a right pain, isn't it?
[16:36] <tarpman> doko, seb128: thanks very much for uploading 937200 :) super pleased to have that in trusty.
[16:37] <seb128> tarpman, yw!
[16:43] <xnox> balloons: commented on the bug report about music-app. It works and passes correctly on the current trusty-proposed channel, with current 389 music-app, latest phablet-tools, under python3.
[16:43] <xnox> balloons: how is popey running that music-app tests that shows errors?
[16:44] <popey> xnox: phablet-test-run -v  music_app
[16:46] <balloons> xnox, I'll leave you to popey as it works for me too :-)
[16:46] <popey> thanks ☻
[16:46] <balloons> popey, well, which version are we running
[16:46] <balloons> xnox answered that v369 or earlier don't work
[16:47] <popey> 369 of what?
[16:47] <balloons> I see 389 right?
[16:47]  * balloons opens myapps
[16:47] <popey> i have tried 389 and 403
[16:48] <balloons> popey, ahh right then. indeed
[16:50] <popey> xnox: feel free to ping if you need me to test anything, or need more detail.
[16:50] <balloons> biab
[16:54] <psusi> cjwatson: so do you have any idea why the ddebs for the last 2-3 releases of parted are broken?
[16:58] <xnox> popey: 389 works fine.
[16:58] <xnox> popey: how do you build, install and test 403?
[16:59] <slangasek> cjwatson: bug #1298653> err, I honestly have no idea, it's not supposed to be a boot menu option
[16:59] <popey> xnox: i got 403 from the store,  uploaded by balloons, installed using "pkcon install-local foo.click"
[17:00] <popey> xnox: I test using 4 lines... phablet-config autopilot --dbus-probe enable, phablet-click-test-setup --click  com.ubuntu.music, adb reboot, then phablet-test-run -v music_app
[17:00] <popey> xnox: which is what I've been doing for all apps. I ran the tests on gallery earlier on the same device and it was fine.
[17:00] <cjwatson> psusi: hm, broken how?
[17:01] <xnox> popey: right, let me wipe my device clean, to make sure i'm clean.
[17:01] <psusi> cjwatson: it's empty
[17:01] <cjwatson> psusi: there are -dbg packages
[17:01] <psusi> for libparted that is...
[17:01] <cjwatson> psusi: IIRC pkg-create-dbgsym doesn't bother to create contentful -dbgsym packages if -dbg is meaningful
[17:02] <psusi> ohh... didn't realize -dbg got added... and that makes the ddebs still there, just empty?
[17:02] <cjwatson> think so, they should have a dependency?
[17:02] <Laney> dbgsym should have a dependency
[17:02] <psusi> I would have thought it wouldn't create them at all... weird
[17:07] <xnox> popey: can you get me output of $ click list --manifest ?
[17:08] <popey> xnox: http://paste.ubuntu.com/7185790/
[17:09] <xnox> popey: and when running as a user phablet I guess as well, so $ sudo -u phablet -i click list --manifest ?
[17:09] <popey> that was as phablet
[17:09] <xnox> popey: cool, thanks.
[17:10] <xnox> popey: so autopilot/python blows up on one of those =)
[17:10] <popey> oh nice
[17:10] <xnox> popey: in particular with the fact that it's not running in UTF-8 locale, I think.
[17:10] <xnox> popey: (same as all other locale based problems recently reported)
[17:10] <popey> makes sense ☻
[17:12] <ogra_> hmm, is the randomization of PIDs a kernel feature ? and if so, is there wa way to switch it off ?
[17:13] <ogra_> it just struck me how helpful it would be to have the processes visually ordered in a bootchart
[17:13] <ogra_> (which proper ordering of the PIDs would achieve)
[17:16] <sarnold> ogra_: yes, it would be a kernel feature if it exists; are you confident you're seeing that behaviour? to my knowledge, linux has never had it..
[17:16] <sarnold> (and my week-old-ish uuntu touch image doesn't show that behaviour..)
[17:18] <ogra_> well, looking at bootcharts i see things started with a lower PID than the process starting it ... it seems to start randomizing at some point
[17:20] <sarnold> crazy thgh, running 'ps ; ps' in terminal shows 10151 and 10156. that's far more intervening processes than I would have expected
[17:21] <Snow-Man> or it just wrapped?
[17:22] <mdeslaur> sarnold: if I run it a couple of times, I get sequential pids once in a while
[17:22] <sarnold> iirc cking mentioned some new tool recently, a fork-tracker... it'd be worth tracking that down
[17:22] <sarnold> mdeslaur: heh, I never got two consecutive pids
[17:23] <mdeslaur> sarnold: you need to stop running the fork bomb in the other window :)
[17:24] <sarnold> mdeslaur: oh is -that- why my battery life is not so good? :)
[17:26] <mdeslaur> sarnold: hehe :)
[17:26]  * sarnold mumbles "last time I trust an article that says you can speed up your phone with this one simple trick..."
[17:29] <balloons> xnox, popey so what's the synopsis?
[17:35] <popey> balloons: xnox was reflashing his device, but seems maybe one of the apps I have installed on my phone was triggering the issue. But we don't know which one (yet)?
[17:37] <zyga> ogra_: IIRC kernel has PID reuse but the way it reclaims dead pids is unclear to me
[17:37] <ogra_> it seems slightly random ...
[17:38] <ogra_> but not completely
[17:38] <zyga> ogra_: probably next free from a rotating counter *but* given that this is the kernel I woudn't be surprised if there are some multi-core features to avoid any locking on next
[17:39] <ogra_> yeah
[17:46] <xnox> popey: i think i do know what's triggering this.
[17:46] <xnox> popey: working on a fix.
[17:47] <xnox> popey: please don't change your phone =)
[17:49] <popey> ok
[17:55] <xnox> popey: make your phone RW (if not already) then do:
[17:55] <xnox> adb shell "echo exec su - -c adbd > /etc/init/android-tools-adbd.override"
[17:55] <xnox> adb reboot
[17:55] <xnox> popey: then try running music-app tests again and it should work.
[18:02] <xnox> popey: right, the UTF-8 app is tradera that you have installed, and i've now reproduced your bug and the fix for it.
[18:07] <leftyfb> paul_1: can you hop onto the webex and login to the local 12.04 install for me?
[18:08] <leftyfb> paul_1: in a meeting at the moment so can't talk on the webex call
[18:12] <leftyfb> paul_1: thank you
[18:23] <popey> xnox: sorry, was on a call..
[18:23] <xnox> popey: no worries. Fix uploaded into unapproved queue. Hopefully would be reviewed and accepted soon.
[18:38] <infinity> bdmurray: Yup.
[18:39]  * popey hugs xnox
[18:39] <popey> xnox: so just removing Tradera will allow me to run the tests?
[18:41] <xnox> popey: or doing: adb shell "echo exec su - -c adbd > /etc/init/android-tools-adbd.override"
[18:41] <xnox> popey: and rebooting
[18:42] <popey> xnox: i went for removing the app
[18:42] <xnox> popey: you might have other apps installed which would also affect the results....
[18:42] <xnox> popey: it's the first problematic one, not sure if there are others =)
[18:42] <popey> is there an easy way to tell?
[18:43] <popey> which was the problematic app?
[18:46] <xnox> freeciv, airbnb, baboom, bytesjack, ....
[18:46] <xnox> popey: is your phone not in RW mode?
[18:47] <xnox> in that case wait for adbd fix to get accepted.
[18:50] <popey> no, not rw, I dont really want to do that
[18:50] <ogra_> xnox, did you run any AP tests for this ? would be good to know that still works with the multiple sudo hoops they jump through in adb
[18:50] <xnox> popey: well, it got accepted now. So in one of the next images it should be available via channel updates ;-)
[18:51] <xnox> ogra_: all works correctly, tested with click and non-click AP tests.
[18:51] <ogra_> cool
[18:51]  * ogra_ wishes we could drop that some day .... it is awful
[18:55] <slangasek> drop which?
[19:01] <ogra_> slangasek, the sudoing to become phablet
[19:01] <slangasek> what's awful about it, and what are you wanting to drop it in favor of?
[19:02] <ogra_> proper pam integration of adbd ... or running adbd as user by default
[19:03] <slangasek> well, I don't think that's an "or"; running it as a user by default still doesn't give you a pam session unless you add the pam integration
[19:04] <slangasek> I'm unconvinced that there's anything wrong with the current solution that's worth the effort of adding pam integration to adbd
[19:06] <ogra_> adb shell "sudo -u phablet -i 'bash -i -c $command'" ...
[19:07] <ogra_> i still find it awful and ugly :)
[19:07] <ogra_> not to mention it gets you into quoting hell with a little complex commands
[19:10] <slangasek> ogra_: well, there's certainly some redundancy there
[19:11] <slangasek> but that should be fixed directly
[19:12] <ogra_> well, we have plenty different vesions of that command in different plases and tools ...
[19:12] <ogra_> phablet-test-run has: adb $ADBOPTS shell sudo -u $USER -i sh -lc \'"$@"\' ...
[19:12] <ogra_> slightly less ugly
[19:12] <slangasek> no, that's even more ugly
[19:13] <ogra_> oh ?
[19:13] <slangasek> '-i sh -lc'?
[19:13] <slangasek> you want 'sudo -u $USER -i -c "$@"'
[19:14] <ogra_> that somehow didnt work for the people writing the tests
[19:14] <slangasek> then they should've asked for advice from someone who knows how sudo and the shell work
[19:15] <hallyn> hm, maybe i'm having a pulseaudio bug.  mplayer keeps saying 'audio device got stuck.'  banshee last night seemed to keep completely hanging my laptop (to the point that sysrq didn't work)
[19:15] <ogra_> i think that doesnt process profile.d
[19:15] <ogra_> which we need to get the proper env
[19:15] <hallyn> i'll test some more witih banshee tonight after a reboot ...
[19:15] <slangasek> and actually, I'm wrong, what you actually want is 'sudo -u $USER -i "$@"'
[19:15] <slangasek> ogra_: 'sudo -i' is all you need in order to get a login shell
[19:16] <slangasek> all the other crufty arguments here are cruft, but that has nothing to do with adbd supporting pam, that just has to do with people piling on commandline arguments without understanding them
[19:16] <ogra_> well, there was a reason for the bash call in there
[19:16] <slangasek> not a good reason
[19:16]  * ogra_ cant remember anymore, thats nearly a year old
[19:17] <ogra_> but i know that the SDK ads well as the automation uses it like that
[19:17] <slangasek> it's possible that the phablet user had the wrong login shell.  That should have been fixed by fixing the phablet user's login shell.
[19:17] <slangasek> (and if that was the problem, it has been fixed since)
[19:18] <ogra_> i dont think it ever changed from /bin/bash
[19:19] <ogra_> what i remember is that it had something to do with the environemnt not being proper
[19:23] <slangasek> regardless, this is unnecessary complexity.  phablet-test-run should just be 'adb $ADBOPTS shell sudo -u $USER -i $@', and the other invocations likewise
[19:24] <ogra_> right, i was promoting that back then ... but for some reason it didnt work
[19:35] <slangasek> ogra_: ok, so the issue within phablet-test-run is that it's trying to run a sequence of commands under sudo, so yes, that requires sh -c.  It certainly doesn't require 'bash -ic', however... 'sh -c' is fine and it will inherit the environment from the login shell that's already been launched
[19:44] <Justanick> Hello, is it useful, that an upgrade from the last LTS did not remove the packages
[19:44] <Justanick> linux-image-generic-lts-quantal
[19:44] <Justanick> linux-headers-generic-lts-quantal
[19:45] <Justanick> Also the new gcc is not added to update-alternatives
[19:45] <Justanick> Still showing the old gcc 4.6
[19:46] <cjwatson> gcc is intentionally not managed in update-alternatives, to avoid determinism problems in builds
[19:47] <leftyfb> paul_1: Would you mind joining us on that call? Having some issues.
[19:47] <cjwatson> A normal upgrade should simply repoint the /usr/bin/gcc symlink directly at gcc-4.8, assuming that you upgraded gcc
[19:48] <Justanick> cjwatson: The gcc 4.6 has been still installed after the update. I have just purge it with apt-get purge
[19:50] <Justanick> This has also delete the gcc 4.6 entry on update-alternatives
[19:50] <Justanick> The new entry for gcc 4.8 is still missing
[19:51] <Justanick> The binaries are at /usr/bin/
[19:51] <cjwatson> There has never been a gcc-4.6 entry in update-alternatives at all, as far as I'm aware
[19:51] <cjwatson> I suggest "sudo apt-get install gcc"
[19:57] <Justanick> cjwatson: The message is "newest version is installed". I will add the entry manually.
[19:59] <infinity> Justanick: There should be no "entry", there should be a straight symlink, as provided by the "gcc" package.
[19:59] <infinity> Justanick: If you had alternatives before, that was not from the Ubuntu packaging, but perhaps something you added yourself?  In which case, you should expect that to break.
[20:01] <Justanick> infinity: I could be added by myself.   Installing it as an alternative locally is going to lead to trouble.
[20:06] <cjwatson> Try 'dpkg -L gcc' and see whether it lists /usr/bin/gcc.
[20:07] <cjwatson> And in future use CC=gcc-4.8 or whatever if you need to switch versions rather than mucking around with system-level alternatives.
[20:08] <Justanick> cjwatson: Yes it is on the list.
[20:09] <cjwatson> Then I might try "sudo apt-get --reinstall install gcc" to see if that resurrects /usr/bin/gcc.
[20:09] <cjwatson> And make sure that you have no alternatives for gcc now.
[20:09] <Justanick> gcc -v returns now the ubuntu build of 4.8.2
[20:09] <cjwatson> I don't really want to think about what an alternative for a file name also shipped directly in a package would do to dpkg, but it wouldn't be good.
[20:10] <cjwatson> It certainly isn't a valid configuration.
[20:11] <cjwatson> There are alternatives for c89, c99, and cc, those are OK (they're for switching between gcc and clang)
[20:11] <cjwatson> Though CC= is still usually preferable
[20:12] <Justanick> Okay.
[20:13] <cjwatson> I think it's probably more or less expected that linux-*-generic-lts-quantal aren't removed, not sure; might be nice to sort that out via an upgrade quirk in ubuntu-release-upgrader
[20:14] <cjwatson> Clearing out old kernels requires care ...
[20:16] <infinity> cjwatson: The release-upgrader already violently tears out old kernels, I thought.  Maybe it's being fooled by the lts backports.
[20:16] <Justanick> cjwatson: Or a question to the customer, if the older kernel should be removed?
[20:18] <doko> xnox, thanks for taking care about the python3.3 drops
[20:19] <xnox> doko: no problem.
[20:19] <xnox> doko: need to make up uploads since missing in action for a wekk =)
[20:31] <Justanick> Should scons work on the daily?
[20:38] <Justanick> g++ has not been valid
[20:42] <jtaylor> xnox: whats different in the headless builders? or why is stuff suddenly failing to build after beta freeze?
[20:42] <Justanick> At the boot grub2 shows me 3 times error:file not found. What the source of the problem could be?
[20:43] <xnox> jtaylor: it has also been failing in all test rebuilds.
[20:43] <jtaylor> it didn't fail in february
[20:43] <xnox> jtaylor: the errors are comming from X server, on initial inspection, maybe the problem is somewhere else.
[20:44] <xnox> jtaylor: it did fail in early march. http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140307-trusty.html
[20:45] <xnox> jtaylor: well, march 16th.
[20:45] <xnox> ~ 2 weeks ago.
[20:46] <jtaylor> ah, mixed it up with pytables that still build a week ago
[20:46] <jtaylor> I'll check it out
[21:02] <jtaylor> xnox: oh I remember, its nose thats broken
[21:02] <jtaylor> fixed in debian svn
[21:03] <jtaylor> want to sponsor :)
[21:03] <jtaylor> oh been done today, so just needs syncing
[21:04] <xnox> jtaylor: which package? =)
[21:04] <jtaylor> python-nose
[21:05] <xnox> jtaylor: done - https://launchpad.net/ubuntu/trusty/+queue?queue_state=1&queue_text=nose
[21:05] <jtaylor> thx
[21:06] <xnox> jtaylor: thanks for tracking this down =)
[21:06] <jtaylor> mitya57 tracked it down, I just reported :)
[21:12] <slangasek> ogra_: so I proposed a fix to phablet-test-run, and the testsuite fails CI because of unrelated bashisms in phablet-screenshot :-P https://jenkins.qa.ubuntu.com/job/phablet-tools-trusty-amd64-ci/67/console
[23:04] <hallyn> hi - could someone on sru team please look at https://launchpad.net/ubuntu/saucy/+queue?queue_state=1&queue_text=libvirt?
[23:05] <hallyn> the version currently in -proposed failed to build, 8.9 in unapproved fixes that
[23:33] <bdmurray> infinity: nag about bug 1296386


[07:24] <slyon> JornS: Yeah, you cannot have two default gateways "gateway4" fields.. those will be in conflict with each other, but need to configure your routes manually: https://netplan.io/reference/#default-routes
[09:13] <JornS> tried setting up routing tables and via per the documentation, but still no replies on ping for the 10/16 interface :/ https://pastebin.com/nPZCQGx2
[09:14] <JornS> anyone able of seeing what i'm doing wrong here?
[09:25] <schopin> JornS: on-link: true + gateway feels weird to me? Are you sure about that part?
[09:31] <schopin> JornS: more generally, do you know if the pings actually get to your interface? Are they registering if you use `tcpdump -i enp1s0 icmp` ?
[09:39] <JornS> tried adding the on-link-parameter per netplan docs, but I've tried quite a few variations to this without success so far :/
[09:41] <JornS> pings are getting through to the interface: 09:40:15.441275 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 8, seq 2695, length 64
[11:11] <schopin> JornS: on-link means machines on the subnetwork are reachable directly, e.g. are on the same switch as your interface. That's usually incompatible with having a gateway specified.
[11:11] <schopin> At least that's my understanding of it.
[11:15] <schopin> JornS: My understanding of routing tables is somewhat fuzzy, but shouldn't your routing-policy also specify that all traffic *to* <IP_ADDRESS> should use the table 101?
[11:15] <schopin> Hem, to <IP_ADDRESS>/16
[12:37] <JornS> idk, I'm out of ideas - imho this should work, but I'm too dumb to figure it out :/ https://pastebin.com/4UtkzuDZ
[12:38] <JornS> like, the setup is far form complex - it's just a host with two nics, where one would be used for internal traffic, and another one for internet
[12:38] <JornS> shouldn't be _that_ much of an issue to figure out :'(


[00:02] <apachelogger> my kdm is the broken \o/
[00:04] <apachelogger> ok
[00:04] <apachelogger> either my upgrade really went to shit or natty on armel is in a bit of a dead state
[00:05] <apachelogger> doesnt even get a stack -.-
[00:05] <apachelogger> oh well
[00:06] <apachelogger> kernel panic
[00:12] <JontheEchidna> lol @ bug 609247
[00:15] <apachelogger> hm
[00:15] <apachelogger> ehm
[00:15] <apachelogger> uh
[00:15] <apachelogger> bug 689109
[00:16]  * apachelogger considers libpackagekit-qt-14 -> libpackagekit-qt14 at least as disobeyment of the policy
[00:16] <apachelogger> IIRC the policies goes like 'if appending the soversion to the name would confuze the people, make it dashed'
[00:16] <apachelogger> now clearly having it say -qt14 is confusing
[00:18]  * JontheEchidna is worried by the lack of attention to bug 680328 too
[00:21] <apachelogger> cool
[00:21] <apachelogger> bug 689113
[00:21] <apachelogger> he recons that it is shitty that the messages are french
[00:22] <apachelogger> yet he does no bother to translate them
[00:22] <apachelogger> <3
[00:22] <apachelogger> ^ one more reason why cli apps should not be translated anyway
[00:22] <apachelogger> ...
[00:44]  * apachelogger loves how debhelper drags in man-db and thus causes a stupid database building
[00:44] <apachelogger> that takes *ages*
[00:48] <apachelogger> CMake Error at /usr/share/cmake-2.8/Modules/FindKDE4.cmake:98 (MESSAGE):
[00:48] <apachelogger>   ERROR: cmake/modules/FindKDE4Internal.cmake not found in
[00:48] <apachelogger> that is a new ne
[00:48] <apachelogger> *one
[00:48] <apachelogger> I lov eit
[00:48] <apachelogger> makes me wanna thorw up
[00:52] <apachelogger> aha!
[00:52]  * apachelogger is being armed again
[00:53] <apachelogger> Riddell, ScottK: I think kdebase-workspace on armel is utterly broken ... getting segfaults on the mobile and in a qemu pbuilder
[00:53] <apachelogger> or maybe libs in general or something
[00:53] <apachelogger> oh, more like libs
[00:53] <apachelogger> kde4-config also segfaults
[00:54] <Riddell> ug
[00:55] <apachelogger> oh
[00:55] <apachelogger> nvm
[00:55] <apachelogger> seems I ran a maverick base tgz as natty
[00:55] <apachelogger> that is bound to fail
[00:55]  * apachelogger tries again
[01:03] <ari-tczew> apachelogger, Riddell: could you (1 person from you) take a look on clementine review tomorrow? It's not updated yet. I'm ordering sponsor for future. (:
[01:04]  * apachelogger will not have much time tomorrow
[01:05]  * apachelogger wonders how ccache always ends up in pbuilder's PATH
[01:09] <apachelogger> Riddell: ok, it was just me being stupid, not armel being broken
[05:57] <_Groo_> hi/2 all
[05:57] <_Groo_> can anyone confirm that k3b is broken with kde 4.6 beta 2?
[06:06] <_Groo_> nvm, found apachelogger patch for it...
[12:26] <apachelogger> !find X11/SM/SMlib.h
[12:30] <apachelogger> ScottK, mgraesslin: I think for 11.04 we should have a separate package kde-window-manager-gles
[12:31] <apachelogger> that way one can still use kde-window-manager on armel
[12:31]  * mgraesslin agrees
[12:31] <Riddell> apachelogger: what would go into it?
[12:31] <apachelogger> mgraesslin: building right now
[12:31] <apachelogger> Riddell: mgraesslin's opengles enabled kwin
[12:31] <mgraesslin> and please package it also for desktop
[12:32] <apachelogger> mgraesslin: why that?
[12:32] <Riddell> it'll get packaged everywhere, we don't discriminate in our packages generally
[12:32] <mgraesslin> apachelogger: because it's better and the ES backend will on long term become the default one
[12:32] <apachelogger> I see
[12:32] <mgraesslin> Wayland requires ES, so we *need* it
[12:33]  * apachelogger loves wayland already
[12:33] <apachelogger> well then
[12:33]  * apachelogger changes the architecture from armel to any
[12:33] <mgraesslin> I want to tune the CMakeLists.txt to built both kwin-desktop and kwin-mobile
[12:35] <apachelogger> mgraesslin: CMakeFiles/kworkspace.dir/kworkspace.o: In function `~KRequestShutdownHelper':
[12:35] <apachelogger> /tmp/buildd/kwin-gles/libs/kworkspace/kworkspace.cpp:134: undefined reference to `SmcCloseConnection'
[12:36] <mgraesslin> erm
[12:36] <apachelogger> libs&m is installed though
[12:36] <mgraesslin> apachelogger: best you wait till workspace is migrated to git - I will then use a complete clone of workspace
[12:37] <apachelogger> awww
[12:37] <apachelogger> mgraesslin: but I wanted to see if maybe kwin works, even though plasma-mobile refuses too :
[12:37] <apachelogger> S
[12:37] <mgraesslin> strip the patches and apply them to normal workspace
[12:37] <mgraesslin> all commits in the scratch repo are for GLES
[12:39] <apachelogger> oh noes, that sounds like work ^^
[12:40] <apachelogger> cc1plus: error: unrecognized command line option "-fno-strict-volatile-bitfields"
[12:40] <apachelogger> fancy
[12:40] <apachelogger> <3 gcc + qt
[12:40] <mgraesslin> just use git format-patch to extract all commits
[12:41] <apachelogger> k, well, later
[12:41] <apachelogger> gotta run o/
[13:07] <ari-tczew> Riddell: could you review clementine? http://revu.ubuntuwire.com/details.py?upid=8778
[13:11] <Riddell> ari-tczew: ok
[13:12] <ari-tczew> nice!
[15:18] <pgquiles> what will be the default browser in 11.04? rekonq again?
[15:18] <Riddell> that's the plan yes
[15:18] <Riddell> with qtwebkit 2.1
[15:18] <pgquiles> ok
[15:55] <aakshay> where to look for  tarball for kdetoys maverick upstream 4.5.85?
[15:55] <aakshay> please help
[15:57] <Riddell> aakshay: err you already packaged that
[15:57] <Riddell> https://launchpad.net/ubuntu/+source/kdetoys/4:4.5.85-0ubuntu1
[15:57] <aakshay> Riddell: hi.. i packaged for natty 4.5.85..
[15:59] <tsimpson> the tarball would be the same for maverick
[15:59] <aakshay> Riddell: now i would like to package it for maverick
[16:00] <Riddell> yes, just add a new changelog entry with dch -i  and set the version to 4:4.5.85-0ubuntu1~maverick1~ppa1  and the series to maverick (not natty)
[16:00] <Riddell> then build it on maverick to check it works
[16:00] <aakshay> tsimpson: ok. thanks.. :)
[16:01] <aakshay> Riddell: ok.. thanks.. i will buils it also
[16:01] <aakshay> Riddell: can you please tell me how to save the work of chroot login?
[16:03] <aakshay>  how to save the work of chroot login?
[16:04] <tsimpson> aakshay: you need to add the --save-after-login option when entering the chroot
[16:04] <tsimpson> (assuming you mean a pbuilder chroot)
[16:05] <aakshay> tsimpson:  in this command "sudo DIST=maverick pbuilder --login" where i add this?
[16:05] <tsimpson> after the --login part
[16:05] <aakshay> tsimpson:  thankyou... :)..
[16:08] <aakshay> tsimpson:  i made a directory to check it but it removed the build along with the subdirectories.. :(
[17:01] <yofel> aakshay: how exactly are you trying to use pbuilder?
[17:01] <aakshay> yofel
[17:01] <yofel> You should have created a source package with debuild -S and then called pbuilder with pbuilder build XY.dsc
[17:02] <aakshay> yofel:  m trying it for packaging.
[17:02] <aakshay> yofel:  i just want to acess my work after i exit the chroot..
[17:02] <aakshay> yofel: but i thnk it is not possible...??
[17:03] <yofel> aakshay: pbuilder will delete the chroot and the build files after it finished, but copy the built .deb files and the build log to /var/cache/pbuilder/result/
[17:04] <yofel> you use pbuilder to make sure your package builds fine on the launchpad buildds, which requires a clean chroot without any files left over from previous builds
[17:04] <aakshay> yofel:  ok.. i wil do this to save them.. thankyou.. :)
[17:05] <yofel> aakshay: what exactly do you want to do with pbuilder? (or what did you do after dch -i)
[17:05] <aakshay> yofel:  i am packaging kdetoys 4.5.85 maverick....
[17:06] <aakshay> yofel: so i need to save the files like .deb... so i wil first copy them before exit
[17:06] <aakshay> yofel: please tell me one thing
[17:06] <yofel> ok, so you took the natty source package, added a changelog, ran debuild -S and then?
[17:06] <yofel> aakshay: pbuilder will copy those by itself!
[17:07] <aakshay> yofel:  where?
[17:07] <yofel> as I said /var/cache/pbuilder/result/
[17:07] <yofel> if not, please pastebin your ~/.pbuilderrc
[17:08] <aakshay> yofel: its not.. let me add my ~/.pbuilderrc
[17:08] <apachelogger> aakshay: it would be much better if you did not query me but asked int he channel
[17:08] <apachelogger> as I am not available 90% of the time and I guess about half the actual talking people in here have access to the tarballs anyway :)
[17:09] <apachelogger> mgraesslin: maybe I should wait until workspace goes to git ^^
[17:09] <apachelogger> I'll try to get something going tomorrow, otherwise I will just wait
[17:09]  * apachelogger is currently drunk and thus not able to mess with patching
[17:11] <yofel> aakshay: ? (you can install 'pastebinit' and run 'pastebinit ~/.pbuilderrc' as an easy way to pastebin things)
[17:11] <aakshay> Yofel: ok thats better..
[17:11] <aakshay> apachelogger: yes.. thanks..
[17:12] <apachelogger> aakshay: do you have the tarball yet?
[17:12] <aakshay> apachelogger: yes.i got it...
[17:12] <apachelogger> k
[17:13] <aakshay> apachelogger:  :)..
[17:13] <aakshay> yofel: pastebinit ~/.pbuilderrc
[17:13] <aakshay> yofel: http://pastebin.com/SDrHcpe2
[17:14] <yofel> k
[17:15] <yofel> aakshay: look in /var/cache/pbuilder/maverick-amd64/result (if you are on 64bit, else maverick-i386)
[17:15] <aakshay> yofel: what corrections i need to make?
[17:15] <aakshay> yofel: ok
[17:17] <aakshay> yofel: its saying "no such file or directory"
[17:18] <yofel> hm, you have BUILDRESULT="/var/cache/pbuilder/$NAME/result/" though, where name should be something like $distribution-$architecture
[17:18] <yofel> aakshay: sorry phone, be back in a few minutes
[17:19] <aakshay> yofel: sure... :).... wil be waiting..
[17:28] <yofel> aakshay: re
[17:28] <aakshay> yofel: i think its already added:
[17:28] <aakshay> NAME="$DIST" if [ -n "${ARCH}" ]; then     NAME="$NAME-$ARCH"     DEBOOTSTRAPOPTS=("--arch" "$ARCH" "${DEBOOTSTRAPOPTS[@]}") fi
[17:29] <aakshay> yofel: in above code.. NAME is edited
[17:30] <yofel> right, how did you try to build the package?
[17:31] <aakshay> yofel: <debuild> command..
[17:31] <aakshay> yofel: then with debuild -S for source packages..
[17:33] <yofel> and then?
[17:33] <aakshay> and then i get .orig.tar; debian.tar..
[17:33] <yofel> you didn't use a chroot in those steps yet
[17:33] <yofel> right
[17:34] <yofel> (and a .dsc)
[17:34] <aakshay> yofel:  i am working  in a chroot only
[17:34] <aakshay> yofel: yes.. ;)
[17:34] <yofel> wait, you're doing the packaging in a chroot? why that?
[17:35] <yofel> ah, for debuild to build binary packages probably
[17:35] <aakshay> yofel: yes..
[17:36] <aakshay> yofel:  i use chroot only for complete package builing
[17:36] <aakshay> yofel: is this wrong??
[17:37] <yofel> well, that's right, but you seem to do it differently than I do, I do the packaging outside, run debuild -S and then use the chroot with 'pbuilder build XY.dsc'
[17:37] <yofel> now let me check how you can get stuff from within the chroot to the outside
[17:38] <aakshay> yofel:  ok.. yes please..
[17:40] <yofel> aakshay: er wait, that's actually easy, I'm just thinking slowly
[17:40] <aakshay> yofel: :).. no problems...
[17:40] <yofel> aakshay: the system sees your chroot as /var/cache/pbuilder/build/<a number>, just go there from the outside and you can copy stuff from the chroot somewhere else
[17:41] <aakshay> yofel: yups.. this i can do but the result stuff is not done in my system...
[17:42] <yofel> aakshay: didn't 'debuild' build the package? what do you need to do now?
[17:43] <yofel> the package files should be somewhere in /var/cache/pbuilder/build/<a number>/tmp/buildd/
[17:43] <aakshay> yofel: now i have copies simply from /var/cac.......
[17:43] <aakshay> yofel: *copied
[17:44] <yofel> aakshay: ok, do you have the source folder, orig.tar, debian.tar and .dsc now?
[17:44] <aakshay> yofel: i wanna know one more thing, i need dch -i command inside my chroot, but its not installing it
[17:44] <yofel> aakshay: well, usually you don't do that in your chroot
[17:44] <aakshay> yofel: yes i hav these..
[17:44] <aakshay> yofel:  ok
[17:45] <yofel> pbuilder installs the *bare minimum* system, since you usually only use pbuilder once you've finished the packaging
[17:45] <aakshay> yofel: then i wil add changelog outside
[17:45] <aakshay> yofel:  and then build inside chroot..
[17:45] <aakshay> yofel:  this will work correctly then... ;-)
[17:46] <yofel> right, add changelog on the outside, run debuild -S and then build in chroot with 'DIST=maverick pbuilder build ....dsc' - NOT --login
[17:47] <aakshay> yofel: "-NOT --login"..??
[17:47] <aakshay> yofel:  what it means?
[17:47] <yofel> aakshay: you don't usually login to the chroot
[17:47] <aakshay> yofel: okk... this is the thing
[17:47] <yofel> aakshay: that was me telling you not to login, the pbuilder command is: DIST=maverick pbuilder build ....dsc
[17:48] <yofel> where ....dsc is the name of your .dsc file
[17:48] <aakshay> yofel:  i can directly build from outside..i will do this way only now....
[17:48] <aakshay> yofel: thanks for helping me... :)
[17:49] <yofel> aakshay: here's the ubuntu guide for pbuilder, good read https://wiki.ubuntu.com/PbuilderHowto
[17:49] <aakshay> yofel: okiez.. i will read this.. one thing i always confuses in is editing the version
[17:50] <aakshay> yofel: sometimes its 4.5.4 or 4.5.85 which means the same i think..??
[17:50] <yofel> aakshay: no, 4.5.4. is the KDE 4.5.4 release, 4.5.85 stands for 4.6 beta2
[17:51] <aakshay> yofel: ok but is there any written table of such conversions..:p
[17:52] <yofel> aakshay: hm? that naming scheme is kde standard, and your original source file was called kdetoys-4.5.85.tar.bz2 after all
[17:52]  * apachelogger completley forgot about thursday's random facebook friending
[17:52] <apachelogger> oh dear oh dear
[17:52] <apachelogger> yofel, aakshay: are you on the facebook?
[17:52] <yofel> aakshay: as for how debian versions are constructed, like what the '4:' at the beginning means is described in the debian policy
[17:52] <aakshay> apachelogger: yes..
[17:53] <yofel> apachelogger: I have an account, unused
[17:53] <apachelogger> yofel: how do you herd your fans then?
[17:53] <aakshay> apachelogger: i have using active one..
[17:53] <yofel> I have fans? :D
[17:54] <aakshay> yofel:  abd the rest like its 4.6 but still written as 4.5.85...
[17:54] <yofel> apachelogger: yes, since 4.6 isn't released yet, the beta2 is called 4.5.85 so the version number is lower
[17:54] <yofel> aakshay: ^
[17:54] <aakshay> yofel:  i will remeber them nw.. :)
[17:54] <yofel> tab fail :(
[17:54] <aakshay> yofel: :)
[17:55] <aakshay> yofel: okiez... thats nice
[17:55] <apachelogger> aakshay: where can I befriend you on facebook?
[17:55] <apachelogger> yofel: yes I know :P
[17:55] <aakshay> apachelogger: my id is by name "aksahay tayal"
[17:56] <yofel> aakshay: if you want to continue with packaging you might want to read http://www.debian.org/doc/debian-policy/ at one point
[17:56] <yofel> or rather should read it
[17:56] <apachelogger> aakshay: there are three matches
[17:56] <apachelogger> thus my question ^^
[17:56] <apachelogger> actually more
[17:56] <apachelogger> 3 with picture that is ^^
[17:56] <aakshay> i am wearing shorts in pic..:)
[17:57] <apachelogger> I shall hope that I befriended the right person then ^^
[17:57] <apachelogger> oh oh oh
[17:57] <aakshay> apachelogger: got me??
[17:57] <apachelogger> aakshay: check your facebook
[17:57] <aakshay> yofel: i wil read it and implement it.. ;)
[17:57] <apachelogger> you should ahve a friendship request
[17:57] <apachelogger> or  it was random friendshipping with peopel I do not know (again) ^^
[17:58]  * apachelogger apparenlty has to lave for train in a bit
[17:58] <aakshay> yofel: whats your profile name?
[17:58] <aakshay> apachelogger: i have added you.. thanks for sending request.. :)
[17:58] <apachelogger> it would appear that the austrian railway company has cancelled the direct connection from linz to graz
[17:58] <aakshay> yofel: on facebook
[17:58] <apachelogger> adding another 20 minutes to my travel time
[17:58]  * apachelogger loves the austria
[17:58] <apachelogger> hooray
[17:59]  * apachelogger got aakshay as friend \\o/
[17:59] <yofel> let me first try to get my facebook profile, the page looks totally crooked in minefield o.O
[17:59] <aakshay> yofel: ;-O
[17:59] <aakshay> apachelogger: \0/
[18:00] <yofel> aakshay: Philip Muskovac
[18:00] <yofel> now I need to find a usable picture and actually set my account up ^^
[18:01]  * kronos just sent apachelogger a friend request ..
[18:01] <aakshay> yofel: u have lot of fans...:)
[18:01] <apachelogger> hooray
[18:01] <apachelogger> more friends
[18:01]  * apachelogger is not a fand of yofel
[18:01] <apachelogger> :P
[18:01] <apachelogger> actually I am but dont tell him
[18:01] <apachelogger> he will go smug
[18:01] <aakshay> yofel: is your profile has school "Uni Tuebingen"
[18:02] <apachelogger> like shadeslayer
[18:02] <apachelogger> ...
[18:02] <apachelogger> :P
[18:02] <yofel> lol
[18:02]  * apachelogger needs to leave for train
[18:02] <apachelogger> o/
[18:02] <apachelogger> au revior and stuff
[18:02] <yofel> oh, I actually put that in, aakshay: yes
[18:02] <aakshay> lolzzz
[18:02] <aakshay> au revoir
[18:03] <aakshay> yofel: have sent u request.. see your profile... /o
[18:03]  * kronos has more friends than apachelogger .. :P
[18:03] <yofel> accepted, you're the first :P
[18:03] <aakshay> yofel: \o/  congrats!!!
[18:04] <aakshay> yofel: inaugration is successful...:)
[18:09] <aakshay> yofel: i will read all the stuff for packaging now... thanks again..:)
[18:57] <yofel> does anyone know what happened to kdepim 4.4.8 for maverick updates? it's there for lucid, but for maverick only in beta
[19:00] <Riddell> yofel: I didn't upload it and I've not been given anything by anyone else to upload
[19:00] <Riddell> I did lucid because of a canonical customer
[19:01] <yofel> ah, confused someone in #kubuntu that had both maverick and lucid ppa sources since that now tried to mix 4.5.4 maverick with 4:4.4.8 kdepim lucid
[22:42] <apachelogger> ehm
[22:42] <apachelogger> that ALERT thing survey is super buggy
[22:42] <apachelogger> " They doesn't fullfill my needs"
[22:45]  * apachelogger doesnt understand half the questions
[22:45] <apachelogger> ...
[23:39] <apachelogger> cool
[23:39] <apachelogger> pbuilder sets up ccache
[23:39]  * apachelogger loves how that abomination of a bash script manages to do just the thing to piss of apachelogger