[00:19]  * assasukasse is away: Im leaving, query me.
[00:19] <m1ke> What is your opinion towards Sabayon ?
[00:37] <hydrogen> horrible.
[03:54] <compwiz18> did anyone else's X stuff get borked with that last update?
[04:18] <Hobbsee> compwiz18: the silly people who shouldnt be running hardy are in that corner. please join them.
[04:18]  * Hobbsee points
[04:18] <bazhang> haha
[04:24] <compwiz18> I know, it's on the test laptop
[04:25] <compwiz18> and of course, since the topic says "Don't run hardy, it probably doesn't work" naturally, I had to install it.
[04:25] <bazhang> :}
[04:36] <nrp> heh, when an update tells you its about to remove xserver-xorg and everything related to it, its usually not a good idea to choose Y
[04:39] <compwiz18> true
[04:40] <compwiz18> I remember reading that and wondering why they were removing all the xorg stuff
[04:41] <compwiz18> it still starts, but I think xorg.conf got screwed up
[04:57] <Hobbsee> compwiz18: of course, yes.
[04:57]  * Hobbsee is asking for a bump of the xserver packages, so that X is fully installable again
[04:58] <Hobbsee> [14:52] <Keybuk> breaking hardy is to be expected ;)
[04:58] <Hobbsee> [14:52] --> DShepherd has joined this channel (n=dwight@<IP_ADDRESS>).
[04:58] <Hobbsee> [14:52] <Hobbsee> Keybuk: well, of course :)
[04:58] <Hobbsee> [14:52] <Keybuk> if you're running hardy now, you're crazy
[04:59] <Hobbsee> perhaps that should go in the topic
[05:01] <compwiz18> heh
[05:02] <compwiz18> I'm crazy then xD
[05:02] <hydrogen> okay..
[05:02] <hydrogen> its not really worth bragging about
[05:04] <Hobbsee> right.  priority bumped.  waiting time.
[05:23] <shirish> hi all, can somebody tell me http://ubuntuforums.org/showpost.php?p=3690461&postcount=7
[05:24] <shirish> quote from the post "ou go trough apt-get update and download packages but don't upgrade then you go to the update-manager and it downloads more 13 packages that apt-get didn't considered so it is better use update-manager cause they are not synchronized yet."
[05:25] <Hobbsee> shirish: the guy's on crack.
[05:25] <Hobbsee> shirish: it's held back packages - apt will let youf orce them, update-manager wont.
[05:26] <Hobbsee> he's just too much of a git to realise, and should nto be running gutsy
[05:26] <shirish> Hobbsee: ok cool
[05:27] <Hobbsee> er, hardy.
[05:29] <shirish> Hobbsee: This is the way I'm seeing apt-get dist-upgrade is showing me, http://pastebin.ca/760667
[05:29] <shirish> I can see that xserver-xorg all stuff will not be there. line 7 onwards,
[05:30] <shirish> Hobbsee: any comments or suggestions would be welcome.
[05:30] <Hobbsee> shirish: only that you shouldnt upgrade if you cant do it cleanly, and if you dont know what your'e doing.
[05:31] <shirish> that I have never known :)
[05:32] <Hobbsee> if you wait a fe wmore hours, it should all be installable again
[05:32] <Hobbsee> and..
 breaking hardy is to be expected ;)
 if you're running hardy now, you're crazy
