[00:02] <lsv> yofel: so, it is the right one.  You were right about using the md5sum ;)
[00:02] <Daskreech> lsv: Well if you want to know gwenview and dolphin both do that so you can grep through those code bases or you can read the spec on freedesktop.org
[00:03] <Daskreech> or listen to yofel  :)
[00:03] <lsv> yofel: I still can quite get it, must be the spaces in the path.
[00:03] <lsv> Daskreech: haha
[00:03] <Daskreech> permafrost: can you ping the card?
[00:20] <lsv> well thank you yofel and Daskreech
[00:26] <Daskreech> Welcome
[01:42] <ken> #xbox
[01:46] <Daskreech> ken: hmm?
[01:51] <[Relic]> any dick cleaning util that shows progress?  I want to switch file systems but I want to purge and clean the whole drive before I do that
[01:51] <[Relic]> disk
[01:51] <[Relic]> guess I need a new keyboard that has letters on it again  :)
[02:14] <Daskreech> [Relic]: what counts as a purge?
[02:19] <[Relic]> I got a few other drives from misc computers I may want to use soon to so some sort of empty space overwrite
[02:20] <[Relic]> looking for something that at least shows say % done or something like that to see how long it will take
[02:27] <Daskreech> [Relic]: but by purge you mean scrub all data?
[02:27] <[Relic]> yep
[02:28] <[Relic]> would like to be able to purge free space only too, does dd do that or just whole drives?
[02:29] <Daskreech> ?
[02:29] <Daskreech> So you want to scrub all data but only where there is no data?
[02:31] <[Relic]> I want #1, zero? the whole disk and #2, zero? the unused areas on the disk
[02:31] <Daskreech> dd will do the whole disk
[02:32] <Daskreech>  there was an application in Ubuntu that would do free space but I don't know if they still have it
[02:34] <[Relic]> can dd do each partition?
[02:39] <Daskreech> [Relic]: Yep Or portions thereof
[02:40] <[Relic]> then I will use that
[02:46] <Daskreech> [Relic]: The parts thereof are not data based but location based
[03:58] <GH0> Alright, I am having more issues. Getting really ticked off.  This is the fourth time I have had to remove one of the updates for me to have a functioning desktop. The problem is I don't know what update is causing it. Restarting kdm service, deleting my .kde folder, none of that is helping.
[04:01] <Daskreech> GH0: Easy with the language. What did you do?
[04:01] <GH0> Installed Kubuntu, ran sudo apt-get update, then ran sudo apt-get upgrade. Restarted and now I am left with a semi-functioning desktop that only responds to left click.
[04:02] <Daskreech> Well it doesn't normally respond to right click :)
[04:02] <Daskreech> On Left click do you get add new panel ?
[04:03] <GH0> Yes, and when I add a new panel, the graphics look screwed up.
[04:03] <Daskreech> Is there a better explanation of screwed up?
[04:04] <GH0> It looks like the panel is artifacting. That is the best explanation that I can give you right now besides taking a picture.
[04:05] <GH0> Actually, I can't take a picture as my phone is dead
[04:13] <dskreech> GH0: Sorry. Something killed my connection
[04:13] <dskreech> GH0: Did you respond to my query on the panel?
[04:22] <faitdarkness> hello
[04:24] <faitdarkness> ...
[04:24] <GH0> dskreech, yes, after letting it sit for twenty minutes everything magically begin to work.
[04:24] <dskreech> GH0: Hooray I guess?
[04:24] <GH0> Though, I think I may be fit with the problem of the hostname not broadcasting or responding to other machines.
[04:24] <dskreech> Tried testing it?
[04:25] <dskreech> faitdarkness: Hello
[04:27] <GH0> Yeah: Ping request could not find host server. Please check the name and try again.
[04:27] <GH0> Right now, I have a <IP_ADDRESS> localhost and <IP_ADDRESS> server
[04:28] <GH0> I have googled this problem, but the resolutions that have been put forth are run your own dns server (which I intend on doing, but the setup/guide that is given out is for domain groups) or add an entry to your hosts file which isn't feasible because I have guests that access this server.
[04:29] <lanc3r> whats your problem GH0?
[04:29] <GH0> when I attempt to access my server by it's hostname on the network, it isn't responsive. If I access it by it's ip address, it works fine.
[04:30] <lanc3r> Apachae?
[04:30] <GH0> No, just the server itself. "ping server" or vnc'ing into server:1, samba (which I know I can set in the config for), etc.
[04:31] <GH0> I do have apache installed though, yes.
[04:32] <lanc3r> i dont know man, the only server experience i have is hosting a few games.
[04:35] <dskreech> Well you need the DNS entry then
[04:39] <GH0> Yes, but in past installs, the entry prepopulates everything. I will try restarting my router and all other boxes tomorrow and see if that fixes the problme. Right now it is juyst time for me to chill out and go to sleep. I need to unwind
[04:40] <lanc3r> fire it up.
[04:41] <dskreech> It should propogate that's true
[04:41] <dskreech> OK
[06:02] <vipin> Hi anyone please explain me why rekonq take too much time at the very first load of web page. Once the very first page loaded. Even if you close and open the rekonq. It load the page fast. I'm using rekonq
[06:02] <vipin> Version 0.9.1
[06:04] <Daskreech> WOuldn't hazard a correct answer without knowing more but maybe it's the DNS lookup?
[06:05] <Daskreech> Chromium does the same thing here
[06:06] <vipin> I'm able to see google chrome or any other browser donot have this behaviour.. Only for rekonq you can notice this very clearly in kubuntu 12.04 beta2.
[06:11] <Daskreech> This happens once you boot up?
[07:52] <naftilos76> hi, what does akonadi do? Does it just keep emails as a list in a db or also keeps attachments and main body contents?
[08:06] <Daskreech> Ah right I had noticed that beforehi
[08:06] <Daskreech> kjfslkj
[08:06] <Daskreech> 3[D[Clk;;lk/window 2
[08:08] <Daskreech> naftilos76: It's a cache for data so if you have attachements small enough it will keep them in the DB
[08:08] <Daskreech> ok sorry for the outburst but the keyboard froze
[09:21] <guyvdb_> Hi, I downloaded kubuntu-11.10-desktop-amd64.iso. When I boot there is no install options. When I run live CD I get a login error and then a username/pasword prompt (login manager). What is going on?
[09:22] <Peace-> guyvdb_: bad iso ?
[09:22] <Peace-> download again
[09:23] <Peace-> !checksum
[09:23] <guyvdb_> hmm.. how can i check it
[09:23] <guyvdb_> :) thx
[09:25] <guyvdb_> where is the checksum for kubuntu-11.10-desktop-amd64.iso I do not see it on the download page
[09:26] <guyvdb_> oops found it
[09:27] <guyvdb_> checksum is correct.. any other ideas... could it be a bad burn?
[09:27] <Daskreech> could be there is a way to check the CD when you boot it up
[09:28] <guyvdb_> ok.. but it seems strange there is no "install" option in the first menu displayed
[09:28] <guyvdb_> will try reburn
[09:28] <Daskreech> What are the option given?
[09:29] <guyvdb_> boot from cd / boot from disk / check cd / one other -- i thing test mem
[09:29] <guyvdb_> thing = think
[09:30] <Daskreech> Check CD is the way to check the CD when it boots up
[09:30] <guyvdb_> I am trying that now
[09:31] <Daskreech> ok
[09:31] <guyvdb_> I have not looked at KDE since 3.5, I had a look at it by installing it on my ubuntu 11.10 and it is pretty awesome. Going to try it out on a new machine I am building
[10:18] <amichair> kubuntu-devel-release-upgrade on oneiric says 'no new release found' - how do I get it to upgrade to precise beta (or is it RC by now)?
[10:18] <guyvdb_> reburnt the cd and all is working now... thanks for the help
[10:37] <amichair> kubuntu-devel-release-upgrade on oneiric says 'no new release found' - how do I get it to upgrade to precise beta (or is it RC by now)?
[10:47] <ltlynx>  Hello everyone! I've just installed Kubuntu 11.10 on my netbook it has an Intel Atom N270 1.6 GHz processor, 1 GB of RAM. My problem is startup sound is delayed it doesn't play after the animation but it plays along with notifcations. What do I need to do to make it play ahead of the notifications?
[11:46] <BluesKaj> Hiyas all
[11:51] <meNtha> o/ BluesKaj
[11:52] <BluesKaj> hi meNtha
[12:43] <c0p3rn1c> I'm having trouble using activities on KDE 4.8.2, if I enable the option, "Different widgets for each workspace",  they widgets disapear and I can't get them back, is this a bug or am I doing something wrong?
[12:45] <Izinucs> c0p3rn1c: have you changed workspaces to see if they are there?
[12:47] <JJeronimo> oh wait, I can however put widgets on my desktops
[12:48] <JJeronimo> just not the ones in my preconfigured activities
[12:55] <JJeronimo> is it possible to link activities to a virtual desktop?
[12:57] <JJeronimo> wait ... that maybe defeats the purpose :)
[12:57] <JJeronimo> no it doesn't
[13:00]  * JJeronimo found a nice website about switching activities http://hanschen.org/2011/05/15/7-ways-to-switch-activities/
[13:51] <burhan> in the default kubuntu irc client, how do you setup authentication?
[13:52] <Xabster> whats the name of it? i replaced mine
[13:53] <burhan> ah got it.
[13:53]  * burhan first time kubuntu user
[13:53] <burhan> I really couldn't stand unity :/
[13:53] <Tm_T> burhan: you mean identification to freenode? place your account password to server password field
[13:54] <Tm_T> you might like to prefix the password with <youraccountname>:
[13:54] <burhan> really? I just added it to the default identity
[13:55] <burhan> I guess no way to use irssi style /ignore here :/
[14:01] <Tm_T> burhan: I believe it has very similar ignore
[14:01] <Tm_T> I'm irssi user myself though
[14:02] <burhan> I can't believe kubuntu installs mysql-server as a dependency
[14:04] <robertzaccour> I've got a problem trying to launch Kdenlive "kdenlive MLT's SDL module not found. Please check your MLT install. Kdenlive will not work until this issue is fixed." any suggestions?
[14:13] <phypsilon> hi everybody
[14:14] <phypsilon> has anybody experienced high cpu usage by virtuoso-t with 12.04 Beta 2 ???
[14:19] <Peace-> phypsilon: me no
[14:31] <dirty-green> bonjour ?
[14:32] <Peace-> !fr | dirty-green
[14:34] <BluesKaj> phypsilon, yes I have , but since the last upgrade/dist-upgrade it stopped that behaviour
[14:38] <BluesKaj> !pm | phypsilon
[14:59] <sunder> why is acmkdir (part of autotools) not in apt?
[14:59] <tsimpson> what is "acmkdir" supposed to do?
[15:00] <sunder> setup a new project structure for c/c++
[15:00] <sunder> its part of gnu autotoolset
[15:01] <sunder> well, its part of it if you go to their sourceforge project
[15:01] <sunder> but if i pull up autotoolset in Muon, it is not in that package
[15:01] <sunder> and its not its own stand alone package either
[15:01] <sunder> i dont understand why, google is of little help
[15:06] <sunder> nvm, looks like i need to use autoproject instead (im guessing)
[15:08] <tsimpson> sunder: autotoolset is not a GNU project (though it's under the GNU GPL)
[15:08] <tsimpson> so it's just not packaged in Debian and subsequently Ubuntu
[15:09] <sunder> hmm, what does it mean to be a GNU project then? are there *no* non-gnu packages in debian?
[15:11] <sunder> you mean autotoolset as a whole (autoconf, automake, etc) is not a gnu project, but the individual components can be?
[15:11] <tsimpson> no, a GNU project is a project created and maintained by GNU. I just meant that it's not part of the GNU autotools project, which is a standard way to configure things
[15:11] <tsimpson> autoconf and automake are not part of autotoolset, it's part of autotools
[15:12] <sunder> i guess i see
[15:12] <sunder> i found autoproject, it appears that does what acmkdir does
[15:12] <sunder> from reading high-level descriptions of them both :)
[15:43] <robertzaccour> Yes kdenlive launches fine in 12.04
[15:59] <venky80> anyone using external monitor with their laptop in kde 4.8.2 I would like to compare my setup with yours all my settings are reset after restart
[16:03] <zeus> hi - i have a question..: my mouse is crasy..  jumps allways to my 2. Monitor (i have 2 monitor) grafic: nvidia  - anyone know the matter?
[16:04] <venky80> zeus can you verify that your settings is remembered after restart?
[16:06] <zeus> half  an hour ago the xserver worked well... i install some programms like superkaramba etc. an now i have the problem...
[16:06] <zeus> the old xorg.conf i haved backuped - but reset it won't work
[17:12] <jacobrask> How do I upgrade my installation to 12.04? There seem to be some bug fixes in mtp that I need and I figured I might just as well upgrade now instead of waiting
[17:12] <Sentynel> jacobrask: sudo do-release-upgrade -d to upgrade to the development release
[17:13] <tsimpson> jacobrask: use: https://help.ubuntu.com/community/PreciseUpgrades/Kubuntu instead :)
[17:14] <tsimpson> basically run "kubuntu-devel-release-upgrade"
[18:05] <jacobrask> thanks
[18:28] <jacobrask> kubuntu-devel-release-upgrade says "No new release found"
[18:30] <jacobrask> Maybe I used 12.04 when I reinstalled this machine in late frbruari or something, but /etc/lsb-release says 11.10
[18:54] <Daskreech> jacobrask: If it says 11.10 I'd beleive it
[19:01] <Sentynel> jacobrask, Daskreech: interesting; I get the same result (no new release found), and I'm definitely on 11.10
[19:10] <Daskreech> Sentynel: what are you looking for?
[19:10] <Daskreech> jacobrask: do-release-upgrade -d ?
[19:12] <Sentynel> Daskreech: that and the kubuntu-devel-release-upgrade tool both return "no new release found"
[19:12] <jacobrask> Daskreech: same
[19:12] <Sentynel> I'm not personally trying to update, just verifying jacobrask's result
[19:21] <Daskreech> jacobrask: hmm Might want to ask in #ubuntu+1
[19:32] <Volspor> Anyone using 12.04 beta?
[19:33] <Daskreech> Volspor: That would be in #ubuntu+1
[19:33] <Volspor> Okay.
[20:24] <husk> can anyone reccomend a Kubuntu compatible VPN provider? tried iPreditor with no luck
[20:26] <Sentynel> husk: I use witopia; they provide an openvpn-based system, which works fine with *ubuntu
[20:27] <husk> Sentynel cheers will look
[20:29] <Guest11969> is kubuntu desktop suported in 12.04
[20:34] <BluesKaj> Guest11969, kubuntu-dektop is part of kubuntu by default , hence it's supported by all kubuntu OSs
[20:34] <BluesKaj> kubuntu-desktop
[20:38] <jstaniek> Hi, any kubuntu 11.10 users here willing to help? Just run Calligra Kexi to see if the package works. http://forum.kde.org/viewtopic.php?f=221&t=101449
[20:39] <Guest11969> how do i install kubuntu-desktop in ubuntu 12.4?
[20:40] <BluesKaj> Guest11969, open a konsole / terminal ,  sudo apt-get install kubuntu-desktop
[20:42] <BluesKaj> Guest11969, but don't use the muon/software center to update any packages , it's buggy , if you have synaptic installed use that , if you don't , sudo apt-get install synaptic , in a terminal
[20:44] <BluesKaj> Guest11969, or you can use the terminal and do , sudo apt-get update && sudo apt-get upgrade
[20:44] <Terry_> Good morning, all
[20:45] <BluesKaj> 'morning
[20:46] <Terry_> I'm in Qld, how about you?
[20:48] <BluesKaj> Qld ?
[20:48] <Terry_> Australia
[20:49] <BluesKaj> Ontario Canada
[20:49] <Guest11969> how do i add open as administrator entry in nautilus context menu?
[20:49] <Terry_> whats the time there?
[20:50] <BluesKaj>  alt+F2 , kdesudo nautllus
[20:50] <BluesKaj> Guest11969, ^
[20:50] <BluesKaj> 4:50 PM here
[20:51] <amichair> is do-release-upgrade -d (run on 11.10) supposed to install 12.04 beta?
[20:51] <yofel> amichair: yes
[20:51] <Terry_> Wow its 0651 AM here, mate
[20:52] <amichair> yofel: and if is says 'No new release found'...?
[20:52] <BluesKaj> amichair, make sure you update and upgrade in 11.10 first . it will speed things up
[20:52] <amichair> BluesKaj: already up to date
[20:52] <yofel> amichair: what is Prompt= set to in /etc/update-manager/release-upgrades ?
[20:53] <yofel> I think it'll only work if that's set to normal
[20:55] <amichair> yofel: lts. strange, since software-properties-kde is set to 'normal'
[20:55] <yofel> amichair: bug 944876
[21:00]  * BluesKaj looks forward to fun with kubuntu 12.10 ... 12.04 is already becoming old to me :)
[21:00] <yofel> lol, +1 :D
[21:01] <amichair> I hope ath9k gets fixed too... this is barely usable
[21:04] <isme> hello
[21:05] <Terry_> hi, isme
[21:05] <BluesKaj> yofel, yeah  cmake doesn't work on 12.04 .... it says the compiler is in the wrong location , even tho it's in the right path
[21:06] <yofel> BluesKaj: can you remove the contents of the build folder (i.e. the cmake cache) and try again?
[21:06] <yofel> I can build konversation fine here
[21:06] <BluesKaj> from git ?
[21:07] <BluesKaj> dep-build just installs 1.4
[21:10] <yofel> BluesKaj: "sudo apt-get build-dep konversation" -> mkdir build -> cd build -> cmake .. -> http://paste.kde.org/457634
[21:10] <yofel> and that's konversation from git
[21:11] <yofel> the apt command is to install the build-dependencies
[21:11] <Daskreech> BluesKaj: Part of the reason taht I like Kubuntu is that it offsets the KDE cycle. So I can spend time screwing around with a broken Kubuntu till it releases then in about a month I cna start playing with a broken KDE till that releases :)
[21:12] <Daskreech> So I don't get bored to easily
[21:12] <Daskreech> I don't think I could survive them being too much in sync
[21:12] <Daskreech> FOSS is ridiculously sad
[21:14] <amichair> yofel: it looks like the bug is just the order of options in the gui combobox. reordering the combo according to the options (Never last instead of first) would work no?
[21:17] <yofel> amichair: maybe, I didn't look at the code long enough - I'll try to get a fix in that just shifts the index by 1mod3
[21:17] <amichair> yofel: the additional bug is that when u run do-release-upgrade,  or at least the man page or help, should say something about that settings and how it affects behavior
[21:17] <yofel> the GTK UI uses a dbus api now which works, but that's something for 12.10
[21:18] <yofel> amichair: feel free to file a bug about that
[21:18] <amichair> yofel: I thought it would be simpler to just reorder the combo items in main.ui, or more straightforward at least
[21:19] <amichair> yofel: but... whatever works :-)
[21:23] <BluesKaj> yofel the tutorial I was following was incorrect for 12.04...compiling with make now
[21:23] <yofel> amichair: could be, I'll have to ask mvo though what an effect that'll have overall
[21:24] <BluesKaj> yeah Daskreech , i have too much time on my hands , so i get bored sometimes
[21:26] <BluesKaj> bbiab
[21:31] <Ezim> Daskreech, kubuntu 11.10 with kde 4.8.2 have been solid for me
[21:31] <Ezim> nothing of really importance bugs me
[21:34] <Daskreech> Ezim: Which is why FOSS is interesting You can never update if you don't want to or ride on code streaming from the developers keyboards
[21:35] <Ezim> Daskreech, true.
[22:16] <randomDude> my system tray panel widget is refusing to collapse its width to an acceptable width ( the width of its visible child icons )
[22:17] <randomDude> each time i add it to the pane, it some times takes up half the screen width with only five items in it... resulting in massive sections of blank space... screen is 1920x1680
[22:54] <amichair> I ran kubuntu-devel-release-upgrade, when installing packages X died and I re-logged in, now apt-get install -f says "Internal Error, No file name for libapt-pkg4.12" - how do I fix this?
[22:55] <Daskreech> apt-cache policy libapt-pkg
[22:56] <amichair> Daskreech: N: Unable to locate package libapt-pkg
[22:56] <tsimpson> amichair: try just running the updater tool again and maybe it'll just resume
[22:57] <amichair> tsimpson: the updater says there's nothing to upgrade (since it thinks it already did, I guess)
[22:57] <tsimpson> oh, you should trick it by editing a couple of files
[22:57] <tsimpson> let me just remember which
[22:58] <amichair> tsimpson: and that will fix the broken packages better than apt-get? doesn't it use it internaly anyway?
[22:58] <tsimpson> it should do, because it does a better job of upgrading than just apt-get
[22:58] <tsimpson> that's why it was invented ;)
[22:59] <amichair> oh, I thought at this point it's just running apt-get dist-upgrade
[23:00] <tsimpson> amichair: in /etc/lsb-release change "DISTRIB_CODENAME" to oneiric, then just make sure your sources.list and files in /etc/apt/sources.list.d/ are all pointing to oneiric or disabled. then run the updater
[23:04] <Daskreech> tsimpson: /etc/lsb_release? :)
[23:04] <tsimpson> yeah, that one
[23:04] <Daskreech> Bah did't hit pagedown
[23:04] <Daskreech> :)
[23:04] <tsimpson> change the other values as well, I'm not sure if I change one or all the last time the updater failed
[23:05] <tsimpson> and maybe /etc/issue{,.net}
[23:05] <Daskreech> Breaking on a apt package isn't great bythe way
[23:05] <Daskreech> I had apt uninstalled once
[23:05] <Daskreech> was't fun
[23:08] <amichair> tsimpson: did all that and ran the updater, and it gives an error message saying there are broken packages that it can't handle and need to be fixed using apt-get
[23:09] <tsimpson> ooh, that's not so good
[23:11] <Daskreech> can yu pastebin the error ?
[23:11] <tsimpson> I haven't seen a completely broken apt/dpkg system in a while
[23:12] <Daskreech> I have v_V
[23:13] <Daskreech> patience is a tricky jump for a grashopper who jumps too quickly
[23:14] <amichair> Daskreech: the do-release-upgrade error? I closed it already... it was in the gui, and just said in user-friendly english that some packages are broken and that they need to be fixed first using apt-get (or synaptic), no details
[23:15] <Daskreech> amichair: run it from the terminal then
[23:16] <tsimpson> use "sudo do-release-upgrade -d" in the terminal
[23:16] <tsimpson> so it doesn't use the gui method
[23:20] <amichair> ok, I set things back to precise, and ran apt-get -f dist-upgrade, and it seems to be doing something
[23:20] <amichair> let's see what happens...
[23:22] <Daskreech> well amichair went poof
[23:22] <Daskreech> and back! :)
[23:23] <amichair> yeah, the wireless drivers suck (when booting into windows on this laptop, wireless works great, but here it gets disconnected every few minutes and takes its time reconnecting... really annoying)
[23:24] <amichair> I'm running apt-get -f dist-upgrade, and it seems to be downloading a bunch of stuff
[23:28] <amichair> darn it, back to the error: E: Internal Error, No file name for libapt-pkg4.12
[23:28] <Daskreech> OK that's a sign resolution of the packages is running at least
[23:33] <amichair> apt-cache policy libapt-pkg4.12 says: Installed: 0.8.16~exp12ubuntu8
[23:35] <amichair> Daskreech: any idea what to do?
[23:42] <Daskreech> amichair: pastebin the whole policy output
[23:43] <amichair> Daskreech: http://pastebin.ubuntu.com/931861/
[23:44] <amichair> and http://pastebin.ubuntu.com/931864/


 Time for meeting is UTC
 The Calendar on Kubuntu.org is in UTC
 Yeah. I forgot I am on UTC now!
 Ooo yeah, good reminder, I had forgotten that too
 meeting?
 @ahoneybun, Later
 @ahoneybun https://kubuntu.org/event/awareness-promotion-marketing/?instance_id=2
 how much later?
 1 1/2 hrs time
 mm so 3pm my time
 ok works
