[00:39] <jep200404> dekarl: I have changed from mythbuntu to mythtv on Ubuntu 11.10. Check out http://colug.net/~jep/myth/3/Screenshot.png and some other stuff in parent directory. Where is log file for frontend?
[00:39] <Zinn> [colug.net] N/A
[03:14] <tgm4883> jep200404, it's in /var/log/mythtv/
[11:54] <dekarl> jep200404: I've asked over in #mythtv-users and wagn errp suspects it to be an issue with using the old libmpeg2 video decoding (based on the assumption that you're using a Playback Profile that was default once upon a time, but run a more up to date version of mythtv now.) See http://www.mythtv.org/wiki/Playback_profiles and basically avoid the decoders libmpeg2 and XvMC (they are deprecated, see http://www.mythtv.org/news/14
[11:54] <Zinn> [www.mythtv.org] Playback profiles - MythTV
[12:29] <jep200404> dekarl: Thanks. I'll dig into the profile and decoder stuff.
[13:30] <jep200404> dekarl: Thanks for the clues. Changing the playback profile from CPU+ to CPU++ fixed the problem.
[13:34] <dekarl> IIRC using slim/normal/high quality would be preferred
[13:40] <jep200404> dekarl: High Quality works also. I'll be playing around with various profiles.
[13:41] <dekarl> found it https://github.com/MythTV/mythtv/commit/4cd818657100d13a813dfa7a8a44201184c49d71
[13:41] <Zinn> [github.com] Commit 4cd818657100d13a813dfa7a8a44201184c49d71 to MythTV/mythtv - GitHub
[14:20] <jep200404> dekarl: by the way, http://www.mythtv.org/news/14 is a dead link
[14:20] <dekarl> oops, that should have been  http://www.mythtv.org/news/144/XvMC%20and%20libmpeg2%20to%20be%20dropped%20in%200.25 )
[14:20] <Zinn> [www.mythtv.org] MythTV, Open Source DVR
[22:51] <BenFranske> Anyone here who can answer a question about LIRC with an IRMAN on a USB-Serial adapter?
[23:38] <patdk-lap> not me


[16:00] <matsubara> #startmeeting
[16:00] <MootBot> Meeting started at 10:00. The chair is matsubara.
[16:00] <matsubara> [TOPIC] Roll Call
[16:00] <MootBot> New Topic:  Roll Call
[16:00] <sinzui> me
[16:00] <matsubara> Not on the Launchpad Dev team? Welcome! Come "me" with the rest of us!
[16:00] <matsubara> me
[16:00] <henninge> me
[16:00] <bigjools> me
[16:00] <stub> me
[16:00] <intellectronica> me
[16:00] <matsubara> rockstar, hi
[16:01] <matsubara> flacoste, hi
[16:01] <rockstar> em
[16:01] <matsubara> apologies from herb and ursula
[16:01] <matsubara> [TOPIC] Agenda
[16:01] <matsubara>  * Actions from last meeting
[16:01] <matsubara>  * Oops report & Critical Bugs
[16:01] <matsubara>  * Operations report (mthaddon/herb/spm)
[16:01] <matsubara>  * DBA report (stub)
[16:01] <MootBot> New Topic:  Agenda
[16:02] <matsubara> [TOPIC] * Actions from last meeting
[16:02] <MootBot> New Topic:  * Actions from last meeting
[16:02] <matsubara>  * danilos to discuss with herb a fix for bug 388825
[16:02] <matsubara>  * Ursinha to talk to matsubara and spm later about the codebrowse taking 10 mins to restart
[16:02] <matsubara>  * Ursinha to talk to flacoste about buildbot and storm updating for testing when he's available today
[16:02] <flacoste> me
[16:02] <matsubara> ok, Ursula did talk to me and there's a bug filed about the codebrowse issue
[16:03] <matsubara> flacoste, did ursula talk to you about the buildbot thing?
[16:03] <matsubara> henninge, do you know if danilo discussed the fix with herb?
[16:03] <henninge> mthaddon installed an updated version of pytz to fix bug 388825
[16:03] <matsubara> ok, it's fix released. so he did :-)
[16:03] <flacoste> matsubara: we did talk about storm
[16:03] <flacoste> matsubara: not sure what the buildbot stuff was about
[16:03] <henninge> matsubara: yes, I'd expect so.
[16:04] <matsubara> henninge, thanks
[16:04] <matsubara> flacoste, hmm I'll re-add the entry for next meeting to remind her
[16:04] <matsubara> [action] * Ursinha to talk to flacoste about buildbot and storm updating for testing when he's available today
[16:04] <MootBot> ACTION received:  * Ursinha to talk to flacoste about buildbot and storm updating for testing when he's available today
[16:05] <matsubara> ok, moving on
[16:05] <matsubara> [TOPIC] * Oops report & Critical Bugs
[16:05] <MootBot> New Topic:  * Oops report & Critical Bugs
[16:05] <matsubara> two bugs, bug 386759 and bug 361026. first one for rockstar, second one for flacoste
[16:06] <matsubara> rockstar, could you get someone to fix 386759 for 2.2.7?
[16:06] <rockstar> matsubara, yes.
[16:06] <matsubara> rockstar, it's blocking code review for some people
[16:06] <rockstar> Is that deployed on prod now?
[16:07] <matsubara> flacoste, any news about 361026?
[16:07] <matsubara> rockstar, yes
[16:07] <flacoste> matsubara: last news is that it's not easy to fix
[16:07] <sinzui> matsubara: I see other critical bugs we need to watch
[16:07] <rockstar> matsubara, so is it a candidate for CP then as well?
[16:07] <matsubara> sinzui, I'll get there :-)
[16:08] <matsubara> rockstar, might be
[16:08] <matsubara> flacoste, so, can you re-target it to 2.2.7?
[16:08] <flacoste> stub: "no easy fix" was your comment on bug 361026, how not easy is it?
[16:09] <stub> The registration forms on login.launchpad.net need to all stop creating and modifying Person records, and any fallout with that dealt with.
[16:09] <stub> I don't know how much fallout that will be - I'm not that familiar with them.
[16:11] <flacoste> matsubara: yes, retarget to 2.2.7
[16:11] <matsubara> stub, can you assess that and reply back in the bug report? if it's too difficult and the oops is not happening frequently we might want to decrease the importance
[16:11] <matsubara> flacoste, cool. thanks
[16:11] <matsubara> now for the critical bugs
[16:11] <matsubara> we have 8 critical bugs
[16:12] <flacoste> 8!!
[16:12] <matsubara> 4 Fix committed
[16:12] <matsubara> 2 in progress and 2 triage
[16:12] <matsubara> triaged
[16:12] <matsubara> flacoste, bug 390861 is one of the triaged ones
[16:12] <matsubara> sinzui, bug 391175 is the other one
[16:13] <matsubara> I take none of those will make the re-roll today?
[16:13] <matsubara> wait, that last one was in Triaged state a few minutes ago!
[16:13] <matsubara> sinzui, you're fast :-)
[16:13] <sinzui> matsubara: Edwin is having difficulties getting things landed in PQM
[16:14] <sinzui> matsubara: I think it will miss the reroll today.
[16:14] <matsubara> sinzui, the Absent content factory thing?
[16:14] <flacoste> matsubara: actually the 390861 one isn't in effect
[16:14] <flacoste> matsubara: i'll decrease it to high, since the storm update has been reverted
[16:14] <sinzui> matsubara: I don't think so. BjornT landed Bug 388112 for Edwin, but that too does not appear to be in db-devel
[16:15] <matsubara> re-roll will include up to r8203 from db-devel only
[16:15] <matsubara> flacoste, thanks
[16:15] <BjornT> sinzui: what isn't in db-devel?
[16:16] <matsubara> sinzui, that's on r8199
[16:16] <sinzui> matsubara: Given how quick thing are moving the the next release. I think we should assume a CP next week, and  cheer if it is ready for today
[16:16] <matsubara> sinzui, ok, so CP be it.
[16:16] <matsubara> thanks sinzui
[16:16] <sinzui> matsubara: EdwinGrubbs reported that when he pulled db-devel, it was missing that rev
[16:17] <EdwinGrubbs> sinzui: it exists now
[16:17] <matsubara> ok, I think that's it for this section
[16:17] <matsubara> thanks everyone
[16:17] <sinzui> matsubara: bug 287248 is the most pressing critical item my team has. Barry and Edwin are working on it. It may be a data corruption problem in prodution
[16:17] <matsubara> sinzui, that's the other one in progress, right?
[16:18] <sinzui> it is
[16:18] <matsubara> sinzui, so, we'll need to CP that one then
[16:18] <sinzui> If we need to change launchpad/mailman, it will be a CP
[16:18] <matsubara> sinzui, as BjornT cut db-devel on r8203  for the re-roll
[16:19] <matsubara> let's move on
[16:19] <matsubara> [TOPIC] * Operations report (mthaddon/herb/spm)
[16:19] <MootBot> New Topic:  * Operations report (mthaddon/herb/spm)
[16:19] <matsubara> herb and the other losas are sprinting
[16:19] <matsubara> so herb will email the report to the list later on today
[16:19] <matsubara> [TOPIC] * DBA report (stub)
[16:19] <MootBot> New Topic:  * DBA report (stub)
[16:20] <stub> Database part of the rollout seems to have gone smoothly. We still need to rebuild the slave db used for read only mode, which needs to happen some time before the next DB outage so not urgent.
[16:20] <stub> The Storm update was rolled back in case it was causing or contributing to timeouts and memory issues noticed during QA. I'll reland this branch once release mode is over so we can test more fully on staging and edge.
[16:20] <stub> Nothing else to report.
[16:20] <matsubara> cool. thanks stub
[16:20] <matsubara> one final announcement before closing up
[16:21] <matsubara> we need to QA the last itens that landed since the rollout. I've asked Ursinha to fix the test plan script which seems broken and I'll ping the owners of each item after the meeting
[16:22] <matsubara> that's all
[16:22] <matsubara> anything else before I close?
[16:23] <matsubara> Thank you all for attending this week's Launchpad Production Meeting. See the channel topic for the location of the logs.
[16:23] <matsubara> #endmeeting
[16:23] <MootBot> Meeting finished at 10:23.


[21:01] <skellat> .nws 44004
[21:01] <jenni> Lake Effect Snow *_WATCH_* issued November 21 at 3:28PM EST until November 24 at 7:00PM EST by NWS
[21:01] <jenni> Complete weather watches, warnings, and advisories for Ashtabula, OH, available here: http://alerts.weather.gov/cap/wwaatmget.php?x=OHC007 -- You may also PM the bot to get the full list.