[05:33] <shirish> Hobbsee: thanx but then i was born crazy ;)
[05:33] <shirish> Hobbsee: till l8ter, thanx for guiding me :)
[05:42] <bazhang> great new topic
[05:59] <Laser88> Moin!
[08:49] <se7en^Of^9> is someone already running hardy?
[08:49] <rsk> most likely
[08:49] <Hobbsee> yeah
[08:50] <se7en^Of^9> any problems?
[08:50] <Hobbsee> dude.  if you have to ask....
[08:50] <Hobbsee> some, yes.
[08:51] <se7en^Of^9> ok thanks i give it a try
[08:51] <Hobbsee> then you should not run hardy.
[08:51] <Hobbsee> X is partially broken.
[08:52] <se7en^Of^9> i can live with that
[08:53] <Hobbsee> strange.
[08:53] <Hobbsee> okay then.
[08:57]  * Hobbsee figures "what the hell", and says yes to the upgrade
[08:57] <bazhang> haha
[08:57] <bazhang> love the new topic Hobbsee
[09:01] <Hobbsee> oh, sigh
[09:04] <Hobbsee> okay, i *didnt* want to do this.
[09:04] <bazhang> upgrade?
[09:05] <Hobbsee> no, go thru the x transition in the middle.
[09:05] <bazhang> oh. sorry.
[09:06] <Hobbsee> Resolving dependencies...
[09:06] <Hobbsee> Unable to resolve dependencies!  Giving up...
[09:06] <Hobbsee> Abort.
[09:06] <Hobbsee> haha :)
[09:07] <bazhang> well you'll be the one to go to in a month or so..thanks for the sacrifices you are making now
[09:13] <Hobbsee> i thought with evertyhing built, it might just work
[09:13] <bazhang> I was going to say go-to guy, but nixternal set me straight.. :}
[09:16] <Hobbsee> heh
[09:17] <bazhang> :}
[09:17]  * Hobbsee waits for these debs to transfer over.
[09:21]  * Hobbsee ponders downloading a gutsy final ISO, just in case.
[09:21] <Hobbsee> Fujitsu: this stuff really does break :P
[09:23] <Fujitsu> Hobbsee: I decided to try to resolve it this morning, but managed to break it, but was able to revert by manually reinstalling the old bits and pieces.
[09:23] <Hobbsee> Fujitsu: that's what i'm about to ry
[09:23] <Hobbsee> *try
[09:24] <Hobbsee> trouble is, i deleted my aptcache too :)
[09:24] <Fujitsu> Mine wasn't in the apt-cache, so I just downloaded the stuff from LP.
[09:26] <Hobbsee> oh, need old xserver-xorg too
[09:26]  * Hobbsee scp's that too
[09:26] <Fujitsu> xserver-xorg, xserver-xorg-core, xserver-xorg-video-intel, xserver-xorg-input-whateveryouuse.
[09:27] <Hobbsee> yup
[09:30] <Hobbsee> Fujitsu: erm?  how am i supposed to get xserver-xorg, when it's the same version in gutsy and hardy, according to LP?
[09:31] <Hobbsee> oh, i see
[09:34] <level1> Hobbsee: did you just try to upgrade to hardy?
[09:34] <Hobbsee> level1: no
[09:34] <Hobbsee> i went thru the X breakage, to see if it was actually fixed.
[09:34] <level1> I wondering if its a stable enough state that I want to get it
[09:34] <level1> oh, I see
[09:35] <Fujitsu> level1: If you're wondering that, it's not.
[09:35] <Hobbsee> you dont.
[09:38] <Hobbsee> oh, interesting.  new LP feature
[09:38] <Hobbsee> LP has decided it's necessary to show depends, conflicts, etc.
[09:40] <Hobbsee> WTH?
[09:40]  * Hobbsee swears this is circular dependancies.
[09:43] <Hobbsee> Fujitsu: which order did you use to attempt to install this?
[09:43] <Hobbsee> dpkg is being dumb.
[09:43] <Fujitsu> Hobbsee: I think I removed everything, then install everything at once...
[09:44] <Fujitsu> I might have used a --force-depends at one point.
[09:44] <Fujitsu> But it's all OK now.
[09:44] <Hobbsee> hehe
[09:44] <Hobbsee> i'd forgotten abotu --force-depends
[09:44] <Hobbsee> this stuff looks circular, so that's not a bad idea.
[09:44] <Hobbsee> or at least, semi-circular
[09:45] <Fujitsu> It is sorta, yeah.
[09:45] <Fujitsu> Though if you remove everything and install all the old versions, I think it's OK.
[09:45] <Fujitsu> I forget, it was 12 hours ago.
[09:46] <Hobbsee> I WIN!!!
[09:46] <Hobbsee> Fujitsu: eventual solution:  downloaded the bits, let aptitude install the null driver, so that it can get -core installed, so that the -input and -video can get installed, so that you can then go and install xserver-xorg, xorg, and then ubuntu-desktop
[09:46] <Fujitsu> Ahhhh.
[09:47] <Fujitsu> I didn't think about that second step.
[09:47] <Hobbsee> core depends on the input and video, but input and video won't configure without -core installed.
[09:47] <Hobbsee> sounds like circular depends for anyone who removes core.
[09:47] <Fujitsu> Yep.
[09:47] <Hobbsee> which most wont do
[09:47] <Hobbsee> but i think that's a bug.
[09:47] <Hobbsee> you shouldnt *have* circular deps like that at all, to my knowledge
[09:47] <Fujitsu> core doesn't depend on input, does it?
[09:48] <Hobbsee> erm, apparently not.  but xserver-xorg will
[09:48] <Fujitsu> It's still a mess and silly.
[09:48] <Hobbsee> yup
[09:48] <Hobbsee> root@LongPointyStick:/var/cache/apt/archives# show xserver-xorg | grep input
[09:48] <Hobbsee> 11:Depends: xserver-xorg-core (>= 2:<IP_ADDRESS>.dfsg-3), xserver-xorg-video-all | xserver-xorg-video-1.0 | xserver-xorg-video, xserver-xorg-input-all | xserver-xorg-input, debconf (>= 0.5) | debconf-2.0, xkb-data | xkb-data-legacy, xbase-clients
[09:49] <Fujitsu> I guess it does make a bit of sense to have the server depending on them, as it's useful without them.
[09:49] <Fujitsu> But it makes things a bit difficult if they break.
[09:50] <Hobbsee> well, true.
[09:52] <Fujitsu> Erm, s/useful/not useful/
[09:52] <Hobbsee> oh, it's shift+f9 to make the water go away.
[09:52] <Hobbsee> not shift+f8
[09:53] <Hobbsee> Fujitsu: do i want to hold back x11-data, or is that OK?
[09:53]  * Hobbsee doesnt remember
[09:53] <Fujitsu> That's OK.
[09:54] <Hobbsee> right.  fixed. :)
[09:55] <Hobbsee> erm
[09:55] <Hobbsee> ah.  it's just lagging
[09:56] <Fujitsu> ?
[09:56] <Hobbsee> compiz is taking up 90% of cpu
[09:57] <Hobbsee> right.  that's better
[09:57]  * Hobbsee --> dinner
[10:03] <cyphase> Anyone know anything about plans to have a "guest" account in Hardy, e.g. you can logon, do whatever, and when you log off, everything is purged?
[10:08] <Fujitsu> cyphase: I do not know of any, so there probably aren't any.
[10:08] <cyphase> Fujitsu: i suppose you know everything
[10:08] <cyphase> Fujitsu: ;)
[11:06] <neztiti> can someone give me new source.list??
[11:18] <Hobbsee> neztiti: you dont want it.
[11:27] <scizzo-> good topic.. :)
[11:38] <Hobbsee> scizzo-: :)
[11:38] <Hobbsee> scizzo-: was thinking of adding "the idiot corner is over there"
[11:42] <bazhang> :}
[12:44] <compwiz18> "the idiot corner is over by compwiz18" :P
[12:54] <Hobbsee> heh
[13:03] <IdleOne> Hobbsee: if I want to make a wish/ feature request for a package I just add Wish to the bug report?
[13:04] <Hobbsee> IdleOne: what are you wanting a feature for?
[13:04] <IdleOne> xchat
[13:04] <IdleOne> want the upload/download window to be hidden or minimized
[13:04] <IdleOne> or at least the ability to do so
[13:05] <Hobbsee> better to file it in the gnome bugtracker then
[13:05] <IdleOne> url?
[13:11] <Hobbsee> bugs.gnome.org or something?
[13:36] <IdleOne> Hobbsee: filling with gnome bugtracker assumes that I am using xchat-gnome. I run xchat-common I did file a bug anyway because I believe the same issue exists in xchat-gnome but filed with launchpad also
[13:37] <Hobbsee> IdleOne: fair enough.  ubuntu people will just foward it to xchat people, so you may as well do it for them :)
[13:38] <IdleOne> xchat people dont seem to want to fix that seems they like the fact that the winodw covers the chat windows lol
[13:38] <Hobbsee> hooray.
[13:38] <Hobbsee> silly people :)
[13:38] <IdleOne> heh
[13:39] <IdleOne> well guess if it gets fixed it gets fixed if not I will have to live with it
[19:57] <Vegar> will hardy use 2.6.23?
[19:58] <ompaul> hope is for 24 to be in there
[19:59] <sebsebseb> seems  Gutsy is quite a buggy release here and there.  and hardy is probably hardly worth trying in a  VM inside Gutsy,  at the moment?  for a non  developer, because it's very alpha?
[20:04] <ompaul> well you can see it progress if you want
[20:05] <sebsebseb> is hardly at the moment based on Gutsy?
[20:05] <ikonia> sebsebseb: its messy as heck at the moment unless you comfortable with how the distro is packaged together
[20:05] <sebsebseb> I mean basically
[20:05] <sebsebseb> Gutsy with some changes?
[20:05] <ikonia> sebsebseb: no
[20:06] <sebsebseb> how the distro is packaged together?  how differnet components work with each other?
[20:06] <ikonia> yes, versions dependencies and needs and what needs to be where to work
[20:07] <sebsebseb> Gutsy to me seems like hardly an upgrade from Feisty really.  and  pft found what seems to be a bug and this one does effect me a lot
[20:07] <ikonia> thats just opinions
[20:07] <ompaul> !components
[20:07] <ubotu> The packages in Ubuntu are divided into several sections. More information at https://help.ubuntu.com/community/Repositories and http://www.ubuntu.com/ubuntu/components - See also !EasySource
[20:07] <sebsebseb> Gutsy just seems like  a  newer version of Firefox  Pidgin instead of Gaim and  there is Apparmour and  whatever under the hood stuff that I don't know about
[20:07] <ompaul> !timebasedreleases
[20:07] <ubotu> Ubuntu releases a new version every 6 months. Each version is supported for 18 months to 5 years. More info at http://www.ubuntu.com/ubuntu/releases & http://wiki.ubuntu.com/TimeBasedReleases
[20:08] <ompaul> sebsebseb, if you want stability you use the LTS
[20:08] <sebsebseb> yes
[20:08] <sebsebseb> and Hardly is the next LTS
[20:08] <sebsebseb> I know
[20:08] <Vegar> when can I expect to see 2.6.23 in hardy?
[20:09] <sebsebseb> stability lol I expect a  distro to be able to get the names right of a CD
[20:09] <sebsebseb> the track names
[20:09] <sebsebseb> and not come up with unknown
[20:09] <sebsebseb> whatever distro :)
[20:09] <sebsebseb> surely something like that,  is quite basic to do?
[20:09] <sebsebseb> Feisty put a CD in and yeah  it would get the names right
[20:10] <sebsebseb> why do I care that it detects the names of the tracks on the CD?  ,because I have last.fm profile
[20:10] <sebsebseb> and so yeah the names get submitted
[20:10] <sebsebseb> when I listen to that track
[20:10] <ompaul> they are packages that are in gnome one of the main sub components
[20:10] <ompaul> so if you don't like the gnome way use kde
[20:10] <ompaul> it went though a lot of changes for version 4
[20:11] <sebsebseb> the part that tells Rythombox and soundjuicer what the tracks on the CD is called is part of Gnome?
[20:12] <sebsebseb> I never liked KDE much,  except for Konversation and K3B  basically
[20:12] <sebsebseb> however
[20:12] <sebsebseb> by what I read and what screenshots I have seen of KDE 4
[20:12] <sebsebseb> it seems it  is going to be a lot better
[20:12] <sebsebseb> and maybe it will become my main  desktop environment instead of Gnome
[20:12] <ompaul> sebsebseb, that part is a database that is queried
[20:12] <sebsebseb> and I assume Hardly will be suppourting KDE4 by default?
[20:13] <sebsebseb> which part the bit that tells the player what names are on the CD?
[20:14] <ompaul> sebsebseb, well given that http://www.kubuntu.org/ kubuntu 4 beta something is in use now as long as kde get 4 out the door then it will be there
[20:14] <ompaul> sebsebseb, the database it queries
[20:14]  * ompaul urges self not to repeat
[20:15] <sebsebseb> ok so it reads a database that says what  the names of the tracks are on the CD
[20:15] <sebsebseb> and then it should tell the player that
[20:15] <ompaul> yes
[20:15] <sebsebseb> and then it displays that in the player
[20:15] <sebsebseb> however this is not happening in Gutsy
[20:15] <sebsebseb> 99% of the time
[20:15] <sebsebseb> it seems now
[20:15] <ompaul> as long as you are connected to the interweb
[20:15] <sebsebseb> and yes when connected to the Internet as well
[20:16] <ompaul> so what you might want to do is eject the cd and put it in again shortly afterwards
[20:16] <sebsebseb> yes done that
[20:16] <sebsebseb> re booted the computer turned it on back on again blah blah.  logged out of the account and back in again so on
[20:16] <sebsebseb> ejected the CD
[20:16] <sebsebseb> put it back in again
[20:16] <sebsebseb> told it to play,  when it said unknown and it don't change
[20:17] <sebsebseb> after a lot of trying to get it to show the names,  I got it showing the names,  but  one of the tracks wasn't called the right one.  and two of the others didn't have the right name
[20:17] <ompaul> sebsebseb, maybe that entry is not there
[20:17] <ompaul> in the DB
[20:17] <sebsebseb> I tryed differnet CD's also
[20:17] <sebsebseb> and no luck with getting any of the others to say the names of the tracks yet
[20:18] <sebsebseb> is it a bug?  or just something screwed with my set up hummmmmm
[20:18] <ompaul> why don't you look up launchpad.net
[20:19] <sebsebseb> not tryed Vista yet again with the CD's
[20:19] <sebsebseb> ,but I expect that will work fine still
[20:19] <sebsebseb> I am on the bugs thing on launchapd
[20:19] <sebsebseb> ,but that's quite confussing to me
[20:19] <sebsebseb> to me it seems rather geek,  and then it's like,  how would I find out if someone has done a bug report for the thing I am on about and blah blah
[20:20] <sebsebseb> I might have to revert to playing  my CD's on this computer in Vista,  or inside Gutsy in some VM hummmmm
[20:20] <sebsebseb> well that's a bit silly
[20:20] <sebsebseb> they should just work with the names showing
[20:20] <sebsebseb> in Gutsy
[20:20] <ompaul> well then #ubuntu+1 seems to not really sit you as a type of user
[20:20] <ompaul> s/sit/suit
[20:20] <sebsebseb> maybe in a way this is the wrong channel yes
[20:20] <sebsebseb> ,but
[20:20] <ompaul> it is for those testing the next version
[20:21] <sebsebseb> yes I know
[20:21] <sebsebseb> and if what I am having in Gutsy is a bug
[20:21] <ompaul> and if you won't meet the people half way by learning to use launchpad.net
[20:21] <sebsebseb> I hope it won't be in the next one :)
[20:21] <bazhang> is this #ubuntu+1 or #ubuntu-offtopic ? lol
[20:22] <sebsebseb> I  have used launchpad before to order CD's and  maybe I did some sort of bug report or that was some where else
[20:22] <sebsebseb> ages ago
[20:22] <ompaul> bazhang, no longer sure myself
[20:22] <bazhang> ahaha
[20:23] <sebsebseb> I find this a joke that Gutsy won't just  show the names of the CD  tracks
[20:23] <sebsebseb> something as simple as that
[20:23] <sebsebseb> oh yeah and by the way if anyone cares, I tryed out Gutsy when it was being developed
[20:24] <ikonia> ?
[20:24] <sebsebseb> yes had some issues,  but   that was alright nothing major,  untill a kernel update and my sound no longer worked.  there was some bugs or wahtever,  but it was alpha so yeah
[20:24] <sebsebseb> I accepted that
[20:24] <sebsebseb> ended up going back to Feisty :)  then  upgrading to RC of Gutsy and yeah.
[20:25] <sebsebseb> and  after having computer on.  it crashed on me and stuff like that.  not sure why.  and now this CD names thing hummmmmmm
[20:25] <sebsebseb> maybe it is a butg
[20:25] <sebsebseb> I guess it's worth trying to find out yes
[20:25] <sebsebseb> rather then just doing some bug report,  assuming that it is a bug
[20:26] <sebsebseb> and I hope Hardy will be quite a lot better release.  i'll try it eventaully and watch it being developed in VM yeah.  that way if things screw up oh well
[20:27] <sebsebseb> being ignored now?  it seems ok.  well I was off topic anyway in this channel
[20:29] <sebsebseb> #ubotu
[20:35] <ikonia> your not being ignired
[20:35] <ikonia> ignored
[21:51] <Myrth[home]> hi, what means "HDIO_SET_DMA failed: Inappropriate ioctl for device" ?
[23:48]  * assasukasse is away: Im leaving, query me.


