[02:51] <Dragnslcr> Any ideas on why I haven't gotten any kind of notification to upgrade to 18.04? Settings are definitely set to do all new releases.
 are you on 16.04?
 if so they're not going to roll out the notification until 18.04.1 comes out in July-ish
[03:16] <Dragnslcr> Nope, on 17.10
[04:15] <valorie> Dragnslcr: check in say, Muon whether or not you have "lts only" ticked
[04:16] <valorie> oops, 17.10
[04:16] <valorie> hmmmm
[04:16] <valorie> you'll go EOL in a couple of months, so it is time to make the hop
[06:06] <lordievader> Good morning
 Morning
[06:12] <batteronizer> Good morning
[06:12] <lordievader> 👋
 Morning
[07:20] <Quetzlcoatl> hi guys! short question: who uses virtualbox on 18.04? how is running on 18.04?
[07:21] <Quetzlcoatl> are there issues on running virtualbox vms on kubuntu 18.04
[11:00] <BluesKaj> Hey folks
[11:00] <lordievader> 👋
[11:09] <BluesKaj> 😎
[11:21] <user|79852> Any idea when the manual for 18.04 will be available?
[11:24] <BluesKaj> user|79852, https://wiki.kubuntu.org/BionicBeaver/ReleaseNotes
[11:50] <user|79852> BluesKaj, Thanks.
[11:50] <BluesKaj> user|79852, np
[12:17] <laggger164> Guys, I have a problem with my OS detecting the monitor resolution correctly.
[12:17] <laggger164> It sticks at 1024x768 and has no option to go 1920x1080
[12:18] <laggger164> This happened since I put it through a KVM switch, which is probably the reason why
[12:18] <laggger164> When I connect it back directly, it works again
[12:19] <laggger164> I tried xrandr to set up a new resolution and it does work, but it goes away when I restart.
[12:19] <laggger164> Any ideas?
[12:22] <BluesKaj> laggger164, perhaps a small bash script in system-settings startup/shutdown using your xrander setting
[12:24] <laggger164> BluesKaj: I don't particularly fancy that, since it has to make the mode, add the mode and then switch to it.
[12:24] <laggger164> Sounds like a lot of possible problems to me.
[12:29] <BluesKaj> used a small script for networking with one simple command...wprked well til the devs finally realized it was abug, but that's your ..dunno why you won't try it, just to see if it will work
[12:29] <BluesKaj> that's your call
[12:31] <BluesKaj> but you're asking in ##linux too, and the guys there are quite knowledgeable
[12:32] <laggger164> Yeah, it seems like I have no other option. Also, doesn't bash_profile execute every time I start a new shell? Won't that mess up the desktop every time I open a terminal?
[12:36] <BluesKaj> laggger164, I would use the system-settings startup/shutdown ...it's simple , just create a bash script in kate and have system settings>startup&shutdown>autostart>addscript point to the file
[12:36] <laggger164> BluesKaj:  Right. Should have thought of that.
[12:37] <laggger164> Welp, I'll do that.
[12:37] <BluesKaj> cool
[12:46] <mparillo> I am running 18.04 successfully in VirtualBox as a guest. Or are you asking about running VirtualBox on an 18.04 host. In that case, I do not know, but would be surprised if it did not work well.
[14:31] <simulant> hi can anyone help, i upgraded to bionic 18.04 today and now my intel integrated gpu/display is not working. but my nvidia one is ok
[14:32] <simulant> the intel one worked ok in 17.10, but now just has a small underscore line on a black screen in top corner
[14:34] <simulant> lspci shows Intel Corporation Device 3e91
[17:29] <canon> Hello all, looking to mount a remote NFS share on a server that I have access to. I have a local NFS share mounted at the moment
[17:39] <kopito> hey, guys! Could please give me advise what dpi I should choose for 17.3 inch monitor
[17:40] <kopito> because by default it is too small for full hd resolution
[17:44] <BluesKaj> kopito, 96 minimum
[17:46] <kopito> BluesKaj: I've ended at 116, but the shift between 115 is huge
[17:47] <BluesKaj> that's a bit much kopito
[17:48] <kopito> well if I set 96 the browser shows very very small letters that I can't recognize
[17:49] <kopito> I wonder if someone on the channel has 17.3 inch monitor
[17:49] <kopito> to compare settings
[17:49] <kopito> because 116 is pretty the same what I had on Windows
[17:50] <BluesKaj> kopito, don't adjust font size with dpi , use system settings>appearance>fonts
[17:51] <kopito> hm, and any browser will use this settings?
[17:52] <BluesKaj> most browser fonts can be set independently in their own settings options as well
[17:53] <kopito> well, it will be long journey...
[17:53] <kopito> BluesKaj: ok, thank you!
[17:56] <BluesKaj> he left too soon
[18:01] <kopito> BluesKaj: yeah, it works.
[18:01] <kopito> I did pretty mush the same
[18:54] <pan> Does anybody know a qt gui for syncthing?
[18:55] <Guest75695> Does anybody know a qt gui for syncthing?
[21:07] <Fire-Dragon-DoL> kwin is crashing so often that I added an hotkey to restart it :\
[21:07] <Fire-Dragon-DoL> there, crashed again :\
[21:13] <iffraff> NICKSERV identify
[21:13] <genii> Fire-Dragon-DoL: You should install kwin-dbg then to make useful bug reports with, for when it does
[21:14] <genii> iffraff: /msg nickserv identify your-name-here your-password-here
[21:14] <Fire-Dragon-DoL> genii: thanks I'll try that
[21:15] <Fire-Dragon-DoL> genii: doesn't exist for bionic...
[21:15] <Fire-Dragon-DoL> not even for artful, sigh
[21:16] <Fire-Dragon-DoL> maybe it's kwin src
[21:16] <genii> !info kwin-dbg artful
[21:16] <genii> Hm
[21:17] <genii> ( it exists here on my Xenial )
[21:17] <genii> !info plasma-desktop-dbg
[21:18] <genii> Interesting
[21:18] <Fire-Dragon-DoL> yeah it exists on xenial, is the last one
[21:18] <Fire-Dragon-DoL> lol
[21:19] <Fire-Dragon-DoL> I'll try to check in #kde or #kwin
[21:19] <genii> Asking in the dev channel, maybe we'll hear back
[22:13] <BionicMac> !info kdbg
[22:14] <BionicMac> Fire-Dragon-DoL: Perhaps it is ^ this pakage you are looking for?
[22:20] <Fire-Dragon-DoL> mhhh maybe BionicMac, I was looking for debug symbols of kwin
[22:49] <valorie> genii: the dbg packages are now named dbgsm or something stupid by Debian
[22:50] <valorie> !dbg
[22:50] <valorie> huh
[22:51] <valorie> https://wiki.debian.org/DebugPackage
[22:53] <valorie> so dbgsym
[22:53] <valorie> :(
[23:03] <genii> valorie: Thanks!
[23:03] <genii> !info kwin-dbgsym
[23:04] <genii> Hm
[23:04] <valorie> ugh, that means it wasn't generated
[23:04] <genii> !info kwin-dbgsym cosmic
[23:04] <valorie> genii: please file a bug
[23:04] <valorie> like: ubuntu-bug kwin-dbgsym
[23:05] <genii> valorie: I'm on Xenial currently
[23:05] <valorie> unsure why those are not being generated
[23:05] <valorie> oooo
[23:05] <genii> It was for an earlier user
[23:05] <valorie> I think we have a xenial test coming up
[23:05] <valorie> for VLC or so
[23:05] <genii> Fire-Dragon-DoL: ^
[23:06] <valorie> huh, tsimonq2 ain't in here
[23:06] <Fire-Dragon-DoL> oh, I'm here
[23:06] <Fire-Dragon-DoL> thanks genii !
[23:06] <valorie> Fire-Dragon-DoL: please file a bug
[23:06] <valorie> sorry, doing something else and not paying good attention
[23:07] <Fire-Dragon-DoL> sure no problem, I'll file it immediately
[23:07] <Fire-Dragon-DoL> !bug
[23:08] <valorie> `ubuntu-bug kwin-dbgsym` is the easy way
[23:08] <valorie> and say: it should exist but it doesn't
[23:08] <valorie> or "needs packaging"
[23:10] <krytarik> https://wiki.ubuntu.com/DebuggingProgramCrash#Non-built-in_debug_symbol_packages_.28.2A-dbgsym.29
[23:11] <Fire-Dragon-DoL> so wait, should I file a bug or follow what krytarik says?
[23:15] <genii> Fire-Dragon-DoL: The current problem is that to file an usable bug report for the crashing of your kwin, kwin-dbgsym should be available to install to give a more comprehensive dump in the rport for the developers. But it's the catch-22 of the situation where that package does not seem to be built
[23:15] <genii> Fire-Dragon-DoL: So a bug for kwin-dgbsym needs to be filed, saying, "Hey! Please build this package!" .... basically
[23:16] <Fire-Dragon-DoL> oh, good, so ubuntu-bug can't be used
[23:16] <Fire-Dragon-DoL> lol
[23:16] <Fire-Dragon-DoL> can I add it to `kwin` package and say `kwin-dbgsym` should be available to install?
[23:16] <krytarik> https://launchpad.net/ubuntu/%2Bsource/kwin
[23:18] <Fire-Dragon-DoL> https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1773271
[23:18] <valorie> krytarik: ugh, this is known and we have to do a crazy work-around?
[23:18] <valorie> grrrr
[23:19] <krytarik> Ugh, have fun..
[23:19] <valorie> this is one of the worst thing that Debian has done
[23:19]  * genii screams into a couch pillow
[23:19] <valorie> it makes KDE "dr konqui" not work
[23:19] <valorie> for starter
[23:19] <valorie> s
[23:19] <Fire-Dragon-DoL> it's fantastic that the entire thing starts as "kwin crashes 30 times a day, I want to debug it"
[23:20]  * valorie goes out to take vengeance on dandelions and other weeds
[23:20] <Fire-Dragon-DoL> and I end up filing a bug to debug another bug... xd
[23:20] <krytarik> !info kwin
[23:20] <Fire-Dragon-DoL> oh and by the way, there is a bug to file a bug to debug the other bug, since I can't file a bug for kwin-dbgsym XD
[23:21] <Fire-Dragon-DoL> WAIT
[23:21] <Fire-Dragon-DoL> kwin-x11-dbgsym
[23:21] <Fire-Dragon-DoL> if kwin is a dummy package for kwin-x11
[23:21] <Fire-Dragon-DoL> the dbgsymbols maybe are those?
[23:21] <krytarik> Yeep!
[23:21] <Fire-Dragon-DoL> DOH let me close the bug...
[23:22] <Fire-Dragon-DoL> and I cannot find a "Close" button :S
[23:24] <Fire-Dragon-DoL> ok I have no idea how to remove a bug, if someone has some kind of access, please mark as useless https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1773271
[23:24] <krytarik> You just set it to 'invalid'
[23:25] <Fire-Dragon-DoL> mh ok. krytarik looks like kwin-x11-dbgsym is not available for bionic anyway
[23:25] <Fire-Dragon-DoL> I have to add some repository probably
[23:26] <krytarik> Yes, as I linked above.
[23:26] <Fire-Dragon-DoL> ok good
[23:42] <Fire-Dragon-DoL> mhhh do I have any way to distinguish between a binary and a string? (I have a UUID in one of the two formats)