[16:51] <giuliano> Hi. I'm building a uvcvideo.ko module, but have difficulties loading the new module on the system. May I ask for some help ?
[16:52] <giuliano> I opened bug 2000947, and received from<EMAIL_ADDRESS>some c code to test...
[16:52] -ubottu:#ubuntu-kernel- Bug 2000947 in linux (Ubuntu) "UVC  Quanta 0408:4035  camera PROBLEM" [Undecided, Confirmed] https://launchpad.net/bugs/2000947
[16:52] <giuliano> yes
[16:52] <giuliano> this is the ghithub I'm testing right now
[16:52] <giuliano> https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-Facing-0x0408-0x4035-
[16:53] <giuliano> I made a script to compile the module. The compilation ends correctly
[16:53] <giuliano> BUT the module is non loaded
[16:53] <giuliano> Hope the bash is well documented... what am I missing ?
[16:54] <giuliano> I see two main problems:
[16:54] <giuliano> 1) the dmesg shows this error failed to validate module [uvcvideo] BTF: -22
[16:55] <giuliano> 2) there is a version mismatch between $ cat /proc/version_signature shows Ubuntu 5.15.0-57.63-generic 5.15.74.
[16:55] <giuliano> and modinfo uvcvideo.ko
[22:10] <Jeremy31> giuliano: I just commented on your bug
[22:29] <giuliano> thanks Jeremy ! I saw your messagge on launchpad..
[22:30] <Jeremy31> giuliano: It is how I do bluetooth patches and I didn't see any module version issue with my method
[22:31] <giuliano> I installed inux-modules-extra-$(uname -r) where `uname -r` is  5.15.0-57-generic BUT ..
[22:31] <giuliano> The directory /usr/src/linux-headers-5.15.0-57-generic/drivers/media/usb/uvc/ has got only two make files, no C lang. File…
[22:31] <giuliano> do you mean a different directory ?
[22:32] <Jeremy31> giuliano: You need the source code for linux-modules-extra
[22:32] <giuliano> I entered "sudo apt-get source linux-modules-extra-$(uname -r)
[22:32] <giuliano> "
[22:32] <giuliano> and it pulled 2045Mb...
[22:32] <giuliano> 204
[22:32] <Jeremy31> Don't use sudo for that
[22:34] <giuliano> Reading the console I now see... "dpkg-source: Informazioni: extracting linux in linux-5.15.0
[22:34] <giuliano> "
[22:34] <Jeremy31> Hopefully it isn't owned by root
[22:35] <giuliano> I ran the command from my home directory...
[22:36] <Jeremy31> It might have different permissions
[22:36] <giuliano> hops... it created a new dir in my home .... owned by root....
[22:36] <giuliano> gonna change the owner...
[22:37] <Jeremy31> That will simplify things
[22:39] <giuliano> ok ... changed owner:group..
[22:39] <giuliano> ok... the directory has got the c file inside...
[22:40] <giuliano> I would kindly ask...
[22:40] <Jeremy31> Rename the original and copy the patched version in
[22:40] <giuliano> I've got in /usr/src/ a BIG tar file linux-source-5.15.0.tar.bz2
[22:41] <giuliano> I used that file, extracting in my home and compiling
[22:41] <giuliano> that tar file is 153 MB but expanded got 1-2 Gb....
[22:41] <giuliano> Shouldn't it be the ALL linux kernel ? Why I need to downlaod the linux-extra inf already is present that tar file ?
[22:42] <Jeremy31> Just eliminating some possible problems with that linux-source file
[22:43] <Jeremy31> I am not real sure how your built module ended up with vermagic of 5.15.64
[22:44] <giuliano> renamed and downloaded the uvcvideo.c
[22:45] <giuliano> Should I run "make -j4 -C /lib/modules/$(uname -r)/build M=$(pwd) modules" in the top level of  ~/linux-5.15.0 I just created ?
[22:46] <giuliano> or in the uvc dir ?
[22:46] <Jeremy31> Run it in the uvc directory
[22:46] <Jeremy31> Faster
[22:46] <giuliano> Skipping BTF generation for /home/giuliano/linux-5.15.0/drivers/media/usb/uvc/uvcvideo.ko due to unavailability of vmlinux
[22:47] <Jeremy31> normal
[22:47] <giuliano> ??
[22:47] <giuliano> what does it mean ?
[22:47] <Jeremy31> IIRC it means Secure Boot is disabled
[22:47] <giuliano> my previous compileed module, failed modprove because "failed to validate module [uvcvideo] BTF: -22"
[22:48] <giuliano> is something similar with BTF ?
[22:48] <Jeremy31> giuliano: Is there a uvcvideo.ko file in the directory now?
[22:48] <giuliano> yes, AND vermagic:       5.15.0-57-generic SMP mod_unload modversions
[22:49] <Jeremy31> Copy it to the kernel
[22:49] <giuliano> cat /proc/version_signature
[22:49] <giuliano> Ubuntu 5.15.0-57.63-generic 5.15.74
[22:49] <giuliano> Is  the .63 missing ?
[22:52] <Jeremy31> That is normal also, check in terminal>  uname -r
[22:53] <giuliano> COPIED into /lib/modules/5.15.0-57-generic/kernel/drivers/media/usb/uvc
[22:53] <giuliano> should i change owner:group befor modprobe ?
[22:53] <Jeremy31> No need to do that to anything in /home
[22:54] <giuliano> well... destination file was copied in system path /lib/modules/...
[22:54] <giuliano> and file shows
[22:54] <giuliano> -rw-rw-r-- 1 giuliano giuliano 4386720 gen  9 23:46 uvcvideo.ko
[22:54] <Jeremy31> And using sudo to copy into /lib/modules already changed it
[22:55] <giuliano> I thougt... but checking ... it has not (?)))
[22:55] <giuliano> [103970.912878] usb 3-6: Found UVC 1.50 device ACER HD User Facing (0408:4035)
[22:55] <giuliano> [103970.912882] usb 3-6: Forcing UVC version to 1.0a
[22:55] <giuliano> [103970.949432] input: ACER HD User Facing: ACER HD Us as /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.0/input/input38
[22:55] <giuliano> [103970.949630] usbcore: registered new interface driver uvcvideo
[22:55] <giuliano> from dmesg
[22:56] <giuliano> Well... I can get back to Pinchart.... the Cheese program is running
[22:57] <giuliano> and I can see myself in the window... BUT it is very slow.... extremely slow...
[22:58] <giuliano> thanks a lot for your help
[22:59] <Jeremy31> Good luck
[22:59] <giuliano> thanks...
[23:00] <giuliano> I will try to fix this for all the other that have similar problem
[23:00] <Jeremy31> If he has any new updates run this in the source directory before trying to make modules again>  make -j4 -C /lib/modules/$(uname -r)/build M=$(pwd) clean
[23:02] <giuliano> you mean to run it in the uvc directory or in the root of the source ?
[23:03] <Jeremy31> The linux-5.15 uvc directory in /home
[23:04] <giuliano> ok
[23:05] <giuliano> BTW I've got also another bug with the screen luminisity control. I can see the OSD reacting to my key pressed, but the screen does not change intensity.
[23:05] <giuliano> Even the top menu screen luminosity slider does not work…
[23:05] <giuliano> Strangely, I installed https://github.com/lordamit/Brightness, and it works…
[23:05] <giuliano> Where do you suggest me to  start inspecting the code ?
[23:05] <giuliano> may be something ACPI related, or something at more higer leverl (gnome) ?
[23:07] <Jeremy31> I have no clue, most of what I do is with wifi and bluetooth, but I can fix some issues compiling drivers
[23:14] <giuliano> ?? wifi ?? I noticed a failure about wifi in the dmesg.... but then it said it was loaded something...
[23:14] <giuliano> [    3.286067] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-hr-b0-66.ucode failed with error -2
[23:14] <giuliano> [    3.286082] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-hr-b0-65.ucode failed with error -2
[23:14] <giuliano> [    3.288700] iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
[23:14] <giuliano> [    3.288719] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: <IP_ADDRESS>
[23:14] <giuliano> [    3.289123] iwlwifi 0000:00:14.3: loaded firmware version 64.97bbee0a.0 so-a0-hr-b0-64.ucode op_mode iwlmvm
[23:14] <giuliano> Is someting to not working properly ?
[23:17] <Jeremy31> giuliano: Normal for iwlwifi, the max and min firmware versions are specified in the module but it seems that version 65 or 66 aren't available so version 64 loaded
[23:17] <giuliano> thanks again for your help
[23:18] <giuliano> gonna inform Pichard of the progress !!
[23:18] <giuliano> Have a nice day !
[23:18] <Jeremy31> Good, later


[08:02] <mwhudson> er
[08:02] <mwhudson> is it possible to get the teams subscribed to a source package over the api?
[08:03] <mwhudson> source_package is series-specific and so not quite the right thing?
[08:03] <mwhudson> oh distribution_source_package


[06:10] <flocculant> :D
[07:37] <ochosi> hey flocculant
[07:39] <Unit193> flocculant: Always knew he liked you better.
[09:07] <akxwi-dave> flocc
[09:07] <akxwi-dave> flocculant:  just give me the nod when we can move to AA+ppa's  new setup ready and waiting for it..
[17:49] <flocculant> Unit193: what can I say ...
[17:49] <flocculant> ochosi: hi :)
[17:50] <flocculant> akxwi-dave: ack - will do, as far as I'm aware they're all up now - mostly just need to be sure I can ping lists
[19:29] <akxwi-dave> flocculant: ta
[23:31] <Unit193> -<!ENTITY devel-codename 'zesty' >
[23:31] <Unit193> +<!ENTITY devel-codename 'b' >


[00:11] <wxl> oh man, lfnw rules.
[00:35] <wxl> sgclark: just a friendly reminder to send along that packaging info mentioned. hope you're resting. still on the bus here.
[05:40] <wxl> sgclark: look what i found: trying out snappy core and it's transactional updates using kvm https://developer.ubuntu.com/en/snappy/start/#snappy-local


[16:39] <BigOrNo> Hello, i've looked at the v5.17.12 and v5.18.1 but it seems that the files names aren't correct (<IP_ADDRESS>). is that normal or not ?
[16:40] <BigOrNo> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.17.12/
[16:40] <xnox[m]> BigOrNo: sounds buggy...... let's see.....
[16:40] <BigOrNo> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.18.1/
[16:40] <BigOrNo> ok..thank you :)
[16:41] <xnox[m]> BigOrNo: so we normally reuse packaging from another place.... and normally it is supposed to override the changelog versions to what is being built. i wonder if you can pull the cod/mainline/v5.17.12 tag to see if the code that is build is in fact v5.17.12 and that somehow it is hopefully jsut the version mangling of packaging that is broken.
[16:42] <xnox[m]> otherwise, if the tag points and actually is building v5.15.0 code we have probably some bigger issues in the automatation.
[16:42] <BigOrNo> ok...i'm going to wait a little then...
[16:42] <xnox[m]> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.17.11/ did build with correct version numbers
[16:42] <BigOrNo> yes i've seen that
[16:43] <xnox[m]> also it is holiday this week in UK & US and many people are off. and i don't think i actually have access to the right bot that generates these =/
[16:43] <BigOrNo> the v5.18 was correct too
[16:43] <BigOrNo> erf... lol :)
[16:45] <BigOrNo> it seems both v5.17.12 and v5.18.1 have the same checksums
[16:45] <xnox[m]> i love mondays
[16:57] <BigOrNo> i'm wrong about the checksums...
[16:57] <BigOrNo> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.17.12/armhf/CHECKSUMS
[16:58] <BigOrNo> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.18.1/armhf/CHECKSUMS


[22:19] <akshatj> hello
[22:20] <akshatj> I am running 11.04 on a t1.micro instance and SSH hangs when too much text is being transferred


[13:12] <BluesKaj> Hi all
[14:42] <RikMills> 5.26 beta needs quite a few changes. working through them


[09:11] <bhechinger> "Corrupted download, check the checksums"
[09:11] <bhechinger> "I did, they're different, but that's ok!"
[09:11] <bhechinger> Miss the point often?
[14:57] <OvenWerks> Eickmeyer: that is why I feel grub should show it correctly ;)  And allow setting it as default.
[14:57] <Eickmeyer> OvenWerks: In 23.10 it will and does.
[14:57] <OvenWerks> Eickmeyer: I am not using it right now, personally, but have used it in the past for similar reasons
[14:59] <Eickmeyer> Looking at the liquorix kernel's file format, it's identical in name format, so theoretically GRUB_FLAVOUR_ORDER should be able to specifiy it, so on a user level one could simply edit that.