[01:54] <SteveH0> I have a dying hard drive (hardware errors) and after I reinitialize a replacement, I'd like to know what the easiest method would be to move the old configuration and data (shows) onto the new drive. Any assistance would be most appreciated!
[02:18] <Hydr0p0nX> dd
[02:19] <SteveH0_> I have a dying hard drive (hardware errors) and after I reinitialize a replacement, I'd like to know what the easiest method would be to move the old configuration and data (shows) onto the new drive. Any assistance would be most appreciated!
[02:19] <Hydr0p0nX> dd
[02:21] <SteveH0> Thanks for the comment about dd, but as I said, the drive is dying.  I'm really looking for which directories or files I need to try to move.
[02:22] <Hydr0p0nX> just worried about recordings ?
[02:23] <SteveH0> some about the shows, but also my canned searches.
[02:26] <Hydr0p0nX> then, database backup + your media directory
[02:29] <Hydr0p0nX> i use dd or ddrescue in those cases though
[02:29] <Hydr0p0nX> and I just dealt with it a few months back
[02:32] <SteveH0> Not sure about db backup?  Is this a MySQL thing?  (Sorry, my SIL called to wish me happy veterans day)
[02:42] <Hydr0p0nX> yep
[02:44] <Hydr0p0nX> http://www.mythtv.org/wiki/Backup_your_database
[02:44] <SteveH0> OK, I see the recordings at /var/lib/mythtv.  I'll look at your link.
[02:46] <Hydr0p0nX> once you have those backed up
[02:46] <Hydr0p0nX> try a dd or ddrescue
[02:46] <Hydr0p0nX> you might be able to get everything mirrored
[02:48] <Hydr0p0nX> dd is just, dd if=/dev/src of=/dev/dest
[02:48] <Hydr0p0nX> ddrescue is covered pretty well here: http://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html
[03:58] <SteveH0> Hydr0p0nX: Thanks!  I have made several back ups, and have stored at least one off the dying drive.
[14:08] <qwebirc17277> I've installed mythtv on top of ubuntu 12.04.1, and for some reason, when mythfronted starts up, my keyboard doesn't work until I click the mouse - any ideas?
[15:14] <skd5aner> superm1: ping, you around?
[15:14] <superm1> Yep
[15:15] <skd5aner> hey, had a quick question about the current upstart script you guys use...
[15:16] <skd5aner> I can't seem to get it to work for me - I run vanilla ubuntu server, and had used an older version of the script you posted to the wiki for probably 3+ years...
[15:17] <skd5aner> however, I tried to pull in the changes from the latest you have in the packaging folder on git, but now whenever I try to do a "service mythtv-backend start", it basically just hangs and never launches mythbackend - any ideas?  I'm not exactly sure how to even troubleshoot upstart
[15:18] <skd5aner> superm1: ^ :)
[15:19] <superm1> skd5aner: which version of ubuntu?
[15:19] <skd5aner> 12.10
[15:19] <superm1> ok so not the super newest version of upstart at least
[15:20] <superm1> and i'm assuming you're using master version of packaging and master mythtv too?
[15:20] <skd5aner> nope, but I am considering upgrading to 13.10 probably sometime soon
[15:20] <skd5aner> 0.27-fixes
[15:20] <skd5aner> for both
[15:20] <superm1> Oh ok
[15:21] <skd5aner> sorry - I thought I mentioned...
[15:21] <skd5aner> I compile mythtv from source :)
[15:21] <skd5aner> I don't actually use mythbuntu, but I do like to mirror some of things you guys do (like upstart) :)
[15:21] <superm1> right i knew you compiled from source, just wasn't sure what you were compiling these days
[15:21] <skd5aner> gotcha :)
[15:21] <superm1> so have you already tried to make sure those pre-start parts work?
[15:22] <skd5aner> I'm wondering if that's actually the problem...
[15:22] <skd5aner> just a quick sec
[15:22] <superm1> i mean it should only hang for 15 seconds or so if the pre-start part fails
[15:22] <superm1> but mythbackend also wouldn't start
[15:24] <skd5aner> here's what the script looks like
[15:24] <skd5aner> yea, I've waited for several mins just to make sure I wans't impatient, heh
[15:25] <skd5aner> http://pastebin.com/Wk3gC7g0
[15:25] <skd5aner> actually
[15:26] <skd5aner> I commented out that pre-start section just to test
[15:26] <skd5aner> and it still doesnt' work
[15:26] <superm1> oh ok
[15:26] <superm1> and already tried to comment out the ulimit change?
[15:26] <skd5aner> well, hang on... :P
[15:26] <skd5aner> I hadn't tried to work on this in about a month
[15:26] <skd5aner> so I forgot where i left off...
[15:26] <skd5aner> lol
[15:27] <superm1> and the other change you have is syslog logging, idk does that syntax still work in 0.27?  i know we had to make changes for syslog7
[15:28] <superm1> if neither of those yield anything, next thing you should go investigate is /var/log/upstart and see if there is a myth related log sitting in there
[15:29] <skd5aner> ok, ok...
[15:29] <skd5aner> I remember sorta where I left off - sorry for mumbling through my self-made confusion here...
[15:29] <skd5aner> the version I sent you is from my slave backend... I commented out the pre-startup stuff because I don't have mysql on that machine...
[15:30] <skd5aner> my mbe is in the process of rebooting and has still not come backonline, I think it's checking disks...
[15:30] <skd5aner> superm1: yea, that log was very vauge...
[15:30] <skd5aner> also, I don't use syslog, that was one of the differences I made in the script, I output to a file
[15:30] <superm1> ah
[15:31] <skd5aner> I made only a very few slight tweaks... 1) path to mythbackend was slightly different, and 2) syslog to logfile/path
[15:31] <superm1> well if /var/log/upstart isn't too useful when the MBE comes up, you can --verbose to your kernel command line to get upstart into a more verbose mode (http://upstart.ubuntu.com/wiki/Debugging)
[15:31] <skd5aner> beyond that, it's almost identical
[15:32] <skd5aner> k, let me see where I get... it had stumped me for quite a while and I just gave up and started using the CLI to launch mythbackend in the interim :/
[15:32] <skd5aner> thanks for the leads, I'll keep you posted
[15:32] <superm1> sure
[15:33] <skd5aner> also, thanks for all the hard work on mythbuntu!  I'm possibly going to be implementing a new frontend soon and I think I'll just go the straight mythbuntu route this time :)
[15:34] <superm1> awesome :)
[15:34] <superm1> if your timing lines up with our 14.04 ISOs starting to stabilize it would be great to have a live tester on them
[15:34] <superm1> right now they're a bit of a mess since the installer switched to python3 and not everything is ported yet for the mythbuntu apps
[15:40] <skd5aner> superm1: cool - I'll let you know, it may be at least until Christmas before I'd even consider spending money on hardware
[15:40] <skd5aner> funds are tied up for other reasons this time of year :)
[15:42] <skd5aner> superm1: ok, ran to the basement and my mbe had a kernel panic during reboot (odd)... just came back up...
[15:42] <skd5aner> superm1: so, during boot, the upstart script appears to work.  Mythbackend is running....
[15:42] <superm1> cool on the new HW, that's closer to when i'll have more contiguous free time to be fixing 14.04 stuff anyhow
[15:43] <skd5aner> however, when I do a service mythtv-backend stop, nothing happens
[15:43] <superm1> can you pastebin the script as it is?  are you maybe missing some fork or --daemon or exec lines?
[15:43] <superm1> we did make some changes there specifically in the past months
[15:44] <skd5aner> http://pastebin.com/HCpZs40C
[15:45] <superm1> yep you're missing the exec command at the start of your mythbackend call
[15:45] <skd5aner> omg
[15:45] <skd5aner> UGH!
[15:45] <superm1> haha, it's always the small things!
[15:47] <skd5aner> superm1: good eye, but I definitely feel like I have egg on my face now
[15:47] <skd5aner> I swear it had to have been something like that at first and thought I went through it with a fine tooth comb line by line
[15:48] <skd5aner> made the change, trying now
[15:49] <skd5aner> hmmmm
[15:49] <skd5aner> not sure that "fixed it"
[15:49] <superm1> you'll need to reboot most likely
[15:49] <superm1> we made that change because upstart was getting in this weird state where it couldn't properly track processes
[15:49] <skd5aner> ah
[15:50] <skd5aner> k, rebooting
[16:15] <skd5aner> superm1: works after a reboot!
[16:15] <skd5aner> thanks superm1, really... that was starting to get under my sking, thanks for the second set of eyes :S
[16:15] <superm1> woot. sure glad to help
[16:15] <skd5aner> s/sking/skin
[16:19] <skd5aner> superm1: out of curiosity... if mythbackend were to segfault, would the upstart script attempt to relaunch?
[16:19] <superm1> Yep
[16:20] <skd5aner> ok, that's great news!
[16:20] <superm1> that's what that respawn thing should do for you
[16:20] <skd5aner> Right now, mythbackend segfaults for me every morning... I've got a couple bug reports in
[16:20] <superm1> if it respawns more than twice within 3600 seconds though it won't do it again
[16:21] <skd5aner> gotcha
[16:21] <skd5aner> that makes sense given the context of the script
[16:21] <skd5aner> I thought that's what those lines did, but I know very little about upstart :)
[16:23] <superm1> yeah it's one of the big benefits imo on how it does process tracking and can do that
[16:23] <superm1> we do the same thing with mythfrontend with a wrapper around it
[16:23] <superm1> for 14.04 we might actually make mythfrontend an upstart tracked job though too since it can track user jobs in 14.04
[17:13] <skd5aner> superm1: yea, I "borrowed" your idea for mythfrotnend too... I used to use gdm with an .xsession, and when mythfrontend died, it'd restart the gdm session.  However, when I switched to lightdm, it didn't handle the auto-login as gracefully
[17:14] <skd5aner> superm1: so, I saw how you guys did it with the loop and now it's rediculously quick to recover
[17:14] <skd5aner> that's been a very welcome addition
[17:15] <Jay2k1> how cool is that
[17:16] <Jay2k1> i mapped a shell script to the power button on my remote which does a killall mythfrontend.real and then starts it again because it freezes every now and then
[19:12] <qwebirc66608> Hello room
[20:53] <TandyUK> hey guys having issues with one of my frontends
[20:54] <TandyUK> several of my channels show up as unknown(unknown) on the frontend, with no channel data.  If i watch it however, i am viewing the correct channel
[20:54] <TandyUK> if i access mythweb however, all listings are present and correct
[20:55] <TandyUK> i have 2 frontends and one backend, both frontends have the problem
[20:56] <TandyUK> any idea what is wrong?


