[04:38] <freakyy> hi all. is there any way i can set the automatic screenshot usin print, to only record 1 screen and not two of my screens?
[05:21] <lotuspsychje> charmer: can you define whats happening exactly?
[05:21] <charmer> yes, but it varies depending on whether its Ubuntu or Kubuntu.  Kubuntu gets farther.
[05:21] <lotuspsychje> charmer: got nvidia card?
[05:22] <charmer> yes, unfortunately.  Nvidia Optimus ... i think Quadra M2200 but that could be wrong.  Also Xeon
[05:23] <lotuspsychje> charmer: i think wayland might be blocking nvidia
[05:23] <lotuspsychje> charmer: but describe whats happening exactly?
[05:23] <charmer> what is wayland?
[05:24] <charmer> with Ubuntu install, the boot process fails.  i have a screenshot of messages on my cell phone, but it appears that it is unable to find the USB thumbdrive after the initial kernel loads.  it drops into busybox.
[05:24] <lotuspsychje> charmer: how did you create your stick?
[05:24] <lotuspsychje> !wayland
[05:24] <charmer> with Kubuntu install, it gets farther (how peculiar!).
[05:25] <charmer> in both cases usb-creator running on Kubuntu 14.04.03.
[05:26] <lotuspsychje> kk
[05:26] <lotuspsychje> sounds good
[05:26] <lotuspsychje> charmer: so at wich point does kubuntu get?
[05:26] <charmer> Note that i've installed Kubuntu 17.04 and Kubuntu 16.04.02 and 16.04.03 on the laptop successfully, though i've had video driver problems with all 3.
[05:27] <lotuspsychje> charmer: did you clean install or upgrade?
[05:28] <charmer> with Kubuntu 17.10 beta 2, if i select "install Kubuntu" from the graphics, i get all the way to manual partitioning of the disk before it fails in a manner similar to Ubuntu 17.10 beta 2.
[05:28] <charmer> this is clean install.  i lack faith in upgrades.
[05:29] <lotuspsychje> ok good
[05:29] <lotuspsychje> charmer: so what happens after disk partitioning?
[05:30] <charmer> note: the laptop has an NVME disk but the "default" Kubuntu install tries to install to /dev/sda, which is really just an archive.  Hence, manual partitioning.
[05:31] <lotuspsychje> kk
[05:32] <lotuspsychje> uefi settings set correctly to install ubuntu?
[05:33] <charmer> i just repeated the attempt ... after choosing /dev/nvme0n0p3 as "/" file system, and p1 for EFI and p2 for /boot, the installer has a stack traceback and then the screen goes black.
[05:33] <charmer> i think its /dev/nvme0n0p3 ... i could be a couple of characters off.
[05:34] <charmer> i think the UEFI settings are correct ... i got Kubuntu 16.40.02/03 and 17.04 to install, but of course i could be wrong.
[05:34] <lotuspsychje> for ubuntu singleboot= fastboot =off and secureboot=off
[05:37] <lotuspsychje> !bug | charmer 
[05:40] <charmer> i'm sorry, can you be more specific?  are you suggesting that i add "singleboot= fastboot=off secureboot=off" to the grub boot line for the kernel?
[05:40] <lotuspsychje> charmer: no, sorry in your bios/uefi settings before boot disable both
[05:41] <lotuspsychje> in case your not dualboot with windows?
[05:42] <charmer> and does "!bug | charmer" mean this is pilot error?
[05:42] <charmer> i wiped the Windows partitions (after backing them up to a thumb drive). i don't do Windows.
[05:43] <lotuspsychje> kk
[05:43] <lotuspsychje> charmer: you can start a bug with ubuntu-bug affected-package
[05:43] <charmer> ubottu: not really possible when there's an install error.  the "ubuntu-bug" command is not available.
[05:46] <charmer> unless you want me to run "ubuntu-bug" from a different release installed on the same laptop ;) i think that might just confuse things.  and i'd guess the affected package is "install"?
[05:46] <charmer> lotuspsychje: i'm going into bios setup to look around ...
[05:48] <lotuspsychje> ok
[05:58] <charmer> lotuspsychje: in the summary there is "UEFI Secure Boot" setting that shows "On" (can't change  it there).  in the "Security" -> "Secure Boot" sub-menu, i changed "Secure Boot" "Enabled" -> "Disabled" (yes, it shows on/off in the summary screen and Enabled/Disabled in the sub-menu).  in the "Startup" sub-menu there is a "Boot Mode" setting with "Quick" and "Diagnostics" as the choices.  I'm changing Quick --> Diagnostics.  in the "Startup" sub-menu, t
[05:58] <charmer> here is a "UEFI/Legacy Boot" setting which is currently "UEFI Only".  it could be "Legacy Only" or "Both".  there's a sub-heading about "CSM Support" which is curently set to "No".  i do not see a "fastboot" option, but i have not worked through all of the sub-menus.
[06:04] <lotuspsychje> fastboot and secureboot should be both off
[06:04] <charmer> lotuspsychje still there?  changing the BIOS options does not seem to affected booting from the Ubuntu thumbdrive.  it still fails at BusyBox.
[06:04] <charmer> lotuspsychje: secure boot is disabled. i do not see a "fastboot" option.
[06:05] <charmer> lotuspsychje: ... fastboot option in the bios settings
[06:05] <lotuspsychje> should be there
[06:06] <charmer> lotuspsychje OK.  i'm looking.  could it be the the "Startup" -> "Boot Mode" option with choices of "Quick" and "Diagnostics"?  i changed it to "Diagnostics".
[06:06] <lotuspsychje> try legacy only
[06:07] <charmer> kk
[06:09] <charmer> lotuspsychje: it may be useful to know that after a failed boot attempt with Ubuntu (but not Kubuntu) the USB thumbdrive is not visible at the BIOS boot devices settings unless i remove it and put it back.
[06:09] <charmer> with Kubuntu that doesn't seem to be the case (but if its important i should verify to be sure)
[06:09] <lotuspsychje> charmer: F12 should be able to load your usb stick
[06:09] <lotuspsychje> if uefi settings correctly also
[06:11] <charmer> lotuspsychje: yes ... <Enter> then <F12> gives me a choice of boot devices.  but "USB HDD: SanDisk Ultra" does not appear *after* I use it to try and boot Ubuntu 17.10 beta2 *unless* i remove the thumb drive and reinstall it before I attempt the second boot.
[06:12] <lotuspsychje> hmm
[06:12] <charmer> lotuspsychje: after setting to "Legacy Only" i get a different pattern.  after selecting the UBS drive at the BIOS boot menu, i see "Missing paramter in configuraiton file. Keyword: path" and then repeating lines of "gfxboot.c32: not a COM32R image" followed by "boot:"
[06:13] <lotuspsychje> try TAB key to bypass that?
[06:13] <charmer> previously it was more informative ... i could send a screenshot?
[06:13] <charmer> with <TAB> i get several options.  i'll try "live" ...
[06:14] <lotuspsychje> what else you get
[06:14] <lotuspsychje> install?
[06:14] <charmer> yes, "live-install", "memory"? and others
[06:14] <lotuspsychje> yeah live-install, as you wanna install right
[06:15] <charmer> after typing "live" it actually booted to something that looks like a working live environment!
[06:16] <lotuspsychje> :p
[06:17] <charmer> lotuspsychje: well, what i want is Kubuntu with a video driver that supports external monitors.  that works on Kubuntu 17.04 but its butt ugly ... i've been resigning myself to living with "butt ugly".
[06:18] <charmer> lotuspsychje: i'm doing the Ubuntu/Kubuntu 17.10 stuff to help Ubuntu have a better relase (and maybe get better Kubuntu video support).
[06:19] <charmer> lotuspsychje: so i'm happy to try a Ubuntu 17.10 beta 2 install if that will help the release effort.
[06:19] <lotuspsychje> great for the community tnx
[06:19] <charmer> lotuspsychje: i can wipe this laptop multiple times -- not a problem
[06:21] <charmer> ... in addition to ordering the laptop with the Nvidia graphics (mistake) it also has a 4K screen (3840 x 2160).  i think that was an even bigger mistake.
[06:22] <lotuspsychje> charmer: we have to see at final whats gonna happen
[06:23] <charmer> lotuspsychje: so there's no point in testing on beta2? providing feedback is not useful? i'm sorry ... i thought filing a bug would be helpful ...
[06:23] <ducasse> charmer: just so you know, the rc is supposed to be out later today
[06:24] <ducasse> or was it tomorrow?
[06:24] <charmer> ha ha! should i try with that or is feedback on that also not helpful?
[06:25] <ducasse> it's tomorrow. there are so many changes to artful that trying the latest daily or waiting for the rc tomorrow might help. either way, report your findings on the qa tracker :)
[06:26] <ducasse> http://iso.qa.ubuntu.com/
[06:27] <charmer> and where is the qa tracker? i should probably mention that over the years Lenovo has been one of the better (best?) supported laptops for Ubuntu.  having the install completely fail on their newest high-end model is not pretty, particularly when 16.04.02/03 and 17.04 work ...
[06:27] <charmer> ahhh, thanks.
[06:28] <ducasse> your problem might be just that - 'newest model' is often not the best to buy when you need linux support...
[06:29] <ducasse> but i'm sure the devs would be glad to know if you file a report
[06:29] <charmer> yes ... i know.  its been out for a year now, i think (and still the newest model), but the Nvidia support in particular has always been patchy.
[06:30] <charmer> its particularly frustrating that support seems to be regressing! 16.04.02 works fine, 16.04.03 somewhat less well, 17.04 works as well as 16.40.03, and 17.10 can't install ...
[06:31] <ducasse> can you briefly sum up where it fails for me?
[06:32] <charmer> Ubuntu 17.10 beta2 install fails to boot.  it looks like the kernel loads but loading initrd fails (just my guess).  after complaining that the USB device is unreachable it drops me into BusyBox.
[06:33] <charmer> Kubuntu 17.10 beta2 actuall gets farther!  i get the graphical screen with a choice of "Try Kubuntu" and "Install Kubuntu".  but either choice eventually winds up at a similar place.
[06:33] <charmer> if you want, i can repeat and give you exact error messages or a screen shot (from my cell phone).
[06:34] <ducasse> can you  download and try the latest daily (link in the topic)?
[06:34] <charmer> errata: when i said "16.04.02 works fine" i should have said "kind've works".  
[06:34] <ducasse> :)
[06:36] <charmer> with all releases the Noveau video driver and Nvidia video drivers have had bugs that make them pretty much unusable with external monitors.  but that's a separate issue ...
[06:36] <ducasse> are those monitors also hidpi?
[06:37] <charmer> i can pull the latest daily and try it.  that will take awhile, though.
[06:38] <ducasse> we can look at what you have while it downloads and writes if you can post screenshots somewhere?
[06:38] <charmer> somewhat less so -- 2560 x ???.  but Noveau can't handle them at all (not recognized) and Nvidia is not much better.
[06:39] <charmer> ducasse: probably google drive since its on my cell phone.  hold on for a few minutes ...
[06:39] <ducasse> ok
[06:40] <ducasse> have you tried other nvidia versions from the graphics-driver ppa?
[06:42] <charmer> is there a torrent download for the daily?  i have a fast connection, but the download is showing 6 hours (~50 Kbyte/sec).  i don't know what zsync is and i'm not sure i want to learn right now.
[06:44] <ducasse> not afaik, people mostly use zsync since it's able to only download changes from your last image
[06:44] <charmer> ducasse: i've tried a variety of ppa for Kubuntu 16.04.03, but none work well .. i have not gone that route with 17.04 and have not tried 16.10 at all.
[06:45] <charmer> but my memory is poor so i'd rather retry those from scratch to report errors as they happen if it would actually be useful.
[06:45] <charmer> OK, i guess i'll figure out what zsync is.
[06:46] <ducasse> i expect you can just rename the beta2 and zsync will treat it like some daily. that's a guess, though.
[06:47] <ducasse> not a zsync users myself, it's so rare i download a daily that i tend to just grab the whole thing :)
[06:47] <flocculant> charmer: zsync is easy - all it does is grabs the difference between latest and whatever you have
[06:49] <flocculant> ducasse: yup - make sure name of b2 to daily name and that's what it will do
[06:51] <charmer> it appears that zsync is another name for rsync?  i'm not sure why a name change was required ....
[06:51] <charmer> ahhh, i see.  it runs over http instead of ssh.
[06:54] <charmer> i tried 'cp ubuntu-17.10-beta2-desktop-amd64.iso artful-desktop-amd64.iso' and then 'zsync artful-desktop-amd64.iso.zsync' and it seems to be working ....
[06:54] <charmer> after downloading  artful-desktop-amd64.iso.zsync, of course 
[06:56] <charmer> whoops!  that failed after awhile.  let me try again ...
[07:03] <charmer> after downloading the .zsync file, and then copying my existing file to the new name (see above) the invocation 'zsync -u http://cdimage.ubuntu.com/daily-live/current/ artful-desktop-amd64.iso.zsync' seems to be working, though the download rate is still 10% of my download bandwidth.
[07:03] <charmer> but there's less to download
[07:04] <flocculant> charmer: not sure what's up there, but I zsync http://cdimage.ubuntu.com/xubuntu/daily-live/current/artful-desktop-amd64.iso.zsync in the same folder as the destination file and it runs at normal speed, usually takes me less than a minute
[07:05] <flocculant> I've never downloaded the zsync file :)
[07:05] <flocculant> anyway - if you get it in the end, it's enough
[07:09] <charmer> flocculant: then your connection is faster then mine!  i get 1 - 2 Mbyte/sec download, but this was running at ~200 Kbyte/sec.  but its done now!
[07:09] <flocculant> charmer: was more commenting on it no being 10% :)
[07:17] <charmer> separate question: it looks like Kubuntu has some kind of paid support available.  i'd be willing to pay 1 K$ or more to get Kubuntu working well on my new laptop (my intended primary development environment after i retire this Kubuntu 14.04 laptop).  do you know if paid Kubuntu support is worthwhile for problems like this?
[07:18] <ducasse> no idea, maybe #kubuntu can tell you something about that?
[07:18] <charmer> ducasse: thanks for the suggestion!
[07:19] <ducasse> if you'd rather want to get 16.04 running, we can help you with that in #ubuntu instead of spending time on this - it's really up to you which release you want to run
[07:24] <charmer> OK ... i downloaded today's Ubuntu 17.10 and "burned" it to a usb-drive.  after booting it with the revised BIOS settings (above), the behavior was the same (repeating  "Missing paramter in configuraiton file. Keyword: path" and then repeating lines of "gfxboot.c32: not a COM32R image" followed by "boot:".  pressing <TAB> and then typing "live-install" brings up a full graphical interface install probmpt.
[07:24] <flocculant> oh that's an old bug
[07:24] <flocculant> try using something else to create the usb 
[07:26] <flocculant> currently I use gnome-disks and the restore disk image option 
[07:31] <charmer> ducasse: unfortunately, i gave up on Ubuntu (in favor of Kubuntu) in the 14.04 time frame.  the Ubuntu cell-phone/user-friendly focussed direction become too frustrating for me to use (i'm old-school).  i want to use an LTS release for my development environment because i don't enjoy installing a new OS every 6 months.  but i understand that supporting the latest hardware is easiest on the newest release (backports not required) so i'm willing to go t
[07:31] <charmer> hrough the pain for the latest release in the hopes that my hardware support gets rolled forward to the next LTS release, or perhaps even the last LTS release)! 
[07:33] <ducasse> !hwe
[07:33] <ducasse> ^^ this what you want?
[07:36] <charmer> flocculant: i'm using usb-creator on a Kubuntu 14.04 to create my bootable USB-drive.  i could use Kubuntu 17.04 on the new laptop to do it (but not tonight).  if you think the results would be different, i could do that.
[07:37] <ducasse> can you just use 'dd' to write the usb stick again?
[07:40] <charmer> ducasse: if that also applies to Kubuntu LTS, then "yes", that's what i want.  my thought was that it was easier to get this to work on the "latest" release and then ask that it be back-ported (or attempt to do that myself).  do you think i'm better off asking for support on Kubuntu 16.04 even though it doesn't seem to work on Ubuntu/Kubuntu 17.10 beta 2?
[07:43] <ducasse> well, on 16.04 your major issue was graphics problems, right? since kernels and drivers are made available for lts releases i think you should stick to that if an lts release is what you really want in the first place.
[07:44] <ducasse> and #ubuntu supports kubuntu as well, so you can get help from a lot of people there - at no charge, it's what we're there for :)
[07:45] <charmer> ducasse: creating a bootable USB drive is a multi-step process, which starts with partitioning, running grub, copying various files to various partions, running grub (or syslinux), etc. its certainly possible for someone to create a boot image that i could just slap down on (real) sector 0 of a USB-drive, but i haven't see images like that for download (the image would need to include boot sector, partition table, etc.).  
[07:48] <ducasse> the ubuntu images contain everything you need - they're hybrid images
[07:49] <ducasse> just dd them to a usb stick and boot
[07:53] <charmer> ducasse: somewhat ironically, 16.04 worked better then anything more recent ... up until i tried to connect an external monitor, which was completely unrecoginized.  google searches found one web post that suggested moving from the open-source Noveau driver to the _very latest_ proprietary Nvidia driver would solve them problem, but that did not work for me.  so i started trying the latest releases in the hope that 1) the latest release would work or 
[07:53] <charmer> 2) there would be more support available for the latest release.
[07:54] <charmer> ducasse: you're correct.  the downloaded install images do seem to include a boot sector and partition table, so i should be able to just slap them down on a USB-drive.
[07:56] <charmer> woot!  'sudo dd if=artful-desktop-amd64.iso of=/dev/sdb bs=1M oflag=dsync'  i'll see if that boots!
[07:56] <ducasse> in general, a release that is actually released has better support than a development release, with an lts release probably the best supported. where did you get the latest nvidia driver from - ppa or directly from nvidia?
[07:58] <charmer> i believe there were ~3 Nvidia drivers from a PPA release that i tried.  all failed to work well enough to be usable.  but i should repeat this experiment before i give you a definitive answer about which failed and why.
[08:00] <DiveSurfer> hi guys, i have some trouble with my gdm on a ubunut 17.10
[08:01] <DiveSurfer> i swichts from lightDM to gdm3, now when i press "SUPER +L" the screen is locked, when i login the lockscreen my session is generated new
[08:02] <charmer> ducasse: anyway, is that really true?  will Ubuntu actually want to GA a release that doesn't install at all on Lenovo's flagship laptop (which has been out for ~1 year)?
[08:06] <ducasse> i don't know if this problem has been reported or not, but it's impossible to test on every single model out there
[08:06] <ducasse> didn't the newly written image work either?
[08:13] <charmer> ducasse: the newly written image (dd of today's 'artful-desktop-amd64.iso') worked slightly better.  the boot proceeded to a graphical screen that let me choose "Try Ubuntu" or "Install Ubuntu".  but clicking "Try Ubunutu" leads to a wedged laptop with a black screen (<ESC> or <Ctrl>-<Alt>-<F1> do not produce any output).  Choosing "Install Ubuntu" gets me a longer series of choices ...
[08:14] <ducasse> !nomodeset | charmer can you try this?
[08:17] <charmer> ducasse: i'm investigating the "Install Ubuntu" choices.  it appears that going through manual disk setup works at least well enough to let it start copying packages to the root disk.
[08:18] <ducasse> progress, i guess :)
[08:19] <charmer> ducasse: the black screen is not (i think) a kernel boot paramater problem.  note that the boot gets to the point of giving me a choice of "Try Ubuntu" and "Install Ubuntu".  its only when i click "Try Ubuntu" that i get the black screen and wedged computer.
[08:21] <ducasse> if x started up properly, then it's probably not your problem, no
[08:22] <charmer> ducasse: after the "install" of Ubuntu, my laptop will no longer boot past the BIOS boot device selection.  i think that's a new and different problem, which i may try to chase down ... 
[08:24] <charmer> it appears that the boot disk (NVMe0) was not initialized correctly.  Ubuntu/Kubuntu seems to want to setup /dev/sda as the boot device instead of the /dev/nvme0n1* unless i explicitly tell it otherwise, so that may be the problem.
[08:26] <charmer> i need to go to bed soon.  do you know if there is any laptop known to run Kubuntu well with external high resolution external monitors? i'm willing to put in some time helping the community but i want to be aligned with the direction of current development.
[08:27] <charmer> ... and i want something i can use to get my day job done ...
[08:32] <ducasse> type of monitor shouldn't really matter in my experience, but different resolutions on them can give you scaling issues
[08:43] <charmer> ducasse: with Kubuntu 17.10 i got to the point where i was dealing with scaling issues (it looks awful but i think i can get xterm/Konsole to work well enough to be usable). 16.04 and 17.10 don't even get that far.  16.04 -- external monitors don't work; 17.10 -- won't install.
[08:43] <charmer> whoops!  i meant:
[08:44] <charmer> i meant: with Kubuntu 17.04 and the Nvidia driver i got to the point where i was dealing with scaling issues (it looks awful but i think i can get xterm/Konsole to work well enough to be usable). 16.04 and 17.10 don't even get that far.  16.04 -- external monitors don't work; 17.10 -- won't install.
[08:45] <charmer> thanks!  but i'm going to bed now ....
[13:29] <DiveSurfer>  hi, ich habe ein problem beim starten von ubunut 
[13:29] <DiveSurfer>  [  167.030879] Could not find key with description: [02d6d39d1ddaf903]
[13:29] <DiveSurfer>  [  167.030914] process_request_key_err: No key
[13:29] <DiveSurfer>  [  167.030915] Could not find valid key in user session keyring for sig specified in mount option: [02d6d39d1ddaf903]
[13:29] <DiveSurfer>  wenn ich ein keyctl show mach, wird mir aber der schlüssel angezeit
[13:29] <DiveSurfer>   953781914 --alswrv      0     0       \_ user: 02d6d39d1ddaf903
[13:31] <DiveSurfer> im einsatz ist ubunut 17.10
[13:35] <SwedeMike> DiveSurfer: we speak english in here.
[13:36] <DiveSurfer> ok, sry
[13:38] <DiveSurfer> i have a problem with the ubuntu keyring the key is not found
[13:38] <tomreyn> it is also preferred not to cross post
[13:39] <DiveSurfer> tomreyn, soryy
[16:40] <netsrot> Hi, I'm using artful and it's killing processes when I switch between desktops in xorg/openbox. Has only happened to processes using gpu acceleration on radeon driver.
[17:06] <ignacio> HI everyone!
[17:06] <ignacio> I ran sudo do-release-upgrade -d, and it's upgrading, but I'm afraid of rebooting my laptop :(. When I try to run gnome-screenshot I get this error
[17:06] <ignacio> Gtk:ERROR:/build/gtk+3.0-4jVu5z/gtk+3.0-3.22.21/./gtk/gtkiconhelper.c:493:ensure_surface_for_gicon: assertion failed: (destination) || this started to happen after I started the upgrade
[17:09] <Faux> ignacio: Thats quite likely to be fixed by restarting gdm after the upgrade is done.