[19:36] <valorie> ronnoc posted this in #kubuntu - https://www.reddit.com/r/kde/comments/7ae1cf/kde_papercuts/?st=j9kasnov&sh=99c54b5d
[19:36] <valorie> one of us should anser
[19:36] <valorie> answer, gosh
[19:46] <valorie> I did, but one of the devels would be good too
[19:52] <clivejo> what can we do?
[19:57] <valorie> if you read the comments, there is a lot of "kubuntu is the worst" stuff there
[19:58] <valorie> by actually responding to one of our potential users, it shows that we are responsive
[19:58] <clivejo> people have a right to there opinion and nothing you or I say will convince them otherwise
[19:58] <valorie> rik is fixing the notification issue for instance
[19:58] <valorie> of course
[19:58] <valorie> I just want us on the record responding, if possible
[19:59] <valorie> I didn't respond to the nay-sayers
 @Valoriez meeting?
[21:01] <valorie> logging in


[03:34] <Nikola> Hello ! unfortunately I have to write about my monitor again , I get a message from devs today that is really confusing
[03:35] <Nikola> I have 4k monitor and want to set resolution 2560x1440 2k on that monitor but after installing driver 2k option disappears
[03:35] <Nikola> "It appears 2560x1440 was a fake mode created by the open source driver.
[03:35] <Nikola> It's not a mode that is officially supported by the monitor itself,
[03:35] <Nikola> whose data I have decoded below:" this message I have from devs
[03:37] <Nikola> it is officially supported by monitor manufacturer or not I know that under any windows I can set 2k on that monitor anytime
[03:38] <Nikola> under fedora I was able to set 2k anytime after installing nvidia drivers ...
[03:43] <guiverc> Nikola, your issue is more of a support one as I see it (#lubuntu makes more sense for support), as Lubuntu does not manage xorg (it's a Ubuntu package where vanvugt is a developer) or nvidia as bug now applied to (again a Ubuntu development package; not Lubuntu; we're just a user of them)
[03:43] <guiverc> you've already spoken to a Lubuntu dev here (not me) and he provided all the support he could
[03:44] <Nikola> no I cant blame nvidia for that bug because I was set 2k on nvidia drivers on any linux except that one I have
[03:44] <Nikola> tell me how to blame nvidia if any linux distro is able to do that except this one I have
[03:45] <Nikola> why you redirecting me into ubuntu if I'm using lubuntu ? and utilities I have installed is lubuntu specific
[03:45] <Nikola> in ubuntus forum they will say install gnome and then come and tell us about your issue
[03:45] <guiverc> when I meant nvidia I meant `nvidia-graphics-drivers-460` which is specific to the kernel used; were other 'distros' using the same 5.11 kernel & kernel module?
[03:47] <Nikola> he didn't do everything he could , because you again will release OS that will be unable to handle 2k
[03:47] <guiverc> the 460.67-0ubuntu1 package is restricted, meaning Ubuntu control is minimal
[03:48] <guiverc> hirsute is frozen currently so changes are restricted, now requiring SRU & all fixes are too occur post-release in most cases now.. development will start soon on the i-series release
[03:49] <Nikola> so when it will release officially it might appear possible ?
[03:50] <guiverc> the release is likely exactly what we have now due to frozen state.
[03:51] <guiverc> 'drivers' are really kernel modules; the hirsute kernel freeze has already hit (https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue678#Hirsute_Hippo_.2821.04.29_kernel_freeze)
[03:52] <Nikola> I'm trying to understand simple things , there is experimental build close to release 22april as fa as I know , it is still planned to that date ?
[03:53] <guiverc> Yes the release is scheduled for 22 April - https://discourse.ubuntu.com/t/hirsute-hippo-release-schedule/18539
[03:54] <Nikola> good , another simple question , will I be able to get that 2k resolution on my monitor after official release or anytime soon (as I can get with ALL other dostros)
[03:55] <Nikola> I mean 1920x1080 is very big UI it hurts my eyes I can't work in CGI softwares in full HD .. nor I can work in them with 4k state that UI is very small it hurts my eyes
[03:55] <guiverc> I don't know sorry; I doubt much will change between now and actual release.
[03:57] <Nikola> I cant believe I need to change linux now because of that damn 2k resolution issue ... and there is lots of people on ubuntu + nvidia drivers + 2560x1440
[03:59] <guiverc> have you tried another desktop?  You can experiment easily  using *live* systems in try mode (no install), but what you're mostly describing isn't 'dstiro' releated by kernel (5.11) OR desktop related  (LXQt has less HiDpi support than some other desktops, but again more than others)
[03:59] <Nikola> I can't install nvidia on live right ?
[04:00] <guiverc> i forgot about that.... that for sure complicates things..
[04:00] <Nikola> you know what is main problem here , when asked about issue you are not treating that issue like yours
[04:01] <guiverc> xorg & nvidia are not Lubuntu packages.. we're just users of them
[04:01] <guiverc> and this is mostly a support discussion, not development (what this channel is intended for)
[04:02] <Nikola> but it says ubuntu-devel right ?
[04:02] <guiverc> this is #lubuntu devel, not #ubuntu-devel
[04:03] <guiverc> you could try #ubuntu-quality (great place for other flavors & testing or hirsute) or #ubuntu+1
[04:03] <Nikola> wait , you know way more about ubuntu than me for sure
[04:04] <Nikola> if I will switch to nouveau now if will be possible to set 2k on my monitor
[04:04] <Nikola> it means it takes that resolutions list from somewhere
[04:05] <Nikola> I mean that list of 3840-2160 , 1920x1080 etc
[04:05] <Nikola> those modes are listed in file somwhere on disk right ?
[04:07] <guiverc> I don't know sorry; I think they come from your GPU though in answer to query 'what modes you support' from the OS
[04:08] <guiverc> refer to comment #2 by Daniel/vanvugt on your bug report... (your monitor returned no support for the resolution)
[04:09] <Nikola> my monitor returned no support for resolution but all distros except that one can do 2k
[04:10] <Nikola> how do you think if ALL distros can do but that one can't is this monitor issue or something related to distro
[04:19] <guiverc> you're using distros in a way that is likely incorrect; were all distros using the same kernel thus same kernel modules (ie. drivers), as if they weren't your comparison is invalid/incomplete...  later kernels have better error checking (and you'll likely same restrictions with others when they use the same software stack unless you've missed something else in your comparison)
[04:20] <Nikola> I didnt miss anything all that kernel and distro comparisons are good , but I know 1 simple thing
[04:21] <Nikola> only lubuntu are unable to set monitor at 2k with nvidia drivers , I dont remember but I guess even focal fossa lubuntu was able to do that
[04:22] <Nikola> LTS one , focal fossa lubuntu , but this one cant.. after that you can blame distros , me , drivers , kernels etv
[04:23] <guiverc> if lubuntu focal could do it, then lubuntu can do it.   Focal has two kernel stack options, GA 5.4 or HWE which currently is 5.8, bu will become 5.11 when it reaches 20.04.3 so it'll risk having the same issue you're describing now, ie. kernel related and not distro related
[04:24] <guiverc> if you were good with focal & using the GA kernel, that is supported for 3 years from release by Lubuntu, ie. till 2023-April and could a solution
[04:25] <Nikola> I just wanted to be updated , of course I can roll back , is that good solution to rolling back ?
[04:25] <Nikola> according to you all ubuntu users will be unable to set 2k resolution while kernel will reach it's new release  ?
[04:26] <Nikola> then simple question why are kernel developers doing that to users ?
[04:27] <Nikola> do you understand that many people using ubuntu with all distros in CGI industry ?
[04:28] <Nikola> you can't have resolution issue in that situation , it's not UI issue or something simple and useless like that
[04:30] <Nikola> I'm comming from fedora , it was very good but little bit complicated compared to ubuntu , so I switched to ubuntu , fedora 34 was released weeks ago , it is new kernel new OS and of course can do anything with monitor 2k 4k 8k..
[04:31] <Nikola> all linuxes today can do 2k except that one , what is going on here ?  how to set that 2560x1440 entry back into monitor settings menu ? like it was in hippo while nouveau driver
[04:32] <Nikola> and devs are calling 2560x1440 mode fake , it's not fake mode if it works good.
[04:34] <guiverc> I didn't say ubuntu users won't be able to, I don't know enough.. I was trying to explain why you've had issues; Daniel was very explicit on your bug report.   Linux always moves; LTS users have two kernel stacks they can choose to use; GA that stays the same the entire life of the product, or the HWE that moves/follows upstream; been that way for a long time
[04:35] <guiverc> see https://wiki.ubuntu.com/Kernel/LTSEnablementStack and https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack  (the initial stack is chosen by the ISO you install; though recent server ISOs (subiquity) ask you which you want to use)
[04:36] <guiverc> Nikola, ^
[04:37] <Nikola> waht is that ?
[04:37] <Nikola> I dont want to reainstall whole thing I have all softwares installed and everything cutomized
[04:38]  * guiverc realized I didn't include you name in prior detail, so the ^ was to say who it was directed to
[04:39] <Nikola> guiverc , how many years are you using and helping to develop ubuntu \?
[04:40] <guiverc> you can re-install without loosing configs (https://phab.lubuntu.me/w/release-team/testing-checklist/ will show I last tested that with lubuntu hirsute on 9th of this month; select existing partitions & don't format)  but you can change stack (GA -> HWE or HWE -> GA for LTS releases; see prior links I gave)
[04:41] <Nikola> what I will do with that actions ? will I get back to focal fossa or what ?
[04:48] <guiverc> you always need to backup first, but you can boot & install fossa/20.04 or any release; manual partitining, use existing partitions & do not format.    (20.04.2 will use HWE kernel, 20.04 media will use GA)  .. here is an answer I gave somewhat recently that describes it somewhat  (something-else is Manual.Partininong with Lubuntu's calamares installer)
[04:48] <guiverc> Nikola, ^
[04:49] <guiverc> also note going backwards (older release) can have issues with certain programs, if you've used a newer feature in the later release that didn't exist in earlier release... that's program specific & isn't always easy to spot/predict so check what programs you use
[05:03] <Nikola> in other words I will stay with hippo and will try to solve that issue myself , if not I will repot a bug again maybe one day something will change
[05:03] <Nikola> thank you for your time . guiverc
[05:25] -lugito:#lubuntu-devel- [Lubuntu CI] merger_sddm FAILURE: https://ci.lubuntu.me/job/merger_sddm/304/
[05:25] -lugito:#lubuntu-devel- [Lubuntu CI] merger_calamares FAILURE: https://ci.lubuntu.me/job/merger_calamares/796/
[05:56] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/289/
[05:56] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_compton-conf just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_compton-conf/382/
[05:56] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/649/
[05:56] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/638/
[05:56] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/638/
[05:56] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/478/
[05:56] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/478/
[05:56] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_liblxqt/430/
[05:56] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_liblxqt/152/
[06:11] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/290/
[06:11] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_compton-conf just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_compton-conf/382/
[06:11] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_liblxqt/431/
[06:11] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/650/
[06:12] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_liblxqt/153/
[06:16] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/650/
[06:26] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/702/
[06:27] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/703/
[06:27] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/703/
[06:41] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/702/
[06:42] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/587/
[06:42] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/250/
[06:42] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/587/
[06:43] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/251/
[06:47] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/703/
[06:47] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/702/
[06:57] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-admin just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-admin/661/
[06:57] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-admin just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-admin/661/
[06:58] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-build-tools/363/
[06:58] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-build-tools/146/
[06:58] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-build-tools/363/
[07:12] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-admin just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-admin/661/
[07:13] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-build-tools/584/
[07:13] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-build-tools/147/
[07:13] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-build-tools/585/
[07:13] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-build-tools/585/
[07:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/734/
[07:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/734/
[07:44] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/734/
[07:59] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/196/
[08:09] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pcmanfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pcmanfm-qt/742/
[08:09] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pcmanfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pcmanfm-qt/742/
[08:09] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qps UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_qps/153/
[08:10] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qps UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qps/675/
[08:10] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_obconf-qt just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_obconf-qt/413/
[08:23] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_qtermwidget/157/
[08:23] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_obconf-qt just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_obconf-qt/413/
[08:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qtermwidget/854/
[08:24] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pcmanfm-qt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_pcmanfm-qt/441/
[08:24] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pcmanfm-qt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_pcmanfm-qt/165/
[08:24] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pcmanfm-qt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_pcmanfm-qt/165/
[08:24] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pcmanfm-qt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_pcmanfm-qt/441/
[08:25] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qps UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qps/447/
[08:25] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qps UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qps/447/
[08:25] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qps UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qps/676/
[08:29] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pcmanfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pcmanfm-qt/742/
[08:30] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qps UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qps/676/
[08:45] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_liblxqt/431/
[08:45] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_liblxqt/153/
[08:45] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/290/
[08:45] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/650/
[08:45] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/478/
[08:46] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/404/
[08:48] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/404/
[08:49] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/focal_stable_screengrab/851/
[08:49] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/638/
[08:49] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qtermwidget/855/
[08:49] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_screengrab/158/
[08:49] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_qtermwidget/158/
[08:49] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_screengrab/423/
[08:49] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_screengrab/423/
[08:49] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/focal_stable_screengrab/852/
[08:49] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_screengrab/159/
[08:50] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qps UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_qps/154/
[08:50] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_compton-conf FAILURE: https://ci.lubuntu.me/job/groovy_stable_compton-conf/383/
[08:50] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/479/
[08:54] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qtermwidget/855/
[08:54] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/focal_stable_screengrab/852/
[09:04] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/704/
[09:04] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/704/
[09:04] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/702/
[09:05] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-admin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-admin/661/
[09:09] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/703/
[09:19] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qtermwidget/855/
[09:20] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/735/
[09:20] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/735/
[09:20] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-admin just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-admin/662/
[09:21] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pcmanfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pcmanfm-qt/743/
[09:21] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pcmanfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pcmanfm-qt/743/
[09:21] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qps UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_qps/154/
[09:21] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qps UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qps/676/
[09:22] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_qtermwidget/158/
[09:34] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qps UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qps/447/
[09:35] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_liblxqt/153/
[09:35] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_liblxqt/431/
[09:35] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/290/
[09:35] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/650/
[09:35] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/479/
[09:35] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/404/
[09:35] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/focal_stable_screengrab/852/
[09:35] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/638/
[09:35] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-admin just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-admin/662/
[09:35] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_screengrab/159/
[09:36] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_screengrab/423/
[09:36] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/196/
[09:36] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/480/
[09:37] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/197/
[09:37] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_obconf-qt just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_obconf-qt/414/
[09:37] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/705/
[09:37] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/705/
[09:50] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/703/
[09:51] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_compton-conf just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_compton-conf/384/
[09:53] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/704/
[09:53] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qtermwidget/855/
[10:07] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_qtermwidget/158/
[10:07] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qps UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qps/447/
[10:08] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/focal_stable_screengrab/852/
[10:08] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/404/
[10:08] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_screengrab/423/
[10:08] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_screengrab UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_screengrab/159/
[10:10] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/736/
[10:10] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/736/
[10:11] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pcmanfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pcmanfm-qt/744/
[10:11] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pcmanfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pcmanfm-qt/744/
[10:11] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qps UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_qps/154/
[10:12] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qps UNSTABLE: https://ci.lubuntu.me/job/focal_stable_qps/676/
[10:23] <guiverc> kc2bez, you can close t179 (21.04 artwork) I believe now given daily has ...
[10:40] <kc2bez> Thanks guiverc I need to do some task management soon.
[10:41] <guiverc> when you find time right :)
[10:43] <kc2bez> Yes :) I should have some time today. I did some work on release notes yesterday so those are coming along.
[10:43] <guiverc> :)
[11:33] -lugito:#lubuntu-devel- [T179: Lubuntu 21.04 Artwork contest] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T179#4447
 NVIDIA comes pre installed on Ubuntu Official Release (the one from Canonical). I strongly recommend you to use it instead of Lubuntu because even been Lubuntu such a great distro must of the Desktop Environments don't proper support HiDPI nor Wayland session. (re @lubuntu_bot: (irc) <Nikola> I can't install nvidia on live right ?)
[11:37] -lugito:#lubuntu-devel- [T182: SDDM theme needs a full overhaul] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T182#4461
[11:38] -lugito:#lubuntu-devel- [T96: migrate from compton to picom] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T96#4465
[11:41] -lugito:#lubuntu-devel- [T188: Add kystemlog to the default install.] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T188#4476
[11:42] -lugito:#lubuntu-devel- [T175: GeoIP service in automirror module] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T175#4481
[11:43] -lugito:#lubuntu-devel- [T189: change name of Openbox config] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T189#4485
[11:44] -lugito:#lubuntu-devel- [T186: add keyboard layout flag] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T186#4489
[11:45] -lugito:#lubuntu-devel- [T173: Clean default-settings] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T173#4494
[11:45] -lugito:#lubuntu-devel- [T184: create mechanism to update Calamares and settings before running] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T184#4499
[11:47] -lugito:#lubuntu-devel- [T106: 18.04 SRUs] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T106#4504
 I'm going to point out this is Lubuntu Development channel - you might want to consider keeping these recommendations to yourself - post installation you can easily install the nVidia drivers. (re @Crixero: NVIDIA comes pre installed on Ubuntu Official Release (the one from Canonical). I strongly recommend you to use it instead of Lubuntu because even been Lubuntu such a great distro must of the Desktop Environments don't proper
 I'm not trying to offend anyone, although you allow one user to ask for support on a Dev channel. (re @teward001: I'm going to point out this is Lubuntu Development channel - you might want to consider keeping these recommendations to yourself - post installation you can easily install the nVidia drivers.)
 considering none of us were *around* that's a different issue
 it also doesn't help the user you *replied* to left shortly after their issue over 8 hours ago
 so...
 OK. I apologize for the disturb. (re @teward001: so...)


[07:41] <pitti> elopio: where are you running this? --flavor autopkgtest is a custom flavor that only exists in scalingstack
[07:41] <pitti> elopio: in principle that looks like a correct invocation, yes; add some -d after adt-run and ssh to see what happens
[08:08] <fgimenez> good morning
[08:23] <dholbach> good morning
[08:24] <zyga> good morning :)
[08:25] <didrocks> good morning dholbach, fgimenez and zyga!
[08:25] <dholbach> salut didrocks
[08:27] <fgimenez> hey hey didrocks, dholbach and zyga :)
[08:27] <dholbach> hola fgimenez :)
[08:31] <fgimenez> zyga, quick question for you (i guess), what is the minimum yaml for a snap to provide a skill, is this enough http://paste.ubuntu.com/15072870/ ?
[08:35] <zyga> looking
[08:36] <zyga> fgimenez: I think you can abbreviate that further to offsers: [bool-file]
[08:36]  * zyga checks the spec
[08:36] <zyga> type defaults to name
[08:36] <zyga> unless changed explicitly
[08:36] <zyga> fgimenez: are you building a snap that provides the bool file skill?
[08:38] <fgimenez> zyga, i'm beginning with integration tests for skills, i'm using the branch you pointed out last friday as a base
[08:38] <fgimenez> yep, thanks already looked at that, but was having problems after building the snap, let me try again and paste you the results
[08:38] <zyga> nice
[08:39] <zyga> fgimenez: sure, let's work together on this
[08:39] <fgimenez> zyga, great :)
[08:48] <clobrano> hello everybody, I assume that it's possible to install different version of the same snap, but I'm getting an error like this "failed to install: a package by that name is already installed". I'm installing a snap file in my filesystem, it's version is 0.7, while the version installed is 0.6. Any Idea? Thanks!
[08:51] <fgimenez> zyga, ok for the provider, the problems are with the consumer, probably uses: [bool-file] doesn't work there? http://paste.ubuntu.com/15072941/
[08:55] <zyga> fgimenez: hmm, yes, it seems that snappy-side parsing is not correct yet
[08:56] <zyga> fgimenez: note that we haven't enabled bool-file (or any other non-migration skill) -- we are trying to do that since last week but we need to do it in the state engine desing and that's not trivial
[08:56] <zyga> fgimenez: so even if all my branches today would land, you would still not be able to use bool file in practice
[08:57] <fgimenez> zyga, ok np, i'll try to keep an eye on the development and update the tests accordingly, bool-file is the first skill type that is going to be available, right?
[08:57] <zyga> yes
[08:58] <fgimenez> zyga, ok thanks, could we write something about the migration-skill or is this going to go away shortly?
[08:59] <fgimenez> zyga, write some integration tests i mean :)
[09:01] <zyga> fgimenez: I think not shortly
[09:01] <zyga> fgimenez: but that's not exercising anything new (though the test will stay valid)
[09:02] <zyga> fgimenez: migration skill is not using the skills system yet
[09:02] <zyga> fgimenez: I think a lot will become clearer this week
[09:02] <zyga> fgimenez: then we can plan which tests to invest in
[09:04] <fgimenez> zyga, great thanks
[09:05] <clobrano> uhm, I just read this https://developer.ubuntu.com/en/snappy/guides/packages-names/, at which Phase are we now? Is it already possible to install more version of the same snap? Thanks
[09:48]  * zyga writes a small piglow demo
[10:25] <ysionneau> asac: Hi! I just managed to get snappy boot correctly in qemu (with cloud-init working and therefore the ubuntu/ubuntu login working)
[10:26] <ysionneau> I had indeed to merge a bit of kernel config + extract the initrd from the rpi2 snappy .img
[10:32] <ysionneau> I still need to figure out why I don't have any network interface (apart from lo) :o
[10:37] <zyga> ysionneau: out of curiosity, how do you run qemu?
[10:39] <ysionneau> ./arm-softmmu/qemu-system-arm -M raspi2 -smp 4 -kernel ~/dev/kernel-rpi2/linux/arch/arm/boot/zImage -sd ~/Downloads/ubuntu-15.04-snappy-armhf-raspi2.img -append "rw earlyprintk loglevel=8 console=ttyAMA0,115200 dwc_otg.lpm_enable=0 root=/dev/mmcblk0p2" -dtb ~/dev/kernel-rpi2/linux/arch/arm/boot/dts/bcm2709-rpi-2-b.dtb -usbdevice mouse -usbdevice keyboard -net nic,model=smc91c111 -net user -nographic -redir :8090::80 -redir :8022::22 -initrd ~/initr
[10:39] <ysionneau> something like that
[10:41] <ysionneau> maybe I should extract snappy dtb and use that instead of my own vanilla dtb
[10:41] <ysionneau> let's try that.
[10:46] <ysionneau> Warning: requested NIC (anonymous, model unspecified) was not created (not supported by this machine?)
[10:46] <ysionneau> hmmm I guess the raspi2 qemu port just does not support NIC
[10:46] <ysionneau> :/
[10:49] <ysionneau> what's weird is that even with a usb network device it does not work (-usbdevice net). The kernel detects the USB NIC, but no usb0 is created
[12:12] <asac> ysionneau: nice!
[12:12] <asac> ysionneau: is raspi2 in standard qemu?
[12:13] <asac> ysionneau: have you tried with our default kernel etc.?
[12:27] <ysionneau> 13:12 < asac> ysionneau: is raspi2 in standard qemu? < nop, I used this: https://github.com/0xabu/qemu
[12:27] <ysionneau> 13:13 < asac> ysionneau: have you tried with our default kernel etc.? < hmm no, lemme try
[12:28] <asac> ysionneau: right. so afaik the NIC is a USB nic on the raspi2
[12:28] <asac> :)
[12:29] <asac> so think you are on right track and just need to get the right kernel that supports the usb device you "plug in"
[12:38] <ogra_> thats quite fiddly with qemu (bot doable)
[12:38] <ogra_> *but
[12:40] <ysionneau> hmm interesting, at least with the snappy kernel, I get an eth0 iface
[12:40] <ysionneau> but I still get some errors and I don't have network
[12:40] <ogra_> it has the driver builtin iirc
[12:41] <ysionneau> http://paste.ubuntu.com/15073838/
[12:42] <ogra_> you probably need some tun/tap device setup the VM attaches to
[12:42] <ogra_> (i'm just widly guessing here though)
[12:43] <ysionneau> in theory, in -net user mode, I should not need that, but let's try in bridge mode
[12:46] <ysionneau> I often think of finding correct qemu args as black magic
[12:46] <ysionneau> like ffmpeg cmdline
[12:47] <ysionneau> when you find the correct line, you keep it preciously
[12:48] <ogra_> hah
[12:54] <asac> yeah i agree
[12:54] <asac> qemu arguments to do what you want and still work together is like ffmpeg :)
[12:55] <asac> but think you are close :_)
[13:10] <ysionneau> hmmm cannot get an ip address
[13:10] <ysionneau> I think the usb nic is buggy somehow
[13:11] <ysionneau> either in qemu or in the linux kernel I use
[13:11] <ysionneau> maybe I should rebase the qemu port onto qemu master
[13:22] <asac> ysionneau: did you try our kernel?
[13:31] <ysionneau> asac: yes, with your kernel it improves the situation a bit, I can get an eth0 iface
[13:31] <ysionneau> but it is not usable
[13:33] <Tomer> hi there, i'm trying to compile bluez5 for an RPi 2 running snappy core 15.04, but the generated snap package is for amd64, is it possible to compile for ARMv7?
[13:35] <ogra_> yes, if you do it on an armv7 system
[13:35] <ogra_> (i.e. on the rpi)
[13:36] <Tomer> how do I install tools like git on the snappy core (apt-get not available...)? I'm a total noob regarding snappy core
[13:37] <ysionneau> asac: hmmm you said I should not use arm64 version on 15.04 because it's not very well tested and not stable. What about having an arm64 kernel but using the arm32 15.04 system? Does this work?
[13:37] <ysionneau> an arm64 kernel should be able to run an arm32 user space
[13:37] <opny> ysionneau, asac I've spent a bit of time on snappy vs qemu too. On 15.04 eth0 never get an ip and cloud-init failed
[13:37] <ysionneau> I'm asking because we have a drone on Tegra X1 (arm64)
[13:37] <ogra_> well, in 16.04 there is the classic dimension, that gives you a full apt environment on demand for such stuff ... in 15.04 you can use a container (lxc or docker) or you can use a chroot
[13:37] <ysionneau> and it would be cool for me to be able to test 15.04 on Tegra X1 board
[13:38] <asac> ysionneau: interesting idea :)
[13:38] <asac> ricmm: what do you think? guess could work to use a arm64 kernel and make it work with our 15.04 image
[13:38] <asac> ?
[13:39] <ysionneau> arm64 kernel + your arm32 images
[13:39] <ysionneau> opny: which -M were you using? (which board were you emulating?)
[13:40] <opny> ysionneau, vexpress-a9
[13:40] <ogra_> asac, i think 15.04 is still a bit risky wrt arm64, i'D go straight to 16.04 for that
[13:41] <asac> nah
[13:41] <asac> ogra_: we are talkinga bout using 32-bit image
[13:41] <ricmm> you can try armhf userland sure
[13:41] <asac> with 64-bit kernel
[13:41] <ogra_> (and actually use arm64 for the rootfs too)
[13:41] <asac> no
[13:41] <asac> its not ready enough :)
[13:41] <ogra_> why not ?
[13:41] <asac> not ready enough
[13:41] <ogra_> nonsense :P
[13:41] <ogra_> i'm just running it here ... rock solid :)
[13:43] <ogra_> (and i compiled some quite heavy stuff on the weekend (webkit and qtwebkit) on it ... i have seen no issues)
[13:45] <opny> ysionneau, I was trying to emulate armhf/ armv7 https://github.com/muka/qemu-snappy-experiments/blob/master/run-snappy.sh
[13:46] <ysionneau> opny: have you tried with a usb NIC? maybe you will be luckier than me
[13:46] <ysionneau> ogra_: I'm a bit lost, you are saying 15.04 is risky for arm64 (kernel ? or user space?) and then afterward you say it's rock solid? Maybe I misunderstood something
[13:48] <ogra_> ysionneau, i'm not sure how ready 15.04 is ... we just added arm64 to 16.04 though, this is what i'm using here and it is rock solid
[13:48] <ysionneau> ah ok arm64 with 16.04 is rock solid, got it
[13:48] <ogra_> (15.04 will be droped when 16.04 goes stable so all dev focus is on 16.04 currently)
[13:48] <zyga> ogra_: hey
[13:48] <ysionneau> but, what about having the arm32 userland on 15.04 but with an arm64 kernel?
[13:48] <ysionneau> should be "ok", right?
[13:49] <ogra_> technically, yes
[13:49] <ogra_> practically i have no experience with that :)
[13:49] <ysionneau> only thing that bothers me with 16.04 is 1°) it's not released yet 2°) it's not much documented like 15.04
[13:49] <ogra_> yeah, and constantly moving
[13:50] <ysionneau> 15.04 dev/support will be dropped as soon as 16.04 is released?
[13:50] <ysionneau> meaning all the ubuntu website documentation will turn into 16.04 compatible tutorials?
[13:50] <ogra_> (its a bit of a pain to make snaps if your floor changes underneath you all the time ... but the worst changes should have landed by now)
[13:50] <ogra_> yeah
[13:51] <ysionneau> if the snappy release cycle is like normal ubuntu, 16.04 release is pretty soon :o
[13:51] <ysionneau> but I would have finished my evaluation long before the release anyway
[13:52] <ogra_> well, snappy is a rolling release, so they are not really synced up (156.04 will see fixes and changes after release for sure) ... but the stable channel will switch to it by 16.04 release or shortly after
[13:52] <ogra_> s/156.04/16.04/
[13:53] <ysionneau> hmmm doesn't rolling release mean there is "no" release?
[13:53] <ysionneau> like a 15.04 will become automatically a 16.04?
[13:54] <ogra_> it isnt that easy since the image design changed in an incompatible way
[13:54] <ogra_> so you have to re-flash for 16.04 ...
[13:54] <ysionneau> ok
[13:55] <ogra_> (there is no easy way to migrate to the new partitioning for example)
[14:01] <ysionneau> right got it
[14:11] <elopio> fgimenez: do you know why I can't ssh into an scalingstack ubuntu-server instance created from jenkins?
[14:31] <fgimenez> elopio, mm no idea, are you adding the user's keypair in the create command?
[14:32] <elopio> fgimenez: there is one keypair for RegionOne in the slaves. I'm passing it's name to the create command.
[14:32] <fgimenez> elopio, and then you try to ssh from a canonistack instance passing as -i the private key, right?
[14:36] <dpm> davidcalle, dholbach, popey mentions that on the getting started snappy page the rpi2 image link is out of date - could perhaps one you update it to the 16.04 image? Either popey or ogra should have the right link
[14:36] <ogra_> dpm, no
[14:37] <ogra_> dpm, 16.-04 isnt released, we only point to stable images
[14:37] <ogra_> (the links will be updated once we release 16.04 as stable)
[14:38] <elopio> fgimenez: where is the private key of the RegionOne keypair?
[14:39] <ogra_> we could perhaps link to dev images additionally, once we actually have the all-snaps one coming from the build system
[14:39] <ogra_> but thats still a bit away
[14:39] <fgimenez> elopio, i think it must be in the tarmac server, let me check
[14:39] <ogra_> (the only "proper" 16.04 image is atm the one that mvo builds by hand ... nothing we should promote yet)
[14:41] <fgimenez> elopio, yes, there it is, ~/credentials/scalingstack/ues-snappy-integration_RegionOne.key
[14:41] <elopio> fgimenez: yes, I tried with that one.
[14:41] <elopio> no luck.
[14:43] <fgimenez> elopio, no idea, the snappy instances used in the tests doesn't use this keypair, anyway you can always create a new one
[14:44] <elopio> fgimenez: should I create a new keypair as part of the deploy?
[14:47] <fgimenez> elopio, sure that way it won't need any secret management, if the deploy and the keypair have short live it's a good solution. if the deployed instances are expected to last longer maybe you could use an existing keypair
[15:17] <opny> Hi, in a snap (xenial) I've used printenv to have  a clue of avail vars but I'm a bit confused now ..  $SNAP is where the executable is. What is the difference of $SNAP_APP_DATA_PATH and $SNAP_USER_DATA ?
[15:18] <opny> http://paste.ubuntu.com/15075093/
[15:33] <ogra_> opny, there used to be a wikipage but i cant find it anymore
[15:33] <opny> ok thanks
[15:34] <ogra_> the USER stuff is all for actual executables a user can manually run though
[15:34] <ogra_> SNAP_APP_DATA_PATH is just the writable area of the snap ... used by services etc
[15:36] <opny> Do you think there is a sane way to have like a `ln -s` at build time paths that are hardcoded in the app runninig in a snap?
[15:38] <ogra_> i would do that from a startup wrapper
[15:42] <opny> ogra_, oh that's right.. I have a read call like /run/resolvconf/resolv.conf I cannot see a way to solve that..
[15:46] <opny> or read from  something like /proc/2368/net/ipv6_route (read)
[15:53] <ogra_> opny, yeah, i dubt confinement will allow you
[15:53] <ogra_> probably tyhicks or jdstrand have some hint if/how thats possible
[15:54] <opny> ogra_, I've noticed. Shouldn't the app see the fs as root (/) ?
[15:55] <ogra_> nope
[15:55] <ogra_> it sees its real path ... but cant access anything outside
[15:56] <olli_> hey
[15:56] <olli_> morning
[15:56] <opny> ouch, so bad...
[15:56] <opny> and let's add either a  "only a single skill is supported, 2 found"
[15:56] <opny> to the soup
[15:57]  * ogra_ isnt much familiar with skills yet ... i had just started to understand caps ... then they were replaced :)
[15:58] <opny> ogra_, well being aware that I am not alone is a good start :)
[16:00] <opny> ogra_, *IRC101* how do you do that chat reflection thingy?
[16:01] <ogra_> "chat reflection thingy"?
[16:01] <opny> * ogra_ isnt much familiar with skills yet ..
[16:01] <ogra_> /me isnt much familiar ....
[16:01]  * opny is learning IRC
[16:01] <ogra_> :)
[16:02] <opny> that's has been a productive day
[16:02] <opny> :)
[16:02] <zyga> opny: skills are not live yet
[16:02] <zyga> opny: except for migration-skill
[16:03] <opny> zyga, oh that's good
[16:06] <opny> zyga, thanks, do you know if they will be avail ? (I found them in snapcraft json/yaml schema)
[16:08] <ysionneau> when using arm64 kernel with rpi2 (arm32) image it boots but I get cloud-init issues (url_helper.py) when not using any initrd.
[16:09] <ysionneau> if I use the initrd from the rpi2 snappy img I get this : http://paste.ubuntu.com/15075934/
[16:09] <ysionneau> boot freezes at this point
[16:09] <ogra_> you *need* to use the initrd, else you wont get the proper mount farm ...
[16:10] <ysionneau> that's what I understood
[16:10] <ysionneau> ah, if I wait long enough I get some timeout and it told me it's a rootfs name issue ("could not find fe02 root partition")
[16:10] <ysionneau> I'll try other names
[16:11] <ogra_> Kernel command line: rw earlyprintk loglevel=8 console=ttyAMA0,115200 root=fe02
[16:11] <ogra_> this cant work at all
[16:11] <ogra_> u-boot has a huge scriptery that assembles an actual cmdline
[16:12] <ogra_> try mimicing one from a booted system instead
[16:12] <ogra_> (i.e. boot snappy once and copy the cmdline into your qemu call)
[16:12] <ogra_> since you are not using uboot
[16:13] <wigleworm> I used the java "hello-world" example in snapcraft and the resulting snap was 130MB - is that correct?
[16:13] <wigleworm> why so large
[16:13] <ogra_> because it includes hjava i'd guess :)
[16:13] <ogra_> *java
[16:14] <ysionneau> 17:12 < ogra_> try mimicing one from a booted system instead  < ok :)
[16:14] <wigleworm> any clue where to look for a method to pair that down?
[16:15] <ogra_> i dont think there is one ... apart from making java itself smaller or some such
[16:15] <ogra_> if you want your snap to run java bits the jvm needs to be shipped along
[16:15] <wigleworm> also, from the example I could not see where the script was pulling JAVA from - anyone know?
[16:16] <wigleworm> ogra - thank you
[16:16] <ogra_> that would be a quaesion for the snapcraft guys ... but sergiuens isnt arund and i dont know if kyrofa is familiar with the java bits
[16:17] <ogra_> you should be able to dig though the snapcraft plugin code though ...
[16:19] <wigleworm> is there another channel for snapcraft or is this it?
[16:19] <wigleworm> irc channel that is
[16:19] <ogra_> this is it ...
[16:20] <ogra_> there is a sprint at the US westcoast that many are attending, so catching people from the team might be hard this week
[16:20] <wigleworm> -orga_- thank you, I will dig into the snapcraft docs
[16:21] <fgimenez> elopio, i'm getting lots of errors like this http://paste.ubuntu.com/15076159/, can you please try to reproduce when you have time?
[16:22] <elopio> fgimenez: sure.
[16:24] <fgimenez> elopio, the image used by jenkins was built a few weeks ago and we still don't have the automation in place with the new sources, maybe something has changed somewhere that make the new one fail, if you confirm the error i can manually trigger the build to make it visible in the PRs
[16:26] <fgimenez> elopio, we can also put the build job in cron mode and create a new image every day, the cleanup jobs are working now
[16:31] <elopio> fgimenez: I updated my snappy image and I can install hello world.
[16:31] <elopio> it's using ubuntu-core 2016-02-12.
[16:31] <ogra_> crazy stuff !
[16:33] <elopio> fgimenez: ah, the error is running it.
[16:33] <elopio> fgimenez: yes, confirmed. Pleaes report the bug.
[16:34] <ogra_> elopio, did you guys already start testing with all-snap images ?
[16:34] <fgimenez> elopio, sure, i'll fire up also a new image build
[16:34] <ogra_> or are you wating til they come from the official build system
[16:34] <elopio> ogra_: jenkins is testing the pull requests with all-snaps.
[16:35] <ogra_> cool !
[16:35] <elopio> fgimenez: also confirmed that it doesn't happen with ubuntu-core from 2016-02-03
[16:36] <ysionneau> with root=/dev/vda2 now it boots, and cloud-init works (I also added a few parameters from a /proc/cmdline of a live snappy system=
[16:36] <ysionneau> and I also have a network iface ... "sit0" but it only gets ipv6 address upon dhcp :o
[16:36] <ogra_> ysionneau, still wrong
[16:37] <ogra_> ysionneau, root=/dev/disk/by-label/writable net.ifnames=0 init=/lib/systemd/systemd ro panic=-1 fixrtc
[16:37] <ogra_> thats the least you want in the kernel cmdline ...
[16:37] <elopio> wigleworm: it is installing the default-jdk package from the archive.
[16:37] <ysionneau> yes I've put the panic=-1 and init stuff
[16:38] <ysionneau> I'll try with the remaining parts
[16:40] <ysionneau> are you sure I'm supposed to boot on the writable rootfs ? :o seems weird
[16:40] <ysionneau> others seem to boot from the system-a or system-b fs
[16:41] <ogra_> ysionneau, you want the init= and the root=
[16:42] <ogra_> panic and fixrtc arent that important
[16:46] <ysionneau> if I do root=/dev/disk/by-label/system-a it works way better than writable
[16:46] <ogra_> lol
[16:47] <ogra_> yeah, sorry
[16:47] <ogra_> i'm running the all-snaps image ... you indeed want system-a on older images
[16:47] <ogra_> sorry
[16:47] <ogra_> (in all-snaps system-a is actually a loop device living in /writable which is why thats the rootfs device)
[17:02] <fgimenez> elopio, the new image is uploaded and it's already showing the error http://<IP_ADDRESS>:8080/job/snappy-daily-rolling-openstack/103/console
[17:03] <elopio> fgimenez: great. I set the bug priority as critical.
[17:05] <wigleworm> elopio: :) I wish I knew - do you know how I find out?
[17:06] <elopio> wigleworm: https://github.com/ubuntu-core/snapcraft/blob/master/snapcraft/plugins/jdk.py#L24
[17:07] <fgimenez> elopio, thx, i'll prepare the changes for reacting to modifications in the snaps from the store and build the images accordingly, hopefully it won't take too long
[17:07] <elopio> fgimenez: have you decided on a name for the images?
[17:08]  * ogra_ votes for "fred"
[17:08] <ogra_> (unless they are female indeed)
[17:08] <fgimenez> elopio, i think that your idea of the timestamps is great, we can sort and select them without modifying the existing tools, -tests-job and -cloud-image
[17:09] <elopio> elsa for female.
[17:09] <ogra_> +1
[17:10] <elopio> fgimenez: but then the -1 trick wouldn't work. Because it won't necessarily be ubuntu-core -1. It could be kernel -1.
[17:10] <wigleworm> elopio: from the file that you linked me to, I am guessing it is installing whatevere I have installed - is that correct
[17:10] <elopio> I think we need to modify the tools.
[17:11] <ogra_> wigleworm, it is running "apt-get install default-jdk"
[17:11] <ogra_> inmside the snapcraft dir
[17:11] <elopio> wigleworm: https://github.com/ubuntu-core/snapcraft/blob/master/docs/snapcraft-parts.md
[17:12] <ogra_> ogra@styx:~$ apt-cache show default-jdk|grep Depends
[17:12] <ogra_> Depends: default-jre (= 2:1.7-52), openjdk-7-jdk (>= 7~u3-2.1.1)
[17:12] <ogra_> (thats what i get on 15.10)
[17:12] <elopio> take a look at stage-packages in that link.
[17:14] <wigleworm> ok, I see default-jdk :) - understand that
[17:14] <wigleworm> where does default-jdk get defined - i.e. is it set to 1.7.x. or 1.8.x?
[17:14] <fgimenez> elopio, ok, i'll submit a PR and we can discuss there, the alternative could be 3 separate padded version numbers of our own, so that we can sort and compare
[17:15] <ogra_> wigleworm, in the ubuntu archive
[17:15] <elopio> fgimenez: maybe we extend snappy-cloud-client to receive optional versions for the three snaps. If there's no image, it will create one and upload it to glance.
[17:15] <elopio> fgimenez: then we don't care about the name, we'll just use whatever ip it returns.
[17:16] <wigleworm> ogra_ - thanks, can you point me in the direction of the ubuntu archive or tell what I am searching for exaclty?
[17:16] <ogra_> wigleworm, like the gcc package depends on a specific gcc-$version package ... it is selected during a release
[17:19] <fgimenez> elopio, but how do we know if we have available an image for the requested versions, if the versions are not stored in the name? and it can be ugly, only ubuntu-core's version looks like 2016-02-12 16.04.0-14... well, we can discuss in the PR
[17:19] <ogra_> wigleworm, just run "apt-cache show default-jdk|grep Depends" on your machine and it will tell you which open jdk version it would install
[17:19] <wigleworm> so is it looking at the dev system and saying "which version is the default java?" and then down loading that version?
[17:20] <wigleworm> ok, so basically the default jdk for the development system that was used to create the snap
[17:20] <ogra_> yeah
[17:21] <elopio> fgimenez: yes, I mean that the name will only be important for the tool that returns the ip, not for the jobs. But of course we need a way to identify the versions in the image. It's late for you, let's talk later.
[17:21] <wigleworm> ok, thank you
[17:23] <fgimenez> elopio, ok nice evening everyone o/
[17:23] <longsleep> hey folks it has been a while since i had time to work with snappy, to get up to speed is there a vagrant box to get a 16.04 snappy running quickly?
[17:24] <elopio> longsleep: we are finishing the details of the new all-snaps images for 16.04. In the meantime you can get images from https://people.canonical.com/~mvo/all-snaps/
[17:24] <longsleep> elopio: great thanks
[17:25] <ogra_> elopio, not sure thats suitable for vagrant without converting it though
[17:25] <ogra_> there are currenly no all-snap cloud images afaik
[17:26] <longsleep> well i can upgrade my odroidc stuff but i guess i have to learn some new stuff first then
[17:26] <longsleep> so i would need something which runs in kvm or virtualbox
[17:30] <ogra_> the amd64 one runs fine in kvm
[17:31] <longsleep> ogra_: ah ok great - i will use that one for now then - thanks!
[17:31] <ogra_> but iirc vagrant needs a special image format you need to convert to
[17:31] <longsleep> no problem - i can boot a plain disk image
[17:31] <ogra_> longsleep, good to have you back btw :)
[17:32] <longsleep> ogra_: yeah - i am still very busy and not much snappy time unfortunately :/
[17:32] <ogra_> sad ... but busy means you guys are getting forward, thats good :)
[17:36] <wigleworm> ok, new issue with java-hello-world. I installed the snap and ran it - error - no java found. Then I did some searchs on the system and I found that java is on the system, under the snap I just install but it seems like my program (snap) does not know where to look. Should I be setting a "path" somewhere in the hello sample or somewhere else?
[17:37] <ogra_> dont you need JAVA_HOME in java ?
[17:37] <ogra_> or some such
[17:37] <ogra_> the wrapper script that runs the app should set this to your snap dir
[17:38] <ogra_> (or respectively to the path underneath the snap dir actually)
[17:52] <longsleep> ogra_: amd64-all-snap.img.xz booted just fine thanks!
[17:52] <ogra_> awesome
[17:52] <longsleep> some grub migration service failed, thats normal?
[17:52] <ogra_> longsleep, sudo snappy enable-classic; snappy shell classic
[17:53] <ogra_> thats one of the new awesome things ;)
[17:53] <ogra_> longsleep, yeah, we need to look into that
[17:53] <ogra_> should be harmless though
[17:53] <longsleep> yeah i follow the maillinglist - will try that for sure
[17:56] <longsleep> ogra_: no more snappy search?
[17:56] <ogra_> snap find
[17:56] <longsleep> cool thanks
[17:56] <ogra_> (but snapy install ..., yay consistency)
[17:57] <longsleep> well - once you know it :)
[18:01] <longsleep> ogra_: ok, maybe last question for today - how do i sideload a snap quickly now?
[18:01] <ogra_> same as before
[18:01] <longsleep> mhm getting some wild error
[18:01] <longsleep> /tmp/spreed-webrtc_0.24.10-1_amd64.snap failed to install: can not open /tmp/spreed-webrtc_0.24.10-1_amd64.snap: cannot open snap: unknown header: "!<arch>\ndebian-binar"
[18:01] <ogra_> suo snappy install --allow-unauthenticated /peth/to/snap
[18:01] <ogra_> yeah ... it should rather say "unsupported snap version"
[18:01] <longsleep> ah
[18:02] <ogra_> 16.04 requires squashfs snaps without the click package legacy (which is dpkg based)
[18:02] <longsleep> good, i guess then i have something to work on for tomorrow
[18:02] <longsleep> i assume snapcraft has the gear to build those snaps?
[18:03]  * ogra_ looks forward to 16.04 release ... all that "floor moves underneath you all the time" is really painful
[18:03] <ogra_> yeah
[18:03] <ogra_> you need xenial though
[18:03] <ogra_> (a chroot or what not)
[18:03] <longsleep> ok, xenial vagrant already somewhere?
[18:04] <ogra_> dunno ... you mean normal server ?
[18:04] <longsleep> yes to run snapcraft
[18:04] <ogra_> there surely is ... but dont ask me where :)
[18:04] <longsleep> guess i can use those https://cloud-images.ubuntu.com/xenial/
[18:04] <ogra_> yeah
[18:10]  * zyga hacks on i2c skills
[19:13] <elopio> kyrofa: are you here today?
[20:50] <zyga> ogra_: hey, still around? would you mind telling me where the gadget snaps live (sources?)
[21:32] <wigleworm> back again looking for java and snapcraft help
[21:32] <wigleworm> I have now twice used the example code
[21:33] <wigleworm> and both times snapcraft completes and creates a snap (java-hello-word exaple)
[21:34] <wigleworm> install the snap and run the wrapper <-- I think thats what I am suposed to do
[21:34] <wigleworm> I get "./wrapper: 2: ./wrapper: java: not found
[21:35] <wigleworm> Comments on what I should do to debug this would be welcome
[21:47] <barty> hi! just a fast question. I've discovered today snappy and installed it in a RPI2. I'm from Spain and I'm unable to change the default keyboard layout to spanish. I've search a lot over the web and found nothing. Anyone there know how to do it?
[21:53] <wigleworm> barty: are you familiar with desktop ubuntu "dpkg" program?
[21:55] <wigleworm> more than likely you can use that and install the "consol-common" deb pkg on the system - you will need to make sure that you get the dependencies that are needed though
[21:56] <barty> ok :)
[21:56] <barty> I thought there will be a command already installed like locale-get or something
[21:56] <barty> thank you very much!!!!
[21:58] <wigleworm> @bar(input):button2
[21:58] <nothal> wigleworm: No such command!
[21:58] <wigleworm> huh?
[22:01] <wigleworm> nothal: are you saying dpkg wont work?
[22:01] <wigleworm> I just used it the other day
[22:01] <barty> I'm using dpkg right now. I think nothal says no such command like locale-gen
[22:01] <longsleep> bug #1458866