[04:28] <lempel> ...
[07:36] <happyaron> ypwong JackYu http://www.ubuntu.com/download/ubuntu-kylin-zh-CN
[07:36] <JackYu> ok


[02:48] <psusi> anyone know anything about g_udev_device_get_sysfs_attr?  it seems to cache the attribute the first time it is read and never re-reads it
[05:31] <pitti> Good morning
[05:32] <Logan_> hey pitti
[05:37] <Logan_> quilt patches that delete files make me (and bar) sad
[05:37] <Logan_> *bzr
[05:39] <mterry> stgraber, the lxc autopkgtests seem to be failing?
[05:41] <stgraber> mterry: they sometimes do that but usually end up passing, if they're now all failing, that's because something somewhere regressed
[05:42] <mterry> stgraber, I don't know about all failing.  I just noticed it holding up a cgmanager update: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html  - looks like the unpriv tests failed?
[05:42] <mterry> stgraber, if that's the sort of thing that might pass if retried, I can do tht
[05:43] <stgraber> mterry: hmm, no, retrying won't help with that one, we apparently switched to 3.15 and we need some upstream fix for that. I'll cherry-pick and upload in a bit
[05:44] <mterry> stgraber, oh cool, glad it's a known issue  :)
[05:45] <stgraber> mterry: yeah, the 3.15 kernel now prevents reading some files to non-root users...
[07:16] <infinity> @pilot in
[07:53] <timchen119> hi, I found lp:ubuntu/python-debian is not sync with lp:python-debian , anyone know how do I help? any wiki page describe this sync process?
[07:54] <timchen119> last commit in lp:python-debian is 2012-10-08, but it still not in Utopic.
[08:27] <zbenjamin> cjwatson: ping, is there any directory i can put a file that i can read from inside confinement? i get permission denied for /tmp
[08:38] <sarnold> zbenjamin: hopefully this can help: https://wiki.ubuntu.com/SecurityTeam/Specifications/ApplicationConfinement/Manifest
[08:40] <cjwatson> zbenjamin: yep, security team for confinement questions :)
[08:50] <zbenjamin> sarnold: thx
[08:56] <zbenjamin> sarnold: i'm working on debugging confined apps. What i need to do is run gdbserver inside a click package so i can connect to it
[08:58] <sarnold> zbenjamin: I suspect the ptrace attach will fail; why not run gdb 'outside' the click package?
[08:58] <zbenjamin> sarnold: how should i connect to the application running inside then?
[08:58] <zbenjamin> sarnold: attaching is no option, it would make it impossible to debug the application startup
[08:59] <sarnold> zbenjamin: that's a fine question.
[09:00] <zbenjamin> sarnold: also we need a way to connect to the qmljs debugger which always runs inside the app and opens a port so the IDE can connect to it
[09:00] <zbenjamin> sarnold: i guess we will need a debug policy that allows this stuff
[09:01] <sarnold> zbenjamin: what kind of port? tcp would be currently unmediated, that ought to work fine today.
[09:02] <zbenjamin> sarnold: i think its tcp
[09:02] <zbenjamin> sarnold: thats basically the wrapper script that sets up the stuff inide the confinement : http://pastebin.ubuntu.com/7519903/
[09:02] <sarnold> zbenjamin: ah, good. so that means qmljs ought to work ..
[09:03] <zbenjamin> sarnold: thats how it fails: http://pastebin.ubuntu.com/7519911/
[09:04] <sarnold> zbenjamin: I think that script would work alright from outside confinement though
[09:05] <zbenjamin> sarnold: yeah but i was told we want to debug our apps in confinement because we need to be as close as possible to the real environment a app gets
[09:06] <sarnold> zbenjamin: yeah, I can understand that desire. I'm not sure how well it'll work though.
[09:07] <zbenjamin> sarnold: so gdbserver will listen on a tcp port as well, the only thing that needs to be sorted out is the ptrace call you mentioned. Any idea how we can get there?
[09:07] <zbenjamin> i'm actually not really sure if the failure i see is because of that, i get permission denied but the exception still happens in python.
[09:08] <sarnold> zbenjamin: yeah, that's a simple denied for exec(gdbserver), they'll get worse and scarier once that execute is allowed. :)
[09:10] <zbenjamin> sarnold: can i allow that call somehow?
[09:12] <sarnold> zbenjamin: if you edit the generated apparmor policy (in /var/lib/apparmor/profiles/) and then install that updated policy, you can probably get there
[09:13] <zbenjamin> sarnold: how about providing a debug policy ? The store would need to reject that of course
[09:13] <sarnold> zbenjamin: you -might- get lucky if you add /usr/bin/gdbserver Ux, permissions to your policy
[09:13] <sarnold> zbenjamin: yeah, that's a really good idea
[09:14] <zbenjamin> sarnold: can you help me put one together?
[09:14]  * zbenjamin <-- app armor noob
[09:14] <sarnold> zbenjamin: sure
[09:15] <zbenjamin> for now we "only" need to execute gdbserver and be able to connect with tcp
[09:15] <sarnold> zbenjamin: do you see a file in /var/lib/apparmor/profiles that cooresponds to your app?
[09:15] <zbenjamin> sarnold: no the app is uninstalled after executing it :/ the adk-launcher script is doing that automatically  but i can disable it for now
[09:16] <sarnold> zbenjamin: oh nuts. well, okay...
[09:16] <zbenjamin> now i have that file
[09:18] <zbenjamin> sarnold: best would be if i could just add "debug" to my policy list
[09:18] <sarnold> zbenjamin: sure, that's a nice end goal :) but won't happen today, hehe
[09:19] <sarnold> zbenjamin: if you can stand a bit of hackery in the meantime, try adding "/usr/bin/gdbserver Ux," to the file and reload it with apparmor_parser --replace /path/to/file
[09:19] <sarnold> zbenjamin: -- this step will need to re-executed after package install but before the application is started
[09:20] <zbenjamin> the problem the script does not run as root since we connect with ssh
[09:20] <zbenjamin> and we install to the local click database
[09:21] <sarnold> ahhh.
[09:24] <zbenjamin> sarnold: gdbserver starts now, the app does not seem to come up and the ide does not connect ..
[09:26] <sarnold> zbenjamin: woo, nice, can you grep DENIED /var/log/syslog  and pastebin those? (the pastebinit program can help here)
[09:27] <zbenjamin> sarnold: http://pastebin.ubuntu.com/7520065/
[09:28] <zbenjamin> sarnold: but looking at the timestamps they are not related
[09:29] <sarnold> zbenjamin: some of them, indeed -- we shold probably file a bug or two for that, too
[09:31] <zbenjamin> sarnold: meh the time on the phone is not correct ;)
[09:31] <zbenjamin> sarnold: so they are related
[09:32] <sarnold> zbenjamin: the [ dddd ] bits ar enormally 'seconds after boot'..
[09:32] <zbenjamin> sarnold: i was able to connect from the gdb cli tool on the phone, but when i try to continue i get SIGTRAP'ed and then SIGABORT'ed
[09:32] <sarnold> zbenjamin: did you get any new DENIED lines from that?
[09:33] <zbenjamin> there are a few more http://pastebin.ubuntu.com/7520085/
[09:37] <sarnold> jjohansen: is this one of those LSM calls that happens before the usual kernel security mechanisms? apparmor="DENIED" operation="mknod" ... name="/usr/lib/python3.4/__pycache__/shlex.cpython-34.pyc.3063768112" pid=5862 comm="qtc_device_debu" requested_mask="c" denied_mask="c" fsuid=32011 ouid=32011
[09:42] <jjohansen> sarnold: yes
[09:48] <Laney> bdmurray: could you upload ubuntu-release-upgrader?
[09:49] <Laney> release upgrades are crashing with the bug you fixed in https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-release-upgrader/trunk/revision/2808
[09:50] <bdmurray> Laney: will do
[09:50] <Laney> thanks!
[09:53] <sarnold> zbenjamin: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1323233
[09:53] <zbenjamin> sarnold: fyi this is the debug script for the official ubuntu sdk ;)
[09:54] <zbenjamin> sarnold: i'm part of the SDK team
[09:54] <zbenjamin> sarnold: and this is part of RTM so we really need that
[09:55] <zbenjamin> sarnold: because currently we use a bunch of hacks to provide debugging mechanism which fall apart every other day. We really need to replace this with something sane
[09:55] <sarnold> zbenjamin: ah, I hadn't realized that was 'more official' :)
[09:55] <zbenjamin> sarnold: yeah sorry i should have mentioned that ;)
[09:56] <sarnold> zbenjamin: I just thought it was a nice script that'd been hacked together in desperation, hehe
[10:01] <zbenjamin> sarnold: basically it is ;). I wrote it at the last week on the sprint. There is also the sdk launcher now that takes a click package as a argument and installs , executes and uninstalls after the application finishes running
[10:02] <sarnold> zbenjamin: very nice
[10:05] <zbenjamin> sarnold: i can confirm tcp connect works at least for the qmldebugger. Now we "just" need the c++ side ;)
[10:06] <sarnold> zbenjamin: did you have to add anything to the apparmor policy to get the qmldebugger to work?
[10:07] <zbenjamin> sarnold: i just added your gdbserver line
[10:08] <sarnold> zbenjamin: was that necessary for the qmldebugger?
[10:08] <zbenjamin> i can try to remove it
[10:08] <bdmurray> pitti: libc6-dbg did not improve the crash files
[10:09] <pitti> bdmurray: ah, too bad; so the badness is in gdb itself then :/
[10:10] <pitti> xnox: lp:~upstart-devel/upstart/upstart-jobs doesn't yet have the init scripts from your unreviewed branch, but I guess that's expected
[10:11] <slangasek> bdmurray, pitti: are we sure about the integrity of the core files themselves?
[10:12] <pitti> slangasek: certainly not "sure", but I can't believe that we really get stack corruption on pretty much all the crashes, while they mostly work on x86
[10:12] <zbenjamin> sarnold: ok the line is not required. But the connection is slow, but that comes from qtc its waiting for some output from the app which it can not get of course
[10:13] <pitti> many that we looked at have two frames in libc (I suppose the usual "pass NULL pointer to string comparison" etc.), and then nothing else, just the "corrupted stack" error
[10:13] <pitti> slangasek: ^
[10:13] <slangasek> pitti: have we tried native backtracing with gdb on armhf?
[10:14] <slangasek> (to rule out whether it's a gdb vs. gdb-multiarch problem)
[10:15] <pitti> slangasek: that already was native, AFAIUI
[10:15] <pitti> slangasek: i. e. it's gdb running *on* the phone at the time of the crash
[10:15] <slangasek> mmm
[10:15] <pitti> slangasek: so we ruled out foreign arch problems
[10:16] <slangasek> does gdb get a useful backtrace if you attach it to a running process on armhf?
[10:16] <zbenjamin> sarnold: would be nice if you could change the bug report so its clear that this is more official ;)
[10:17] <zbenjamin> sarnold: or should i just  comment on it
[10:17] <sarnold> zbenjamin: I can fix it up some :)
[10:17] <zbenjamin> sarnold: awesome
[10:17] <pitti> slangasek: I don't know right now, that's an interesting test; although it needs to happen on something which is actually busy, otherwise we'll just catch some poll()/select(); bdmurray, did you happen to try that already?
[10:18] <GunnarHj> Hi pitti!
[10:19] <pitti> hey GunnarHj
[10:19] <GunnarHj> pitti: People are asking for langpack updates. Any chance that you can press the button?
[10:19] <GunnarHj> https://lists.ubuntu.com/archives/ubuntu-translators/2014-May/006507.html
[10:20] <pitti> GunnarHj: for trusty?
[10:20] <pitti> GunnarHj: I can copy the current PPA to -proposed, yes
[10:20] <GunnarHj> pitti: Yes.
[10:20] <GunnarHj> pitti: Would that be an SRU?
[10:20] <pitti> GunnarHj: yes, they've always been
[10:21] <GunnarHj> pitti: Ok, I keep learning. :)
[10:22] <pitti> GunnarHj: meh, https://launchpad.net/~ubuntu-langpack/+archive/ppa times out
[10:22] <pitti> GunnarHj: does this actually have recent trusty updates?
[10:23] <GunnarHj> pitti: Actually I haven't checked... Just saw the postings.
[10:23] <seb128> pitti,  language-pack-de 	1:14.04+20140522
[10:23] <seb128> one example
[10:24] <seb128> you can try reloading, it didn't timeout here
[10:24] <pitti> https://launchpad.net/~ubuntu-langpack/+archive/ppa?field.series_filter=trusty
[10:24] <pitti> ah, that looks fine
[10:24] <pitti> yeah, I'm fine with uploading that
[10:24] <bdmurray> pitti: no, I have not
[10:25] <pitti> GunnarHj: we need a wiki page where testers mark the tested languages; would you mind setting that up?
[10:25] <pitti> GunnarHj: I think we haven't actually done that (updates) for a long time :/
[10:25] <pitti> GunnarHj: ah, on https://wiki.ubuntu.com/Translations/LanguagePackUpdatesQA
[10:27] <GunnarHj> pitti: Hmm.. I may take a look, but it will have to take a while.
[10:27] <pitti> GunnarHj: so it's just a new entry on above wiki page and sending a call for testing AFAICS
[10:28] <GunnarHj> pitti: Is the purpose of that page to document tests before SRUing translations?
[10:29] <pitti> GunnarHj: the purpose is that people run these standard tests (desktop comes up, you can run updat-emanager, etc.) for a particular language
[10:29] <pitti> GunnarHj: and after the timeout we release the languages which got tested
[10:30] <GunnarHj> pitti: I see. Have to quit now. Talk to you later.
[10:31] <zbenjamin> sarnold: any chance we can get that in in the next days?
[10:31] <sarnold> zbenjamin: could be, depends how much of jamie's time I can get :)
[10:54] <shadeslayer> ev: can usb-creator 0.2.57 be released for trusty too?
[11:34] <xnox> pitti: correct. Cause it's not in the archive yet.
[11:58] <pitti> xnox: http://paste.ubuntu.com/7520913/
[12:06] <xnox> pitti: ^
[12:07] <slangasek> seb128, pitti: is bug #1289031 assigned to the right component?
[12:08] <seb128> slangasek, could be bug #1283863
[12:08] <seb128> but if you run unity, unity-settings-daemon is the right component
[12:08] <seb128> (well, assuming the issue is with the settings daemon, and not xorg/synaptic driver)
[12:08] <slangasek> right; I think I filed that bug before u-s-d was a separate thing
[12:10] <seb128> slangasek, if you can reproduce, it would be interesting to see if that happens as well when unity-settings-daemon is not running
[12:10] <slangasek> ok
[12:10] <slangasek> it's intermittently reproducible
[12:10] <seb128> :-/
[12:11] <slangasek> if I killall unity-settings-daemon, does it stay dead?
[12:11] <seb128> it's an upstart job, just stop it
[12:11]  * slangasek nods
[12:13] <dobey> seb128: hey, can you approve or whatever needs to be done to unity-scope-click to get it from u-proposed into the archive? seems it's held for migration as it added a dependency on ubuntu-sdk-libs
[12:18] <seb128> dobey, "unity-scope-click/arm64 unsatisfiable Depends: ubuntu-sdk-libs "
[12:19] <seb128> dobey, you need to make ubuntu-sdk-libs available on arm64, or to make unity-scope-click not build there (or not depends on the libs)
[12:19] <pitti> xnox: bug 1323274
[12:20] <dobey> seb128: oh, ugh
[12:25] <tseliot> seb128: what are the plans on unity-settings-daemon? Are we going to rebase our changes on topo of the latest g-s-d? Also, where's the RCS?
[12:25] <tseliot> *top
[12:25] <seb128> tseliot, what is "RCS"?
[12:25] <pitti> revision control system?
[12:25] <tseliot> seb128: revision control system
[12:25] <seb128> oh, VCS?
[12:26] <seb128> lp:unity-settings-daemon
[12:26] <tseliot> yes
[12:26] <tseliot> sorry
[12:26] <tseliot> seb128: or is it a permanent fork that we should develop separately?
[12:26] <seb128> rebase ... we might, depends of how much work it is/the benefits/who has slots to work on that
[12:26] <seb128> it's a fork
[12:27] <seb128> but it doesn't mean we should backport commits that benefit us
[12:27] <seb128> or rebase on newer versions if it makes sense
[12:27] <tseliot> they fixed a lot of use cases for wacom tablets and touch screens
[12:27] <tseliot> that is why I'm asking
[12:27] <seb128> we are likely to update e.g the wacom code, not sure about the other plugins there
[12:27] <xnox> pitti: http://paste.ubuntu.com/7521117/
[12:27] <seb128> wacom needs to be updated in sync with the control center I think
[12:28] <tseliot> seb128: they introduced a new device mapper that requires a fair amount of work to backport and to hook into the plugins
[12:28] <seb128> in what cycle?
[12:28] <tseliot> I had a look at git master
[12:29] <tseliot> those are changes from 2013-2014
[12:32] <tseliot> seb128: g-s-d 3.12 includes all the fixes, except for one
[12:35] <dobey> seb128: can i make a binary dep be used on all archs except for arm64?
[12:35] <seb128> tseliot, I'm not sure we are going to update that this cycle, somebody owning wacom hardware and having slots to work on that working on updating that code would be nice
[12:36] <seb128> dobey, you need to list the archs manually
[12:36] <dobey> ogra_: hi. what's keeping ubuntu-touch-meta from being built on arm64?
[12:36] <dobey> seb128: but i can't do [!arm64] for binary deps?
[12:36] <ogra_>  no idea, doesnt it build ?
[12:37] <seb128> dobey, I don't think so
[12:37] <dobey> ogra_: i guess ubuntu-touch-meta has explicit archs listed. it's only built on i386, amd64, and armhf
[12:38] <dobey> ogra_: i'd expect it will build fine, but maybe all the binary deps don't build fine on arm64?
[12:38] <ogra_> ogra@styx:~/Devel/packages/ubuntu-touch-meta-1.141$ grep amd64 update.cfg
[12:38] <ogra_> architectures: i386 amd64 armhf
[12:38] <ogra_> right
[12:38] <tseliot> bdmurray: hi, can you have a look at LP: #1322212 please?
[12:38] <ogra_> it is explicitly disabled atm ...
[12:39] <tseliot> seb128: ok, I'll see what I can do...
[12:39] <ogra_> dobey, why do you need it on arm64 ? and 64 bit phones in sight =
[12:39] <ogra_> ?
[12:39] <seb128> thanks
[12:39] <dobey> ogra_: is there a list of what's keeping it from being built elsewehre?
[12:40] <ogra_> dobey, it was never enabled on anything else but the three arches my grep above lists
[12:40] <sarnold> ogra_: apple sells one :)
[12:40] <ogra_> and i assume the seeds are set up similar
[12:40] <dobey> ogra_: because unity-scope-click is architectue: any in the control file, and we just added a binary dep on ubuntu-sdk-libs, because it is what provides the list of frameworks
[12:40] <ogra_> sarnold, oh, you are planning to purt ubuntu-touch to an iphone ?
[12:40] <ogra_> :P
[12:40] <ogra_> *port
[12:41] <sarnold> ogra_: wouldn't that be a fun target? :)
[12:41] <ogra_> doanac, hrm
[12:41] <ogra_> err
[12:41] <ogra_> dobey,
[12:41] <dobey> so right now this makes the scope uninstallable on arm64, though otherwise it builds and installs fine there
[12:42] <sarnold> it'd actually make more sense for us; apple sells content consuming devices. we've aiming for a converged computing device, and I haven't had < 4 gigs of memory on my computer in a very long time..
[12:44] <ogra_> dobey, hmm, i would actually prefer to have an override for the autopkgtest stuff in that case ... i suspect blindly enabling arm64 in the seeds and metapackages will open a big can of worms and cause a lot of extra work
[12:44] <ogra_> dobey, did you ask infinity or cjwatson if we could jet override it for now ?
[12:44] <bdmurray> tseliot: is that supposed to superceed the existing package in precise-proposed?
[12:44] <ogra_> s/jet/just/
[12:45] <dobey> ogra_: and just have an uninstallable unity-scope-click on arm64?
[12:45] <ogra_> dobey, right
[12:45] <ogra_> until we have actually seeds for that arch
[12:45] <dobey> i haven't asked, no.
[12:46] <tseliot> bdmurray: yes. I also included the previous changes in the diff
[12:46] <ogra_> switching the seeds on on this arch will likely mean we need to make the whole of ubuntu-touch ... or at least the whole of the sdk-libs installable in the end
[12:47] <ogra_> (or alternatively make the scope use [!arm64] but thats more ugly imho
[12:47] <dobey> ogra_: a good thing i think, but i do agree it might mean a lot of work. i wonder if there's an easy way we can test it
[12:47] <ogra_> )
[12:47] <dobey> well, it's ugly, but probably less ugly than a built package that can't be installed :)
[12:48] <bdmurray> tseliot: okay, could you add saucy tasks?
[12:48] <bdmurray> tseliot: I mean precise
[12:49] <tseliot> bdmurray: I think xorg-server-lts-saucy is only available in precise, isn't it?
[12:49] <cjwatson> ogra_: that's not autopkgtest
[12:50] <cjwatson> dobey: you can do [!arm64] in debian/control as long as it's not for an Architecture: all package
[12:50] <cjwatson> dobey: though in this context it would be more correct to do [amd64 armhf i386]
[12:51] <bdmurray> tseliot: While that may be true I'm pretty all the sru tools / reports want a task for the relevant release.
[12:51] <dobey> cjwatson: might be better to just not build on arm64 i guess, since unity8 isn't building there currently
[12:51] <cjwatson> well
[12:51] <cjwatson> let me check what rdeps are already there
[12:52] <dobey> well, it's depwait
[12:52] <cjwatson> but it built before?
[12:52] <dobey> i don't know
[12:52] <cjwatson> must've done
[12:52] <cjwatson> otherwise it wouldn't be a proble
[12:52] <cjwatson> m
[12:52] <cjwatson> ok, there are no reverse-dependencies of unity-scope-click/arm64
[12:52] <dobey> it shows depwait on trusty and saucy too
[12:52] <dobey> so i guess it's always been that way
[12:53] <cjwatson> no it doesn't
[12:53] <cjwatson>  unity-scope-click | 0.1+14.04.20140410.1-0ubuntu1 | trusty/universe          | source, amd64, arm64, armhf, i386
[12:53] <cjwatson> dobey: so, I can remove this, but you'll have to actually stop it building
[12:54] <ogra_> great :)
[12:56] <dobey> cjwatson: ok, that's great. i'll make a branch to stop it building on arm64. and you'll override it for now to get the current package migrated?
[12:56] <cjwatson> not override, but remove
[12:56] <cjwatson> (done)
[12:58] <cjwatson> I wouldn't just override this because adding uninstallable packages can make proposed-migration take bad decisions
[12:58] <ogra_> ah, i didnt know that
[13:00] <cjwatson> dobey: to be clear, if your branch doesn't land, the next upload will have the same problem :)
[13:00] <dobey> oh ok
[13:00] <dobey> cjwatson: yeah, i will make a branch now(-ish)
[13:01] <cjwatson> ta
[13:27] <tseliot> bdmurray: ok, let me fix that then
[13:28] <tseliot> yay, launchpad failed...
[13:35] <bdmurray> tseliot: hmm it oops'ed for me too. I'll just accept it then.
[13:40] <tseliot> bdmurray: good. I think we can add a task later
[13:46] <mterry_> stgraber, is there a bug for the lxc/kernel issue so I can subscribe?
[13:53] <mterry_> stgraber, ah I see you uploaded a fix.  But it still fails autopkgtest?
[13:56] <mterry_> But only two failures rather than three this time!  :)
[13:59] <tseliot> bdmurray: thanks
[14:04] <stgraber> mterry_: yeah, there's another kernel bug, jjohansen is on it
[14:05] <jjohansen> mterry_: if you revert to the 3.13 kernel from earlier, that should work until the 3.15 kernel with the fix lands
[14:07] <mterry_> jjohansen, I'm not concerned with testing it myself so much, it's just blocking a cgmanager update in utopic
[14:07] <jjohansen> mterry_: ah okay
[14:11] <Laney> woah
[14:11] <Laney> I've never noticed that quilt series colours patches based on applied/top/unapplied
[14:11] <Laney> is that new?
[14:12] <GunnarHj> pitti: still there?
[14:22] <ev> shadeslayer: if you want to go through the paperwork for an SRU, I'm happy to sponsor the upload
[14:22] <shadeslayer> ev: heh
[14:22] <shadeslayer> that's like the most annoying part of it :P
[14:22] <shadeslayer> ev: anyway, I'll file the paperwork
[14:23] <ev> :-P
[14:23] <ev> thanks!
[14:23] <shadeslayer> np
[14:23] <ev> I've got the branch queued up and ready for a bug number to inject
[14:25] <shadeslayer> ev: 1289026
[14:25] <ev> cheers
[14:26] <ev> shadeslayer: is that right? It's a regular bug not following the SRU format: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
[14:26] <shadeslayer> ev: yes, I'm fixing that
[14:26] <ev> ah right
[14:26] <ev> I'll feed that into the branch
[14:27] <shadeslayer> ev: done
[14:28] <shadeslayer> ev: it's the bug that errors.ubuntu.com had linked to all the error reports
[14:28] <shadeslayer> thought I'd just repurpose it
[14:29] <ev> uploaded
[14:29] <shadeslayer> cheers
[19:32] <n4uah> hello..
[19:32] <n4uah> is anyone can help with the ubuntu touch?
[19:33] <rww> tried #ubuntu-touch?
[19:35] <n4uah> i think some of them works at canonical.
[19:35] <rww> Yep, and they also tend to hang out in #ubuntu-touch, hence me pointing you there. Have you tried it? :)
[19:36] <n4uah> no..
[19:36] <n4uah> now at their..
[19:36] <n4uah> :)
[21:02] <LLKCKfan> Hello
[21:02] <LLKCKfan>  How can someone who is almost 30 and never had a job get one? I have been applying just to be told I am not what they are looking for or they are not hiring.
[21:08] <Noskcaj_> LLKCKfan, I think you're asking in the wrong place
[21:08] <LLKCKfan> then what is the right place
[21:09] <genii> Probably some channel to do with employment
[21:36] <Noskcaj_> pitti, Is it ok if i merge flashplugin-nonfree-extrasound?
[21:37] <LLKCKfan> There are none