[00:04] <Finetundra> anyone have success with the att streaming feature with any browser?
[00:20] <wolferz> Anyone active on this channel?
[00:21] <wolferz> Would anyone have a minute to help me figure out why my system is using 4.5GB of memory simply from booting and sitting at the desktop in Kubuntu 15.04?
[00:22] <Finetundra> what's up?
[00:23] <wolferz> idk, my system is seriously hogging memory for no apparent reason, and did not before the upgrade.
[00:27] <Finetundra> how many widgets do you have? Also, have you checked top/htop?
[00:28] <wolferz> I have the systray widget, the kde launcher widget, the panel, and the desktop widget, I think that is it. How do I check top/htop?
[00:31] <Finetundra> open the terminal and type top
[00:33] <Finetundra> there you can find a list of proceses although i like htop better
[00:34] <wolferz> top: https://paste.kde.org/pwm0ppftq
[00:36] <Finetundra> well, I'm not seeing anything that's using too much RAM alone
[00:36] <Finetundra> are you still reading high usage levels?
[00:37] <wolferz> https://paste.kde.org/pgi9ka7v4
[00:37] <wolferz> systray says a lot, I guess this says its all cache
[00:39] <Finetundra> hmm
[00:41] <M8ty> i had various performance issues when i installed Kubuntu 15.04  , the best thing to do is to not run install / widgets... Plasma 5.3 seems to not get on very well with widgets ...
[00:41] <Finetundra> yeah, that may be it. I'm still on 14.04 with plasma 4
[00:42] <Finetundra> I haven't touched plasma 5 yet
[00:42] <wolferz> ok, thanks guys
[00:42] <M8ty> am running plasma 5.3 without widgets, no issues at all
[00:42] <Finetundra> speaking of, is 5 any good?
[00:43] <M8ty> pretty snappy and reliable so far.. there is the occasional hang, crash etc
[00:45] <Finetundra> sounds like it still needs work
[00:45] <Finetundra> guess I'll stick with 4 for now
[00:45] <M8ty> Plasma 5 on VM though is a whole ball game... just gave up testing it carshed that much
[00:46] <Finetundra> yikes
[00:46] <wolferz> Other than it telling me I've no memory left, it does everything without hesitation.... I haven't gotten the notification sounds to work after changing them though, still the default, and I can't right click on system load viewer widget and pull up the system monitor anymore
[00:48] <Finetundra> yeah, well, I've gotten plasma 4 working ok so I'll stay here for now. Or just use the plasma 5 lxqt theme and some magic
[00:49] <M8ty> sounds like a good idea.
[00:50] <Finetundra> anyway, anyone know how I make a proper keyboard shortcut for a terminal?
[00:54] <Finetundra> and how would one change the lock screen wallpaper?
[00:55] <wolferz> you mean the sign in screen?
[00:57] <wolferz> sddm?
[00:57] <M8ty> i think he's talking about sddm
[00:58] <M8ty> system settings>Startup and Sutdown>login Screen (SDDM)
[00:59] <M8ty> there you may change the login background
[01:01] <wolferz> Directory for the splash screen: /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/splash/images/
[01:02] <wolferz> Directory for sddm screen: /usr/share/sddm/themes/breeze/components/artwork/
[01:02] <wolferz> Make sure you chmod o+r the file you put in that directory
[01:04] <wolferz> MSty, I don't know if it is just my system, or an issue with 15.04, but changing the background there does nothing. I had to do it the manual way.
[01:07] <wolferz> speaking of the manual way... My system also will not allow me to change my notification sounds, and I cannot find the config file in google. Anyone know where it is to manually change it?
[01:26] <mohamad> Hi people. I install the new Kubuntu 15.04 in my PC and now the KDE (just KDE, e20 works fine) is stop work sometimes.
[01:33] <M8ty> wolferx_ did you log off and log back on when you changed the background?
[05:27] <Finetundra> hey guys, how can I set the terminal,, konsole or other, to launch with key combo ctrl+alt+t?
[06:54] <michael___> zoot365
[06:54] <michael___> Anybody home?
[07:15] <patrik_> Morning,
[08:10] <lordievader> Good morning.
[09:27] <Guest18878> Im in the process of installing KDE and am a live user right now. `sudo fdisk -l` gives no output. I need to copy files
[10:37] <yossarianuk> is the PPA going to be updated for plasma 5.3.2 / frameworks 5.12 ?
[10:47] <lordievader> The backports? Eventually, when the packages have gotten round to it.
[10:47] <lordievader> Never mind, see #kubuntu-backports.
[10:47] <lordievader> Err #kubuntu-devel
[11:47] <Kiranos_> anyone using Gigolo with kde to connect to remote server shares?
[11:47] <Kiranos_> the layout of the software is very weird and doesnt work in 15.04 of kubuntu, but works in official ubuntu
[12:10] <BluesKaj> Hiyas all
[12:16] <jsl1> after installing kubuntu 15.04, i've got this issue: http://www.legendiary.at/2015/04/03/logitech-k800-wireless-not-working-on-dm-crypt-passphrase/
[12:17] <jsl1> but it seems dracut isn't the correct solution for kubuntu, anyone had the issue about logitech hw not working in dm-crypt?
[12:17] <lordievader> jsl1: I guess the driver ain't in your initramfs.
[12:18] <jsl1> yap, sounds rigth, but I have no idea as to how i'd include it :|
[12:18] <jsl1> in previous versions, this just worked
[12:20] <lordievader> jsl1: Find what module you need and add it to /etc/initramfs-tools/modules
[12:21] <jsl1> thank you :D
[12:22] <lordievader> After doing that don't forget to update your initramfs.
[12:24] <ikonia> win 1
[12:24] <ikonia> oops, sorry
[12:26] <jsl1> lordievader: lsmod tells me I've loaded these modules for hid: "hid_multitouch,usbhid,hid_logitech_dj,hid_logitech_hidpp" - is there any way I could figure out which one I need, or should I just include them all?
[12:26] <lordievader> Probably wouldn't hurt to include them all.
[12:28] <jsl1> haha
[14:26] <frederick> hi
[14:27] <lordievader> o/
[14:32] <frederick> I need to make a technical question of kde
[14:33] <frederick> I have installed Kubuntu 15.04 on a acer aspire s3, 4GB of RAM, processor 4 cores and 2GB of RAM consume kubuntu only with the Firefox browser is normaleso abirto? consuming much RAM?
[14:35] <lordievader> Firefox is a memory hog. How much does what program consume?
[14:37] <frederick> yes firefox is a memory hog, but chrome is very ver very bad also
[14:38] <frederick> i can see my monitor and the apps is
[14:39] <frederick> plasmaShell = 265 mb | Kde5 = 131 mb | mysqld = 123 mb | firefox = 195 mb
[14:39] <frederick> but the mysqld is a server of index baloo
[14:42] <lordievader> Hmm, it seems I have forgotten what is sane.
[14:42] <lordievader> ahoneybun: You around? Could you give us your insight about ^
[14:44] <ahoneybun> PlamsaShell = 330 mb | chromium = 1200 gb or so | mysqld = 110 mb |
[14:44] <ahoneybun> somehting like that for me
[14:45] <lordievader> I think chromium should be 1200 Mb?
[14:45] <lordievader> 1Tb of memory would be a bit much.
[14:47] <ahoneybun> yea
[14:48] <ahoneybun> lol
[14:51] <lordievader> ;)
[14:51] <lordievader> frederick: Anyhow seems like it is sane. Probably much of that reported memory usage is cache.
[14:54] <frederick> mm ok, the cache is consumig this memory, but came out Ubuntu  precisely by excess consumption of ram, I thought it would consume less kde
[14:59] <lordievader> Caching ain't bad, it is memory used to increase the speed of disk access. But it is memory that can be freeed at a moments notice.
[15:01] <frederick> ok then i wait to kde caching and i can see a reduce of memory, excuseme my english is very bad jajaj i a chrome
[15:03] <lordievader> frederick: http://mugurel.sumanariu.ro/linux/the-difference-among-virt-res-and-shr-in-top-output/
[15:06] <frederick> very thanks,
[18:39] <vbgunz> aplay sounds horrible, any idea why?
[18:39] <vbgunz> I'm just calling aplay <file> on any file and they all sound horrible, what's up?
[18:41] <lordievader> What kind of file?
[18:43] <vbgunz> both a flac and an mp3
[18:44] <vbgunz> I just settled on using cvlc, glad I had it installed, just need a quick way to make a beep using a shortcut
[18:44] <lordievader> I thought aplay only works with wav files.
[18:45] <vbgunz> maybe, I just needed a quick way to play a file from command line, I thought aplay could play either
[18:45] <lordievader> From the man page: File type (voc, wav, raw or au).  If this parameter is omitted the WAVE format is used.
[18:45] <lordievader> Ie, -t needs to be specified if anthing other than wav is played.
[18:45] <vbgunz> thanks lordievader, I'm glad it's not broken
[20:45] <valorie> hi folks, I have a broken install of wily, and I think a still-working install of unity wily
[20:45] <valorie> I can get to the recovery menu
[20:46] <valorie> is there any way from here I can either fix my kubuntu or at least log into unity?
[20:46] <Unit193> Depends on how it is broken.
[20:47] <valorie> I got a new little laptop and my son set it up for me but was unable to boot into kubuntu
[20:48] <valorie> so last night I tried apt-get install-f
[20:48] <valorie> and there is something in telepathy that could not be overcome, even with force-overwrite
[20:48] <valorie> layers of dependencies
[20:49] <valorie> so I uninstalled telepathy, which seems to have uninstalled most of kubuntu
[20:49] <valorie> including kubuntu-desktop, breeze, etc.
[20:50] <valorie> attempts to fix that are stymied; since there are broken packages it won't allow me to even install pastebinit
[20:50] <valorie> so I'm looking for some way to just get back to unity
[20:50] <genii> Maybe wget / dpkg -i pastebinit
[20:51] <Unit193> apt-get download pastebinit  for the lazy.
[20:51] <valorie> if I could get back to unity I presume I can install anything I want
[20:51] <Unit193> Why?  That's just the DE, unless you dual-boot.
[20:51] <valorie> but in the broken kubuntu, I can't install anything
[20:51] <valorie> dpkg and apt-get refuse
[20:52] <genii> If dpkg/apt-get fail there, will fail in unity also, since same backend
[20:53] <valorie> ok
[20:53] <valorie> I guess I'm looking at a reinstall
[20:53] <valorie> :(
[20:54] <genii> Getting pastebinit manually installed and seeing some output might help
[20:54] <valorie> sure
[20:56] <ahoneybun> 15.10 is running well here so far
[20:58] <valorie> ahoneybun: son couldn't find a bootable ISO, so he used unity
[20:58] <valorie> and the kubuntu install failed
[20:59] <ahoneybun> very weird
[20:59] <ahoneybun> I upgraded from 15.04
[21:00] <ahoneybun> valorie: https://community.kde.org/Kubuntu/Artwork
[21:02] <genii> valorie: In the end, probably faster to reinstall than dissect. Although I'm curious now what it's up to
[21:03] <valorie> I love it, ahoneybun
[21:03] <valorie> I think there was a packaging problem with telepathy
[21:03] <valorie> but I don't know why that should have brought down my system
[21:04] <Unit193> genii: More fun to figure it out. :P
[21:04] <genii> Unit193: My main problem right now is that I was awake at 4:30am and it's also payday/bills day right after work :)
[21:04] <valorie> any, from recovery I can get to root shell, so I'm willing to try
[21:04] <valorie> genii: you nut, go to bed!
[21:05] <genii> valorie: Maybe tomorrow then if system is still in the same state
[21:05]  * genii wanders off
[21:15] <ahoneybun> valorie: still can get to tty?
[21:15] <valorie> sometimes
[21:17] <ahoneybun> oh boy
[21:17] <ahoneybun> so apt-get is broke?
[21:17] <valorie> it's not that it's broken, it's that there is a file conflict that seemingly can't be resolved
[21:18] <valorie> or rather, numerous ones
[21:18] <valorie> see the backlog in #kubuntu-devel
[21:18] <ahoneybun> from today?
[21:18] <valorie> if I could install pastebinit it would help
[21:18] <valorie> last night
[21:19] <valorie> I wonder if I could download the deb and put it on a USB or something
[21:19] <camper> hi
[21:21] <ahoneybun> so you removed telepathy valorie?
[21:21] <valorie> yes, and that's what broke it
[21:21] <valorie> seemingly irretrievably
[21:22] <ahoneybun> oh
[21:22] <ahoneybun> so Unity wouldn't boot?
[21:22] <ahoneybun> do you have LightDM at all?
[21:22] <valorie> I don't know because it just always boots into kubuntu which is just a dark screen
[21:23] <valorie> and usually no access to terminal
[21:23] <valorie> no, just sddm
[21:23] <ahoneybun> so you installed the kubuntu-meta package ontop of a standard Ubuntu installation
[21:24] <valorie> son did, yes
[21:25] <ahoneybun> valorie: http://cdimage.ubuntu.com/kubuntu/releases/wily/alpha-1/ ?
[21:26] <valorie> I don't know if he tried that
[21:27] <ahoneybun> if wily works decent so far with dealing Nvidia+intel Prime crap I have high hopes for a simpler Intel setup :)
[21:30] <valorie> I guess I'll download that and write it to a thumbdrive and see if it boots up
[21:30] <valorie> can
[21:30] <valorie> 't be worse than what I have now
[21:34] <valorie> ! on like the 40th restart, it seems to be working normally, which ..... can't quite believe, so I'm doing updates
[21:35] <valorie> woah, I now see what people mean about the update thing being annoying
[21:36] <valorie> ubottu: gosh you are sweet
[21:41] <valorie> and now seemingly doing a full-upgrade
[21:41] <valorie> can't actually quite believe it
[21:41] <valorie> torrenting the alpha anyway, just in case
[22:28] <bprompt> !bot | valorie
[22:28] <bprompt> what the?


