| drasch | somehow light-locker got installed along with mate-screensaver ... this seemed to cause double-locking, suspend troubles, and other oddness. | 01:33 |
|---|---|---|
| drasch | is this something that should be bugged? or documented somewhere? | 01:34 |
| drasch | I'm happy to do either/both, looking for direction... | 01:34 |
| cim209 | so i upgraded from 16 to 18, no issues :D | 01:49 |
| qwefytuoityty | Athlon X4 840 Quad Core, two modules 4 cores, fm2+. Need 4 or 2 control cores? https://screenshots.firefox.com/8PixeHdOSoIM3xct/null | 02:17 |
| qwefytuoityty | If the Intel processor with Hyper-Threading technology, it's clear to me. Control of logical cores is not necessary. | 02:28 |
| qwefytuoityty | Control of logical cores don't need | 02:32 |
| m4t | drasch: uhm, installing any of these packages would've pulled it in light-locker-dbgsym light-locker-settings lubuntu-gtk-desktop lubuntu-desktop light-locker:i386 xubuntu-desktop xubuntu-core xfce4-session ubuntustudio-desktop-core ubuntustudio-desktop lxqt-session lxlock lubuntu-gtk-desktop lubuntu-desktop | 02:36 |
| m4t | could check for their presence with: dpkg -l|egrep 'light-locker-dbgsym|light-locker-settings|lubuntu-gtk-desktop|lubuntu-desktop|light-locker:i386|xubuntu-desktop|xubuntu-core|xfce4-session|ubuntustudio-desktop-core|ubuntustudio-desktop|lxqt-session|lxlock|lubuntu-gtk-desktop|lubuntu-desktop' | 02:38 |
| pavlushka | sixwheeledbeast: https://imgur.com/rbOds3U, RPI#B ubuntu-mate bionic | 08:40 |
| pavlushka | RPI3B | 08:41 |
| pavlushka | and this https://imgur.com/a/DudWbiW of RPI3B ubuntu-mate bionic \o/ | 09:39 |
| cim209 | pavlushka, that gtk warning | 10:00 |
| pavlushka | cim209: topmenu-gtk package is not available, I tried compiling that but no change | 10:27 |
| cim209 | i just joined the 18.04 club | 10:28 |
| pavlushka | cim209: aha, and about that topmenu-gtk from github is here https://github.com/dnk/topmenu-gtk | 10:30 |
| cim209 | i get that error too | 10:30 |
| pavlushka | cim209: but I think that's not much of a problem | 10:30 |
| cim209 | yeah i don't mind | 10:31 |
| pavlushka | cim209: the issue is because that package is only available for Ubuntu 16.04 xenial, https://launchpad.net/ubuntu/+source/topmenu-gtk | 10:34 |
| cim209 | i see | 10:37 |
| pavlushka | cim209: oh, the reason to drop topmenu-gtk is that it is based on gtk2 and ahs issue with gtk3, so Ubuntu-mate which is based on gtk3 had to drop topmenu-gtk | 11:13 |
| pavlushka | so now the question is, how to fix those topmenu-gtk false messages just not to appear | 11:15 |
| pavlushka | for those who upgraded from xenial to bionic. | 11:15 |
| drasch | m4t: you're definitely right. I installed xubuntu-desktop pulled this in. My issue was that there was undesirable interaction between this and the MATE desktop. | 11:56 |
| m4t | ¯\_(ツ)_/¯ | 11:56 |
| JustJohnny | I have a weird problem, maybe someone here can help. I use firefox on my Ubuntu Mate, but some textboxes appear dark-grey instead of white, and on others the font color is nearly white so its difficult to see anything you type. I think it might have something to do with the Mate skin i'm using but, is there any way to configure just firefox to solve this? | 12:52 |
| pavlushka | JustJohnny: yes, go to Firefox's preference and select not to use system theme | 13:07 |
| pavlushka | JustJohnny: instead choose the theme that suits you | 13:08 |
| JustJohnny | I already did, but still the text shows lightgrey sometimes | 13:18 |
| JustJohnny | still, solved in most pages except one (that I use a lot) could it be a problem with the page itself? Thanks pavlushka! :) | 13:24 |
| pavlushka | JustJohnny: could be, I cant tell for sure without viewing the page :) | 13:25 |
| JustJohnny | its an internal dolibarr server for my company :( | 13:26 |
| JustJohnny | thin is, it works fine in other browsers | 13:26 |
| pavlushka | JustJohnny: try to change fonts colors in the preference to see if that helps | 13:27 |
| JustJohnny | I did, no effect just on this page | 13:29 |
| pavlushka | JustJohnny: if you can share a screenshot of that | 13:32 |
| JustJohnny | can I? would be my first on IRC :$ | 13:33 |
| pavlushka | JustJohnny: use this to do that, imgur.com | 13:34 |
| JustJohnny | I will if I can connect later, I have to go. But thanks for the help :D | 13:36 |
| sixwheeledbeast | pavlushka: just because it is possible, that doesn't make it supported or stable | 15:53 |
| pavlushka | sixwheeledbeast: my question was is it safe? and it looks like possible and safe enough | 15:55 |
| sixwheeledbeast | Oh it's possible. you can always do-release upgrade or dist-upgrade if upstream has a new version but that doesn't mean you should | 15:57 |
| pavlushka | sixwheeledbeast: and packages are already ported, they just didn't finished that and didn't bundled those | 15:57 |
| sixwheeledbeast | There have been plenty of people upgrade to 17.10 on Rpi and come here saying this and that doesnt work for example. | 15:57 |
| sixwheeledbeast | You results may vary is the answer I suppose. | 15:58 |
| pavlushka | sixwheeledbeast: "do-release-upgrade" and "do-release-upgrade -d" has a fundamental difference | 16:00 |
| pavlushka | if "do-release-upgrade" is applicable and works without issue, then care has been taken enough for the upgrade | 16:02 |
| sixwheeledbeast | I mentioned nothing about development releases. | 16:02 |
| pavlushka | sixwheeledbeast: other than LTS to LTS upgrade, the upgrade is a development upgrade | 16:22 |
| pavlushka | if they already in 17.10 on RPI, then they have done it before, the dev upgrade | 16:22 |
| pavlushka | but only the 17.10 to 18.04 lts got messy in their case | 16:23 |
| sixwheeledbeast | no I assume they did a dist-upgrade before 18.04 was released. Development (alpha), Normal (Official) and LTS releases are different | 16:32 |
| sixwheeledbeast | I am talking about waves of questions asked here before 18.04 was even released for ubuntu upstream | 16:32 |
| pavlushka | sixwheeledbeast: dist-upgrade is just for making the system packages up-to-date | 16:33 |
| pavlushka | and yes may there was many issue | 16:34 |
| pavlushka | which looks like has been almost fixed by now | 16:34 |
| pavlushka | *may be, were | 16:35 |
| sixwheeledbeast | dist-upgrade forces all dependencies of all packages to upgrade. do-release-upgrade is preferred for ubuntu but it basically does dist-upgrade with added checks and cleanup | 16:41 |
| pavlushka | sixwheeledbeast: what you are talking about is "sudo apt-get dist-upgrade" but it will remain in the same distribution. | 16:45 |
| pavlushka | it sounds like a distribution upgrade but its not :) | 16:46 |
| sixwheeledbeast | Anyway put basically 18.04 may work in the most part but you may run into issues that nobody knows of yet. Hence my point about just there is an option to upgrade that doesn't mean you can. the upgrader just knows there is a new distribution version available not your architecture. I have seen it with other Debian based distros. | 16:50 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!