[02:25] <Flannel> rww: Already left him some stuff in query, but he's doing it every ten minutes
[02:25] <rww> ah, okay
[02:30] <IdleOne> !language > potat0
[03:02] <rww> BajK_: Hi, welcome to #ubuntu-ops. Can we help you with something?
[03:08] <BajK_> rww: eh, i did not join here on purpose
[03:08] <rww> BajK_: It appears that you were banforwarded here from #ubuntu by IdleOne because ... alrighty then.
[03:08] <IdleOne> he should be right back
[03:26] <rww> BajK_: It appears that you were banforwarded here from #ubuntu by IdleOne earlier. He asked you not to use impolite language, and you repeated it.
[03:26] <BajK_> hmkay
[03:27] <rww> !guidelines
[03:27] <rww> BajK_: Can you have a read of those and let me know when you've done so, please?
[03:27] <BajK_> it's just, I am so damn angry about those stupid ATI flgrx developers because they make my life hard because they program things that are just so unneccessary and annoying to me
[03:27]  * rww sighs
[05:45] <rww> Any objections to adding "Please don't suggest setting one or ask for help with it if you have." between the two existing sentences in !noroot?
[05:45] <rww> !noroot
[05:48] <tonyyarusso> rww: Those phrases actually used to exist, back in the day.
[05:48] <rww> I vaguely remember this. Any idea why it got removed?
[05:49] <tonyyarusso> nope
[06:26] <rww> ah, http://irclogs.ubuntu.com/2009/07/15/%23ubuntu-ops.txt is the log of it being changed
[08:20] <rww> if anyone sees NAVEENGF so much as join an Ubuntu channel, I'd appreciate a poke so I can keep an eye on them.  I'm bored, may as well.
[08:58] <Ormie> Did you just blocked me while having conversation on #ubuntu? (After you answer i will go)
[08:59] <Flannel> Ormie: You were speaking recently, has that changed?
[09:00] <Flannel> The last thing you said was < Ormie> Where can i get old screensavers that exist in ubuntu 8.04 (Now i am using 10.10) and i have tried gnone-(something).com but i can't see any thing good
[09:00] <Flannel> I don't think you're blocked, do you think you might be?
[09:00] <Ormie> Flannel: Usually someone will answer me. But no one answered.
[09:01] <Flannel> Ormie: Ah, well, that just means that no one right now who is free has an answer to that question.  Feel free to ask again every half hour or so.  As people cycle in and out of being AFK and awake and stuff, you'll get an answer soon enough.
[09:03] <Ormie> Flannel, Thanks and goodbye
[09:06] <Tm_T> awww
[09:08] <Flannel> What?
[09:11] <Tm_T> that he thought being blocked
[18:28] <jussi> !papercut
[18:28] <jussi> !papercut is <reply>A papercut is a trivially fixable usability bug in a central Ubuntu component. See https://wiki.ubuntu.com/PaperCut for more info
[22:31] <Guest34415> hi
[22:32] <Guest34415> stop my ban
[22:32] <Guest34415> I am good man
[22:34] <Guest34415> SO WHAT???
[22:36] <Jordan_U> Guest34415: There aren't any #ubuntu-ru ops around at the moment, please be patient.
[22:38] <Guest34415> ok
[22:41]  * jussi points to #ubuntu-irc for issues with #ubuntu-ru or other loco/non core chans
[22:44] <Myrtti> could someone with a better keyboard ban forward rawrite of whatever over here for their quit message?
[22:55] <Guest34415> WHAT?
[22:57] <Jordan_U> Guest34415: The message from Myrtti was not aimed at you. The message from jussi was (try asking in #ubuntu-irc about your ban in #ubuntu-ru).
[22:58] <Myrtti> Guest34415: anything else we can help you with?
[22:59] <Guest34415> how to stop ban on ubuntu-ru?
[22:59] <Myrtti> we can't help with that here
[23:00] <Myrtti> it's a topic for #ubuntu-irc
[23:03] <Myrtti> anything else?
[23:06] <Myrtti> Guest34415: anything else we can help you with?
[23:06] <Guest34415> NO
[23:06] <Guest34415> how to stop ban on ubuntu-ru?
[23:06] <Guest34415> how to stop ban on ubuntu-ru?
[23:06] <Guest34415> how to stop ban on ubuntu-ru?
[23:06] <Guest34415> how to stop ban on ubuntu-ru?
[23:06] <Guest34415> how to stop ban on ubuntu-ru?
[23:06] <Guest34415> how to stop ban on ubuntu-ru?
[23:07] <Guest34415> how to stop ban on ubuntu-ru?
[23:13] <Jordan_U> Myrtti: Can you confirm that I setup that banforward correctly?
[23:13] <Myrtti> looks ok to me
[23:31] <Myrtti> attn: he was klined on xmas eve for being a spamming troll (mindwarper)
[23:32] <Myrtti> iirc
[23:34] <Myrtti> Jordan_U: ^
[23:36] <Jordan_U> Myrtti: Thanks.


[02:32] <jiffe> should 22.04 be available via do-release-upgrade from 20.04 ?  I'm getting There is no development version of an LTS available.
[02:54] <Eickmeyer> jiffe: Not until 22.04.1 is available in August.
[02:54] <Eickmeyer> !ltsupgrade | jiffe
[02:57] <jiffe> interesting, ok thanks