[00:40] <dr`venom> I'm upgrading to Kubuntu 19.10. I got this  configuring grub-pc and I don't know what to pick. It says: A new version (/tmp/grub.zl5etoJx5W) of configuration file /etc/default/grub is available, but the version installed has been locally modified. What do you want to do about modified configuration file grub: Install the package maintainer's version, Keep the local version currently installed.
[00:40] <dr`venom> I don't k now what to pick.
[00:42] <tomreyn> dr`venom: does it not offer to show the differences?
[00:44] <tomreyn> if it doesn't, you can compare yourself using    diff /etc/default/grub /tmp/grub.zl5etoJx5W     in a separate terminal window / tty / screen window
[00:44] <dr`venom> yes
[00:44] <dr`venom> I just wouldn't know what to look for in the differences
[00:45] <dr`venom> If I keep the one I had, would my system still work?
[00:49] <tomreyn> dr`venom: probably so, but i have not done an upgrade from 19.04 to 19.10, yet, so can't promise
[00:50] <tomreyn> dr`venom: feel free to share the differences:    diff -u /etc/default/grub /tmp/grub.zl5etoJx5W | nc termbin.com 9999
[00:50] <dr`venom> No problem, if it breaks i'll try that grub repair program or do a clean install. Thank you. I looked at the differences but it was over my head. I'm new at all this stuff.
[01:31] <mariano> Update went fine, but one issue. Whenever I open writer or libreoffice, the document recovery dialog box opens up. It shows an untitled document 1, whether I chose to start the recover or discard it, libreoffice crashes.
 Hey, … Can anyone help regarding partition while installing Kubuntu without losing existing data
[06:44] <diogenes_> !ask
[08:36] <enkeyz> Just want to thank Kubuntu team making this Linux distro, and just want to say, I'm moving to Manjaro, because making snap as package manager is a big no no for me
[08:36] <enkeyz> o7
[08:37] <enkeyz> just an example: today installing VSCode from snap taken 8minutes, but installing it on Manjaro with pacman taken about 20 seconds
[09:12] <nigthelf7> hello everyone
[09:12] <nigthelf7> I do not know if you suffered the same issue but the battery remaining time in Kubuntu 19.10 does not refresh itself
[09:13] <nigthelf7> it always show the same remaining time
[09:15] <diogenes_> nigthelf7, do you have upower installed?
[09:16] <nigthelf7> yes
[09:16] <nigthelf7> upower -d show the right time
[09:16] <diogenes_> is upower.service runming?
[09:19] <nigthelf7> https://pastebin.com/KJpDjtEA
[09:19] <nigthelf7> yes
[09:20] <nigthelf7> and I see the messages of the battery with dbus-monitor --system sender=org.freedesktop.UPower
[09:20] <nigthelf7> it is weird
[09:20] <nigthelf7> I think it just get it from the bootup process
[09:20] <nigthelf7> right now it has 15 minutes left and the percentage is 94%...
[09:20] <diogenes_> nigthelf7, what is you systemctl restart upower
[09:21] <nigthelf7> but the weirdest part is that the percentage of the battery is getting it right
[09:21] <nigthelf7> I already did it the restart part
[09:21] <nigthelf7> it is not working either
[09:21] <nigthelf7> :-(
[09:23] <nigthelf7> this what I get from dbus:dict entry(
[09:23] <nigthelf7>          string "TimeToEmpty"
[09:23] <nigthelf7>          variant             int64 39225
[09:23] <nigthelf7>       )
[09:23] <nigthelf7> this what I get from dbus: https://pastebin.com/3fZetm0b
[09:23] <nigthelf7> maybe you have different messages and that is why is working for you
[09:23] <nigthelf7> I do not know
[09:25] <nigthelf7> I have opened a bug in ubuntu site
[09:25] <nigthelf7> I do not see a place to do it for kubuntu
[09:30] <Linneris> Greetings!
[09:31] <Linneris> I just updated from Kubuntu 19.04 to 19.10, and font rendering in Qt applications (including KDE) has become noticeably worse. The fonts look thinner and gaps between glyphs are inconsistent.
[09:31] <Linneris> GTK applications look fine. Any ideas?
[10:46] <Ilgaz> Hello all, back to Kubuntu finally. One issue here. GDK_BACKEND=wayland thing to enable Firefox wayland fails, strange thing is it works under ubuntu 19.10
[11:07] <BluesKaj> Howdy all
 @BluesKaj, Howdy BluesKaj!
 I have a question: how unstable Kubuntu becomes after updating Plasma through the backports PPA? Does anyone have experience on this?
[11:29] <BluesKaj> hey Linuxophil
[11:30] <BluesKaj> emanuel_lima , which kubuntu release?
[11:33] <BluesKaj> backports are normally not a ppa nowadays, they're a part of the default sources, which may or may not be commented
 @emanuel_lima, I use Kubuntu 18.04 with backports since its release. It is super stable.
[11:34] <BluesKaj> I don't think you'll have any stability problems with 18.04
 @emanuel_lima, However, backports with 18.04 stay with the LTS Plasma 5.12 and its point releases.
 @BluesKaj, I have Kubuntu Eoan and was thinking about upgrading to plasma 5.17.1
 @emanuel_lima, For 19.04 and 19.10 you will get new Plasma releases and thus the bugs that come with it.
 @emanuel_lima, Maybe wait for 5.17.2 before upgrading. Then you should be fine.
 @BluesKaj, It says it is a PPA here  … https://kubuntu.org/news/plasma-5-17-for-kubuntu-19-10-available-in-backports-ppa/
 @Linuxophil, Good advice
 @emanuel_lima, I have long wanted a "stability ppa" that only includes the later point releases of a new Plasma version. Like skipping 5.17.1, 5.17.2 and 5.17.3. Just make the user upgrade from the last version of Plasma 5.16 to a mature 5.17.4 or similar.
[11:40] <BluesKaj> emanuel_lima, then if you want stability don
[11:40] <BluesKaj> don't use ppas
 Will the backports PPA continue to receive new plasma versions indefinitely or just 5.17 point releases?
[11:41] <BluesKaj> maybe ask the devs
 Thanks :)
 @emanuel_lima, It should get Plasma 5.18 when that goes into the 20.04 development release.
 @RikMills, Right 👍
 For what it's worth I have used backports on 18.04, 18.10, and 19.04 and never had any stability issues. The random app might crash but the shell never has nor has it frozen. I think that has as much to do with Plasma releases being generally high quality as it does with Ubuntu's base. Also not saying that is everyone's experience or that you'd want to do the same. Keep in mind you can roll back from backports to stock if something
 How would I rollback?
 ppa-purge
 https://manpages.ubuntu.com/manpages/eoan/man1/ppa-purge.1.html
 Right, so I only have to remove the ppa, and the packages rollback automatically?
 the ppa-purge command downgrades all the packages from the ppa to the version from the main archive, then disables ppa
 Nice. Thanks
 So for example here, this would do the job … ```sudo ppa-purge kubuntu-ppa/backports```
 oh, and 'ppa-purge' is a package you need to install 1st
 👍🏻
[19:07] <denza242> how easy is it to move a partition over to another drive? What i'd like to do in my new laptop, is get a new ssd, and transfer my linux partition onto it, as currently, i have both my windows partition and linux partition on the same ssd
[19:07] <denza242> the end goal is that windows is on one drive, while kubuntu is on the other
[19:08] <oerheks> dd the partition, reinstall grub with the right new UUID..
[19:09] <oerheks> not worth the trouble with allignment and such , i would go for fresh install
[19:28] <Ilgaz> does anyone use Firefox in wayland mode on 19.10? Here it fails to launch
[19:28] <Ilgaz> on normal Ubuntu 19.10 it works. Strange
[19:29] <denza242> under kwin?
[19:31] <Ilgaz> Yes I am using kde, in wayland mode. Intel gfx.
[19:32] <Ilgaz> https://paste.ubuntu.com/p/y8C3s2F4JB/
[19:33] <Ilgaz> I know I can't expect too much from Firefox on wayland but working on ubuntu and not working on kubuntu, I thought I should report it
[19:33] <denza242> might be a kwin thing
[19:33] <denza242> hmm
[19:34] <Ilgaz> Oh yes on Ubuntu, gnome-wayland was running
[19:35] <Ilgaz> Hey perhaps I am missing stuff to make gtk apps work on wayland
[19:35] <denza242> i'm no expert on the matter btw, so take what i say with a grain of salt. I'm looking stuff up
[19:37] <Ilgaz> I better find a similar bug report or create my own. Wayland users would want Firefox in wayland mode. Especially people with 4K displays etc
[19:37] <denza242> yeah
[19:45] <oerheks> try GDK_BACKEND=wayland ./firefox
[19:45] <oerheks> known issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1551664
[19:47] <Ilgaz> Weirdest thing ever, solution is on youtube? https://www.youtube.com/watch?v=1xIvppquqco
[19:48] <Ilgaz> oerheks: will try now
[19:51] <Ilgaz> no difference. If it wasn't kubuntu, I wouldn't say a word since I am tired of being lectured about how wayland isn't needed, hardware acceleration is needless etc
[19:51] <Ilgaz> It seems KDE guys really take such stuff serious
[19:51] <oerheks> some older bugreports talk abou --no-remote when you get the error ff is already ruinning, ff 67 or so
[19:51] <oerheks> kubuntu and wayland.. hmm
[19:53] <Ilgaz> oerheks: KDE devs are very eager to support, even at one point people misunderstood the enthuiasm and thought KDE is dropping X11 lol
[19:53] <Ilgaz> Oh it works great under X11, I am just on Intel gfx 5500 here, I need every possible acceleration for battery life
[20:00] <Ilgaz> aha oerheks firefox nightly produced the same message
[20:00] <Ilgaz> dbus thing
[20:02] <Ilgaz> OK when you add that argument, it doesn't core dump stating dbus. It just says can't open display
[20:02] <Ilgaz> The browser I truly like is Konqueror btw, it is just sites not caring about it
[20:34] <bprompt> Ilgaz:  is not that site do not care about Konqueror, is that Konqueror is deprecated and standards are changing quite a bit, btw I do use Konqueror, as a File Manager, as a file manager is terrific
[20:56] <Ilgaz> well at least I learned firefox enables gpu process and webrender even on Intel/Linux in firefox 71
[23:41] <leonardo_> Sistema operacional: Kubuntu 19.10  ----    Versão do KDE Plasma: 5.17.1
[23:41] <leonardo_> I cant save "auto login" in user configuration tab.
[23:41] <leonardo_> I had to edit the login file with kate notepad to change auto login.
[23:41] <leonardo_> Anyone has this issue? Is a known bug?
[23:52] <RikMills> leonardo_: Yeah, I see the same thing in KDE Neon, so not a Kubuntu specific bug