[00:01] <ScottK-laptop> OK. So quassel 0.5.0 seems to work.
[00:01] <ScottK> ScottK-laptop: Ping.
[00:02] <ScottK-laptop> Ship it ....
[00:05] <ScottK> Riddell and Sput: Finall Quassel 0.5.0 uploaded.
[00:06] <Sput> \o/
[00:06] <Sput> thanks :)
[00:06] <ScottK> A full 54 minutes before final freeze.
[00:06] <Sput> we're getting better
[00:06] <Sput> next time we'll waste even less time!
[00:07] <JontheEchidna> ScottK: eek, could you upload kde4libs then?
[00:08] <DarkwingDuck> 54 Min?
[00:09]  * Sput wasn't even aware that freeze was that close... when I asked the other day, I thought "Tue/Wed" included the usual 1 day package building buffer :)
[00:09] <Sput> or excluded, rather
[00:11] <JontheEchidna> ScottK, Tonio_, Riddell: also kdepim needs a sponsor for a package overwrite fix
[00:43]  * JontheEchidna gets a bit nervous
[00:47] <Riddell> JontheEchidna: fear not I shall upload
[00:47] <JontheEchidna> \o/
[00:48] <JontheEchidna> Riddell: there is a keycodes merge awaiting, but I do not know if 12 minutes before final freeze is the best time for a change like that
[00:49] <Riddell> JontheEchidna: keycodes?  which source package?
[00:50] <JontheEchidna> Riddell: kde4libs
[00:50] <JontheEchidna> [18:23:24] <debfx> I posted a merge request https://code.launchpad.net/~debfx/kdelibs/kaction-qt-keys/+merge/13388 to fix bug #293213
[00:58] <JontheEchidna> Riddell: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549308
[00:59] <JontheEchidna> 20_use_dejavu_as_default_font.diff is currently broken
[01:05] <Riddell> kdepim uploaded
[01:08] <lex79> another trying to overwrite, lp bug 451762
[01:11] <Riddell> kdebase-workspace uploaded
[01:16] <Riddell> uploading kde4libs with this changelog http://paste.ubuntu.com/293571/
[01:17] <JontheEchidna> cool, that should take care of all that I can recall needs done
[01:24] <Riddell> lex79: fixing
[01:24] <lex79> Riddell: I uploaded to bzr
[01:24] <Riddell> oh you got there first
[01:24] <lex79> yeah
[01:24] <lex79> :P
[01:25] <Riddell> uploading
[01:28] <Riddell> anything else needing uploading?
[01:29] <JontheEchidna> I'm good here
[01:31] <JontheEchidna> are things officially frozen or can I still sneak a universe upload in w/o motu-release approval?
[01:34] <Riddell> I don't think it's frozen yet
[01:38] <debfx> Riddell: seb128 uploaded the pidgin tray icon fix, but said he will probably drop it for karmic+1
[01:40] <Riddell> debfx: maybe pidgin will use the nice new systray spec by then (we can hope anyway)
[01:47] <JontheEchidna> bug 448865 needs addressing in some way or another
[01:58] <Riddell> mm, I could just upload the new qtcurve packages but it's the startkde stuff I'm worried about
[01:59] <DarkwingDuck> Is there a way to "undo" an update?
[02:00] <ScottK> JontheEchidna: Universe doesn't freeze for a while yet
[02:02] <ScottK> BTW, final freeze is sometime Thursday, so we just hit the opening of the window.  The actual time is left vague and depends on when slangasek decides.
[02:02] <ScottK> Stuff that fixes significant bugs will get through probably until Tuesday, just needs Ubuntu release approval.
[02:05] <JontheEchidna> now that my sleep button will work, I must make sure I set it not to hibernate/suspend my keyboard
[02:06] <JontheEchidna> I always accidentally hit it when trying to raise the volume
[02:10] <lex79> Riddell: are you uploading qtcurve stuff? there are new versions, 0.69.1
[02:11] <lex79> I'm uploading to bzr btw
[02:15] <Riddell> lex79: what's new?
[02:15] <lex79> bugfixes release, changelog: http://kde-look.org/content/show.php/QtCurve+%28KDE4%2C+KDE3%2C+%26+Gtk2+Theme%29?content=40492
[02:23] <lex79> 0.69.1 uploaded to bzr
[03:54] <JontheEchidna> Riddell: got another -workspace upload, for KDE bug 209271
[03:55] <JontheEchidna> debfx also had another patch for workspace, if it's something we want: https://code.launchpad.net/~debfx/kdebase-workspace/powerdevil-brightness-shortcuts/+merge/13390
[04:23] <ScottK> JontheEchidna: What does that fix?  brightness keys work fine for me now?
[04:24]  * JontheEchidna shrugs
[04:24] <lex79> http://launchpadlibrarian.net/33702652/buildlog_ubuntu-karmic-amd64.kdepim_4%3A4.3.2-0ubuntu4_FAILEDTOBUILD.txt.gz
[04:27] <ScottK> lex79: Archive skew.  Needs a retry after the amd64 binaries get published.
[04:28]  * JontheEchidna is wondering if i386 is published yet, I wanna test it out
[04:29] <lex79> ScottK: Yeah, I put the link here just for you :) just to remember you to retry :P
[04:30] <lex79> JontheEchidna: 386 is published
[04:30] <JontheEchidna> yeah, d/l'ing right now :)
[04:31] <JontheEchidna> same story with workspace: https://launchpad.net/ubuntu/+source/kdebase-workspace/4:4.3.2-0ubuntu3/+build/1292752/+files/buildlog_ubuntu-karmic-amd64.kdebase-workspace_4:4.3.2-0ubuntu3_FAILEDTOBUILD.txt.gz
[04:32] <lex79> seems kdelibs built on cpu Atom this night IoI
[05:47] <Lure> Riddell, ScottK: kdebase-workspace also needs retry on amd64: http://launchpadlibrarian.net/33702490/buildlog_ubuntu-karmic-amd64.kdebase-workspace_4:4.3.2-0ubuntu3_FAILEDTOBUILD.txt.gz
[05:48] <ScottK> Lure: It helps more to give a link to the build page.  I'll have a look.
[05:49] <Lure> ScottK: this one? https://edge.launchpad.net/ubuntu/+source/kdebase-workspace/4:4.3.2-0ubuntu3
[05:53] <ScottK> Lure: Yes, but even more specifically https://edge.launchpad.net/ubuntu/+source/kdebase-workspace/4:4.3.2-0ubuntu3/+build/1292752
[05:54] <ScottK> Retried.
[06:13] <Lure> ScottK: thanks
[08:42] <Lure> Riddell: just thumbs up - latest kde4libs fixes digikam crash in khtml for me
[10:14] <Riddell> Lure: awooga
[10:56] <Riddell> debfx: the brightness keys on my laptop work already, I'm not sure if that's done in hardware or somewhere else along the software stack but it would seem to clash with your merge proposal
[10:58] <debfx> Riddell: are you able to change the brightness using the battery applet?
[10:59] <Riddell> debfx: yes
[11:01] <debfx> so if it's handled by the hardware we would need to detect that
[11:02] <Riddell> right
[11:02] <Riddell> debfx: do brightness keys work for you without the patch?
[11:02] <Riddell> I notice I have this in my lshal output   laptop_panel.brightness_in_hardware = false  (bool)
[12:30] <debfx> Riddell: no they don't
[12:32] <davmor2> Riddell: I'm having to use adept_manager --dist-upgrade-devel-lts to get to karmic is this the way it's meant to be done?  p.s. I'm testing the adept from proposed
[12:45] <debfx> Riddell: are the brightness keycodes sent to X11 on your laptop?
[12:47] <Riddell> debfx: yes, XF86MonBrightnessUp and Down are
[12:48] <Riddell> davmor2: yes it is
[12:48] <davmor2> Riddell: Fails :(
[12:48] <Riddell> davmor2: how so?
[12:50] <debfx> Riddell: are you sure it's not handled by another power manager?
[12:50] <davmor2> the upgrade is now aborted.  Your system could be in an unusable state.  A recovery will run now (dpkg --configure -a) options report bug and close.  Problem is report bug points at +filebug :)  which in turn is redirected to how to file a bug :) yay champion
[12:51] <davmor2> Riddell: ^
[12:51] <EagleScreen> my brightness keys have never worked in 9.10
[12:51] <Riddell> debfx: I really don't know where they're handled I'm ashamed to say
[12:52] <Riddell> davmor2: so it ran the DistUpgrade tool and was upgrading to karmic?
[12:52] <EagleScreen> xev recognise my keys
[12:52] <davmor2> Riddell: Yeap
[12:52] <Riddell> davmor2: file and bug and attach the files in /var/log/dist-upgrade and I'll take a look
[13:04] <davmor2> Riddell: bug 452090 this is an sru test for sbeattie so I'm using adept packages from hardy-proposed.  term.log says it can't be uploaded it's empty but I'll double check that
[13:05] <davmor2> Riddell: yeah it's an empty file
[13:07] <Riddell> hum, there's no obvious errors in those logs
[13:12] <Riddell> dpm: desktop-kdepim-runtime doesn't exist upstream, it's strings are part of desktop-kdepim, could you upload desktop-kdepim's stings to desktop-kdepim-runtime in rosetta? (or is arne better to ask for that?)
[13:14] <jtechidna> Riddell: https://bugs.launchpad.net/ubuntu/+source/kubuntu-default-settings/+bug/293213/comments/20 hm...
[13:16] <Riddell> jtechidna: that bug should also have an entry open on kdebase-workspace which isn't yet closed
[13:17] <dpm> Riddell, you can ask either of us, but where should we fetch the desktop-kdepim translations from?
[13:17] <Riddell> dpm: desktop-kdepim is already in rosetta, it comes from kde-l10n-xx
[13:18] <jtechidna> Riddell: seems python isn't fixed? bug 451105
[13:19] <dpm> Riddell, in which kubuntu source package desktop-kdepim-runtime is in?
[13:20] <Riddell> JontheEchidna: checking
[13:20] <JontheEchidna> dpm: kdepim-runtime
[13:20] <dpm> thanks JontheEchidna
[13:21] <JontheEchidna> yw
[13:23] <JontheEchidna> Riddell: for brightness keys, bug 315001, perhaps bug 318327
[13:25] <Riddell> JontheEchidna: those are part of the same problem yes
[13:26] <Riddell> which I'm suspecting is more complex than it ought to be
[13:36] <dpm> Could anyone have a look at bug 450349? I think this has been mentioned some other times already, and after talking to Arne he seems to think language-selector could take care of those packages
[13:39] <Riddell> dpm: langauge selector does prompt to install kde-l10n-xx when it's missing for a used language
[13:40] <JontheEchidna> Tonio_: your arora default settings stuff causes a new input action entry to be added each login
[13:41] <JontheEchidna> (the mouse gestures stuff for KDE)
[13:41] <dpm> Riddell, it does it in Ubuntu, but it doesn't seem to do it in Kubuntu. I tried it yesterday and it did not prompt me to install the kde-l10n-ca package when I installed Catalan
[13:42] <JontheEchidna> ^update-notifier-kde hasn't notified about that for whatever reason since 8.10
[13:42] <JontheEchidna> upgrade hooks seem busted too
[13:43] <dpm> JontheEchidna, do you know if is there a bug about that already?
[13:43] <JontheEchidna> not that I'm aware of
[13:45] <JontheEchidna> why can't language-selector install 'em by default, though?
[13:46] <dpm> JontheEchidna, Arne tells me that it could do it (let me get him in here)
[13:47] <Quintasan> hiho
[13:47] <Quintasan> what's with updates? it calculates broken dependencies for 5 minutes :S
[14:02] <Tonio_> JontheEchidna: really wried.....
[14:02] <Tonio_> JontheEchidna: well drop them then
[14:03] <Tonio_> JontheEchidna: we have no time to waste on that
[14:03] <dpm> ok, language-selector now prompted me to install additional translation support and it did install the kde-l10n-* packages, but only the second time I tried to install a package...
[14:03] <JontheEchidna> Tonio_: it's a shame, and it seems you've tried to fix this before.. oh well
[14:05] <Tonio_> JontheEchidna: it's okay
[14:05] <Tonio_> you're right with the irst version I uploaded
[14:05] <Tonio_> JontheEchidna: but it works now, it just lached an "importid" field in it, which is there now
[14:06] <JontheEchidna> I installed the latest updates yesterday, rebooted and had two Arora entries in the KHotKeys kcm
[14:06] <JontheEchidna> a few days before that I had like 9 entries which I deleted
[14:08] <Tonio_> JontheEchidna: I just rebooted, and just have one
[14:09] <Tonio_> JontheEchidna: can you tail /usr/share/kubuntu-default-settings/kde4-profile/default/share/apps/khotkeys/arora-gestures.khotkeys
[14:09] <Tonio_> and tell me if you have an importid there ?
[14:09] <JontheEchidna> Tonio_: it has the importID there
[14:10] <Tonio_> and if you logout and login ?
[14:12] <JontheEchidna> before: http://imagebin.ca/view/qTO3BUaY.html
[14:12] <JontheEchidna> (brb, rebooting)
[14:16] <JontheEchidna> the weird thing is, I got a duplicate before I rebooted, in between the time I tested this morning and told you
[14:16] <JontheEchidna> but now I've rebooted and there is only one
[14:17] <Tonio_> JontheEchidna: hum, maybe because you updated kds right after your last reboot ?
[14:18] <Tonio_> I don't know
[14:18] <Tonio_> seems to work afaics
[14:18] <JontheEchidna> I did do an update this morning
[14:18]  * JontheEchidna reinstalls kubuntu-default-settings
[14:21] <Quintasan> wat, IRC Plasmoid - http://kde-look.org/content/show.php/IRC+plasmoid?content=108428
[14:22] <JontheEchidna> maybe it works now?  Do I need a notification to tell me that I have a popup dialog?
[14:27] <Quintasan> urgh, too late for an update
[14:40] <giordy> hi
[14:40] <giordy> I noticed a problem in update-notifier-kde
[14:40] <giordy> I've updated to karmic the day before yesterday
[14:41] <giordy> I tried to run it
[14:41] <giordy> as notifications were lacking
[14:41] <giordy> and I got this
[14:42] <giordy> $ update-notifier-kde
[14:42] <giordy> Traceback (most recent call last):
[14:42] <giordy>   File "/usr/bin/update-notifier-kde", line 29, in <module>
[14:42] <giordy>     from PyKDE4.kdecore import *
[14:42] <giordy> ImportError: No module named kdecore
[14:43] <giordy> anyone here?
[14:46] <debfx> Riddell: I checked how gnome-power-manger handes the brightness hotkeys
[14:47] <ArneGoetje> dpm: here
[14:48] <debfx> Riddell: if the the cached brightness doesn't match the current brightness, it doesn't change the brightness
[14:49] <debfx> and also checks the value of brightness_in_hardware
[14:51] <dpm> ArneGoetje, I was just commenting bug 450349 with Riddell and JontheEchidna, as it seems that the expected behaviour for language-selector would be to install the kde-l10n-* packages, which does not seem to do in all cases
[14:57] <ArneGoetje> dpm: actually the latest ubiquity should pull it automatically now... I will test it with the latest daily plus updates.
[14:58] <dpm> ArneGoetje, ah, sounds good. Could you please comment on the bug with the outcome of the test when you're done?
[15:01] <ArneGoetje> dpm: sure
[15:02] <dpm> thanks
[15:23] <Riddell> debfx: yeah so presumably powerdevil would need to do the same.  also an on screen indicator would be a big bonus
[19:01] <lex79> JontheEchidna: do we want choqok 1.0~alpha2 ? it's too late?
[19:01] <JontheEchidna> too late I'd say
[19:02] <lex79> ok
[19:06] <lex79> oh, I thought that we had the alpha1 in archive, we have still 0.6.6, so it's too late really :)
[19:53] <jussi01> Riddell: kubotujust doesnt like you :P
[19:54] <jussi01> argh.
[19:54] <jussi01> scrolled back and forgot to scroll forward
[19:54] <jussi01> so thats like from afew days back :P
[19:55] <DaskreEch> jussi01: Ha ha You have joined the Higgs boson in time travelling
[20:02] <DaskreEch> Lynx is LTS for Kubuntu ?
[20:05] <lex79> yes
[20:09] <DaskreEch> ok
[20:18] <EagleScreen> hello
[20:18] <DaskreEch> hi
[20:19] <EagleScreen> I feel that Arora loads pages faster in Kubuntu than in other distributions as OpenSuse, anybody can think why can be it?
[20:21] <DaskreEch> placebo efect?
[20:21]  * Sput knows someone who claims that firefox renders faster than arora
[20:21] <tsimpson> maybe it's to do with how they compiled Qt, but it's not a trivial thing to find out
[20:29] <EagleScreen> maybe.. because Qt libraries are the same
[20:37] <lex79> JontheEchidna: I've 40 arora entries in khotkey kcm
[20:39] <JontheEchidna> maybe we should remove it to be on the safe side... iirc it came in pretty late after feature freeze
[20:47] <firephoto> is the karmic installer suppose to download  and install all(?) the language packs?
[20:48] <tsimpson> probably not
[20:48] <JontheEchidna> lex79: btw, with the latest kernel, deleting files works. (you can see the deletion in dolphin without reloading)
[20:50] <lex79> JontheEchidna: yay :) and works also for extract archive? can you see the folder when you exctract an archive?
[20:52] <firephoto> there's a skip button too as the installer progresses. not sure what it's suppose to skip. seems to finish the install anyway when you click it but you just don't get to see it doing it's finishing thing.
[20:52] <lex79> JontheEchidna: I tried, yes it works
[21:02] <EagleScreen> karmic installer does not download language packages for me, i need to run language-selector later to install them
[21:11] <lex79> removing all arora entries manually and reinstallation kubuntu-default-settings the problem of duplicate entries disappears
[21:51] <EagleScreen> all you have done a good work with Karmic, congratulations
[21:52] <JontheEchidna> :)
[22:11] <DaskreEch> kolala Really does feel a lot nicer not only am I not hitting on any showstopper bugs (other than sound) It feels faster than Jackalope
[22:23] <Tscheesy_> on Karmic i have no Keycode-respond in xev on "Fn+BrightnessRaise/Lower" anymore - Kubuntu Netbook Edition, HW:nc10, vmlinuz-2.6.31-14-generic
[22:27] <Tscheesy_> (within Jaunty i used it with: xbindkeys xrandr xbacklight)
[22:35] <DaskreEch> Yeah I don't get PrintScreen bound to Ksnapshot anymore
[22:35] <DaskreEch> No sure what caused that
[22:44] <Tscheesy_> re - Lock-Fn-Key works - but then my PWD is not accepted


