[13:53] <djszapi> How can I run an upstart script manually for testing purpose ?
[14:40] <ion> It’s not a script, and “start jobname”.
[14:52] <djszapi> ion: well, something is wrong :(
[14:53] <djszapi> exec /usr/sbin/start-cupsd.sh -> I try to run this custom file from an upstart job
[14:53] <djszapi> Which is intended to run this script: http://paste.kde.org/73711/
[14:54] <djszapi> and 1) I do not see the created directory 2) cups daemon is not run at all
[14:54] <djszapi> how could I debug the issue ?
[14:55] <djszapi> http://paste.kde.org/73717/ -> this is my apps/cups.conf
[16:26] <djszapi> When are the /etc/init/apps/ jobs run ?
[16:40] <jhunt> djszapi: take a look at http://upstart.ubuntu.com/cookbook/#debugging
[18:21] <SpamapS> Hrm.. so we're hitting the "state problem" again with network-manager. It needs to not stop until after a certain event has run. But right now it is 'stop on stopping dbus' .. so if I make it 'stop on stopping dbus and deconfiguring-networking' .. 'stop dbus' will hang. ...
[18:30] <SpamapS> so I almost have to make dbus have a dbus-shutdown.conf that works like portmap-boot.conf and identifies itself as specifically the dbus that stops on runlevel [06]
[18:31] <SpamapS> s/almost/think I probably/
[19:53] <SpamapS> hmm.. unless I just make dbus stop on my new event


[00:35] <quentusrex_> is there a good way to handle switching the HD-PVR from my cable box to my xbox? I want to be able to record game play.
[00:44] <quentusrex_> ok, I nearly have it. Now I just need to figure out how to cycle a firewire connection.
[00:44] <quentusrex_> the channel changing script is failing to see the cable box
[00:54] <quentusrex_> Where are the livetv recordings located?
[00:54] <quentusrex_> I can't seem to find them listed under Media Library
[01:35] <munson> haup wintv 1600 setup...need help.  its all blue screen on both tuners.  I set one for dvb and an ivtv one. using 11.10 with schedules direct blhablah...any ideas?
[13:34] <munson> haup wintv 1600 setup...need help.  its all blue screen on both tuners.  I set one for dvb and an ivtv one. using 11.10 with schedules direct blhablah...any ideas?
[18:49] <christoph_> Problem with mythbackend on oneiric during upstart
[18:49] <christoph_> Anybody?
[18:50] <dekarl> what problem?
[18:52] <dekarl> can you paste your backend.log from start to crash at paste.ubuntu.com ?
[18:54] <christoph_> Problem is mythtv-backend.conf in /etc/init related: LANG=$LANG /usr/bin/mythbackend --logfile /var/log/mythtv/mythbackend.log --user mythtv -v most,important does not generate a log file
[18:54] <christoph_> and syslog tells me that it's giving up on the upstart script as mythbackend is respawning to quickly during system start.
[18:55] <dekarl> ok, was about to ask what happens when you do "service start mythtv-backend" (or whatever its called) manually
[18:55] <dekarl> is that mythbuntu or ubuntu + mathtv?
[18:56] <christoph_> My mythtv-backend.conf at is http://paste.ubuntu.com/728439/
[18:56] <Zinn> [paste.ubuntu.com] Ubuntu Pastebin
[18:57] <christoph_> Manual startup works. It a generic oneiric installation with 0.24.1 added from the repos.
[18:57] <christoph_> Just stopped working yesterday...
[18:58] <dekarl> I'd bet upstart is trying to start the backend to early...
[18:59] <christoph_> Crazy thought (as I removed fglrx from that machine due to a kernel oops and replaced it with the generic radeon drivers for X): could this be related? Does the backend do any video driver things or is this purely frontend-related?
[18:59] <christoph_> For some reason I recall coming a remote suggestion in a forum recently...
[18:59] <dekarl> the backend does nothing X related as far as I know
[19:00] <christoph_> Thought so too but then I replaced
[19:00] <dekarl> I have changed the start line to wait for "eth0" instead of "lo" so I can bind to the real network instead of the loopback
[19:00] <christoph_>  sleep .5
[19:00] <dekarl> or just sleep more...
[19:00] <christoph_> with sleep 2 in the .conf script -> same problem
[19:01] <christoph_> Cool - will try right now!
[19:02] <christoph_> But should this matter? I thought the backend would connect using localhost instead of the real NIC?
[19:02] <dekarl> depends... for remote frontends it needs to listen on the real network
[19:03] <dekarl> basically you just make it wait more by that
[19:03] <christoph_> Not running any frontend bar xbmc on this machine. I noticed that the backend was gone when xbmc couldn't connect to it anymore...
[19:05] <dekarl> you could try with sleep 60 just to see if that helps, but put the sleep to the pre-start script *and* script... gtg
[19:05] <dekarl> if it does call the backend then the latter is enough
[19:07] <christoph_> still doesn't work though...
[19:10] <christoph_> Syslog says:  init: mythtv-backend main process (1347) terminated with status 127Nov  4 20:06:23 htpc kernel: [   16.153872] init: mythtv-backend main process ended, respawningNov  4 20:06:23 htpc kernel: [   16.163405] init: mythtv-backend main process (1352) terminated with status 127Nov  4 20:06:23 htpc kernel: [   16.163437] init: mythtv-backend main process ended, respawningNov  4...
[19:10] <christoph_> ...20:06:23 htpc kernel: [   16.173241] init: mythtv-backend main process (1357) terminated with status 127Nov  4 20:06:23 htpc kernel: [   16.173272] init: mythtv-backend respawning too fast, stopped
[19:24] <dekarl> which means its not working... 20:06:23 until 20:06:23 is not what sleep 60 (a minute) should do
[19:29] <christoph_> BTW: any idea what exit status 127 means?
[19:32] <dekarl> sorry no, maybe its time to try on #mythtv-users (gtg again)
[19:32] <dekarl> or #mythtv-de ;)
[19:32] <christoph_> libs/libmythdb/exitcodes in the source code talks about about CMD_NOT_FOUND... If I could have the backend produce a proper log, this may help...
[23:12] <suprdave> none of my channels match up with schedules direct.  which makes set up recording very hard
[23:13] <suprdave> I'm using an HD Homerun box
[23:15] <suprdave> How can I re aline the listings to match the channel scan?