[00:56] <knome> tgm4883, superm1: you affected by/will want to fix bug 1284910 ?
[00:56] <knome> hmm, no bot... https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1284910
[03:01] <tgm4883> knome, yep, I think superm1 is fixing that


[09:51] <darkxst> so seb says we need RT approval for https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1330037
[09:53] <darkxst> should I subscribe release team to that bug?


[00:35] <skaet> Riddell, ScottK - images for Kubuntu are now up on the beta 1 tracker.   http://iso.qa.ubuntu.com/qatracker/milestones/302/builds.
[00:35] <skaet> hmm... just notice the back scroll,   sorry for the chatter.
[00:36] <skaet> On a separate but related noted,   https://wiki.ubuntu.com/SaucySalamander/Beta1/Kubuntu is available for your input now.
[07:40] <Riddell> sweet, we made slashdot :)
[07:41] <lordievader> Whoo, nice :D
[07:48] <Riddell> a random e-mailer points out a launchpad milestone I had failed to notice "WTG on breaking the 100k karma point barrier dude."  my day just gets better and better
[08:08] <smartboyhw> Hmm, the topic is TOO long
[08:17] <yofel> removed Alpha2 and 12.04.3 notes
[08:18] <smartboyhw> !testers | http://iso.qa.ubuntu.com/qatracker/milestones/302/builds
[08:23] <lordievader> smartboyhw: I'm already on it, testing amd64
[08:24] <smartboyhw> lordievader, good
[08:48] <Crumble__> hello all!  I apologize if I am not allowed to be here... but i need some help.  It is in regards to a linux mce install.  and a very strange df -h output. any help is appreciated.
[08:57] <lordievader> Crumble__: User support for Kubuntu is in #kubuntu.
[08:57] <Crumble__> thankyou lordievader  :)  have a good one
[08:57] <lordievader> Oem install still has problems...
[09:04] <soee> test 13.10 beta 1 ?
[09:04] <smartboyhw> Riddell, you want to enable the upgrade tests or not?
[09:04] <soee> im running saucy at home, except i have 2 NM widgets all is fine :)
[09:04] <smartboyhw> soee, we mean fresh install
[09:04] <smartboyhw> lordievader, ouch
[09:04] <smartboyhw> What problems?
[09:05] <smartboyhw> (We won't be respinning for OEM install problems I think BTW)
[09:05] <soee> smartboyhw, ok ill test in on VM at gome
[09:05] <soee> *home
[09:05] <smartboyhw> soee, great.
[09:05] <smartboyhw> Do the i386 might be good, since lordievader is doing amd64
[09:06] <kubotu> ::workspace-bugs:: [1206371] kwin is not starting: cannot find libwayland-egl.so.1 @ https://bugs.launchpad.net/bugs/1206371 (by Chupligin Sergey)
[09:07] <soee> can i do i386 on VM running in amd64 ?
[09:07] <smartboyhw> soee, yes
[09:07] <smartboyhw> Not the opposite though:P
[09:07] <soee> ok so np
[09:21] <Riddell> sigh, ubiquity broken on arm bug 1220139
[09:22] <Riddell> smartboyhw: yeah we should test upgrades
[09:22] <smartboyhw> Riddell, please add the testcases yourself:P
[09:25] <Riddell> ScottK: re bug 1220139 there's no known problem with pyqt/sip is there? I thought it was only pykde that had an issue
[09:25] <Riddell> everything else pyqt worked
[09:25] <Riddell> bug 1220139
[09:25] <Riddell> humph, well I made it public now
[09:26] <smartboyhw> Bug 1220139
[09:34] <lordievader> smartboyhw: They are minor, #1154535, #1204524
[09:34] <smartboyhw> Bug 1154535
[09:34] <smartboyhw> Bug 1204524
[09:35] <smartboyhw> lordievader, OK
[09:35] <lordievader> err that ^
[10:14] <mck182_> how the heck is it possible that regular package updates remove kde-window-manager package?
[10:15] <smartboyhw> mck182_, -.-
[10:15] <smartboyhw> What packages are you updating?
[10:15] <mck182_> just got returned a laptop with "unable to move windows"...apparently the user just installed offered updates to kde 4.11
[10:16] <mck182_> somehow that removed kwin
[10:16] <mck182_> that should just never ever happen :S
[10:20] <debfx> a bit hard to tell without sources.list{,d/*} and apt logs
[11:07] <Riddell> mck182_: the only thing I can think of that might cause that is if they have an obscure kwin theme installed which is incompatible with 4.11, we did recompile all the ones we could which are in the archive, but you're right it's not a good experience
[11:07] <Riddell> thanks for your testing lordievader
[11:07] <lordievader> No problem, Riddell :)
[11:20] <yofel> mck182_, Riddell: another thing is a weird issue I've seen with the mesa backports in precise. E.g. if you have the quantal backports installed and kde 4.10  then the upgrade to 4.11 can in some circumstances kill kde-window-manager.
[11:20] <yofel> the dependency resolver is rather strange when it comes to alternate deps and deciding what to install
[11:20] <mck182_> yofel: that might be what happened
[11:20] <Riddell> agateau: meh wireless ubiquity module causes crash when in ubiquity only mode bug 1220193
[11:37] <Riddell> lordievader: did you try oem?
[11:38] <Riddell> I just did it and keeps the oem user but also keeps auto login as owm user which is just confusing
[11:45] <Riddell> ah I already commented as much on bug 1204524
[11:48] <Riddell> yuck rekonq is crashy :(
[11:50] <Riddell> bug 1219695
[11:51] <Riddell> do we (release team) let it in?
[11:55] <Riddell> agateau: another issue I think I found on wireless bug 1220212 probably easy to fix this one
[11:56] <xnox> Riddell: that's chicken & egg problem, the solution is to move wireless step before "prepare" screen, that hasn't been done in the gtk_ui yet.
[11:57] <Riddell> xnox: aah good to know we're not alone :)
[12:01] <lordievader> Riddell: Jup got exactly the same on the oem test.
[12:03] <BluesKaj> Howdy folks
[12:04] <Riddell> hi BluesKaj, able to do any beta testing?
[12:04] <xnox> Riddell: where is qt.conf on Ubuntu ?
[12:05] <BluesKaj> Riddell:  maybe , what's up ?
[12:05] <Riddell> xnox: I have a ~/.config/Trolltech.conf
[12:05] <Riddell> xnox: I'd guess qt.conf is the qt5 equivalent but I'm not sure
[12:05] <Riddell> BluesKaj: beta 1 candidates need testing
[12:06] <Riddell> http://iso.qa.ubuntu.com/qatracker/milestones/302/builds
[12:06] <xnox> Riddell: ":/qt/etc/qt.conf using the resource system"
[12:06] <xnox> what's the resource system on linux ?! =)
[12:08] <xnox> Riddell: i've straced it to find out =)
[12:08] <BluesKaj> Riddell: I'm running kubuntu13.10 , and currently I'm fooling with ubuntu/unity ... I'll switch over and dist-upgrade
[12:09] <BluesKaj> Riddell:  or are you looking for ppl to install the beta image ?
[12:11] <Riddell> BluesKaj: yes install the candidate images or upgrade from raring
[12:12] <Riddell> xnox: I'd guess it's the file system :)
[12:12] <BluesKaj> I haave kubuntu 13.10 and ubuntu 13.10 on separate partitions already, Riddell
[12:13] <BluesKaj> ok will try the new beta image
[12:13] <Riddell> BluesKaj: a reinstall doesn't hurt :)
[12:16] <BluesKaj> Riddell:  np , I'll install the image to /
[12:37] <Mirv> I wonder if yofel or someone would be interested in merging latest pkg-kde-tools changes (well, one commit + version number bump) from Debian, or shall I do that? it'd be needed so that qtscript-opensource-src could be synced directly from Debian instead of patching the build dependency
[12:37] <yofel> don't count on me until next week, but go ahead if you want to do it
[12:38] <Riddell> Mirv: I can look at it, is it in the FFe?
[12:38] <Mirv> ok, I can do/prepare that if no-one else does, just a heads-up. it was added to the Qt 5.1.1 FFe bug #1219695
[12:38] <Mirv> Riddell: now it is yes, as Scott asked for it
[12:39] <Mirv> Riddell: thanks. although it can't be uploaded before the FFe is formally accepted, but it'd be nice to have that ready.
[12:39] <Riddell> Mirv: well I can accept that too since you did ask nicely
[12:41] <Mirv> Riddell: heh, that's fine as well
[13:08] <Riddell> Mirv: voila
[13:08] <Mirv> \o/
[13:08] <Riddell> Mirv: some new source packages in there?
[13:13] <Mirv> Riddell: yes, four, they haven't been addressed separately in the text. adding a comment about those.
[13:59]  * Riddell blogs http://blogs.kde.org/2013/09/03/kubuntu-commercial-support
[14:02] <smartboyhw> Riddell, \o/
[14:04] <smartboyhw> Riddell, BTW I do suppose you know that you are the only active blogger on KDE Blogs that submits blog posts more than 3 times a month? :P
[14:06] <Riddell> I do feel a little guilty that kde sysadmins maintains it mostly for my benefit
[14:06] <smartboyhw> Riddell, if you make your own blog, then I'm going to file a sysadmin ticket to shut it down\o/
[14:09] <BluesKaj> Riddell:  got some errors on boot after the install seemed to work ok . After the error appears , there's no KB response at the shell prompt.Here's the error list: http://pastebin.com/6feJgQKJ
[14:10] <BluesKaj> I tried to install twice ..guess I'll have to install 13.04 again and release upgrade
[14:11] <Riddell> BluesKaj: um yeah something very broken there
[14:11] <BluesKaj> ok , later
[14:44] <Riddell> hmm, upgrades on virtual machines are slow,I wonder if it's worth the effort compared to just bare metal
[15:25] <BluesKaj> ok, Riddell , solved the error and uuid recognition problemn with the beta1 install , I merely open an older kernel and rebooted , then the new install booted properly
[15:28] <Riddell> um hmm that's not an ideal issue
[15:28] <Riddell> BluesKaj: do you think you have any hardware which the default kernel wouldn't like?
[15:31] <BluesKaj> Riddell, Idid have a previous problem with Ubiquity hanging and unable to move any further on Kubuntu 12.10 iirc ,and 13.04 . Also 13.10 alpha daily would do the same . I suspected HW recognition problems , but I could never track it down exactly
[15:33] <BluesKaj> this has been the first successful clean install from a live-cd since 12.04 due to the troubles above
[15:34] <Riddell> for some definition of successful
[15:34] <BluesKaj> anyway Riddell , I'm happy it worked out
[15:35] <BluesKaj> ubuntu 13.10 installs ok tho , i have it on a separate partition
[15:36] <Riddell> BluesKaj: do you have a uefi laptop?
[15:36] <BluesKaj> no I'm running an older HP desktop
[15:37] <BluesKaj> with a couple of media pci cards in it
[16:34] <Arhi> hello
[16:37] <Arhi> Can I ask a question? Becouse i have problem with install
[16:40] <Arhi> huh...
[17:08] <shadeslayer> Arhi: #kubuntu for support
[18:17] <shadeslayer> !find /usr/lib/i386-linux-gnu/libpython2.7.so raring
[18:19] <shadeslayer> yofel: [  4%] make[4]: *** No rule to make target `/usr/lib/i386-linux-gnu/libpython2.7.so', needed by `lib/libcompoundviewer.so.4.11.1'.  Stop.
[18:20]  * yofel runs
[18:20] <shadeslayer> yofel: thoughts on explicitly adding libpython2.7-dev to kalzium build deps?
[18:20] <yofel> do that if it helps
[18:20] <shadeslayer> won't it help?
[18:20] <shadeslayer> why did amd64 build though
[18:20] <yofel> if that's the file it's looking for, it will
[18:20] <yofel> and the correct location
[18:21] <shadeslayer> why does amd64 pull in libpython2.7-dev
[18:21] <shadeslayer> :/
[18:28] <shadeslayer> yofel: we don't have a ppa:kubuntu-ppa/ninjas right?
[18:29] <yofel> we don't
[18:29] <shadeslayer> okay cool
[18:29] <shadeslayer> I uploaded to ppa:kubuntu-ppa/ninjas and didn't get a rejection email so far
[18:40] <shadeslayer> can someone atleast QA Saucy so that we can upload it?
[18:41] <shadeslayer> *QA KDE 4.11.1
[18:44] <soee> when Raring possible?
[18:44] <shadeslayer> soonish
[18:45] <shadeslayer> !find /usr/lib/libboost_python.so raring
[18:45] <shadeslayer> whut
[18:46] <shadeslayer> !find libboost_python.so raring
[18:46] <shadeslayer> o_o
[18:46] <tsimpson> !find libboost_python-py27.so
[18:47] <shadeslayer> ahh
[19:29]  * shadeslayer is compiling a patched kernel to fix his cable problems
[19:29]  * yofel wonders why everyone has kernel issues today
[19:32] <shadeslayer> not exactly
[19:32] <shadeslayer> I've been told that the cable might not be terminating the load correctly on one pin
[19:32] <shadeslayer> so I patched the kernel so that my mini DP always outputs TMDS mode
[19:32] <yofel> uh huh...
[19:33] <yofel> well, I guess that's better than me removing kernels to not hit the panics caused by bug 1220284
[19:33] <shadeslayer> yofel: http://paste.fedoraproject.org/36763/13782233/raw/
[19:33] <shadeslayer> ouch
[19:34] <shadeslayer> ofcourse, this patch doesn't really solve the problem, and I'll still have to get a replacement cable
[19:34] <shadeslayer> except now it's financially unfeasible to go to the place I got this cable from :P
[19:34] <yofel> heh
[19:35] <shadeslayer> cable cost me 2 EUR, cost of travel + time spent > 2 EUR
[19:35] <shadeslayer> so I'll just buy another one from a nearby vendor for a bit more cost
[19:38] <shadeslayer> hmm
[19:38] <shadeslayer> yofel: what do you recommend for kalzium
[19:38] <shadeslayer> adding those 2 python deps fixed it
[19:39] <yofel> well, for the backports just hack that into the hook IMO
[19:39] <yofel> or you'll have to backport avogadro
[19:39] <shadeslayer> I see
[19:39] <shadeslayer> korundum exhibits similar symptoms
[19:39] <shadeslayer> nepomuk-core-dev isn't pulled in
[19:40] <yofel> I think there it's kdepimlibs assuming nepomuk exists
[19:40] <shadeslayer> nope
[19:40] <shadeslayer> -- Skip KorundumModules bindings: Kate;Nepomuk
[19:40] <yofel> though I wonder why it would work in saucy
[19:40] <shadeslayer> and nepomuk-core-dev is pulled in in saucy
[19:41] <yofel> Setting up nepomuk-core-dev (4:4.11.1-0ubuntu1~ubuntu13.04~ppa1) ...
[19:41] <shadeslayer> yofel: can you take up korundum? I don't want to look at packaging right now
[19:41] <yofel> in raring too o.O
[19:41] <shadeslayer> oh
[19:42] <yofel> heh
[19:42] <yofel> oh lol
[19:42] <yofel> -- Could NOT find Nepomuk (missing:  SHAREDDESKTOPONTOLOGIES_FOUND)
[19:42] <shadeslayer> pft
[19:42]  * shadeslayer goes about fixing his Qt patch
[19:43] <yofel> wait a second: shouldn't nepomuk kinda depend on sdo o.O?
[19:45] <yofel> hm, kde-runtime depends on it
[19:45] <yofel> I'll add it to nepomuk-core-dev depends anyway
[21:40] <Riddell> http://www.eweek.com/developer/kubuntu-linux-emerges-from-ubuntus-shadow.html/
[23:01] <ronnoc> nice article, Riddell :)


[21:49] <pwnguin> who do i need to bribe with drinks to explain how ubuntu scales their moinmoin wiki?
[21:50] <belkinsa> Whut?
[21:50] <pwnguin> wiki.ubuntu.com uses moinmoin, right?
[21:51] <belkinsa> Yes, but a older version
[21:51] <pwnguin> i'm having a wealth of problems with wiki.ros.org
[21:51] <pwnguin> and i'm looking for other people running large moin instances =)
[21:51] <belkinsa> ubuntu is but Canonical IS is the maintainer of the wiki.
[21:52] <pwnguin> i know this
[21:52] <belkinsa> Okay, just checking
[21:52] <pwnguin> I have a lapsed membership from like 2008


[08:07] <tjaalton> bregma: hi, if you have xmir ported for 1.19 could you push the repo?
[09:00] <alan_g> greyback: happy with this? https://code.launchpad.net/~alan-griffiths/miral/merge-release-changelog/+merge/313783
[09:02] <greyback> alan_g: yep, acked
[09:04] <alan_g> thanks


[01:51] <jose> aisrael: gotcha, thanks!
[02:25] <thomi> thumper: does 'juju destroy-service <foo>' call the 'stop' hook for the service's juju charm?
[02:25] <thumper> thomi: by default, I think yes
[02:25] <thomi> hmmm
[02:58] <thomi> thumper: ...and 'juju destroy-service <foo>' should block until the 'stop' hook has finished, right?
[02:58] <thumper> no
[02:58] <thomi> oh?
[02:58] <thumper> nothing blocks
[02:58] <thumper> except bootstrap
[02:58] <thomi> ahhh, well that might explain something
[03:39] <thomi> thumper: is there a way to call a charms 'stop' hook from within a deployed unit? I'm seeing some odd things where calling 'service stop <foo>' does something different to asking juju to destroy the service
[03:39] <thumper> from the client do this:
[03:40] <thumper> juju run --unit=foo/2 'hooks/stop'
[03:40] <thomi> ahh, thanks
[04:38] <thomi> ok, problem solved. Turns out if your charm is missing relation-departed and relation-broken hooks (even though this charm doesn't use relations), 'juju destroy-service' won't shut down the service nicely... confusingly, 'juju debug-hooks stop' shows the stop hook getting called. I have no idea what's going on, but happy that I found a reproducible way to get things back into a sane state.
[09:49] <Zetas> i've got my openstack infra stood up and connected, everything is green across the board and i can login to horizon
[09:50] <Zetas> but im trying to make sure my changes to the ceilometer charm are working and im not sure how to force it to log something to the database
[11:26] <bloodearnest> hmm, any idea why I might be getting a permssion denied error running relation-get from inside a juju-run environment?
[11:26] <bloodearnest> specifically:
[11:27] <bloodearnest> relation-get --format=json -r db-admin:42 - updown-app/0
[11:28] <bloodearnest> some context: I previously added/removed the db-admin relation to perform a db migration
[11:28] <bloodearnest> if I juju run again, it works
[12:21] <lovea> users
[12:27] <lovea> Trying to use JUJU with aprivate Openstack cloud
[12:31] <lovea> All the Openstack endpoints, e.g. keystone and swift and nov-cloud-controller have IP addresses belonging to a management network. The juju bootstrap process fires up a juju-state-machine-0 but this is on the private tenant network and cannot see the management network endpoints. Bootstrap fails with connection errors. Any ideas?
[15:57] <mattyw> lazyPower, ping?
[15:57] <lazyPower> mattyw: pong
[15:58] <mattyw> lazyPower, hey hey, hope you're well... The mongodb charm. If I deploy 1 unit, relate it to my charm. Then add some units to mongo at a later date it should still setup a replicaset right?
[15:59] <lazyPower> mattyw: correct, i would test in a staging env however
[15:59] <lazyPower> i haven't looked at mongo in quite some time
[15:59] <lazyPower> i'm not even sure if we've upgraded to deploy the 3.x series
[16:25] <mattyw> lazyPower, ok thanks
[16:29] <lazyPower> Hmm.. do we not have access to unit-get in action context?
[16:29] <lazyPower> i take that back, we do when i'm in debug hooks
[16:37] <lazyPower> marcoceppi: tvansteenburgh aisrael - is there a pattern for calling actions from amulet? eg: i have a health check action, and i''d like to flex it in an amulet test. is our path forward for now to just subprocess call it and parse the output of the uuid? or is there a branch w/ action helpers pending?
[16:38] <marcoceppi> lazyPower: there is not a mechanism yet in amulet
[16:38] <marcoceppi> I'll open a feature request for it
[16:38] <lazyPower> ok, i figured that might be the case. Thanks for the confirmation
[16:38] <lazyPower> http://paste.ubuntu.com/11373549/
[16:38] <lazyPower> however that is silly nice to have, at a glance health check until we get the actual health-check hook
[16:41] <marcoceppi> lazyPower: we've talked a bit more about health and we're shying away from actions tbh
[16:41] <lazyPower> marcoceppi: considering its a stop-gap fix until the hooks are impl, whats the issue w/ an action?
[16:41] <lazyPower> just curious
[16:42] <marcoceppi> lazyPower: well it's not a wholistic view of health, which is what you really want, it's just a snapshot. cory_fu and I (and others) talked about using a monitoring relation instead for this
[16:43] <lazyPower> well, thats a fair statement in 80% of services out there. YOu're polling for a snapshot of a single units health vs the cluster - whereas this is a builtin of the service.
[16:43] <lazyPower> etcdctl does introspection of the cluster and reports a sanity check essentially - this is like the benchmark to figure out if your cluster is even configured properly
[16:44]  * marcoceppi nods
[16:44] <lazyPower> but most services wont have something like this, so yeah - 100% understood
[16:44] <lazyPower> and i agree w/ that statement too
[16:52] <tvansteenburgh> hazmat: are we on for 4pm today?
[16:54] <hazmat> tvansteenburgh: yup
[16:54] <lazyPower> yo yo hazmat o/
[16:55] <hazmat> lazyPower: greetings!
[16:55] <lazyPower> glad to see you're still kickin over there :)
[16:58] <jose> hey guys, any idea when that hvm patch for aws t2.micros is landing?
[17:26] <lazyPower> jose: i haven't heard anything about it yet
[17:26] <jose> lazyPower: huh. I saw the mp being approved on gh
[17:26] <jose> or, well, as you call it on gh, pr
[17:26] <lazyPower> seems like you know more about it than I do
[17:27] <lazyPower> if you're using the nightly docker container, should be able to test it now
[17:27] <lazyPower> or you can fetch/compile if you're opposed to using the container
[17:28] <jose> I'll check.
[17:31] <lazyPower> hmm... getting an interesting error when attempting to bzr branch lp:charm-helpers -  http://paste.ubuntu.com/11374382/
[17:32] <aisrael> lazyPower: I get the same error
[17:32] <lazyPower> marcoceppi: have we updated charm-helpers repo with anything? or is this a breaking change introduced in bzr?
[17:37] <jose> that issue should be there if the branch is set to be private, but it's public...
[17:38] <jose> lazyPower, aisrael: seems to be a LP error. getting it with another branch
[17:38] <lazyPower> thanks for confirming jose
[17:41] <marcoceppi> thats' weird
[17:41] <marcoceppi> lazyPower: what did you do to achieve this?
[17:41] <jose> marcoceppi: general LP error
[17:42] <lazyPower> marcoceppi: it appears to be an outage spurned by a launchpad rollout that just hit about 20 minutes ago
[17:42] <lazyPower> marcoceppi: see #is-outage, they're on it.
[17:42] <aisrael> Seems to be working now
[17:43] <lazyPower> aisrael: weird, still broken for me
[17:44] <jose> ^
[17:44] <lazyPower> must have a sweet canadian LP mirror thats got the fix
[17:44]  * lazyPower is instantly jealous
[17:48] <lazyPower> jose: try now, appears to be resolved for me
[17:48] <jose> +1
[17:48] <jose> thanks for the heads up
[19:02] <tvansteenburgh> dpb: can you meet at 3:30 instead of 4?
[19:03] <tvansteenburgh> dpb1: ^
[19:06]  * dpb1 checks
[19:06] <dpb1> tvansteenburgh: so, in 30 min?  (meeting is at "2pm" here)
[19:07] <tvansteenburgh> dpb1: yeah
[19:07] <dpb1> tvansteenburgh: ok
[19:07] <tvansteenburgh> cool, thanks
[19:47] <Zetas> i finally got my openstack system running but I'm not the best way to get images added. I followed marcoceppi's guide for standing up openstack on 2 machines but every image i try to add just sits there and says "queued" forever.
[19:49] <lazyPower> Zetas: incoming help
[19:49] <Zetas> i've tried uploading some of the images found at this url http://docs.openstack.org/image-guide/content/ch_obtaining_images.html
[19:49] <Zetas> ok thanks lazyPower
[19:51] <beisner> hi zetas - can you tell us the command you're using to add the glance image?
[19:51] <zetas> beisner: im adding it from horizon :/
[19:52] <beisner> zetas, ok, t-shooting needs command line.
[19:54] <zetas> ok, I thought maybe there was a command to add some basic images by default. When I stood up the openstack bundle on AWS it came with come coreos images if i recall correctly.
[19:54] <zetas> My manual installation did not
[19:55] <beisner> zetas, yep, glance will be empty by default.
[19:55] <lazyPower> beisner: are we planning on adding an action to glance to load up the Ubuntu images? *shameless plug*
[19:55] <beisner> zetas, as far as troubleshooting it, I'd use the glance command line api to confirm basic service functionality.   ie.     glance image-list       should exit 0 (good), even with no images.  that would confirm that glance is able to authenticate and talk to all of its friends.
[19:56] <beisner> lazyPower, you're the 2nd to ask ;-)   I think an "import all currently-supported Ubuntu cloud images" action would be really useful.
[19:56] <zetas> ok, i'll google for glance commands to add images and stuff as well, thanks for your help
[19:58] <zetas> hrm... beisner: i take it this isn't a good sign heh http://paste.ubuntu.com/11376730/
[19:58] <lazyPower> beisner: I should have known you cats were already on the trail for that one, but it never hurts to ask :)
[20:00] <beisner> zetas, http://paste.ubuntu.com/11376741/
[20:00] <zetas> ok awesome, thanks
[20:01] <beisner> lazyPower, so actually, the glance simplestreams sync charm has some awesomeness.   configure it and relate it to glance, and you always have fresh images in glance as they hit cloudimages.
[20:01] <beisner> but yeah, use cases for actions is likely to grow wildly.
[20:01] <lazyPower> wat
[20:01] <lazyPower> we have a charm that does this for you?
[20:01] <beisner> i think it needs a little updating love, but yep.
[20:02] <beisner> we use it in serverstack
[20:02] <beisner> that ensures that when CI nova boots new instances, they are the most up-to-date (smallest apt-get update delta).
[20:04] <zetas> woot it worked, thanks beisner
[20:08] <zetas> im gonna try cs:trusty/glance-simplestreams-sync-1
[20:08] <zetas> see how it works
[20:08] <beisner> zetas, great!  so before adding to it,  i'd poke around the cli to see if you can import a small cirros or ubuntu cloud image.   generally speaking, if glance image-list works, the apis and authentication are probably happy.   next line of t-shooting might be command syntax, image format, or a storage issue.
[20:10] <zetas> yea, image-list output an empty table
[20:10] <zetas> im gonna keep poking around the CLI while this allocates
[20:11] <zetas> my poor macbook is not loving running all these inside a virtualbox vm haha
[20:11] <beisner> zetas, an empty table with no errors is actually good.
[20:11] <beisner> echo $?
[20:11] <beisner> after glance image-list    to confirm it exits 0, without error.
[20:12] <zetas> 0
[20:12] <zetas> yep, seems to be all good
[20:13] <beisner> zetas, http://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img
[20:13] <beisner> zetas, glance image-create --name="trusty" --is-public=true --progress --container-format=bare --disk-format=qcow2 < trusty-server-cloudimg-amd64-disk1.img
[20:14] <beisner> zetas,  ^ those are rips from some automation which I know work.
[20:14] <zetas> awesome, as soon as it finishes downloading that image im gonna run it and see what happens
[20:15] <beisner> zetas, good luck, i've got to head out for a bit.
[20:15] <zetas> thanks for all your help beisner
[20:15] <beisner> zetas, you're welcome - happy to help
[20:15] <zetas> :)
[20:24] <zetas> hmm poop. I tried to deploy an instance with my new image but apparantely i don't have a hypervisor haha. I guess nova-compute isn't happy for some reason.
[20:24]  * zetas debugs
[21:59] <thumper> lazyPower: ping
[21:59] <lazyPower> thumper: pong
[22:00] <thumper> lazyPower: got a few minutes for a hangout?
[22:00] <lazyPower> thumper: not atm
[22:00] <thumper> lazyPower: will you later?
[22:01] <lazyPower> After dinner
[22:01] <thumper> eta?
[22:02] <thumper> lazyPower: are you east coast?
[22:02] <lazyPower> thumper: yup
[22:02] <thumper> lazyPower: so 6pm there now?
[22:02] <lazyPower> yup
[22:02] <thumper> when would be good?
[22:02] <lazyPower> i'll ping after i eat
[22:03] <thumper> :)
[22:03] <thumper> ok
[22:03] <lazyPower> i'll be around fairly late this evening, working on some leftover stuff from before holiday
[22:03] <thumper> kk
[23:44] <lazyPower> thumper: ping/pong - back from food
[23:47] <thumper> lazyPower: hangout?
[23:48] <lazyPower> https://plus.google.com/hangouts/_/canonical.com/django-afterhours
[23:48] <thumper> hah


[10:13] <jms> why would the display config screen in jaunty not offer resolutions over 1600x1200 on my external (vga) monitor?
[10:14] <RAOF> Could you pastebin the output of "xrandr -q"?
[10:16] <jms> http://paste.debian.net/44661/
[10:22] <RAOF> Ok, so that's why the display config screen won't offer higher resolutions :).
[10:22] <RAOF> It looks like it should only be offering up to 1024x768; is that what it's offering?
[10:25] <jms> it's offering 1024x768
[10:25] <jms> i think it's misinformed
[10:26] <RAOF> Probably.  I'd guess that your monitor doesn't provide correct DDC information.
[10:26] <jms> RAOF: well, yeah, except hwinfo is rather better informed
[10:28] <jms> and so is ddcprobe for that matter
[10:28] <jms> although... hm, interesting
[10:29] <RAOF> Hm?
[10:29] <jms> what's the difference between "timing", "ctiming" and "dtiming"?
[10:29] <RAOF> Do idea.
[10:29] <RAOF> No idea :)
[10:32] <jms> ddcprobe shows a max timing of:
[10:32] <jms> timing: 1024x768@75 Hz (VESA)
[10:32] <jms> but it also shows the correct maximum of:
[10:32] <jms> ctiming: 1600x1200@60
[10:32] <jms> so whatever voodoo nonsense xrandr uses to determine available modes, it ought to be offering the ctiming ones but isn't
[10:33] <RAOF> That'd be a driver issue.
[10:34] <RAOF> You should probably file a bug against the driver.
[10:34] <jms> (II) intel(0): Printing DDC gathered Modelines:
[10:34] <jms> (II) intel(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz)
[10:34] <jms> pretty sure the driver knows about the mode too
[10:36] <jms> hm, Bug #395140
[10:37] <jms> nope, similar but unrelated i think
[10:37] <RAOF> jms: I'd guess that the intel driver is filtering that out; it seems to suggest a refresh rate of 0.0Hz, which I wouldn't be surprised if the driver filtered out as obviously wrong.
[10:38] <hyperair> hmm? external monitor? it usually works for me, very well
[10:39] <tjaalton> what card is it?
[10:40] <tjaalton> jms: ^^
[10:40] <jms> tjaalton: intel
[10:40] <tjaalton> model?
[10:40] <hyperair> intel produces many cards.
[10:40] <jms> 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
[10:41] <jms> (II) intel(0): Integrated Graphics Chipset: Intel(R) Mobile Intel® GM45 Express Chipset
[10:42] <tjaalton> are you using clone mode?
[10:42] <jms> no
[10:42] <jms> the two displays don't have the same mode. and i'd be happy if vga-only worked as expected really
[10:43] <tjaalton> ok
[10:51] <jms> brb, rebooting
[11:05] <directhex> simultaneously fighting getting a TPM chip working with the 1600x1200 problem
[11:05] <directhex> hence reboots
[15:00] <jg> bryce: ping
[16:43] <AndyB> Hi, i am trying to install this https://edge.launchpad.net/~ubuntu-x-swat/+archive/xserver-no-backfill package so i can use desktop effects with my ati card. I have added the software sources but it does not say what do to next. Any advice?
[21:10] <mdz> bryce, I had a crash this morning which looked very much like bug 343528
[21:11] <mdz> bryce, but I'm quite certain I was running 1:2.2.2-1ubuntu2
[21:13] <bryce> hmm
[21:16] <bryce> mdz, and you see 	pEvdev = (EvdevPtr) 0x0  in the #0 call in your backtrace?
[21:22] <jg> bryce: I "up"graded to koala on this intel laptop: but it is a bit exciting, from the display point of view.  If I try the gnome display preferences program and enable the cmo panel, my screen goes almost entirely black (a few lines at the top seem to survive).
[21:23] <bryce> mdz, weird.  I rebuilt the package and verified the patch is getting applied properly and so on.  To my knowledge, it may still crash since we're papering over what is probably some deeper bug, however it should *not* produce the exact same backtrace.  i'd like to look at your trace if you still have it handy.
[21:24] <jg> bryce: and the X server has crashed at least once while playing around....
[21:24] <bryce> jg, bummer, does the same thing happen if you use only the xrandr tool?  (Gnome's implementation of the Xrandr stuff has proven to be incorrect in the past.)
[21:26] <jg_> bryce: to answer your question, xrandr is just as exciting.  typing xrandr<cr> does the same thing.
[21:26] <bryce> wow
[21:26] <jg_> definitely dramatic.
[21:26] <jg_> downright cool...
[21:26] <bryce> indeed
[21:27] <bryce> something is really bad on your system
[21:27] <bryce> can you post your Xorg.0.log.old somewhere?  (Or file a bug via `ubuntu-bug xorg`)
[21:28] <bryce> I have never yet seen a bug where running xrandr crashes the system.
[21:29] <jg_> bryce: didn't crash the system.
[21:30] <jg_> just screwed up the video on the panel entirely.
[21:30] <bryce> ohhh
[21:30] <jg_> (on the built in panel; all I did was type xrandr, no arguments.
[21:30] <jg_> quite fun, acutally.
[21:33] <jg_> bryce: exactly repeatable; plug the panel in, type xrandr, and the same thing happens again.
[21:36] <mdz> bryce, I couldn't retrace it, because it didn't leave a crash report behind (it is actually the crash which inspired my mail to -devel about apport)
[21:37] <mdz> bryce, the trace from the X server log is at http://pastebin.com/f1424d503
[21:41] <bryce> mdz, ok my guess here is that maybe it's crashing now due to something other than a null pointer
[21:43] <jg> bryce: anything you'd like me to try?
[21:43] <bryce> jg, well if you're game, we do have some debugging tools to use for cases like this, let me grab a link
[21:44] <bryce> jg, https://wiki.ubuntu.com/X/Troubleshooting/Freeze
[21:44] <jg> I'm game....
[21:44] <bryce> jg, what anholt will want is that batchbuffer dump
[21:44] <jg> bryce: the thing is, it isn't a freeze.
[21:44] <jg> Cursor still responds, and changes....
[21:44] <bryce> jg, changes?
[21:45] <jg> shape changes as to underlying windows.
[21:45] <bryce> hmm
[21:46] <bryce> ok, then maybe it can be treated as a blank screen issue
[21:46] <jg> so the server is still alive; the screen mostly dark, but a few lines on the top clearly come from someplace real (part of a panel).
[21:46] <bryce> https://wiki.ubuntu.com/X/Troubleshooting/BlankScreen - go to the section 'Register Dumps for -intel'
[21:47] <superm1> bryce, regarding bug 341898, what's in 529d1d72 ? did upstream mesa finally acknowledge it's a mesa bug?
[21:47] <bryce> hmm, well what you describe doesn't fall neatly into one of the known failure cases.  But my guess is that upstream would like either the register dumps or the batchbuffer dump
[21:47] <bryce> jg, maybe jbarnes can give some advice here?
[21:48] <jg> yeah, I've not seen anything quite like this bug in > 25 years of messing with video cards....
[21:49] <jg> bryce: I agree the register dumper is the place to start....
[21:49] <bryce> superm1, your comment on the upstream bug indicated that patch fixed it - https://bugs.freedesktop.org/show_bug.cgi?id=20843#c4
[21:50] <superm1> bryce, oh, that only fixed it for -vesa
[21:50] <bryce> superm1, maybe that bug report has become an aggregation of various unrelated issues?
[21:50] <superm1> yeah
[21:50] <bryce> :-(
[21:51] <superm1> well it's two issues that aggregated on there with similar symptoms
[21:51] <superm1> one of them was on -vesa and the other on -ati
[21:51] <jbarnes> jg, bryce: well the probe path is clearly doing *something* bad :)
[21:51] <superm1> the remaining open item was on -ati
[21:51] <jbarnes> jg: what chipset?
[21:51] <jg> jbarnes: Intel 945, IIRC.
[21:51] <bryce> superm1, it really makes it hard to determine the current status on a bug report, when it involves multiple unrelated issues on differing hardware.
[21:51] <superm1> as soon as we have new mythbuntu disks rolled for karmic (ttf-bitstream-vera is the end of me right now), we've got trunk builds of mythtv with QT4, which I heard don't exhibit these situations
[21:52] <jbarnes> jg: any reg dump differences before & after?
[21:52] <superm1> bryce, i agree.  i'll try to update the status of it and the description after I can have this data point with mythtv 0.22 / QT4
[21:52] <jg> jbarnes: I'm collecting data now.
[21:52] <bryce> superm1, because the bug is targeted to karmic, I'm getting management asking me for status on the bug
[21:53] <bryce> superm1, ah, so it is a QT bug?
[21:55] <superm1> bryce, well that depends on who you talk to :)
[21:55] <superm1> the mesa folks say its a QT bug, the mythtv folks say it's a mesa bug, and QT3 isn't developed anymore
[21:55] <jg> jbarnes: lots of differences...
[21:55] <superm1> i'm really hoping it just goes away with QT4 like I have heard.  if not, then at least QT4 people can weigh in on it too
[21:58] <jbarnes> jg: can you file a bug at fdo with the dumps attached?
[21:58] <jg> bryce, jbarnes: looks like 11 registers differ
[21:58] <jg> jbarnes: sure.
[21:58] <jbarnes> thanks
[21:58] <jbarnes> are they the mode timing regs by chance?
[21:58] <jg> jbarnes: what all do you want exactly?
[21:58] <jbarnes> (H_TOTAL etc)
[21:59] <bryce> superm1, ok thanks
[21:59] <jbarnes> jg: usual stuff, driver kernel x mesa versions
[21:59] <jbarnes> dmesg & x log
[21:59] <jbarnes> reg dumps from before & after
[21:59] <bryce> superm1, it would be wonderful if we could split the bug up into its constituent bugs, but if you think you'll be able to get the bug closed soonish it may not matter
[22:00] <superm1> bryce, yeah as soon as all of ttf-bitstream-vera's rdepends are cleaned up, I can verify it myself whether it's fixed
[22:00] <bryce> superm1, great thanks
[22:00] <jg> jbarnes: they are ADPA DSPACNTR DSPABASE PIPEACONF PIPEACONF PIPEASTAT DPLL_A DSPBSTRIDE DSPBBASE FENCE 3 FENCE 4 and FENCE 5
[22:00] <superm1> if it's not, then splitting it up is probably the next step and getting more updated data etc
[22:00] <bryce> superm1, we also have a newer mesa git build in xorg-edgers that could be tested
[22:01] <jbarnes> jg: oh hm
[22:01] <jg> lots of fun registers....
[22:01] <bryce> jbarnes, pipea bug?
[22:01] <superm1> bryce, okay good to know.  hopefully dont need to go down that route :)
[22:01] <jbarnes> jg: unless the pipe config got messed up or we're pointing at a different base I don't see why those would mess up your panel
[22:01] <jbarnes> bryce: that usually leads to hard hangs
[22:25] <jg> jbarnes, bryce: bug 23429
[22:29] <jcristau> clearly ubottu needs some more brains. :)
[22:30] <bryce> fdo #23429 ?
[22:30] <bryce> freedesktop bug #23429 ?
[23:29] <Ng> bryce: hrm, not sure those anti-random-power-event patches helped any :/
[23:29] <bryce> Ng, no?
[23:30] <bryce> Ng, I'd assumed they were confirmed to fix it
[23:31] <Ng> I updated this morning and got a new xserver core. set all my power management settings back from "never do anything" this afternoon and this evening I was just browsing the web and my laptop suspended
[23:31] <Ng> I wonder if there were associated changes to g-p-m
[23:32] <Ng> I also badly wish that syslog mentioned pm events and what triggered them
[23:34] <bryce> yeah
[23:34] <bryce> that's what I was just thinking myself...  if the fixes aren't fixing it, at least give us better debugging tools
[23:35] <Ng> I've just stabbed g-p-m and will leave it running in a terminal with --verbose, but I'm going to be really really offline for most of the next week
[23:43] <bryce> Ng, ironically my monitors just now blanked ;-)
[23:43] <bryce> (however I've not yet rebooted this box into the "fixed" xserver
[23:43] <bryce> +)
[23:45] <Ng> heh
[23:46] <bryce> Ng, maybe there are multiple bugs that result in the same symptom
[23:46] <bryce> so maybe the patches have helped, but they're just not sufficient to eliminate it entirely
[23:47] <Ng> yeah
[23:47] <Ng> or my laptop just hates my freedom ;)
[23:49] <bryce> Ng, is it screaming, "Put windoze on me pleeaaaseee..."?  :-)
[23:49] <Ng> haha
[23:50] <Ng> I ripped off its vista sticker, so it had better not!