[05:17] -queuebot:#ubuntu-release- New binary: python-opcua [amd64] (disco-proposed/none) [0.98.6-1] (no packageset)
[07:51] -queuebot:#ubuntu-release- Unapproved: libseccomp (bionic-proposed/main) [2.3.1-2.1ubuntu4 => 2.3.1-2.1ubuntu4.1] (core)
[08:52] <LocutusOfBorg> https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1815567
[08:52] <LocutusOfBorg> :)
[08:52] <LocutusOfBorg> jbicha, ^^
[09:07] -queuebot:#ubuntu-release- New: accepted python-opcua [amd64] (disco-proposed) [0.98.6-1]
[09:07] -queuebot:#ubuntu-release- New: accepted rust-rusty-tags [arm64] (disco-proposed) [3.4.0-1]
[09:07] -queuebot:#ubuntu-release- New: accepted rust-rusty-tags [i386] (disco-proposed) [3.4.0-1]
[09:07] -queuebot:#ubuntu-release- New: accepted rust-rusty-tags [s390x] (disco-proposed) [3.4.0-1]
[09:07] -queuebot:#ubuntu-release- New: accepted rust-rusty-tags [amd64] (disco-proposed) [3.4.0-1]
[09:07] -queuebot:#ubuntu-release- New: accepted rust-rusty-tags [ppc64el] (disco-proposed) [3.4.0-1]
[09:07] -queuebot:#ubuntu-release- New: accepted rust-rusty-tags [armhf] (disco-proposed) [3.4.0-1]
[09:13] <LocutusOfBorg> seriously AA, what the hell is going on?
[09:13] <LocutusOfBorg>  virtualbox-dkms | 5.2.24-dfsg-4build1                 | disco/multiverse           | all
[09:13] <LocutusOfBorg>  virtualbox-dkms | 6.0.4-dfsg-5                        | disco/multiverse           | all
[09:14] <LocutusOfBorg>  virtualbox-source | 5.2.24-dfsg-4build1                 | disco/multiverse           | all
[09:14] <LocutusOfBorg>  virtualbox-source | 6.0.4-dfsg-5                        | disco/multiverse           | all
[09:14] <LocutusOfBorg> all the vbox binaries seems to be having some sadness :(
[09:14] <LocutusOfBorg> vorlon, ^^
[09:51] <cjwatson> LocutusOfBorg: I think that's just because virtualbox-qt is NBS on i386
[09:52] <cjwatson> so there are different versions of arch-dep binaries in the suite and so all the arch-indep ones get held
[09:55] <cjwatson> LocutusOfBorg,vorlon: I've removed that, so the rest should clear out shortly
[10:33] -queuebot:#ubuntu-release- Unapproved: accepted apt [source] (trusty-proposed) [1.0.1ubuntu2.20]
[10:56] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-143.169] (core, kernel)
[11:00] <LocutusOfBorg> yeah, vbox seems sorted out, lets see what happens now with autopkgtests
[11:01] <LocutusOfBorg>  ./sil2100:force-badtest virtualbox-ext-pack/all/i386
[11:02] <LocutusOfBorg> can we please add virtualbox/all/i386? same reason for it...
[11:02] <LocutusOfBorg> sil2100, ^^
[11:02] <LocutusOfBorg> it is blocking lots of stuff, e.g. libnotify, kernel xinerama qtbase...
[11:04] <LocutusOfBorg> linux-signed and libnotify actually, maybe a versioned hint is enough, because a no-change rebuild of linux and libnotify might actually be enough to not trigger the new test at all
[11:08] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-143.169]
[13:20] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (cosmic-proposed/partner) [1:20190108.1-0ubuntu<IP_ADDRESS> => 1:20190212.1-0ubuntu<IP_ADDRESS>] (no packageset)
[13:20] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (xenial-proposed/partner) [1:20190108.1-0ubuntu<IP_ADDRESS> => 1:20190212.1-0ubuntu<IP_ADDRESS>] (no packageset)
[13:21] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (bionic-proposed/partner) [1:20190108.1-0ubuntu<IP_ADDRESS> => 1:20190212.1-0ubuntu<IP_ADDRESS>] (no packageset)
[13:21] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (trusty-proposed/partner) [1:20190108.1-0ubuntu<IP_ADDRESS> => 1:20190212.1-0ubuntu<IP_ADDRESS>] (no packageset)
[13:59] <fidencio> cyphermox: around? so, basically, I've got to your http://people.canonical.com/~mtrudel/preseed/full-bionic.cfg preseed. Were you able to have it working with live medias? What's the kernel command line you've used for that? I'm struggling really hard to have live medias (both server and desktop) to work with preseed as it doesn't pass the "Please choose your preferred language." screen
[14:05] <jbicha> LocutusOfBorg: I rebuilt libnotify but we still got the virtualbox/i386 trigger
[14:05] -queuebot:#ubuntu-release- Unapproved: openssl-ibmca (bionic-proposed/universe) [1.4.1-0ubuntu1 => 1.4.1-0ubuntu1.1] (no packageset)
[14:05] -queuebot:#ubuntu-release- Unapproved: openssl-ibmca (cosmic-proposed/universe) [2.0.0-0ubuntu2 => 2.0.0-0ubuntu2.1] (no packageset)
[14:10] <cyphermox> fidencio: for preseeded live images (desktop, not server); you need a few different keys in
[14:11] <cyphermox> a bit like what's in the utah-bionic.cfg file
[14:11] <cyphermox> if you're talking about server-live, then I don't know how to preseed it
[14:13] <fidencio> cyphermox: do you have the kernel command line somewhere that could be used for that? seems that the kernel command line is quite different for live and non-live medias
[14:17] <cyphermox> sure. it's mostly the same actually
[14:17] <cyphermox> you need to set url and 'automatic-ubiquity' IIRC
[14:17] <fidencio> cyphermox: seems that if I don't pass boot=casper the boot up bails
[14:17] <cyphermox> fidencio: right
[14:17] <fidencio> and I'm stuck in initramfs screen
[14:18] <cyphermox> I mean, everything that is normally on the kernel command-line
[14:18] <cyphermox> you change url= from the standard desktop one, and add 'automatic-ubiquity'
[14:18] <cyphermox> and that will only work for desktop images
[14:19] <cyphermox> everything else stays the same; especially boot=casper. You can't get around that
[14:20] <fidencio> cyphermox: okay, seems that I was using a server live media
[14:21] <fidencio> cyphermox: just using automatic-ubiquity boot=casper + the very same preseed I had for the server image works as expected
[14:21] <cyphermox> with server media?
[14:21] <fidencio> cyphermox: no, with desktop media
[14:21] <cyphermox> ok, got it
[14:21] <fidencio> cyphermox: that was my mistake :-(
[14:21] <fidencio> now, time to try to figure out what I do need to make a server live media to work
[14:22] <cyphermox> well, not a mistake if you want to test the server media
[14:22] <fidencio> cyphermox: I want both and, for some reason, I thought that starting with the server live would be easier
[14:22] <fidencio> okay, okay
[14:22] <fidencio> cyphermox: thanks *a* *lot* for the help
[14:48] <fidencio> didrocks: out of curiosity, is ubuntu-18.10 live server already using the yaml files?
[14:49] <fidencio> didrocks: *already using the yaml files for unattended installation
[14:49] <didrocks> fidencio: yes, even 18.04 are using curtin, but it seems that subiquity needs its own preseeding still
[14:49] <didrocks> so, it's not pure yaml only
[14:49] <fidencio> didrocks: aha! 18.04 live server, right? not live desktop
[14:49] <didrocks> but only people who worked on subiquity would really know at this stage (cyphermox, xnox, mwhudson…)
[14:50] <didrocks> fidencio: yes, live server
[14:50] <fidencio> didrocks: now it makes a lot of sense why I'm failing miserably to make the installation work with a live server
[14:50] <didrocks> fidencio: normally, I think that preseeding should create the yaml file, but again, not a subiquity expert :p
[14:51] <didrocks> the finale goal though (but will take some times) is to only have yaml for those anyway
[14:55] <xnox> fidencio, hi, if you are preseeding, just use MAAS. server live is meant to be used interractively only, and unlike the d-i based server install, it only has a handful of screens to answer anyway.
[14:55] <xnox> didrocks, there is no unattended install support in server live
[14:56] <fidencio> xnox: perfect!
[14:56] <fidencio> xnox: thanks a lot for the answer!
[14:56] <didrocks> xnox: wondering why there are some debconf hooks (but I may be wrong, maybe there isn't)
[14:57] <xnox> didrocks, that's in curtin....
[14:57] <xnox> didrocks, and cloud-init can do that too
[14:57] <xnox> didrocks, but that's not for installer.
[15:05] <Laney> vorlon: juliank: sil2100: would any of you like to look into what is going on with armhf?
[15:06] <Laney> e.g<EMAIL_ADDRESS>[15:14] <juliank> ack
[15:18] <juliank> Laney: works for me
[15:19] <juliank> Laney: were there a lot of failures like this?
[15:19] <juliank> sounds like the server went out between update and install
[15:19] <Laney> yes
[15:19] <Laney> lots and lots
[15:19] <juliank> this is odd
[15:20] <Laney> look for /unknown on excuses
[15:20] <Laney> but I've been retrying them so it doesn't look as bad as it really is
[15:29] <juliank> Laney: I did 3 runs and could not reproduce the issue, so it's unclear to me what's going on. It looks like a networking issue, but who knows
[15:30] <Laney> well yes, that's the problem
[15:32] <Laney> Sometimes it happens in the middle of a run too, so some of the armhf regressions will be due to this
[16:06] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi3 [Bionic 18.04.2] (20190210) has been added
[16:33] <fidencio> cyphermox: last question, what's the way to avoid the "Please remove the installation medium, then press ENTER:" message that I get when using a live desktop media?
[16:36] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (cosmic-proposed) [1:20190212.1-0ubuntu<IP_ADDRESS>]
[16:36] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (bionic-proposed) [1:20190212.1-0ubuntu<IP_ADDRESS>]
[16:36] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (xenial-proposed) [1:20190212.1-0ubuntu<IP_ADDRESS>]
[16:37] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (trusty-proposed) [1:20190212.1-0ubuntu<IP_ADDRESS>]
[16:37] <cyphermox> fidencio: IIRC it's ubiquity ubiquity/reboot boolean true
[16:37] <cyphermox> "ubiquity ubiquity/reboot boolean true" but it may or may not only deal with ubiquity's prompting.. it's been a while since I looked in that
[16:39] <blackboxsw> ffe
[16:49] <blackboxsw> sil2100:  I've queued an FFE bug that probably needs some attention at some point and I'm not certain of the next steps. UA Client is in progress and will be waiting on availability of an active backend service before I can attach package diffs for this FFE.  https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1814157
[16:52] <blackboxsw> sil2100: do you, or others have suggestions on next steps to ensure this FFe gets a review before freeze? Would I need wait until I can attach the intended package patch/diff and manual test runs against the backend services before trying to get a review on this FFe, per the docs https://wiki.ubuntu.com/FreezeExceptionProcess?
[16:52] <blackboxsw> I thought it best to queue the FFe bug as early as possible for review, but maybe it just needs to wait until we have final package diff stable/complete.
[16:58] <sil2100> blackboxsw: hey! There's still like 1.5 weeks until Feature Freeze for disco, do you mean the new ubuntu-advantage-tools version won't be available for upload before the deadline?
[17:05] <blackboxsw> sil2100: my expectation is that the backend service code and published routes should be stabilizing this week and that we can shake out bugs over the next week and a half. Having an upload available in 1.5 weeks is a  tight timeline. but I think we'll have something verified by then.
[17:06] <blackboxsw> sil2100: I didn't know if it was best to get review on the FFe prior to having that upload available in this case given that the timeline is tight for having an upload
[17:08] <LocutusOfBorg> doko, may I upload the fixed ncurses? sed vwprintw -> vw_printw on debian/tests/build
[17:20] <sil2100> blackboxsw: hmmm, I guess we could review this beforehand, just in case things slip - but anyway, let's try to get everything landed before FF, I'll take a look at the FFe in the meantime
[17:20] <sil2100> But if the feature will land a week later, I still think it won't be a problem
[17:20] <sil2100> But yeah, let me read the FFe bug you have provided, thanks for that!
[17:21] <blackboxsw> sil2100: thanks for the looksie. I just didn't want to suprise folks if we end up missing by a few days due to not actually being able to validate against a live backend service yet
[17:22] <blackboxsw> when I have something that is functional/tested against a running backend I'll update the bug accordingly and ping
[17:30] <vorlon> mitya57: qtbase-opensource-src-gles seems to be stalled in -proposed because binaries end up uninstallable on arm64; I haven't had a chance to dig into it
[19:36] -queuebot:#ubuntu-release- New binary: budgie-extras [amd64] (disco-proposed/universe) [0.8.0-0ubuntu1] (personal-fossfreedom, ubuntu-budgie)
[22:23] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (bionic-proposed) [2.525.17]
[22:25] -queuebot:#ubuntu-release- New source: matplotlib2 (disco-proposed/primary) [2.2.3-5ubuntu1]
[22:27] <LocutusOfBorg> please accept matplotlib2  [2.2.3-5ubuntu1]
[22:27] <LocutusOfBorg> the sphinx build failure is fixed now
[22:28] -queuebot:#ubuntu-release- New sync: matplotlib2 (disco-proposed/primary) [2.2.3-5]
[23:15] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (xenial-proposed) [2.408.43]


[05:42] <wuxiaoyi> ypwong ,昨天那个bug已经修复
[05:43] <ypwong> wuxiaoyi, 好的，待会让 aron 合并
[06:01] <JackYu> ypwong, 我们正在接入。。。
[06:07] <ypwong> JackYu, ok
[07:03] <ypwong> JackYu, 你们要大声点
[07:04] <JackYu> ypwong, OK


[08:25] <dwa_> if i do a search in the dash, how do i use the keyboard to go through the results?
[08:26] <dwa_> for instance, if i want to launch firefox i press <super>, type in firefox and now i'd have to click on the icon to launch it
[08:26] <dwa_> while i would just like to do <tab> <enter>
[08:27] <dwa_> i'm really hoping it will get anywhere near gnome-do in terms of usefulness
[08:27] <dwa_> but it's a long way from it now
[20:55] <m3ph1s> "HOW TO" spy remote screen? i guess my secretary is going lazy.
[20:56] <m3ph1s> of couser i'll let her know that i can see what she does.
[20:59] <m3ph1s> any keyword to google? please
[21:55] <BDaughtry> we are looking at using ubuntu server as a platform to run a new software we are buying. the software company wants to know what the glib c for ubuntu server is so that can tell us if their software will support it. can anyone help?
[23:11] <m3ph1s> @<BDaughtry> testing is the mother of science ;(
[23:11] <m3ph1s> ;)